How to Use wl in WLTEST Mode

[JaPe_4538256]

I have a microcomputer running an embedded version of Linux 4.1.15-2.0.1. How do I use the wl utility in WLTEST mode?

Here's where I'm at right now:

root@XXXXXXXX:~# wl ver

1.107 RC5.0

wl0: Dec 29 2015 15:56:15 version 7.45.41.24 (r608913) FWID 01-4e412465

root@XXXXXXXX:~# ls /lib/firmware/bcm/

BCM43430A1.1DX.hcd     bcmdhd.cal             fw_bcmdhd.bin          fw_bcmdhd_apsta.bin    fw_bcmdhd_mfgtest.bin

root@XXXXXXXX:~#

What should I do next?

-Jason

[Zhengbao_Zhang]

wl0: Dec 29 2015 15:56:15 version 7.45.41.24 (r608913) FWID 01-4e412465

This is a normal firmware, you need to get a MFG firmware, then try to do the tests.

[JaPe_4538256]

root@XXXXXXXX:~# ls /lib/firmware/bcm/

BCM43430A1.1DX.hcd     bcmdhd.cal             fw_bcmdhd.bin          fw_bcmdhd_apsta.bin    fw_bcmdhd_mfgtest.bin

root@XXXXXXXX:~#

As the above output indicates, I have fw_bcmdhd_mfgtest.bin. Is this the MFG firmware that you mentioned? If so, how do I use it?

[MichaelF_56]

Which of our module partners are you engaged with?  The module partner typically provides MFG_TEST firmware.

A list of our partners is here: IoT Solutions Guide​

[Zhengbao_Zhang · Accepted solution]

Need two steps:

1. cp  fw_bcmdhd.bin fw_bcmdhd_bak.bin

2. cp fw_bcmdhd_mfgtest.bin fw_bcmdhd.bin

then reboot, input "wl ver"  to check the returns.

[JaPe_4538256]

I did those two steps, rebooted, and entered "wl ver", but it appears to hang the system. No output results from the command and the command prompt does not reappear.

[Zhengbao_Zhang]

please use this one for a test to see if it can visited by wl tool.

[JaPe_4538256]

I copied the 43438A1-mfgtest.bin file onto fw_bcmdhd.bin, rebooted, and entered "wl ver", but I got the same result as when I followed your previous instructions. The "wl ver" command appears to hang the system, no output results from the command, and the command prompt does not reappear.

[Zhengbao_Zhang]

Actually, I don't know why , Normally if normal firmware could run well in the platform, if we switched to the mfg firmware with same version, it had no errors.  

[JaPe_4538256]

That makes sense to me, that if normal firmware of a certain version works on a platform, then the mfg firmware of that same version should also work on the same platform. However, I don't know if my /lib/firmware/bcm/fw_bcmdhd.bin is the same version as the 43438A1-mfgtest.bin file that you provided me.

I opened up my /lib/firmware/bcm/fw_bcmdhd.bin file in a text editor and found this string just before the end of it:

43430a1-roml/sdio-g-p2p-pool-pno-pktfilter-keepalive-aoe-mchan-tdls-proptxstatus-ampduhostreorder-lpc-sr Version: 7.45.41.24 CRC: 3451af24 Date: Tue 2015-12-29 15:58:03 PST Ucode Ver: 1043.2060 FWID: 01-4e412465

Then I opened up the 43438A1-mfgtest.bin file that you gave me and I found this string near the end of it:

43430a1-roml/sdio-g-mfgtest-seqcmds-swdiv-srfast-fuart Version: 7.45.98.18 CRC: 94c41b3 Date: Thu 2017-04-27 03:05:53 PDT Ucode Ver: 1043.2089 FWID: 01-ad1b7958

Notice that the strings both start with '43430a1.' Does this mean that they are the same version and that if one works on a certain platform, then they should both work?

If it helps at all, our module model number is 'LBEE5KL1DX.' This page says that our module has a Cypress chipset called 'CYW4343W.'

[Zhengbao_Zhang]

hello:

    I want to know whether the firmware we provided is fine for the test,  if still have problem I suggest you to raise help to  LBEE5KL1DX to see if they have confirmed MFG image which was used on your microprocessor platform,  sometimes we need to do some changing on firmware to match host setting.