Wi-Fi Combo Forum Discussions
I'm having an issue with wiced_network_up returning WICED error after about 30 minutes. I'm connecting to the wifi network, sending a ping, and then disconnecting. I've attached an example program to demonstrate the issue. I'm running SDK 3.5.1 on the BCM4343W Avenet module. Does anyone know of any solutions? Can you reset the broadcom module without resetting the MCU?
Thanks,
-Rob
Show LessThe new SDK 3.7.0-3 that was just released states that "Support for Bluetooth Low Power Mode on 4343x platforms" was added. Does anyone know how to activate low power mode?
Thanks,
-Rob
Show LessHi,
I tested ota_fr with this config (BCM943438 custom platform with sam4s cpu and 4343 wifi-ble chip )
snip.ota_fr-FreeRTOS-LwIP-BCM943438-SDIO-debug download run VERBOSE=1 JTAG=atmel
I found that incorectly using return params of function:
wiced_packet_get_data(temp_packet, 0, (uint8_t**)&request_string, &request_length, &available_data_length);
Using request_length but need use available_data_length. Because request_length is size in first receiver buffer, available_data_length total data size.
If received 1 buffer its ok, but if received 2 buffer request_length show 1 buffer full size etc.: 1152, available_data_length show total size in all buffers.
In this state ota_server hung...
I found that in others applications (ota2, maybe in all?) have are same bug . Same in 3.7.0 SDK.
Possible this bug actual in FreeRTOS-lwip config.
Show LessI am using WICED SDK 3.7.0 and I want to creat some random number.I try
srand(time(NULL));
uint8_t value = rand()%255;
but I get error lib/thumb/v7em\libc.a(lib_a-gettimeofdayr.o): In function `_gettimeofday_r':
c:\pf8_3\Wiced-Tool-Source\ARM_GNU\newlib-build\arm-none-eabi\thumb\v7em\newlib\libc\reent/../../../../../../../newlib-2.0.0/newlib/libc/reent/gettimeofdayr.c:71: undefined reference to `_gettimeofday'
tools/makefiles/wiced_elf.mk:240: recipe for target 'build/' failed
If I block the srand(time(NULL)); the target can be made without error but the value is the same .Can somebody tell me how to creat random value?THS!
Show LessHello,
We are developing an Ethernet driver for the BCM43907 targeting our Nucleus RTOS. We have extracted some information from the WICED SDK but some hardware details are difficult to get without having details on the Ethernet/DMA registers of the BCM43907. Can you point us to the latest Technical Reference Manual for the BCM43907 that includes details on registers and mode of operation for the Ethernet module?
Show LessHi,
I installed the \WICED-SDK-3.3.1, I tried to test "snip/scan" example with my BCM943364WCD1 dev board. To do so, I created a new "Make Target" : snip.scan-BCM943364WCD1. When I compile the project, I get the errors below :
"Making DCT image
tools/makefiles/wiced_elf.mk:220: recipe for target 'display_map_summary' failed
make.exe[3]: *** [display_map_summary] Error -1073741502
make.exe[3]: *** Waiting for unfinished jobs....
[...]
./WICED/internal/dct.c:165:41: error: 'CERTIFICATE_STRING' undeclared here (not in a function)
.security_credentials.certificate = CERTIFICATE_STRING,"
Any idea of the problem ?
thanks
Show LessI just went through the re-installation of SDK 3.7.0-3 on Mac OS X and came across few things that I would like to highlight in this post. It may be helpful for someone else.
The installation is performed on El Capitan: 10.11.6, the WICED SDK is downloaded from here: WICED Wi-Fi Documents & Downloadsselect a *.7z file, those are for Mac OS X.
The steps are:
- Run the instance of WICED Wi-Fi Eclipse CDT. If Eclipse is not installed yet: please use this one here: WICED-SDK-2.4.1 IDE & SDK [Mac OS X Package Installer]There is only one release of the Mac OS X Package installer so you have to start with this version even though the SDK is not the latest one!
- When Eclipse is up and running, do File->Import->Existing Project Into Workspace
- Under "Select root directory" select the decompressed *.7z SDK that you just downloaded above.
- Select "WICED-SDK-xxx" (for example: WICED-SDK-3.7.0-3) under Projects.
- Usually I would not select "Copy projects into workspace" (that's just my current configuration).
- Working sets not selected for this example.
- Press "Finish".
- You should see now under the imported project called WICED-SDK-xxxx (for example: WICED-SDK-3.7.0-3) under "Project Explorer".
- Also the "Make Target" window should be populated with the project.
- If you see folders and source code under the Make Target, just press the button called "Hide Empty Folder", this will keep the rules only (cleaner!).
- At this point you should see the build window with an error similar to the one below (see Logs of error during SDK install, Step 11 below)
- The make used to build is not the right one, you need to use the make provided with the SDK.
- Configure the proper make file via: Project->Properties->Builder, remove the check for "Use default build command", replace the make with: ${workspace_loc:/WICED-SDK-3.7.0-3}/make
- Press Apply and close the window.
- Create a rule in the Make Target window as follow: snip.scan-BCM943362WCD4
- Execute the the build by clicking on the Target rule created above, see successful logs under STEP16 below
Logs of error during SDK install:
Step 11:
make all
tools/makefiles/wiced_toolchain_common.mk:202: *** incorrect 'make' used (/Applications/Xcode.app/Contents/Developer/usr/bin/make) - please use: (Windows) .\make.exe <target_string> (OS X, Linux) ./make <target_string>. Stop.
STEP 16:
**** Build of configuration Default for project WICED-SDK-3.7.0-3 ****
/Users/mickael/Documents/WICED_WiFi/WICED-SDK-3.7.0-3/make snip.scan-BCM943362WCD4
MAKEFILE MAKECMDGOALS=snip.scan-BCM943362WCD4 OTA2_SUPPORT is disabled
Making config file for first time
+-----------------------------------------------------------------------------------------------------+
| IMPORTANT NOTES |
+-----------------------------------------------------------------------------------------------------+
| Wi-Fi MAC Address |
| The target Wi-Fi MAC address is defined in <WICED-SDK>/generated_mac_address.txt |
| Ensure each target device has a unique address. |
+-----------------------------------------------------------------------------------------------------+
| MCU & Wi-Fi Power Save |
| It is *critical* that applications using WICED Powersave API functions connect an accurate 32kHz |
| reference clock to the sleep clock input pin of the WLAN chip. Please read the WICED Powersave |
| Application Note located in the documentation directory if you plan to use powersave features. |
+-----------------------------------------------------------------------------------------------------+
MAKEFILE MAKECMDGOALS=snip.scan-BCM943362WCD4 OTA2_SUPPORT is disabled
Building Bootloader
Finished Building Bootloader
Processing resources
Creating security credentials
Making DCT image
Compiling App_Scan
Compiling Platform_BCM943362WCD4
Compiling WICED
Compiling Lib_SPI_Flash_Library_BCM943362WCD4
Compiling Lib_GPIO_button
Compiling WWD_ThreadX_Interface
Compiling WICED_ThreadX_Interface
Compiling WWD_for_SDIO_ThreadX
Compiling Supplicant_BESL
Compiling Lib_DNS
Compiling NetX_Duo
Compiling Lib_Wiced_RO_FS
Compiling STM32F2xx
Compiling Lib_TLV
Compiling Lib_base64
Compiling Lib_Linked_List
Compiling Lib_crypto_open
Compiling Lib_micro_ecc
Compiling WWD_NetX_Duo_Interface
Compiling WICED_NetX_Duo_Interface
Compiling common_GCC
Compiling STM32F2xx_Peripheral_Drivers
Compiling Lib_Ring_Buffer
Compiling Lib_crc
Compiling Lib_DHCP_Server
Compiling STM32F2xx_Peripheral_Libraries
Making build/snip.scan-BCM943362WCD4/libraries/App_Scan.a
Making build/snip.scan-BCM943362WCD4/libraries/Platform_BCM943362WCD4.a
Making build/snip.scan-BCM943362WCD4/libraries/WICED.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_SPI_Flash_Library_BCM943362WCD4.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_GPIO_button.a
Making build/snip.scan-BCM943362WCD4/libraries/WWD_ThreadX_Interface.a
Making build/snip.scan-BCM943362WCD4/libraries/WICED_ThreadX_Interface.a
Making build/snip.scan-BCM943362WCD4/libraries/WWD_for_SDIO_ThreadX.a
Making build/snip.scan-BCM943362WCD4/libraries/Supplicant_BESL.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_DNS.a
Making build/snip.scan-BCM943362WCD4/libraries/NetX_Duo.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_Wiced_RO_FS.a
Making build/snip.scan-BCM943362WCD4/libraries/STM32F2xx.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_TLV.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_base64.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_Linked_List.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_crypto_open.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_micro_ecc.a
Making build/snip.scan-BCM943362WCD4/libraries/WWD_NetX_Duo_Interface.a
Making build/snip.scan-BCM943362WCD4/libraries/WICED_NetX_Duo_Interface.a
Making build/snip.scan-BCM943362WCD4/libraries/common_GCC.a
Making build/snip.scan-BCM943362WCD4/libraries/STM32F2xx_Peripheral_Drivers.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_Ring_Buffer.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_crc.a
Making build/snip.scan-BCM943362WCD4/libraries/Lib_DHCP_Server.a
Making build/snip.scan-BCM943362WCD4/libraries/STM32F2xx_Peripheral_Libraries.a
Making snip.scan-BCM943362WCD4.elf
Making snip.scan-BCM943362WCD4.bin
snip.scan-BCM943362WCD4
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
App | 404 | 0 |
crc | 1060 | 0 |
Host MCU-family library | 13821 | 2737 |
Interrupt Vectors | 388 | 0 |
libc | 23551 | 3064 |
Networking | 989 | 8523 |
NetX-Duo - Interfaces & Stacks | 0 | 16 |
Other | 3678 | 92 |
Packet Buffers | 0 | 23086 |
platform | 1024 | 168 |
RAM Initialisation | 2316 | 0 |
resources | 16 | 0 |
Ring_Buffer | 116 | 0 |
Startup Stack & Link Script fill | 9 | 3 |
ThreadX | 7868 | 396 |
TLV | 28 | 0 |
Wi-Fi Firmware | 210624 | 0 |
WICED | 3909 | 980 |
WWD | 14391 | 3007 |
----------------------------------+---------+---------|
TOTAL (bytes) | 281876 | 42072 |
----------------------------------|---------|---------|
Build complete
Making .gdbinit
Show LessHi Sir,
Can you please inform the suggested ASD test plan for BCM43907 certification?
I ask test lab to refer ASD1104 and ASD763 but they can't find those documents.
Please advise, thanks.
WFA logo certification reference.
How to get Wi-Fi Logo on WICED device module
Wi-Fi SIG search for ASD plan.
https://www.wi-fi.org/members/certification-testing/asd-test-plans
Platform: BCM943907WAE_1.B0
Show LessCypress team,
Below summary the regressions reported recently, please make sure all these issues will be fixed in next SDK release.
Most of these issues are related to the closed-source part, so people cannot workaround it.
demo.bt_smartbridge easily get GKI_exception 65524 getbuf: out of buffers exception on scan more then 3 connectable BLE peripherals around
https://community.cypress.com/thread/7651 (work in 3.5.2, fail in 3.7.0)
[BLE] [3.7.0-3] BTM_ENABLED_EVT error
https://community.cypress.com/thread/7644 (work in 3.7.0, fail in 3.7.0-3)
SDK-3.6.3 / SDK-3.7.0 wiced_framework_set_boot() doesn't work
https://community.cypress.com/thread/7328 (work in 3.5.2, fail in 3.7.0-3)
BT stack sometimes forgets to unlock mutex
https://community.cypress.com/thread/7659 (fail in 3.7)
Show LessThe problem I encountered in this thread, rfcomm cant reopen, seemed to have been fixed in 3.7. I'm not able to reproduce that exact problem, but a very similar one can be reproduced by lowering the clock speed to very low frequencies, like 12MHz.
When I do that, and open an rfcomm connection, I very often get problems locking mutexes from the BTU, READ_THREAD and HCISU threads. If I log all mutexes locked/unlocked from those threads, I can see that one of the threads pretty often forgets to unlock a mutex. It's not just a matter of several threads competing about the same mutex, one thread really forgets to unlock it, because I can see in the log that a thread locks it, then doesn't execute for a while, and during that time another thread fails to lock it, and after that the first thread locks it again (which it of course shouldn't need to do since it already had the mutex locked.)
Also, it's not just one thread forgetting to unlock it, it can be either one of those 3.
This is why I really try to avoid closed source software. It's impossible to fix problems you encounter, the only thing I can do is half-working workarounds, in this case, instead of using a xSemaphoreTake waiting FOREVER (in wiced_rtos.c wiced_rtos_lock_mutex), I use a 1 second timeout and simply pretend to have locked it if it times out. By doing that, the thread thinks it has locked it and can unlock it as usual when it's done. Of course it's a bit dangerous, but it's the best I can do without the source.
Please fix it on your end proper. If you *really* want to, I might be able to debug which function is locking the mutex and then forgets to unlock it.
Show Less