Hi everyone I'm trying to flash ISM43903_R48_L54 with a particular test target "flash_emc".
Building apps lookup table
make [1]: *** [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?
sudo make -f Makefile.wiced flash_emc
make -C mbedtls/mbedtls-mbedtls-2.7.4/api-renamer "MBEDTLS_DIR=/home/cciavola/Project/smeg/biot-agent/.wiced-fw/mbedtls-mbedtls-2.7.4/mbedtls-mbedtls-2.7.4"
make[1]: ingresso nella directory «/home/cciavola/Project/smeg/biot-agent/mbedtls/mbedtls-mbedtls-2.7.4/api-renamer»
make[1]: Nessuna operazione da eseguire per «all».
make[1]: uscita dalla directory «/home/cciavola/Project/smeg/biot-agent/mbedtls/mbedtls-mbedtls-2.7.4/api-renamer»
tools/gen_version.sh generated/biot_version.h.new I.W.01.01_01 CB01
Building version: v1.8.2-0-ge2c3aca-CB01
Compliance ID: I.W.01.01_01
cmp -s generated/biot_version.h.new generated/biot_version.h \
&& rm -f generated/biot_version.h.new \
|| mv generated/biot_version.h.new generated/biot_version.h
if [ "$(readlink ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi/apps/smeg_emc_test")" != "/home/cciavola/Project/smeg/biot-agent/.wiced-fw/renamed-sources/" ]; then printf 'Need to create a root directory link for "%s".\n' "smeg_emc_test"; rm -f ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi/apps/smeg_emc_test"; ln -s "/home/cciavola/Project/smeg/biot-agent/.wiced-fw/renamed-sources/" ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi/apps/smeg_emc_test"; fi
cd ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi/apps/smeg_emc_test" && if [ "$(readlink "smeg_emc_test.mk")" != "/home/cciavola/Project/smeg/biot-agent/customer/SMEG/emc_test/smeg_emc_test.mk" ]; then printf 'Need to create a make file link for "%s" -> "%s".\n' "smeg_emc_test.mk" "customer/SMEG/emc_test/smeg_emc_test.mk"; rm -f "smeg_emc_test.mk"; ln -s "/home/cciavola/Project/smeg/biot-agent/customer/SMEG/emc_test/smeg_emc_test.mk" "smeg_emc_test.mk"; fi
cd ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi"; ./make JOBS=16 EXTERNAL_WICED_GLOBAL_DEFINES=ADB_CARRIER_BOARD FW_UPGRADE_ON_EXTERNAL_FLASH=1 ADB_BIOT_WICED_MBEDTLS=1 "smeg_emc_test-ISM43903_R48_L54" ADB_BIOT_SOURCE_LIST=/home/cciavola/Project/smeg/biot-agent/customer/SMEG/emc_test/smeg_emc_test_sources.mk
MAKEFILE MAKECMDGOALS=smeg_emc_test-ISM43903_R48_L54 OTA2_SUPPORT is disabled
smeg_emc_test-ISM43903_R48_L54
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
crc | 0 | 1060 |
DHCP_Server | 0 | 1574 |
DNS | 0 | 136 |
Interrupt Vectors | 0 | 288 |
iperf | 0 | 27006 |
libc | 0 | 51004 |
Networking | 0 | 17192 |
NetX-Duo - Interfaces & Stacks | 0 | 16 |
NVRam | 0 | 2243 |
Other | 0 | 101614 |
Packet Buffers | 0 | 34116 |
platform | 0 | 172 |
RAM Initialisation | 32 | 0 |
resources | 0 | 36 |
Ring_Buffer | 0 | 140 |
Startup Stack & Link Script fill | 0 | 240 |
Supplicant - BESL | 0 | 112 |
ThreadX | 0 | 12924 |
WICED | 0 | 4756 |
Wiced_RO_FS | 0 | 568 |
wlu_server | 0 | 7396 |
WWD | 0 | 2099 |
----------------------------------+---------+---------|
TOTAL (bytes) | 0 | 264692 |
----------------------------------|---------|---------|
Creating Filesystem BCM94390x_targets.mk ...
./tools/common/Linux64/mk_wicedfs32 build/smeg_emc_test-ISM43903_R48_L54/filesystem.bin build/smeg_emc_test-ISM43903_R48_L54/resources/Staging/
Creating Filesystem Done
Build complete
Making .gdbinit
cd ".wiced-fw/EMC/WICED-SDK-4.1/WICED-Studio-4.1/43xxx_Wi-Fi"; ./make JOBS=16 EXTERNAL_WICED_GLOBAL_DEFINES=ADB_CARRIER_BOARD FW_UPGRADE_ON_EXTERNAL_FLASH=1 ADB_BIOT_WICED_MBEDTLS=1 "smeg_emc_test-ISM43903_R48_L54" download download_apps run
MAKEFILE MAKECMDGOALS=smeg_emc_test-ISM43903_R48_L54 download download_apps run OTA2_SUPPORT is disabled
Building Bootloader waf.bootloader-NoOS-NoNS-ISM43903_R48_L54-SoC.43909
Building Serial Flash Loader App
Finished Building Serial Flash Loader App
Finished Building Bootloader
smeg_emc_test-ISM43903_R48_L54
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
crc | 0 | 1060 |
DHCP_Server | 0 | 1574 |
DNS | 0 | 136 |
Interrupt Vectors | 0 | 288 |
iperf | 0 | 27006 |
libc | 0 | 51004 |
Networking | 0 | 17192 |
NetX-Duo - Interfaces & Stacks | 0 | 16 |
NVRam | 0 | 2243 |
Other | 0 | 101614 |
Packet Buffers | 0 | 34116 |
platform | 0 | 172 |
RAM Initialisation | 32 | 0 |
resources | 0 | 36 |
Ring_Buffer | 0 | 140 |
Startup Stack & Link Script fill | 0 | 240 |
Supplicant - BESL | 0 | 112 |
ThreadX | 0 | 12924 |
WICED | 0 | 4756 |
Wiced_RO_FS | 0 | 568 |
wlu_server | 0 | 7396 |
WWD | 0 | 2099 |
----------------------------------+---------+---------|
TOTAL (bytes) | 0 | 264692 |
----------------------------------|---------|---------|
Creating Filesystem BCM94390x_targets.mk ...
Downloading DCT ... build/smeg_emc_test-ISM43903_R48_L54/DCT.bin @ SFLASH_DCT_LOC=0x00008000
./tools/common/Linux64/mk_wicedfs32 build/smeg_emc_test-ISM43903_R48_L54/filesystem.bin build/smeg_emc_test-ISM43903_R48_L54/resources/Staging/
Creating Filesystem Done
Building apps lookup table
make[1]: *** [download_dct] Error 1
make: *** [main_app] Error 2
make: *** [Makefile.wiced:428: flash_emc] Errore 2
I started poking around to see if I can get my build files packaged up so we can use them during manufacturing. It looks like the normal build command doesn't create build/$project/APP.bin, but we use that to jlink flash controllers during manufacturing. I started poking around to see how it gets pulled in and it looked like adding either "download" or "package" should build it. I confirmed it happens during download (but that tries to actually use jlink and download to a device). I noticed just adding "package" doesn't do anything. After digging in more I noticed it was setup like this:
package: $(RELEASE_PACKAGE)
$(QUIET)$(ECHO) Created package successfully
$(RELEASE_PACKAGE): create_package_descriptor \
$(STRIPPED_LINK_OUTPUT_FILE) display_map_summary \
package_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,package_dct) package_app package_apps
in tools/makefiles/standard_platform_targets.mk, but RELEASE_PACKAGE isn't defined anywhere. If I pass in something defining it on the make line, I get the next issue:
make[1]: *** No rule to make target `create_package_descriptor',
I can't find any info on create_package_descriptor. I was wondering if this was meant to be removed and/or if I'm even going about this the right way. I'm currently using WICED-Studio-6.2.1.2 but I also tried on WICED-Studio-6.6.1 and saw the same issue. Any help or guidance would be appreciated.
Hi guys,
In our application, we connect to wifi AP and do stuffs. If we got some issues like request http error or disconnect with mqtt broker, we will retry to connect again. Incase retry not success we will disconnect with wifi AP and retry to connect current wifi AP again or connect the another wifi AP.
But sometime we got stuck forever in wiced_leave_ap.
I use CYW54907 with Wiced studio 6.6.
Show LessI'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 just upgraded the version of Wiced we are using from 6.4 to 6.6.1.1. 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 LessHi,
Is there a clear centralized exhaustive list (and history) of know vulnerabilities in the CYW4343W (or all chips) firmware ?
Browsing https://github.com/Infineon/wifi-host-driver commits to RELEASE.md (like that Upload wifi-host-driver 1.94.0.6931 · Infineon/wifi-host-driver@19968e1 (github.com)) I can see that there is a few changelogs related to the CYW4343W firmware.
--- 7.45.98.120 ---
Fix pmk caching
--- 7.45.98.117 ---
Security fixes
Memory usage reduction by disabling debug features
--- 7.45.98.110 ---
Fixed zero stall on UDP
Fixed Tx traffic too less then RX
--- 7.45.98.95 ---
Fixed zero stall on UDP
--- 7.45.98.92 ---
Security fix (KRACK all-zero-key)
--- 7.45.98.89 ---
Security fix(Dragonblood WPA3 attack)
TCP Keepalive Implementation
Security fix(CVE-2019-9501 / CVE-2019-9502)
--- 7.45.98.81 ---
This list is not easy to build and browse, the known vulnerabilities should be centralized.
Is this list exhaustive ?
How can we know what version exactly fixes a vulnerability ? This only show ranges...
Between 7.45.98.110 and 7.45.98.117, it is only mentioned "Security fixes"... Where can we get more details on this/these vulnerability(ies) ?
Looking at this blog post (Potential Fragmentation Vulnerabilities for Wi-Fi ... - Infineon Developer Community), it looks like the CYW4343W could by affected. How can we make sure whether it is or not ?
Any more information about firmware vulnerabilities is welcome.
Thanks and best regards
Show LessMeasuring the 5.8g signal at the FCC test lab and only seeing 8 dbm, when the documents have 13 dbm as an average. I retuned the antenna and still measuring 8 dbm. Any ideas?
Show LessHello.
We develop a board with the same processor in CYW943907AEVAL1F.
We mount CYPRESS S25FL064LABNFI010 instead of MX25L6433FZNI as FLASH.
I modify CYW943907AEVAL1F.mk row 62 from
GLOBAL_DEFINES += SFLASH_SUPPORT_MACRONIX_PARTS
to
GLOBAL_DEFINES += SFLASH_SUPPORT_CYPRESS_PARTS.
We used OLIMEX ARM-USB-TINY-H as programmer and I launch this make target
"My project location"-CYW943907AEVAL1F download run JTAG=Olimex_ARM-USB-TINY-H
The debugger log says that's all it's OK but my APP doesn't start.
I try to modify sflash_write.c to execute this steps in order to understand if FLASH can be programmed properly:
/* init */
if ( 0 != init_sflash( &sflash_handle, 0, SFLASH_WRITE_ALLOWED ))
{
DEBUG_PRINTF(( "init_sflash failed!\n" ));
return -1;
}
/* erase */
DEBUG_PRINTF(( "1. erase\n\n" ));
if ( 0 != sflash_chip_erase( &sflash_handle ))
{
DEBUG_PRINTF(( "sflash_chip_erase failed!\n" ));
return -1;
}
/* write */
int i = 0;
for(i=0;i<256;i++) data_transfer.data[i] = (uint8_t)(i&0xFF);
DEBUG_PRINTF(( "ADDRESS HEX\tWRITTEN HEX\tREAD HEX\n" ));
long j=0;
for(j=0;j<32768;j+=256)
{
/* write */
if ( 0 != sflash_write( &sflash_handle, j, &data_transfer.data[0], 256))
{
DEBUG_PRINTF(( "sflash_write failed!\n" ));
goto end_test;
}
(void) platform_watchdog_kick( );
/* read */
if ( 0 != sflash_read( &sflash_handle, j, &Rx_Buffer[0], 256))
{
DEBUG_PRINTF(( "sflash_read failed!\n" ));
goto end_test;
}
(void) platform_watchdog_kick( );
for(i=0;i<256;i++)
{
DEBUG_PRINTF(( "%08X\t\t%02X\t\t%02X", (int)(i+j), data_transfer.data[i]&0xFF, Rx_Buffer[i]&0xFF));
if((data_transfer.data[i]&0xFF) != (Rx_Buffer[i]&0xFF))
{
DEBUG_PRINTF(( "----> failed !"));
}
DEBUG_PRINTF(( "\n" ));
}
}
This test says that FLASH can be programmed in a properly way ... but I don't undestand why after programming FLASH
the APP does'nt start.
Is there a kind who can help me?
Show LessHi there,
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.
Show Less