Wi-Fi Combo Forum Discussions
From the two modules that I have of CYW954907EVAL-1F, I want one of my boards configured as STA to connect to an AP. While referring to the API reference guide, I came across the function "wwd_wifi_join". The same is declared as follows:
wwd_result_t wwd_wifi_join ( const wiced_ssid_t ∗ ssid, wiced_security_t auth_type, const uint8_t ∗ security_key, uint8_t key_length, host_semaphore_type_t ∗ semaphore, wwd_interface_t interface )
I have defined following parameters in my AP:
- SSID = 802.11ac_try1
- Authentication type = WICED_SECURITY_WPA2_AES_PSK
- Security key = 80211AC
- Key Length = The length of the Security key in bytes
My questions are as follows:
- How would I calculate the security key length in bytes?
- What will be the interface in the function? Will it be WICED_AP_INTERFACE or WICED_STA_INTERFACE?
- In the module that has been configured as STA, how would I pass these parameters to the variables defined in the function so that it can join the SSID 802.11ac_try1.
- Not sure of how to use semaphore here? can anyone please throw some light?
WPRINT_APP_INFO is used for the timer handler function for debugging, but the program operation may be strange after the WPRINT_APP_INFO debug display for the timer timeout.
When WPRINT_APP_INFO of the timer handler function was removed, the operation of the program became normal.
◆QA
Isn't it a problem to debug display such as WPRINT_APP_INFO in the timer handler function?
Please let me know if you have any problems.
◆example
static wiced_timer_t s_wifi_timer = { 0x00 };
static void timer_handler(void* arg)
{
WPRINT_APP_INFO(("time out! ... %s(%d) \n", __func__, __LINE__));
・・・
}
void wifi_connect( void )
{
/* timer init(60sec timeout) */
wiced_rtos_init_timer(&s_wifi_timer, 60000, timer_handler, NULL);
/* timer start */
wiced_rtos_start_timer(&s_wifi_timer);
while(1) {
wiced_rtos_delay_milliseconds(1000);
・・・
break;
}
}
<japanese>
タイマーハンドラー関数のWPRINT_APP_INFOについて
タイマーハンドラー関数に、デバッグのため、WPRINT_APP_INFOを使用していますが
タイマーのタイムアウトに対して、WPRINT_APP_INFOのデバッグ表示後に
プログラムの動作がおかしくなることがあります。
タイマーハンドラー関数のWPRINT_APP_INFOを取り除くと、プログラムの動作に
異常がなくなりました。
◆QA
タイマーハンドラー関数に、WPRINT_APP_INFOなどのデバッグ表示を行っても問題ないでしょうか。
問題があるケースがありましたら、教えてください。
Show LessThere is confirmation about the operation of DHCP.
I received an Offer from the DHCP server, but there is a phenomenon that the Request is not responded.
You can resend Discover and complete the process, but this phenomenon occurs about 5 out of 10 times.
Is there any factor that makes address acquisition unstable?
* It seems that the DHCP IP address acquisition process is being performed by the NET X library "nx_dhcp_request_client_ip, nx_dhcp_start" function in the dhcp_client_init function of WICED API (wiced_network.c).
The .NET X library is a black box and no further confirmation is possible
Show LessHi Sir,
As the title asks,does CYW43455 support WEP40,WEP104 and WEP128 encryption?
If yes,do we need change something to fix it on firmware?
BR,
Leo
Show LessI am using the CY8CKIT-062-WiFi-BT kit and WICED studio 6.2.
I am trying to debug the Scan snip. My make target is "snip.scan-CY8CKIT_062-debug download_apps download".
The board is in CMSIS-DAP mode.
However when I run the windows debug I get the following message.
I am just starting to learn WICED so bear with me if this is a noob question.
Show LessHi all,
We have a product in production based on the NEB1DX_02 platform, and we're currently experiencing some difficulties with network reliability when using mesh routers such as this and this. In the firmware, we have currently set the roaming trigger to -60 dBm using the function wiced_wifi_set_roam_trigger(). We have also set the roam delta to 5dB using the function wwd_wifi_set_roam_delta().
Are there any known issues/workarounds with using wifi mesh routers? We can also conduct any tests that are suggested to better identify the issue and come up with a solution.
Thanks in advance, any insight would be appreciated.
Show LessHello,
I built my project on the WICED SDK available for macos. My project produces slightly different binary size on macos. I also tried to build some examples in the SDK and noticed that its mostly libc that produces the difference. Can any experts comment on why this might be happening? The version of armgcc on Windows is :
PS C:\WICED-Studio-6.4-SDK> .\43xxx_Wi-Fi\tools\ARM_GNU\Win32\bin\arm-none-eabi-gcc.exe --version
arm-none-eabi-gcc.exe (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 7.2.1 20170904 (release) [ARM/embedded-7-
branch revision 255204]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is the output on macos:
./43xxx_Wi-Fi/tools/ARM_GNU/OSX/bin/arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Show LessHi,
I have interface 4343w with NXP FRDM-K64F. I have ported the wiced sdk taking reference of IMRT1020 example project provided by NXP.
I am so far able to flash firmware and NVRAM image with out any issues. When it comes to downloading CLM blob file, I observe a very weird behaviour.
(Max packet size is set to 1000 from 1500 default)
1. The first chunk of the CLM blob data (size 900 bytes + ioctl packet overhead) is successfully transmitted.
2. Interrupt is received and the wwd_thread goes to receive data. The total data received is of size 956 bytes.
When printing the data I observed the following:
- data received contains the sent data i.e the first 900 bytes of CLM blob data is part of the packet.
- The data received is 12 bytes short of the data sent i.e I get 12 less bytes of CLM blob then what is sent.
Is this behaviour expected? Flags of the response does not show error.
3. Transmit of second 900 byte chunk of data fails with data CRC error while transmitting.
What can be causing such behaviour?
Please help me out.
Show LessIt is a confirmation whether the verification process of the SSL certificate of HTTPS communication is performed, but in the following header file,
Since it is "TLS_VERIFICATION_REQUIRED", I think that you are verifying the SSL certificate.
Is the recognition correct?
◆ File
wiced_defaults.h
/* WICED TLS Options * /
#define WICED_TLS_DEFAULT_VERIFICATION (TLS_VERIFICATION_REQUIRED)
◆ Environment
・ WICED SDK: 6.4.0
・ OS: ThreadX
<Japanese>
HTTPS通信のSSL証明書の検証について
HTTPS通信のSSL証明書の検証処理を行っているかの確認ですが、以下のヘッダファイルでは、
「TLS_VERIFICATION_REQUIRED」となっていますので、SSL証明書の検証を行っていると思いますが
認識はあっておりますか。
Show Less