Wi-Fi Combo Forum Discussions
We are using CYW943907AEVAL1F - Free RTOS - LwIP & WICED 6.4. WIFI works with 5Ghz Band.
In our system there will be 8 STA's works with the above said environment.
When the STA tries to Join the Soft AP, some time we see the below error. The error code "1006" , "1024" corresponds to "Not authenticated " , "Specified network was not found " respectively.
Regards
venkatesh
Show LessHi,
I am doing security research on embedded systems bcm43438.
Now I see the ETM (Embedded Trace Macrocell), but I still can't find the ETB(Embedded Trace Buffer). Because I don't want to attach a debugger to trace it.
Is it an ETB or ETF ?
Can't find any tracing related info in the datasheet.
Thanks
Show LessHello,
I have developed an BLE-WiFi app on STM32F412+CYW43434W based module/DevKit (Laird-EWB)
Now I try to move to our proprietary hardware and use Olimex's ARM-USB-TINY-H programmer/debug adapter (rather than the DevKit's FTDI chip).
I can not find any single coherent instructions as how it is done.
Tried to follow all of the methods described out there and neither seemed to work.
Method #1 - Following instruction in the Wiced SDK (6.4) - tools\openOCD\Olimex_Rreadme.txt
- installing drivers from http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-bin-1.2.6.0.zip
- Debug probe in device manager located under 'libusb' node
- Generating target - "snip.scan-LAIRD_EWB JTAG=Olimex_ARM-USB-TINY-H download run"
I get the following error and open_ocd_log.txt:
console
Downloading Bootloader ...
Building apps lookup table
"**** 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 ...
"**** 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 resources filesystem ... build/snip.scan-LAIRD_EWB/filesystem.bin at sector 1 size 104...
tools/makefiles/wiced_apps.mk:335: recipe for target 'FILESYSTEM_IMAGE_DOWNLOAD' failed
make.exe[1]: *** [FILESYSTEM_IMAGE_DOWNLOAD] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2
openocd_log.txt -
Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
post_init_psoc6_setup <<<<<<< WHta;s this? I'm using STM32F412 based design
Error: failed to reset FTDI device: LIBUSB_ERROR_IO
Error: unable to open ftdi device with vid 15ba, pid 002a, description 'Olimex OpenOCD JTAG ARM-USB-TINY-H', serial '*' at bus location '*'
Method #2 - Following OpenOCD-WICED article in Cypress community site
- Using Zadig to replace drivers from libusb0 (1.2.6.0) to WinUSB (6.1.7600.16385) for both interfaces
- Debug probe in device manager located under 'Universal Serial Bus devices' node
Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: stm32f4xx.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
[..... Ton of such comments]Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the debug port
embedded:startup.tcl:21: Error:
in procedure 'init' called at file "./tools/OpenOCD/stm32f4x-flash-app.cfg", line 32
in procedure 'ocd_bouncer'
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
embedded:startup.tcl:21: Error:
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: stm32f4xx.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in
DAP response
[... another Ton of these]
Error: JTAG-DP STICKY ERROR
[.....]Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the debug port
embedded:startup.tcl:21: Error:
in procedure 'sflash_write_file'
in procedure 'sflash_init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 261
in procedure 'init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 155
in procedure 'ocd_bouncer'
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
embedded:startup.tcl:21: Error:
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
Method #3 - Manual drivers installation following Olimex' user manual (pages 17-20)
- Disconnected debug probe
- Cleaned installed drivers using FTClean with VID/PID 15BA/002A
- Disabled drivers auto-update
- Allowed unsigned drivers install
- Reconnected debug probe
- Reinstalled WinUSB 6.1.7600.16385 with Zadig fr both interfaces, Debug probe in device manager located under 'Universal Serial Bus devices' node
Same results as method #2
I've in task manager that no instance of OpenOCD is running.
Mu quetions are:
1. How to make it to work?
2. Is the debug probe driver set depndant on the platform architecture (i.e. - are there different set-ups for STM32 vs. CY9473907 based platforms) ?
Thanks for any advice as I'm pretty lost here...
Show LessIs there any example code on working with the MPU in the CYW43907? The datasheet documentation mentions 8 different MPU regions.
I have found a weird scenario where string literals used to generate JSON messages became corrupt after many hours of running without error. I am not sure if they are being overwritten in SRAM or what. With normal MCU's constants could not be written to directly but when executing from SRAM with the CYW43907, everything is accessible. The device built correct JSON strings after a power cycle.
Observed behavior
"deviceType": "Sensor", "ype": "555555", "status": "Ok"
Expected behavior
"deviceType": "Sensor", "deviceID": "555555", "status": "Ok",
Show Less
cJSON_AddItemToObject(deviceStatus, "deviceType", cJSON_CreateString("Sensor"));
cJSON_AddItemToObject(deviceStatus, "deviceId", cJSON_CreateString(getID_Str(generalStringBuffer)));
cJSON_AddItemToObject(deviceStatus, "statusCode", cJSON_CreateString(get_StatusStr()));
Hi.
I'm trying to create a VERY SIMPLE app, where a user executes the following steps:
- From mobile or pc the user search for the board AP, finds the WICED and connects to it
- Open a browser types 192.168.0.1 and the browsers displays the wifi config page
- chooses a network, types credentials, submit
- the board connects to the network and saves the wifi profile.
So I tried to find documentation on how this whole Web Server, Wifi onboarding process work in WICED Studio WiFi and I couldn't find any detailed document with the explanation other than go to the examples.
I took the example snip/config_mode. ran it several times and all I get is this:
- The snip builds into the board
- from my laptop, I connect to the AP "WICED Config"
- Go to a browser and configure access to a wifi network.
- I get the IP (192.168.0.19) in the UART, that I double check it is also the one assigned by the wifi router
- I switch to the IP provided.
- web page doesn't load, stays forever and I don't get any feedback in the UART.
Questions:
Is there anything that I'm missing here?
Is there any DETAILED documentation on how the wifi onboarding works?: Something that tells me how to capture errors if I type the wrong credentials, manage different network profiles, stored them, Where are the files to configure the web server, html files (I know they are in resouces/../...). I need guidance on how all those things are wired together.
Starting WICED Wiced_006.004.000.0061
Platform CYW943907AEVAL1F initialised
Started ThreadX v5.8
WICED_core Initialized
Initialising NetX_Duo v5.10_sp3
Creating Packet pools
WLAN MAC Address : C4:AC:59:98:AE:36
WLAN Firmware : wl0: May 2 2019 02:34:15 version 7.15.168.130 (r714231) FWID 01-7fc7cd46
WLAN CLM : API: 12.2 Data: 9.10.74 Compiler: 1.31.3 ClmImport: 1.36.3 Creation: 2019-05-02 02:29:29
IPv4 network ready IP: 192.168.0.1
Setting IPv6 link-local address
IPv6 network ready IP: FE80:0000:0000:0000:C4AC:59FF:FE98:AE36
Joining : intheairhome
Successfully joined : intheairhome
Obtaining IPv4 address via DHCP
L1420 : dhcp_client_init() : DHCP CLIENT hostname = [WICED IP]
IPv4 network ready IP: 192.168.0.19
Setting IPv6 link-local address
IPv6 network ready IP: FE80:0000:0000:0000:C6AC:59FF:FE98:AE36
Application DCT Configuration:
First Name = John
Last Name = Citizen
Address 1 = Level 15
Address 2 = 24 Campbell St
Suburb = Sydney
Country = Australia
Zipcode = 2000
Phone = +612 5555 5555
thanks
Show LessHi
I'm trying to connect my dev kit to WiFi using the WICED SDK wiced_network_up() function and the device gets the error 4
the function gets stuck trying to get an IP address. See stack trace below and configuration.
I know this takes quite some time first time to connect in the network that I'm testing (2.4 GHz). sometimes around 20 to 40 seconds
If I switch to the 5GHz channel the process is successful right away
Is there a way to configure the process to reattempt to get the IP several times or wait longer time before it throws the error?
thanks
Starting WICED Wiced_006.004.000.0061
Platform CYW943907AEVAL1F initialised
Started ThreadX v5.8
WICED_core Initialized
Initialising NetX_Duo v5.10_sp3
Creating Packet pools
WLAN MAC Address : C4:AC:59:98:AE:36
WLAN Firmware : wl0: May 2 2019 02:34:15 version 7.15.168.130 (r714231) FWID 01-7fc7cd46
WLAN CLM : API: 12.2 Data: 9.10.74 Compiler: 1.31.3 ClmImport: 1.36.3 Creation: 2019-05-02 02:29:29
Joining : mynetwork
Failed to join : mynetwork
Joining : mynetwork
Successfully joined : mynetwork
Obtaining IPv4 address via DHCP
L1420 : dhcp_client_init() : DHCP CLIENT hostname = [WICED IP]
Unable to obtain IP address via DHCP
/* This is the default AP the device will connect to (as a client)*/
#define CLIENT_AP_SSID "mynetwork"
#define CLIENT_AP_PASSPHRASE "mynetworkpass"
#define CLIENT_AP_BSS_TYPE WICED_BSS_TYPE_INFRASTRUCTURE
#define CLIENT_AP_SECURITY WICED_SECURITY_WPA2_MIXED_PSK
#define CLIENT_AP_CHANNEL 1
#define CLIENT_AP_BAND WICED_802_11_BAND_2_4GHZ
Show Less// Not sure if he question was posted successfully earlier...
OS: openWrt 19.07
HW: iMX6ull eval board with Laird Sterling-LWB5 module with CYW43353 chip.
The iMX6ull board was modified and device tree (dts) file was updated according to spec from Laird.
When brcmfmac.ko was loaded, it tried to copy the firmware and failed with error -84 (#define EILSEQ 84 /* Illegal byte sequence */)
Below are the console output and debug captures:
Any one knows what caused the issue? and know a way to fix this or something I can look into and try??
Thanks,
- ykuo
+++
...
root@OpenWrt:/lib/modules/4.14.171#
root@OpenWrt:/lib/modules/4.14.171# insmod compat.ko
[ 103.069066] Loading modules backported from Laird Linux version LRD-REL-7.0.0.326-0-gb1ee9b1eb665
[ 103.077972] Backport generated by backports.git v7.0.0.326
root@OpenWrt:/lib/modules/4.14.171#
root@OpenWrt:/lib/modules/4.14.171# insmod cfg80211.ko
root@OpenWrt:/lib/modules/4.14.171#
root@OpenWrt:/lib/modules/4.14.171# insmod brcmutil.ko
root@OpenWrt:/lib/modules/4.14.171#
root@OpenWrt:/lib/modules/4.14.171# insmod brcmfmac.ko
root@OpenWrt:/lib/modules/4.14.171# [ 132.976535] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4339-sdio for chip BCM4339/2
[ 133.019182] brcmfmac: brcmf_sdiod_ramrw: membytes transfer failed
[ 133.025335] brcmfmac: brcmf_sdio_download_code_file: error -84 on writing 570007 membytes at 0x00180000
[ 133.034983] brcmfmac: brcmf_sdio_download_firmware: dongle image file download failed
[ 133.082460] mmc0: Tuning failed, falling back to fixed sampling clock
[ 133.089002] brcmfmac: brcmf_sdio_htclk: Failed access turning clock off: -5
[ 133.097904] brcmfmac: brcmf_sdio_htclk: HT Avail request error: -84
[ 133.178333] mmc0: Tuning failed, falling back to fixed sampling clock
[ 133.224433] mmc0: Tuning failed, falling back to fixed sampling clock
[ 133.270498] mmc0: Tuning failed, falling back to fixed sampling clock
...
root@OpenWrt:/lib/modules/4.14.171# cat /sys/kernel/debug/mmc0/ios
clock: 198000000 Hz
actual clock: 198000000 Hz
vdd: 21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 2 (on)
bus width: 2 (4 bits)
timing spec: 6 (sd uhs SDR104)
signal voltage: 1 (1.80 V)
driver type: 0 (driver type B)
root@OpenWrt:/lib/modules/4.14.171#
root@OpenWrt:/lib/modules/4.14.171#
...
root@OpenWrt:/lib/modules/4.14.171# logread | grep mmc
Tue May 19 22:44:12 2020 kern.notice kernel: [ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk1p2 rootwait rw
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.129491] mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
Tue May 19 22:44:12 2020 kern.warn kernel: [ 1.184880] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
Tue May 19 22:44:12 2020 kern.warn kernel: [ 1.192333] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.198620] mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
Tue May 19 22:44:12 2020 kern.warn kernel: [ 1.225747] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
Tue May 19 22:44:12 2020 kern.warn kernel: [ 1.267032] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.309707] Waiting for root device /dev/mmcblk1p2...
Tue May 19 22:44:12 2020 kern.warn kernel: [ 1.324513] mmc1: host does not support reading read-only switch, assuming write-enable
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.341603] mmc1: new high speed SDHC card at address aaaa
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.348292] mmcblk1: mmc1:aaaa SB32G 29.7 GiB
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.358091] mmcblk1: p1 p2
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.453397] EXT4-fs (mmcblk1p2): recovery complete
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.461049] mmc0: Tuning failed, falling back to fixed sampling clock
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.467619] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
Tue May 19 22:44:12 2020 kern.info kernel: [ 1.493574] mmc0: new ultra high speed SDR104 SDIO card at address 0001
Tue May 19 22:44:12 2020 kern.info kernel: [ 5.447594] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
root@OpenWrt:/lib/modules/4.14.171#
Show LessHello
For a customer project we would like to use the Murata module LBEE5KL1DX-883 with the integrated CYW4343W Bluetooth-WiFi combo chip. As host controller we use an STM32L4S7ZI. Since we need to use the SDIO interface from the micrcontroller for something else, we would like to interface the CYW4343W via SPI.
Can you confirm, that it is possible to control the WiFi part via SPI by pulling "SDIO_DATA_2" pin low?
Thanks for your help.
Show LessHi,
I am new to Cypress development kits, As per our understanding CYW4343 is an integrated combo chip, which supports BLE + WiFi.
And this chip can be access by STM32F4 family.
But we are facing the below issues while working with CYW94343WWCD1_EVB platform.
Issue 1:
We have tried to build the target: CYW94343WWCD1_EVB (Board contains CYW4343W + STM32F4) which is available in WICED Studio 6.4.
Which is not successful and observed the below errors:
Downloading Bootloader ...
Building apps lookup table
**** 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 ...
**** 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. ****
make[1]: *** [FILESYSTEM_IMAGE_DOWNLOAD] Error 127
make[1]: *** Waiting for unfinished jobs....
Downloading resources filesystem ... build/snip.scan-CYW94343WWCD1_EVB-FreeRTOS-LwIP/filesystem.bin at sector 1 size 104...
make: *** [main_app] Error 2
Issue 2:
We tried to build the Demo applications bt_wifi_introduce and wifi_onboarding, but no luck.
Got the following errors.
"Host mode"
./tools/makefiles/wiced_config.mk:433: *** ble_wifi_introducer application does not support CYW94343WWCD1_EVB platform. Stop.
make: *** No rule to make target `build/demo.ble_wifi_introducer-CYW94343WWCD1_EVB-FreeRTOS-LwIP/config.mk', needed by `main_app'. Stop.
Could you please let us know whether CYW4343W have support for WiFi+Bluetooth?
Let us know what are the suitable demo application to start work on WiFi and Bluetooth on CYW94343WWCD1_EVB platform and let us know how to build them.
Show LessThe HTTPS server that is called by the snip.https_server application dies with repetitive client requests.
If you simply build the default application (SDK 6.4), then run it, you will see that the server permanently fails if you send closely-spaced client requests. You can do this by simply making a bookmark to the device URL (e.g., https://192.168.2.157/apps/https_server/https_server_top.html), then clicking on the link in quick succession (e.g., 2 to 5 times/sec). After a few seconds of clicking, the server dies (Firefox indicates no further pages are served).
Note that the function http_server_deferred_connect_callback() still appears to be called, but nothing happens after it is called.
Any help is appreciated.
Thanks!
Show Less