I succeed to communicate through SDIO with the module, flash the module without any error but I've the error
/* If your system times out here, it means that the WLAN firmware is not booting.
* Check that your WLAN chip matches the 'wifi_image.c' being built - in GNU toolchain, $(CHIP)
* makefile variable must be correct.
WPRINT_WWD_ERROR(("Timeout while waiting for high throughput clock\n"));
/*@-unreachable@*/ /* Reachable after hitting assert */
The value of the register SDIO_CHIP_CLOCK_CSR is 0x64. One time out of 20 it's working and I've the result 0xC0. (Bit 0x80 is set).
With STM32 Connectivity pack, it's working every times. I can't use STM32 Connectivity pack because I need Wi-Fi Direct (P2P)
I used the STM32 to output the clock for LPO. This clock is always on at frequency 32.768kHz.
The SDIO clock frequency is both 5MHz with WICED and with STM32 Connectivity pack.
I downloaded WICED parameters files from Laird and adapt it to my board. (wifi_nvram_image.h, platform.c/h, platform_config.h). I tested the same set of parameters (wifi_nvram_image.h, binaries files) with STM32 Connectivity pack and it's working.
I check every signals with oscilloscope and I didn't see any major differences.
I use WICED 6.2 because STM32H753 MCU is already added. I adapted files for STM32H733.
Wi-Fi connection(to wireless LAN AP) is lost immediately after 11 hours past with WPA3-SAE. We think it was caused due to Wi-Fi module is down. It's not disconnected by wireless AP. And we have already tried other wireless LAN AP from several vendors, and we confirmed that the same issue was reproduced in every case. However, if we choose WPA2-PSK, the issue doesn't happen. Wi-Fi connection is still alive after 11 hours past.
I have the board CYW954907AEVAL1F and I had an electrical accident the last week. It seems that all was OK but the USB IC (FT2232H) was no...
I have the board CYW954907AEVAL1F and I had an electrical accident the last week. It seems that all was OK but the USB IC (FT2232H) was not. My PC didn't recognize the usual COM port and I was unable to use it for download or debug via WICED STUDIO. After several tests, I realised that the EEPROM associated to FT2232H was broken.
I have replaced it with a new one and the same part number and now the board is recognized on PC, but there are now two COM PORTS and I can't use WICED Studio to download nor Debug any program.
I have downloaded the FT Prog software from FTDI and, after studying this chip, it could be used as JTAG bridge, but after some test, I can't use the board with Wiced Studio for debugging.
Please, could any one tell me how I can reprogram the FT2232H chip implemented on CYW954907AEVAL1F to use with WICED Studio?
There are missing files after wiced studio is installed. Please check the missing files and where to get them to complete the vulnerabili...
There are missing files after wiced studio is installed. Please check the missing files and where to get them to complete the vulnerability.
17:54:07 **** Incremental Build of configuration Default for project 43xxx_Wi-Fi **** "C:\\Users\\Merri\\Documents\\WICED-Studio-6.6\\43xxx_Wi-Fi\\make.exe" Default MAKEFILE MAKECMDGOALS=Default OTA2_SUPPORT is disabled Making config file for first time tools/makefiles/wiced_config.mk:256: platforms//.mk: No such file or directory tools/makefiles/wiced_config.mk:267: *** Unknown component: Default. Stop. make: *** No rule to make target 'build/Default/config.mk', needed by 'main_app'. Stop.
According to the datasheet, the CYW4343W has a WLAN unit and Bluetooth unit, both having an ARM CM3 processor, RAM and ROM on-chip memory. Also accor...
According to the datasheet, the CYW4343W has a WLAN unit and Bluetooth unit, both having an ARM CM3 processor, RAM and ROM on-chip memory. Also according to the datasheet:
"External patches may be applied to the ROM-based firmware to provide flexibility for bug fixes or feature additions. These patches may be downloaded from the host to the CYW4343W through the UART transports."
However, I can't seem to find any clear documentation on how to apply patches to the ROM-based firmware. Can anyone refer me to any documentation on how this is done?
A bit more context from my end: we have our custom hardware including a Murata 1DX module, which includes the CYW4343W chipset.
I am facing the following problem.I would appreciate your help.
There are times when the WPS PBC (Enrollee) cannot connect to the AP (re...
I am facing the following problem. I would appreciate your help.
There are times when the WPS PBC (Enrollee) cannot connect to the AP (register) properly. At that time, I found that the Destination Address in (Request,Identity) packet is set to ALL zero with Air-log. I think this is what causes the WPS connection to fail.
I attached the console log and the air-log files for when the phenomenon occurred.
The environment for the test is as follows.
Wiced version => Wiced_006.002.001.0002 Program => snip.wps_enrollee Wifi Module => Murata Type1LD AP => Synology MR2200
[Need Help] Is there any way to work around this problem ?
Then, in my platform makefile, I define USE_FPU_CM4F . The idea was that I wouldn't have to define a whole new CM4F variant in the build system, just tweak the CM4 one a little bit. Based on what I read about GCC flags, this should work, since soft-fp will still be link-compatible with existing libraries built without FPU support. And the choice of -mfpu was just from other STM32F4xx examples I found.
Then, in system_stm32f4xx.c, at the top of SystemInit(), FPU access is enabled:
SCB->CPACR |= ((3UL << 10*2)|(3UL << 11*2)); /* set CP10 and CP11 Full Access */
So, then the compiler does indeed generate FPU instructions, and they even appear to run OK.
BUT: the system hits a hard fault after running for not very long. Using ETM on the target, I am seeing a crash that appears to originate in tx_thread_create, when the PC is popped, it gets a bad address, spirals out of control, and eventually ends up at a hard fault. See attached screenshot. I could provide a longer trace history privately, if that would help.
I contacted ExpressLogic to get some insight into this, and they indicate that for FPU usage, there must be a call to void tx_thread_fpu_enable(void) to set up correct FPU context saves. Unfortunately, looking at the tx_port.h file provided in the WICED SDK, it seems like there is a single file that covers both CM3 and CM4, and there's no mention of this function anywhere. Looking at the headers from the objdump of ThreadX.ARM , there's no mention of the tx_thread_fpu_enable() function anywhere. And the ThreadX User Guide doesn't mention it, either.
So ... any chance that there is a solution for this?
It seems like it is going to take an upgrade to ThreadX. Or possibly a rebuild of the existing archive(s), with the FPU enables functions not being dropped.
I am developing a project based on wifi connection for use mqtt and the use of UARTs Fast and low (stdio) for control and communication w...
I am developing a project based on wifi connection for use mqtt and the use of UARTs Fast and low (stdio) for control and communication with other devices.
It's all running properly, but to make an enhacement on the control of FASTUART, I decided to use a timer (based on rtos) to managed timeouts when a reception starts and flush the ring buffer when a timeout is trigger before a full frame has been received on the fastuart.
With this addition, when I use the make target "kits.CYW954907AEVAL1F.MyProject-CYW954907AEVAL1F-FreeRTOS-LwIP-debug download" next information is printed on console with the ERRORS:
Building Bootloader waf.bootloader-NoOS-NoNS-CYW954907AEVAL1F-P101-SoC.43909 Building Serial Flash Loader App build/waf.sflash_write-NoOS-CYW954907AEVAL1F-P101-SoC.43909/libraries/Uart_43909_Library_CYW954907AEVAL1F.a(platform_uart.o): In function `Timer_Control_FASTUART_CallBack': C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2672: undefined reference to `wiced_rtos_stop_timer' C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2681: undefined reference to `wiced_rtos_deinit_timer' build/waf.sflash_write-NoOS-CYW954907AEVAL1F-P101-SoC.43909/libraries/Uart_43909_Library_CYW954907AEVAL1F.a(platform_uart.o): In function `uart_seci_process_irq': C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2261: undefined reference to `wiced_rtos_stop_timer' C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2264: undefined reference to `wiced_rtos_deinit_timer' C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2288: undefined reference to `wiced_rtos_init_timer' C:\WICED-Studio-6.6\43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/uart/platform_uart.c:2290: undefined reference to `wiced_rtos_start_timer' collect2.exe: error: ld returned 1 exit status make.exe: *** [build/waf.sflash_write-NoOS-CYW954907AEVAL1F-P101-SoC.43909/binary/waf.sflash_write-NoOS-CYW954907AEVAL1F-P101-SoC.43909.elf] Error 1 make.exe: *** [main_app] Error 2 tools/makefiles/wiced_apps.mk:416: recipe for target 'sflash_write_app' failed make.exe: *** [sflash_write_app] Error 2 make.exe: *** Waiting for unfinished jobs....
I use the timer on the file "platform_uart.c" and its functions are declared via #include "wiced_rtos.h".