AIROC™ Wi-Fi MCUs Forum Discussions

The datasheet CYW43455 Single-Chip 5G WiFi IEEE 802.11n/ac MAC/Baseband/ Radio with Integrated Bluetooth 5.0 Datasheet  states in subsection "8.6 JTAG/SWD Interface" that the CYW43455 supports:
- IEEE 1149.1 JTAG boundary scan
- reduced pin-count Serial Wire Debug (SWD)
- access the chip’s internal blocks and backplane
It further mentions that there are "[...] proprietary debug and characterization test tools [...]", that "The debug access port (DAP) embedded in the ARM processor supports both SWD and JTAG interfaces and can be switched from one to the other through a specific sequence on the TMS/SWD lines.", and that "[...] the DAP allows access to test access points (TAPs) in the CYW43455 for hardware debugging.".

I have a Embedded Artists 1MW M.2 Module. According to EA’s datasheet, the JTAG interface can be enabled and used "[...] for debugging the internal firmware [...]". They also tell here "[...] that the debug interfaces are not always openly documented. Support from Murata, NXP and/or Cypress is likely to be needed to utilize the features." I was hoping to find more about this on Murata’s product page and linked documents, but they do not provide more than can be found in the CYW43455 datasheet.

I would like to know more about those advertised capabilities and mentioned proprietary tools.
Can you provide me with some more details here? E.g. is there a BSDL file describing the JTAG, what is this specific sequence to switch between SWD and JTAG, where can I get the proprietary tools, what TAPs can be accessed...

CYW43455 

The SlotTime defined 20 micro-second in IEEE802.11b. I want to change the parameter , because of I want to do long-distance communication with two CYW5557x. One is operated AP-mode, and the other STA mode. Where can I change the SlotTime from 20 us to  40 us ?  Does it have maximum limit?      

Hello Infineon Community,

I hope this message finds you well. I'm currently facing an issue with the Wi-Fi_MQTT_Client example on the PSoC6 board, and I'm seeking assistance to resolve it.

I've followed the example steps, including generating client.key, client.crt, and other required configurations. The Wi-Fi connection is successful, but when attempting to connect to the MQTT broker (test.mosquitto.org), I encounter the following error:

`MQTT connection failed with error code 0x8060009.`

I have verified the correctness of certificates, key files, and other configurations. The Wi-Fi connection is established without issues.

If anyone has experience with this particular error code or has insights into common pitfalls with the Wi-Fi_MQTT_Client example, I would greatly appreciate your guidance. Is there anything specific I should check or any additional troubleshooting steps I should take?

Thank you in advance for your help!

Best regards,😊

hi Sir

May I know how to enable 11r function with combo chip ?

we did test CYW43455/CYW55571/CYW4373 , there are no any 11r packet can be found . 

neither "mobility domain " or "fast  BSS transition " are not in the sniffer packet. 

what should I do to enable it ?

Hi Team,

I found the failure of sample code in STM32 expansion Pack on Murata Type1LV(CYW43012) by debugger.
But this failure is not found when the application is execute stand alone.
Please let me know the cause of this issue.

Failure message is following and attachment file.
"Interface is not up/NULL and failed in function whd_deinit at line 193
Filed to initialize Wi-Fi"

The emvironment information is following.
- Wifi module: Murata Type1LV (CYW43012)
- Evaluation board: STM32H747 DISCO Kit, muRata uSD-M2 Adapter Kit (rev B1), Embedded Artists 1LV M.2 Module
- Sample code: wifi_scan in STM32 expansion Pack 1.5.1

Best Regards,
Tsutsumi

Hi ,

We are using CYW43455 chip so it switches from Fast Power Save to Power Save mode and vice-versa (wl PM 2 <-> wl PM 1).
The device we are working on is battery powered so we are trying to reduce power consumption as much as we can.

However, although we are not seeing any obvious network traffic problem, our log is full of following messages:

brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110

We have also tried to reduce SDIO clock frequency  by using SDR50 mode instead of SDR104:

mmc1: new ultra high speed SDR50 SDIO card at address

Unfortunately the error  logs are still there.

We are using  Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2.

We are also using https://github.com/murata-wireless/meta-murata-wireless , hash f8724cf98c2d07881c9abb9dac01c0f65d3758d0.

Anyone know what might cause the issue ?

Best regards,

Bogdan

Hi Infineon,

                Can you share the CYW54907 WiFi throughput test value?

Our customer would like to know the WiFi throughput values (max.) of CYW54907 when measured in RF box with no interference, thanks.

We have our first own hardware with CYW954907 in our hands and have started the Hardware Bring-Up which means that we check the basic functionality of all the devices and chips on the board.

We use the same Murata Wifi Module that cypress used on the CYW954907AEVAL1F Evalboard.

We also have external QSPI flash like they have on the on the CYW954907 Evalboard.

We have already checked that all power supply rails are good (also power supply of the CYW954907.

Now we need support in how to verify that the CYW954907 is operable.

We have tried to talk to the chip with the WICED IDE but haven't been successful. There is no response.

We have UART and JTAG accessible on pin headers.

We use an external 4-channel converter board with FTDI FT4232HL that converts the UART to an VCOM port on USB.

The plan is to run the scan snip example that runs fine on the Evalboard on our custom Hardware to prove that it is functional.

So we copied the project and applied patches from Murata that they claimed are necessary.

But the patches did not help with getting the connection up and running.

Some basic questions:

Is the WICED IDE the right tool to connect to a virgin device ?

How does the connection look like. Do we need both UART and JTAG on a USB port for the WICED IDE to work ?

When do we use the UART ? (When) do we use JTAG ?

What are the prerequisites for the device to start up ? Is there a ROM boot loader with boot options ?

Does the WICED-IDE expect to see exactly the WICED-USB devices that the device manager shows when the Evalboard is attached ?

How can we direct the WICED-IDE to use one of the “normal” VCOM COM ports that our 4-channel UART2USB converter offers ?

Can someone please give me some instructions and insight on how to connect to our custom hardware and verify the basic functionality.

Any help would be highly appreciated