Discussion forum regarding WICED Studio Wi-Fi Combo topics.
Using WICED 220.127.116.11, STM32L4+ connected to a 43012C0
I am running into an issue when sending data to a connected socket using the NETX API. After some time, anywhere from 2-20 minutes, my tcp sends return NX_NOT_CONNECTED. I've watched the connection in wireshark, and there is no FIN or RST being sent by either side of the connection. All traffic from the device stops, the server sends one keep alive, and finally the server RST the connection. When this happens, other wiced API calls, like getting the RSSI, hang indefinitely. I have tried closing the socket, and attempting to reconnect, but all attempts at connecting eventually return NX_NOT_CONNECTED. Even taking down the interface and attempting to rescan and connect to the AP fails on the scan call.
What I have noticed is that the WWD thread appears to be waiting on the SDIO semaphore, and never seems to unblock. Does anyone know what is happening, or if there is a work around for this which does not require restarting the chip from scratch?
Below is the stack trace for the WWD thread.
#0 __restore_interrupts (primask_value=2147483648) threadx/5_8/tx_port.h:488 #1 _tx_thread_system_return_inline () threadx/5_8/tx_port.h:488 #2 _tx_thread_system_ni_suspend (thread_ptr=<optimized out>, thread_ptr@entry=0x200019d4 <wwd_thread>, wait_option=<optimized out>) threadx/5_8/tx_thread_system_suspend.c:1278 #3 _tx_semaphore_get (semaphore_ptr=<optimized out>, wait_option=<optimized out>) threadx/5_8/tx_semaphore_get.c:239 #4 _txe_semaphore_get (semaphore_ptr=semaphore_ptr@entry=0x200025b4 <sdmmc1_sem>, wait_option=wait_option@entry=4294967295) threadx/5_8/txe_semaphore_get.c:179 #5 host_platform_sdio_cmd (command=command@entry=SDIO_CMD_53, argument=argument@entry=2751496256, response_expected=<optimized out>, response_expected@entry=(unknown: 164) host_platform_wiced.c:314 #6 host_platform_sdio_transfer (command=SDIO_CMD_53, response=0x0, response_expected=(unknown: 164) host_platform_wiced.c:531 #7 host_platform_sdio_transfer (direction=<optimized out>, command=<optimized out>, mode=<optimized out>, block_size=<optimized out>, argument=<optimized out>, data=<optimized out>, data_size=<optimized out>, response_expected=<optimized out>, response=<optimized out>) host_platform_wiced.c:463 #8 wwd_bus_sdio_cmd53 (response_expected=RESPONSE_NEEDED, response=0x0, data=0x200208f0 <g_tx_mem+64> "a", data_size=<optimized out>, address=0, mode=<optimized out>, function=<optimized out>, direction=<optimized out>) wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/bus_protocols/SDIO/wwd_bus_protocol.c:708 #9 wwd_bus_sdio_transfer (direction=<optimized out>, function=<optimized out>, address=address@entry=0, data_size=<optimized out>, data=0x200208f0 <g_tx_mem+64> "a", response_expected=RESPONSE_NEEDED) wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/bus_protocols/SDIO/ wwd_bus_protocol.c:663 #10 wwd_bus_transfer_bytes (direction=direction@entry=BUS_WRITE, function=function@entry=WLAN_FUNCTION, address=address@entry=0, size=size@entry=97, data=0x200208f0 <g_tx_mem+64>) wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/bus_protocols/SDIO/ wwd_bus_protocol.c:644 #11 wwd_bus_send_buffer (buffer=0x200208b0 <g_tx_mem>) wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/bus_protocols/SDIO/ wwd_bus_protocol.c:220 #12 wwd_thread_send_one_packet () wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/wwd_thread.c:184 #13 wwd_thread_func (thread_input=<optimized out>) wiced-sdk/43xxx_Wi-Fi/WICED/WWD/internal/wwd_thread.c:357
I'm working on a BLE project which has one output data service with three characteristics in it (that correspond to the three data channels I need to send). I'm sending all this data using notifications.
For some reason when I use any of the iOS BLE apps (For example in the screenshot below I have the nRF Connect App for iOS) I cannot see all the characteristics. I can see one of them but I still can't enable the notifications even for that one characteristic. (this happens with the Cysmart app, LightBlue iOS apps as well).
The weird thing about this is that when I use the Android counterparts of the same apps, I don't have this problem. I can see all the characteristics and I can even enable the notifications for them.
Is there anything I can do here to fix this issue with the iOS
This is how my characteristic definitions look like (I can share the code text itself just let me know)
I've bought CYW943907AEVAL1F board.
I develop a firmware that manipulate a mutex (wiced_rtos_lock_mutex) and manipulate a queue (wiced_rtos_push_to_queue) in a ISR (interrupt service routine) but each API calls get me errors:
wiced_rtos_lock_mutex returns 4 (WICED_ERROR)
wiced_rtos_push_to_queue returns 1032 (WICED_QUEUE_ERROR)
I suspect that I can't manipulate mutex or queue in a ISR (interrupt service routine) ...
can you confirm this ?
I am using a Murata's 1LD(CYW43438 combo chipset + STM32F412 MCU) development board. I am using WICED studio's IDE and built system for development and building. I am using ST micro's DfuSe (USB Device Firmware Upgrade host application) for programming, which is expecting a .DFU file to upload. There is another application provided by ST micro (DfuFileMgr) which takes S19, BIN and HEX files as input and output DFU file. Multiple bin files can be used to create a single DFU file. The WICED built system has generated multiple bin files (Bootloader, 2 DCT, Filesystem, APP LUT and sflash_write). I am not sure of the files and flash address for each of the files that has to be given as input to the DfuFileMgr for making a single DFU file. Request your help on the same.
Bin file list
6. 43xxx_Wi-Fi\build\waf.sflash_write-NoOS-MurataType1LD-SDIO\binary\waf.sflash_write-NoOS-MurataType1LD-SDIO.binShow Less
It seems that support of chips such as CYW4343W or CYW43438 on non-PSOC devices (e.g. STM32) will be slowly moved from WICED to WHD (as told in other posts).
I just checked the "STM32 Connectivity Expansion Pack 1.0.1" provided by Infineon. It's a special port of the WHD package v1.93 and seems to fit very well for what we need.
Just a question about Bluetooth part of the Combo: these packages (WHD or STM32 Connectivity) don't contain any bluetooth stack such as what was present in WICED. How to use the BT features of these chips? Do you have a separated package with the firmware related stuffs and the stack part (over the HCI link) ?
It seems that CYW94343WWCD1_EVB platform has been removed from WICED Studio 18.104.22.168.
Any reason why?
How to evaluate WICED 6.6 on this platform?
I have just bought a CYBT-353027-EVAL board, and I have installed WICED Studio.
This page says "Paste the folder in the WICED Studio 6.2 folder path …\ WICED-Studio-6.2\20706-A2_Bluetooth\Platforms\", but this path does not exist on my PC.
I downloaded "ez_serial_cybt_353027_fw_image_22.214.171.124", but I can't find instructions on how to install it.
Can anyone advise on the next step? Thanks.Show Less
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 );
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
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 126.96.36.199 on a Linux VM -> OK withh all the file installed
Any idea?Show Less