I am getting the below issue when I updated the MFG Test Application in Murata board. I haved updated the external flash with respective APPS.bin,filesystem,etc
** ERROR: WLAN: could not download clm_blob file
** FATAL ERROR: system unusable, CLM blob file not found or corrupted.
Is any extra thing need to be added in mfg_test.mk?Show Less
We have a platform that uses WICED Version 3.7.0-7. AN STM32F469 processor uses the WiFi/BT module LBEE5KL1DX. We're able to bond with and connect and reconnect to a BTLE 4.0 keyboard without issues. When we do the same with the same model of keyboard that uses BTLE 5.0, we're able to bond with and connect with the keyboard, but upon re connection, the firmware crashes. From the debugger, it seems to be crashing in a pee-compiled module we have: BTE_low_energy.FreeRTOS.LwIP.ARM_CM4.release.a.
Our belief is that something in the firmware is not handling BT 5.0 events correctly and is causing the firmware crash. But it isn't easy to tell what's going on in the project and the .a file is a bit of a mystery too. Are there any clues as to where to look for this issue? Is there perhaps an updated version of WICED or an updated driver file we should be using?Show Less
1GC sends data using UDP, Call wiced_result_t wiced_udp_send(wiced_udp_socket_t * socket, const wiced_ip_address_t * address, uint16_t port, wiced_packet_t * packet), can only send 1472 bytes?
I have changed NX_DONT_FRAGMENT to NX_FRAGMENT_OKAY when I call wiced_UDP_create_socket to create UDP socket. The result is also not supported.
Call wiced_packet_create_udp(socket, 4000, &packet, (uint8_t**) &data, &available_data_length), The value of available_data_length is 1508.
Hi everyone, I am following a firmware development project based on the WICED 4.1 SDK, I need to update the SDK to solve the famous WPA2 KRACK vulnerability.
Unfortunately, between version 4.1 and the latest 6.6.x.y versions there is no bootloader compatibility and this makes an update via OTA impossible.
So, inevitably, to fix the vulnerability I must necessarily update to version 4.1.3 as it is the last one that maintains the compatibility of the bootloaders. Now I have the problem of having to find the SDK for linux versions.
I found this topic on the support page but the links are not working: https://community.infineon.com/t5/Blogs/WICED-Studio-4-3-1-has-been-released-backport-to-address-KRACK/ba-p/129833
Can you help me by providing me the sdk for linux versions?
Thank youShow Less
To anyone listening. We developed system using a Laird_EWB module. We used the EWB-DevKt to build some basic apps, Dual Mode BT, TCP Server, etc. I am currently using OLIMEX ARM-USB-TINY-H to debug in eclipse. We attempted to make this work with the standard WICED apps with no joy. I have two versions of wiced studio. One is vanilla which allows me to test a small dual mode bt app using the LAIRD DEV kit. The other wiced studio has been modified slightly to allow for the OLIMEX debugger. I am able to build and download in eclipse using OLIMEX with some issues that I have worked out. I begin debugging my app on OUR module and while progressing through the application I keep coming across two unhandled interrupts. The active interrupts are shown to be 33 and 54. I decided to tackle INTERRUPT 33 first. According 8to the STM32F412 manual this is associated with the I2C channel 2 event. When I created my own platform file, I did not include any I2C. I have two USARTS, JTAG header, and power, and a few jumpers. What I am looking for is the steps necessary to override the "unhandled interrupt" using the wiced platform. In fact if there is any manual or detailed document that provides the steps necessary to incorporate interrupts either RTOS or native, please let me know. I have been through WICED-101 but the info that I am looking for appears to be a little more in depth than what WICED-101 provides.
I have also successfully tested our UART app with RTOS with no issues. I would really appreciate if someone could throw me a bread crumb.
Dan TShow Less
Hi everyone I'm trying to flash ISM43903_R48_L54 with a particular test target "flash_emc".
Building apps lookup table
make : *** [download_dct] Error 1
make: *** [main_app] Error 2
make: *** [Makefile.wiced: 428: flash_emc] Error 2
I am under ubuntu 22.04 and the problem is present only with this target, with others the firmware is flashed correctly.
As you will see from the logs the wiced version is 4.1. Do you have any suggestions to try?
I'm trying to build up a test platform for our device off a raspberry pi which is running 32-bit Linux and is an ARM platform. I am trying to j-link flash the device from it. I copied over my build/, my apps/, and my tools/ folders but it looks like the ./tools/OpenOCD/Linux32/openocd-all-brcm-libftdi executible doesn't work on ARM.
Downloading Bootloader ...
./tools/OpenOCD/Linux32/openocd-all-brcm-libftdi: cannot execute binary file: Exec format error
**** OpenOCD failed ****
I don't believe that is built during the normal build process. I think it is just packaged with WICED Studio. Is there any way I can get flashing working on ARM 32-bit? I don't need it to build the full file, just be able to flash it. I'm currently running WICED-Studio 6.6.1
I am looking for an app note or more importantly some WICED sample code which will allow me to, firstly connect a generic BT headset/speaker to the Sterling EWB (CYW4343W). Secondly how to stream an audio signal connected to the BT_PCM pin on the CYW4343W to the headset. There is no requirement to send audio from the headset back to the EWB module.
We have a issue with non-working BLE advertisement after exit from Sleep mode.
Our procedures of enter to and exit from sleep mode looks more or less like that:
// turn on powersave mode (enter to sleep mode)
wiced_wlan_connectivity_deinit(); // WIFI module deinitialization
wiced_gpio_init( WIFI_EN, INPUT_HIGH_IMPEDANCE ); // WIFI module power off (LDO disable)
wiced_platform_mcu_enable_powersave(); // enable MCU sleep mode
// here we have very nice power consumption, about 500uA
// device sleep
// device wakeup
// turn off powersave mode (exit from sleep mode)
wiced_platform_mcu_disable_powersave(); // disable MCU sleep mode
wiced_gpio_init( WIFI_EN, OUTPUT_PUSH_PULL ); // WIFI module power on (LDO enable)
wiced_gpio_output_high ( WIFI_EN );
wiced_wlan_connectivity_init( ); // WIFI module initialization
// enable BLE advertisement after exit from sleep mode
wiced_bt_start_advertisements( BTM_BLE_ADVERT_UNDIRECTED_HIGH, 0, NULL );
Deinitialization WLAN connectivity only (without turning off WiFi power cause high power consumption, above 10mA).
Turning OFF WiFi RF power (by external LDO) decrease power consumption below 500uA which is expected.
Reintialization everything in a clear way, together with turning ON WiFi RF works well until start BLE advertisement.
Starting BLE advertisement causes continuous periodic (every 8.5s) receiving BLE_ENABLE_EVT events from bluetooth stack.
And advertisement doesn't work, we are not able to see any advertisement packets.
We definitely would like to turning off/on WiFi power by external LDO, because it gives us additional 1mA of power savings in compare to powersave only without WiFi deinitialization.
What could be a reason for this behaviour?
Are our enter/exit sleep mode procedures correct?Show Less
I just upgraded the version of Wiced we are using from 6.4 to 184.108.40.206. When the code tries to set wwd_wifi_fast_bss_transition_over_distribution_system the result is now WWD_WLAN_UNSUPPORTED.
The chip is a CY43012C0.
Any ideas why this no longer works?Show Less