CYW4343X "mfgtest" firmware

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
PhKa_4324871
Level 1
Level 1

Hi,

I'm attempting to get a module using the CYW4343SKUBG configured for regulatory testing using the "wl" utility. I believe the CYW4343SKUBG is considered the 43430A0.

When I attempt to start a continuous transmission using pkteng_start, I get the following error:

[root@alarm user]# ./wl pkteng_start 00:11:22:33:44:55 tx 100 1024 0

./wl: error -23

Here are the driver details:

[root@alarm user]# ./wl ver

1.21 RC0.0

wl0: May 29 2017 00:03:43 version 7.13.53.9 (r664949) FWID 01-130000

From what I've read, this happens because I need to load a special "mfgtest" binary into /lib/firmware/brcm. The only problem is, I can't find the binary specific to the CYW4343X. I tried the 4343WA1-mfgtest.bin from the WICED resources, but it returned the following:

[    2.305745] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430a0-sdio for chip BCM43430/0

[    2.315370] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.txt failed with error -2

[    3.350122] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

[    4.361085] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

Do I have a configuration issue somewhere? Or do I need to obtain a "mfgtest" binary specific to the CYW4343SKUBG?

0 Likes
5 Replies
PriyaM_16
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hello,

Please get in contact with your local point of contact for obtaining the manufacturing firmware.

0 Likes

How do I find my local point of contact?

0 Likes

You might want to start with one of the franchised Distributors in your region: https://www.cypress.com/cypress-franchised-distributors

0 Likes

Alright, I'll give that a try.

Can you confirm I do need to obtain a "mfgtest" binary specific to the CYW4343SKUBG?

I'm confused as to why its not part of the WICED resources.

0 Likes

My understanding is that the same binary will work across all devices supported within the the respective release of the FMAC Linux driver.

The tool is used in conjunction with regulatory, which is pre-defined and provided by many partners, so it's best that customers work closely with the module partner they've selected

0 Likes