Wi-Fi Bluetooth for Linux Forum Discussions

Hi there,

We are trying to fcc wifi certify our project which uses a custom buildroot toolchain and arm processor.

We need help to compile the wl_tool so we can proceed with certification, but we need it to be cross compiled for our architecture (arm 32bit).

Can I ask a representative to help us to compile it with our custom toolchain? 

CPU Info:

• armv7l
• little-endian
• hard-float ABI
• neon/vfpv4

Custom Toolchain Instructions:

• download toolchain
• extract toolchain:
  tar jxf  arm-co6-linux-uclibcgnueabihf_sdk-buildroot_2021.02.1.tar.xz
• cd to arm-co6-linux-uclibcgnueabihf_sdk-buildroot
• ./relocate_sdk.sh
• add toolchain into path e.g.
  export PATH="$PATH:$PWD/usr/bin"
• Set cross compile variables:
  export ARCH=arm
  export CROSS_COMPILE=arm-co6-linux-uclibcgnueabihf-

Tagging @VinayakS_26 / @raks_99 / @DoubleLo as I found they have helped another customer to do this.

Hi,

Does the CYW4373 FW included in this package contain a FragAttacks fix?

https://community.infineon.com/t5/Resource-Library/Infineon-Android-Release-2021-06-29/ta-p/281512

Best Regards,

Hi,

We working with Qualcomm SA-8155P on Android 12 (Android S), we found that CYW89072BRFB5GT drivers are required to bring up Bluetooth.

We are using MSM-5.4 kernel + Android 12. Could you please provide the following details?.

1. driver source code.
2. Android HAL code for BT.

We have received the firmware (BCM20703A1_001.001.005.0433.0000_01_Aptiv_IHU42_TEST_ONLY.hcd)for testing the integration. But Driver and HAL code is not shared.

Thanks.
Br,
Aravind

Hello,

We are in the first stages of development of a hotspot wifi transmitter. In order to allow Android devices to connect to it via wifi P2P and iOS devices via a classic wifi AP simultaneously, we guess that the best way to achieve that is to configure a concurrent mode AP + P2P-GO on the computer board.

We tried to configure it on a Raspberry Pi 4 but iw list command return

   valid interface combinations:
         * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
           total <= 3, #channels <= 2
         * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
           total <= 4, #channels <= 1

which made it clear that the combination is not possible.

So we are looking for a computer built on iMX8M like this one https://www.compulab.com/products/sbcs/sbc-imx8m-mini-nxp-i-mx8m-mini-single-board-computer/#overview

Is the combination interface AP + P2P-GO a valid interface for the BCM43353 wifi chipset inside ?

Hi, I've looked all around this site and seen that to request the mfg firmware I would need to open a MyCases technical support case and request it there. I cannot do this because there is no option to create a technical support case so I am requesting a link to the mfg firmware.

The output of uname -a is:

Linux raspberrypi 5.10.74-v8+ #1 SMP PREEMPT Tue Oct 19 00:20:12 EDT 2021 aarch64 GNU/Linux

the output of sudo ./wl ver is:

./wl: /lib/aarch64-linux-gnu/libnl-3.so.200: no version information available (required by ./wl)
./wl: /lib/aarch64-linux-gnu/libnl-genl-3.so.200: no version information available (required by ./wl)
1.28 RC0.0
wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e

the output of sudo ./wl tsf (and various other commands) is:

./wl: /lib/aarch64-linux-gnu/libnl-3.so.200: no version information available (required by ./wl)
./wl: /lib/aarch64-linux-gnu/libnl-genl-3.so.200: no version information available (required by ./wl)
./wl: error -23

@raks_99 Please respond ASAP, thank you!

There is an interesting issue we are running into with the Laird LWB module that has the CYW4343W on it. On some boards the wifi module does not get recognized in Linux issuing a "mmc1: error -110 whilst initialising SDIO card", the processor we are integrating with is an OMAP4.

During initialization the OMAP4 is sending the same data on the CMD line at 400kHz. The only difference is the response to the CMD5 command. On good boards the LWB module responds with the expected response format and the I/O OCR bits are set to 111111111111111100000000, signaling a voltage range of 2.0-3.6V. On boards that the WIFI fails to initialize on we get 11111111000000000000000, which signals a voltage range of 2.7V to 3.6V. 

Currently our VDD_IO on the Laird LWB is set to 1.8V and the VBAT is 3.3V. WL_REG_ON is high at 1.8V. 

Is there a reason for this difference in response? It seems this is the first command that the LWB module responds to and they are different between boards. Which is seemingly causing one to initialize correctly and the other to consistently fail. At this point it looks like the data being sent by the processor isn't different, only the responses from the CYM4343W.

Roam prof command on Embedded Artists board is not working/not supported:

fw version is : wl0: May 22 2020 21:24:34 version 7.45.214 (9c83742 CY) FWID 01-59feefd4.

The firmware which we have on our device is from yocto-release for embedded artists board. This is the repo  : git://github.com/murata-wireless which is used in manifest file for meta-murata-wireless layer.

root@imx7ulpea-ucom:/etc/wpa_supplicant# wl roam_prof b 0 -65 -100 10, -65 20 10 120 20 1 100                                                                                                                    

Unable to get wlc_ver iovar -45.

I'm getting this error.  

Best regards,

Tijana