Wi-Fi Combo Forum Discussions

Greetings everyone,

Kindly provide me the information whether this chip CYW4343W WiFi + BT Combo Chip has in-built Bluetooth and TCP/IP stacks running in it?

I require a Bluetooth WiFi combo chip for my product which has the host as STM32H7 microcontroller. The host is already loaded and it can't take the network stacks running on it. So I'm searching for a wireless combo chip which can communicate to the host with plug and play communication interfaces (like UART, SDIO etc.).

I'm using this PSoC® 6 WiFi-BT Pioneer Kit (CY8CKIT-062-WiFi-BT) eval kit which has CYW4343W WiFi + BT Combo Chip.

My question is can I use this CYW4343W WiFi + BT Combo Chip is

1. independently programmable?

2. portable with different microcontrollers (just by communicating through UART, SDIO etc.)?

3. whether it can be used as a standalone mcu+wireless module (or dedicated host is required for running network stacks)?

I'm also using a CYW943907AEVAL1F kit which has the chip BCM43907, which is a standalone device. Means it has WiFi module + ARM Cortex-R mcu which runs the network stack by itself. All I need is a UART interface from STM32H7 to communicate.

Whether the same can be achieved with CYW4343W, or it requires some additional load in the STM32H7?

Kindly share your knowledge about this chip.

Any help would be very much appreciated at this stage.

Hello,

How to use the 2Mb of SRAM in CYW43907 application?

I want to store data in SRAM and send later via SPI.

Thanks and Regards,

Sapan Shah

Hi!

I'm working with a development platform containing a 4343W using the Wiced SDK. I'm looking for a list of EAP types supported by the Wi-Fi API, but I cannot find the type of list I'm looking for. Is there documentation on this available?

-Nick

I've programmed the kit as an AP and trying to transmit the data over wireless medium. The data rate I'm looking for is not more than 4 Mbps, however, the link shows 40 kbps only. Detailed problem statement is explained in attached PDF. Kindly help me fix this.

Please let me know if more information is required on the same to fix the issue!

Trying to build "wl tool" in WICED-Studio-6.6 on Linux for CYW954907AEVAL1F.

This thread says: Please contact your module vendor for the wl tool for linux:

https://community.cypress.com/message/247863#247863

The module vendor is Cypress for CYW954907AEVAL1F.

How do I build "wl tool" on Linux?

Thanks and Regards

Hello,

I am using a CYW4343W coupled with an STM32L4A6 and am using the BLE capabilities of the radio.

I have defined my own low power system, which enters SLEEP mode or STOP2 mode depending on what peripherals are currently being used.

I have defined functions that are called from platform_mcu_powersave_enable and platform_mcu_powersave_disable which allows me to know when the app would allow to enter STOP mode.

The system works fine until I integrate the BLE stack with my application. I have noticed from the demo that `BTM_LPM_STATE_LOW_POWER` leads to a call to platform_mcu_powersave_enable, but I am struggling to identify the matching call to platform_mcu_powersave_disable. Can anybody point me to where it is, and how this BTM_LPM_STATE_LOW_POWER works?

Has anybody worked with the STOP mode and Wiced, and knows how to handle this situation?

What I notice is that, after a few minutes, there has been more calls to platform_mcu_powersave_enable than there were calls to platform_mcu_powersave_disable which would make it possible to enter STOP mode when one of my thread required not to (using DMA for instance). The BLE stack appears to be what makes this extra call.

Thanks for your help

i try to download with j-link segger ,but dont work , y download with this in the mark target

project.Set2-CYW954907AEVAL1F JTAG=jlink download run

i change the file wiced_toolchain_common.mk

this is the log:

Creating Filesystem Done

WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:394: recipe for target 'download_dct' failed

make.exe[1]: *** [download_dct] Error 1

make: *** [main_app] Error 2

Makefile:351: recipe for target 'main_app' failed

12:50:06 Build Finished (took 1s.377ms)