Wi-Fi Combo Forum Discussions
Hi Guys,
Does CYW43907 support 3 wire Legacy coexistence protocol? I found an application note (AN214852) which mentions that CY43XXX does support Co-existence. But, the Data sheet for CYW43907 does not have any information on 3-wire co-existence support. I need to interface CYW43907 with external 3rd party ZIgbee chip. Please confirm if this is possible and provide any additional info.
Thanks & Regards,
Sandeep
Show LessHello,
I'm trying the snip.sd_filesystem application in Wiced Studio with the CYW43907 eval board and a 2GB SD Card.
In the sd_filesystem.mk makefile I have enabled FileX and exFAT support, as follows:
# for SD/MMC card support
WICED_SDMMC_SUPPORT := yes
USING_FILEX := yes
# default stack size was WICED_DEFAULT_APPLICATION_STACK_SIZE, 6K
# needs big stack size for deep directory processing
GLOBAL_DEFINES += APPLICATION_STACK_SIZE=1024*256
# enable FileX exFAT
GLOBAL_DEFINES += FX_ENABLE_EXFAT
$(NAME)_COMPONENTS := filesystems/FileX
However, the system always fails to mount the filesystem, regardless if the scared is formatted as exFAT or FAT16/32.
If I comment out the FX_ENABLE_EXFAT constant and format the sdcard as FAT16/32, the snip application works as expected.
So, the exFAT support seems not to be working. Is there anything else to do to enable the exFAT support with FileX?
I know that FAT32 is more than enough for a 2GB sdcard, but I'd like to understand if the system can really work with exFAT or not.
Thank you for the assistance.
Show LessSDK being used - 6.0
So I'm trying to use OTA2 on the quicksilver arrow platform (cyw43907 based). I added the platform files to WICED, added the platform as valid for the ota2 bootloader and failsafe, and built the OTA2 example code and it works flawlessly. However when I try to download the ota2 image file (snip.scan, built with make target snip.scan-QuicksilverEval ota2_image) the ota2 code reports that the platform in the header isn't correct. heres the log output:
0273 00:10:45.458 wiced_ota2_image_validate() OTA Image Platform type fail. CYW943907AEVAL1F.B1 != QuicksilverE val
0274 00:10:45.467 wiced_ota2_write() wiced_ota2_update_staged_header() OTA image not supported!
0276 00:10:45.578 OTA header Information: OTA Image Header after Updating OTAImage header:
0277 00:10:45.585 ota_version: 1
0278 00:10:45.589 software_major: 0
0279 00:10:45.592 software_minor: 0
0280 00:10:45.596 platform: CYW943907AEVAL1F.B1
0281 00:10:45.601 status: 0 (invalid)
0282 00:10:45.606 bytes_received: 1215
0283 00:10:45.609 header_crc: 0x1acf1f42
0284 00:10:45.614 magic_string: OTAimage
0285 00:10:45.618 sign_type: 0
0286 00:10:45.622 secure_signature: TODO
0287 00:10:45.626 image_size: 937984
0288 00:10:45.630 component_count: 5
0289 00:10:45.633 data start offset: 4096
0290 00:10:45.637 ota2_get_OTA() FAILED 0 < 937984!
0291 00:10:45.642
ota2_get_OTA_file() Exiting 4
What do I need to change (not including updating the WICED version) to ensure that the ota2 header is written with the proper platform?
Show LessI am trying wifi roaming function on cyw43340.
As we konw,when roaming works,it will scan channels.
I want to konw which channels will be scaned and can I set up these channels?
Show Less
I have installed WICED-Studio-6.2.1.2-IDE.
In 43xxx_Wi-Fi project LwIP present is of Version 2.0.3
I am seeing that changes are done in WICED LwIP 2.0.3 to support wi-fi drivers.
Now, I have to upgrade this 2.0.3 WICED LwIP to 2.1.2 LwIP.
How I can accomplish this job so that there will be no impact on wi-fi drivers.
Any help or suggestion is appreciated.
I know the CYW43907 has 8KB of AON memory. It looks like the tiny bootloader resides in this area and the binary is 4.76 KB. Is the remaining space available for my application to store information across a SW reset or is some of the space allocated for other uses?
Show LessI'm trying to get 2 dev boards working together. I have the CYW493907AEVAL1F along with the CYBT-353027-EVAL This is a cyw43907 wifi chip with a 20707 bt chip. I am trying to get the wifi chip to connec to the hci interface of the bt dev board. So far I haven't had any luck. I am tried to just use the CYW943907WAE3 platform since it is very similar to what I am trying to do. I also have a Murata1QP board which is a single module that uses the same parts. I have tried using that platform file as well with no luck. I am not getting any communication out of uart0. I have been trying to run the ibeacon demo.
I am working on a proof of concept using the devboards, but will be spinning a board shortly. Should I be making my own platform files?
I have the following connections
cyw43907eval cybt353027eval
UART0_RXD_IN J6:18 BT_UART_TXD HCI J1:4
UART0_TXD_OUT J6:20 BT_UART_RXD HCI J1:3
UART0_CTS_IN J6:22 BT_UART_RTS HCI J1:6
UART0_RTS_OUT J6:24 BT_UART_CTS HCI J1:5
RF_SW_CTRL_8 J6:38 GCI_SeCI_IN GPIO6
RF_SW_CTRL_9 J6:39 GCI_SECI_OUT GPIO5
I also tried connecting the rest, host wake and device wake pins as described in the platform.c file
Show LessI have seen in section "7.1 WLAN CPU and Memory Subsystem" in the datasheet https://www.cypress.com/file/297991/download for CYW43362 that there is an integrated ARM Cortex-M3 processor with internal RAM and ROM. what is this processor used for? can I use it to design program? and how to program.
Show LessI have been seeing association issues in our test setup of 100 devices with ubiquiti AP's that use client steering algorithms to balance clients across AP's. We have around two or 3 AP's in the area of the clients but a third of the clients struggle to associate if all are reset at one time, ie OTA update. I am thinking the join behavior hits the closet AP, association fails, and then on the retries it hits the same AP. This behavior appears to be in the WLAN driver and not in WWD/WICED. Is there any way to improve this or at least test for it, short of writing a custom scan and associate function (wouldn't help with roaming and I do not think i would have feedback of association response codes)?
Referencing this site: Client Balancing - Cisco Meraki , client balancing works by either the AP rejecting the association with a response code 17 OR by using 802.11v - BSS-TM to push the client to an AP.
Device: CYW43907
SDK 6.2
Show Less