Wi-Fi Combo Forum Discussions
On an STM32F4 based board...
When hitting ota2_bootloader.c::ota2_failsafe_app_load() the entry point is a flash address 0x800c3e5 but it hasn't been loaded into internal flash from SFlash. I see ota2_failsafe_app_load() erasing (internal?) flash:
/* Erase the application area */
result = ota2_failsafe_app_area_erase( flash_location, &header );
Then reading into RAM from flash:
result = ota2_failsafe_app_read( flash_location, (uint8_t*)prog_header.physical_address, prog_header.data_offset, prog_header.data_size_in_file );
But danged if it's obvious how internal flash get's written! It is quite clear in wiced_waf_common.c::wiced_waf_app_load():
result = platform_load_app_chunk( app_header_location, offset, (void*) prog_header.physical_address, prog_header.data_size_in_file );
Thanks!
Geoff
Show Less
Hello,
I have shared code that has some compiler specific blocks.
I am looking for pre-defined compiler macros in Wiced.
GCC typically uses: __GNUC__
ARM uses: __CC_ARM
What does Wiced use? My platform is the Cypress CYW4343W, STM32F4
Thanks.
Show Less
Hello,
The installation process (with all default options) seems to work, but when finialized I have two issues:
- The "43xxx_Wi-Fi folder only contains the "tools" subfolder and nothing else
- When starting WICED Studio, I've got nothing in "Project Explorer", nothing in "Make Target" and the combo box on the button ribbon displays "WICED Filters OFF".
I tried to switch the workspace manually -> Don't Work
I tried to install as Administrator -> Don't Work
WICED Studio 6.2.1 installed successfully
I tried to install 6.6.0.9 on a Linux VM -> OK withh all the file installed
Any idea?
Show LessHello,
I want to use the Cypress module CYW4343W with a STM32F7xx, I don't know which one yet.
I saw this subject (https://community.cypress.com/t5/Resource-Library/STM32F469-porting-in-WICED/ta-p/246317) but it's only for creating a new platform based on a existing MCU in Wiced. Do you know if there is the same guide to create a MCU?
Do you know if someone already created a STM32F7xx MCU?
Thank you
Jean
Show LessHello,
please suggest where we can obtain following documents:
43455_43457-HR101-R Hardware Reference Guide | Printed Circuit Board Layout Guidelines |
BCM5830X | BCM958305_AUDIO_LC_V0_2.zip | Reference Design | BCM58305 & BCM43455 Low Cost Wireless Audio Reference Design, V0.2 |
We are developing board with BCM43455.
thanks a lot !
P.S.
sorry, if this wrong place.
Show LessWe are currently using WICED WiFi Drivers for a product we are developing, however there is a quirk in their driver implementation which basically forces the WIFI to connect to the first detected Access Point rather than the one with the best RSSI.
That being said, we would like to know if anyone has attempted or encountered any modification for this, since it is a change that would affect their wwd_wifi.c file. Within this file we are looking at two functions:
1) wwd_wifi_join()
2) wwd_wifi_join_specific()
We know that the second function is to connect to the pre-loaded AP in wifi_config_dct.h. However, if this is not available it will then run wwd_wifi_join() to connect to another AP which is referenced to in memory. That being said, we would like to modify wwd_wifi_join() to allow us to connect to the strongest AP with our SSID. So, it is essentially connecting to a specific BSSID.
We are currently stuck in modifying line 1042-1054 within the wwd_wifi_join() function:
The end goal here is for the WIFI module to establish a connection to the SSID with the best RSSI and not simply the first SSID that matches with our saved one.
Please advise. Thank you.
Hi,
When I build any app I always get following error:
tools/makefiles/wiced_apps.mk:423: recipe for target 'APPS_LUT_DOWNLOAD' failed
make.exe[1]: *** [APPS_LUT_DOWNLOAD] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2
What is mean? What I do wrong? Any ideas?
Show LessHi,
The product under development uses a CYW4343W and WICED Version: Wiced_006.004.000.0061
The product provides both a BLE server and client for interfacing with other proprietary devices. The server is used for communications with a beacon while the client interfaces to a periodically Advertising device. The product also uses the CYW4343W WiFi.
While debugging the application, a direct LE connection to the BLE Address of the Advertising device is initiated with a scan window of 120ms in an interval of 190ms using wiced_bt_gatt_le_connect() that returns WICED_TRUE. This call results in a Divide by Zero Exception. The debugger shows the call stack to be:- btu_hcif_process_event(), btm_ble_conn_complete(), btm_identity_addr_to_random_pseudo(), btm_ble_read_resolving_list_entry(), btm_ble_enq_resolving_list_pending() where the exception occurs. A BLE sniffer shows that Advertisements were being issued by the device at the time of the exception.
If the product is allowed to run the same code without the debugger being connected multiple BLE connection are made with the Advertising device before a WICED_TIMEOUT occurs as described in an issue raised by a RoHe_4370821 on 28th Dec 2020: -
BTM_ENABLED_EVT with status WICED_TIMEOUT
(https://community.cypress.com/t5/WICED-Studio-Wi-Fi-Combo/BTM-ENABLED-EVT-with-status-WICED-TIMEOUT/m-p/266895)
Is this a known bug?
Could the issue be caused by the window and interval timings or other settings?
Is there any documentation available about setting scanning windows, intervals and the supervision timer values?
If there is no documentation please could give some guidance on typical settings know to work?
Regards,
Show Less