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.
We have a design that use the laird Sterling EWB (cyw4343w + STM32f4x). I was running test on the sterling laird ewb dev kit via USB (FTDI chip) ...
We have a design that use the laird Sterling EWB (cyw4343w + STM32f4x). I was running test on the sterling laird ewb dev kit via USB (FTDI chip) and everything works fine. Now we are trying to use the JTAG connector with our JLINK segger and we are not able to program the board (our board and the dev kit that as a Jtag connector header).
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****" Downloading DCT ...
Here's what we have done so far :
Change the Jlink driver for the usblibK (18.104.22.168 and 22.214.171.124 try both)
Add reset_config trst_and_srst srst_push_pull to the jlink.cfg file
Change JTAG ?= CYW9WCD1EVAL1 for JTAG ?= jlink.
Our make target look like : "app folder"."app-name"-LAIRD_EWB JTAG=jlink download run.
We try every combination of everything listed but we always add the same result.
In the openocd_log.txt, we got this error (attached files) :
Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc.
Any help would be appreciated, we are running out of solutions here,
Upon this condition, the devB sends a query packet to the group and the devA receives it. Then, the devA makes a reply packet and send to the same group, but the devB never receives it. Wireshark has no packet dump for the devA reply packet, either.
I put some debug message at the function wwd_thread_send_one_packet() in WWD/internal/wwd_thread.c and make sure the packet transfer to the WiFi chip done well as expected.
Here is my question that is any reason the WiFi chip doesn't send a multicast packet out to the network?
(added: it seems to be none of multicast transmit packets actually going out to the network. The call wwd_wifi_get_counters( STA, &counters ) returns counters.txmulti unchanged at all.)
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 ?