Wi-Fi Combo Forum Discussions
Hi Team,
I am working on wiced sdk 6.2.1 in FREE RTOS platform. In this free rtos platform OTA2 is not supported, so i am using OTA.
First I tried writing APP binary into DCT_APP1_INDEX of external flash (chunks of 1024 bytes received from socket) and able to boot properly from this location when you reboot.
In similar way tried to write DCT binary into DCT_DCT_IMAGE_INDEX of external flash. It is able to write but when you reboot it was not effecting that changes.(not booting)
Actually when you update DCT and reboot that changes should reflect in app.
what is exact location to write DCT binary for OTA?
Is there anything to change in lookup table when you update only DCT?
Thanks,
Raviteja.
Show LessI have a code which is having custom_RTOS and is working fine.
I retained custom_RTOS apis as is and internally called FreeRTOS apis.
I integrated WICED wi-fi stack into this code.
As per my understanding WICED wi-fi apis also make use of FreeRTOS apis.
Application is written using custom_RTOS apis and WICED wi-fi apis.
My question is:
custom_RTOS apis and WICED wi-fi apis are calling FreeRTOS apis.
Does it cause any issues ?
We are using the 1GC. We are trying to use the mfg_test app with our design but our stdio_uart is set to WICED_UART_3 per our design. I have compared the results with the cyw949307aeval1f board.
wl43909B0.exe --serial 16 ver fails with our board.
What is also interesting to note is that even with stdio_uart set to uart 3, the cyw943907aeval1f still works.
I am speculating that wiced_wlu_server_serial_start( STDIO_UART ); in mfg_test_init.c does not do anything.
I also suspect that is possible that WIFI_FIRMWARE_BIN := firmware/$(WLAN_CHIP)/$(WLAN_CHIP)$(WLAN_CHIP_REVISION)-mfgtest.bin
43909B0-mfgtest.bin may be hard coded to only use WICED_UART_1.
Is that the case? Is there a way to run mfg_Test using a different uart?
Thanks
Show LessWe recently acquired a license for netx and would like to build and link our code. Wiced uses two functions to enable low power mode, nx_tcp_resume and nx_tcp_suspend. These functions are implemented by wiced, but are linked inside the distributed lib_netx.a library.
Can Cypress share the code for nx_tcp_resume/suspend so that we can link our own code and libraries?
Show LessI compiled demo example provided in 43xxx_Wi-Fi project.
command used is snip.scan-MurataType1LD-FreeRTOS-LwIP-SDIO-debug download.
Flash size is 178984 bytes and ram is 48932 bytes.
I compiled demo example added by me in 43xxx_Wi-Fi project.
command used is ltk_sample_app_wiced_gcc-MurataType1LD-FreeRTOS-LwIP-SDIO-debug download.
Flash size is 0 bytes and ram is 65496 bytes .
Why Flash size is shown as 0 bytes??
Show Less
Hi Sir,
From datasheet,we know 43012 BT TX is 13dbm,belong to class 1.
If we want to change BT classic power class,how can we do it ,HW or FW?
Meanwhile,how to change BLE power class?
Thanks.
BR,
Leo
Show LessWe recently tracked down an annoying issue with DNS reliability when we updated our firmware to wiced SDK v6.1.
Our firmware uses ThreadX and NetX and our hardware is an STM32F4xx and the 4343W module.
The issue originally presented as DNS working reliably at some of our labs and not working reliably or at all at other office sites.
Eventually we traced this to a bug that appears in DNS for v6.1 and is still there in the 6.2.x releases.
Specifically, with the 6.1 update, the endian order of dns server addresses extracted and saved from DHCP responses changed inside WICED/network/NetX/WICED/wiced_network.c::wiced_ip_up() from host order to network order. But the consumer of the DNS addresses inside libraries/protocols/DNS/dns.c::dns_client_hostname_lookup() did not change. So those addressesno longer matched the order expected from wiced_udp_send (used to query the DNS servers). So all queries to DNS servers specified by the DHCP payload were failing.
Why did DNS sort-of work at some sites? Because the bug was partially masked by wiced code that was arbitrarily adding a hard-coded 8.8.8.8 (the google public dns a server) to the list of DNS servers. BUT that fix only worked if the DHCP payload had not already filled the list. So if you connected to an AP that only supplied one DNS address, that DNS server would fail, but the hardcoded google address would work.
It's trivial to reproduce this failure for any wiced 6.1 or 6.2 that uses DNS (including their example apps and snips) by simply commenting out that 8.8.8.8 hardcode inside WICED/network/NetX/WICED/wiced_network.c::wiced_ip_up(). Here are those lines.
/* Add Google DNS server (8.8.8.8) */
memset( dns_ip_string, 8, 4 );
SET_IPV4_ADDRESS( address, nx_dhcp_user_option_convert( dns_ip_string ) );
dns_client_add_server_address( address );
@Cypress can someone please confirm and add this to your bug tracking for the next release?
Show LessIs external flash required for the CYW43907?
Can custom FW be loaded into the onboard ROM? If so, can this FW be updated in the field via UART and an external processor?
If custom FW cannot be loaded into the ROM, does a standard firmware exist there that allows ethernet-to-wifi functionality by default? Or does this ROM only hold bootloader?
Does the presence/absence of external flash impact the correct configuration of the WCPU_BOOT_MODE and ACPU_BOOT_MODE strapping options?
Thank you
Show Less