Wi-Fi Bluetooth for Linux Forum Discussions
text.format{('custom.tabs.no.results')}
Package Version
ahd-2023_1221
Release Date
2023-12-21
Description
Infineon Android release for the broad market.
This release has been qualified on IMX8 SDIO platform and Hikey960 PCIE platform running Android 13.
Customers wishing to leverage the Android Open Source Platform now have an out of the box Android solution for Infineon's connectivity parts.
The release package includes:
* ahd
* 4373-Android13-SDIO
*43012-Android13-SDIO
*43022-Android13-SDIO
*54591-Android13-PCIE
*55572-Android13-SDIO
*AHDBinaries
*device
*firmware
*nvram
* Android13_55572_SDIO_Release_Notes.pdf
* Infineon_55572_Wi-Fi_6_6E_User_Guide.pdf
* confs
* hostapd_supplicant_src
* Android13_PCIE_Bringup.pdf
* Android13_SDIO_Bringup.pdf
* Android13_Feature_Bringup.pdf
Test Environment:
* IMX8 SDIO setup
* Hikey960 PCIE setup
* 55572, 43012, 43022, 54591 and 4373 Sanity, 6G and 11ax features (55572), WOWL via OOB(55572)
and PNO scan offload(55572, 43022)
Show LessDescription
The package contains all the required files (including AIROC™ Bluetooth® stack for ARMv8 Linux, Bluetooth® porting layer, and sample code examples of Bluetooth® profiles) to evaluate and test Bluetooth® Classic and Low Energy on AIROC™ combo chip (CYW4373, CYW43439, CYW55573/2/1).
What's new?
Package comes with codes examples to demonstrate Bluetooth LE Audio capability of CYW55573/2/1 in hosted mode. The code example demonstrates Bluetooth® LE Audio unicast and broadcast functionality.
Functions include:
- Broadcast audio stream scanning
- Receiving broadcast audio stream
- Unicast audio stream establishment
- Unicast audio stream release
- Unicast sink connect to source (1 CIG, 1 CIS)
Bluetooth® Linux Code Examples & Supported Chip
Code example |
Feature demonstration |
Supported chip |
LE Audio CIS Source |
Implements the Unicast Source application using BTSTACK and LE-Audio profile library |
CYW55573/CYW55572/CYW55571 |
LE Audio CIS Sink |
Implements the Unicast Sink application using BTSTACK and LE-Audio profile library |
CYW55573/CYW55572/CYW55571 |
LE Audio BIS Source |
Demonstrates the ability of LE Audio broadcast |
CYW55573/CYW55572/CYW55571 |
LE Audio BIS Sink |
Demonstrates the ability to receive LE Audio broadcast |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® Find me |
Demonstrates the Find Me profile which defines the behavior when a button is pressed on one device to cause an alerting signal on a peer device |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® hello sensor |
Demonstrates GATT database and device configuration initialization, sending data to the client and processing write requests from the client |
CYW55573/CYW55572/CYW55571 CYW43439,CYW4373 |
Linux Bluetooth® Wi-Fi onboarding |
Demonstrates the feature that enables devices to connect to a Wi-Fi access point without requiring a physical interface |
CYW55573/CYW55572/CYW55571 CYW43439,CYW4373 |
Linux Bluetooth® Headset |
Multiple profile code example that demonstrates the use cases and ability of audio-related functions such as A2DP, AVRCP CT, and HFP |
CYW55573/CYW55572/CYW55571 |
Linux Bluetooth® SPP |
Demonstrates how two devices can establish a wireless communication link that emulates a traditional serial port connection |
CYW43439,CYW4373 |
Package GitHub link: https://github.com/Infineon/ifx-linux-bluetooth
Release notes
Please go through the attached released notes for more details on the package.
Show Lessv5.15.58-2024_0118
Release Date
2024-01-18
Github Link
V5.15.58 backport package: Link
V6.1.19 patch: link
Description
This is Cypress's Linux brcmfmac driver and firmware support package.
Brcmfmac is an open-source driver project.
Files in this release:
Part 1: cypress-fmac-v5.15.58-2023_1128.zip
* Backports package (cypress-backports-v5.15.58-2023_1128-module-src.tar.gz)
* Firmware/clm_blob files (cypress-firmware-v5.15.58-2023_1128.tar.gz)
* Cypress fmac patch files (cypress-patch-v5.15.58-2023_1128.tar.gz)
* Device tree files (cypress-devicetree-2023-11-28.tar.gz)
* hostapd/wpa_supplicant patch (cypress-hostap_2_10-2023_1128.tar.gz)
* Cypress customer patch (cypress-custom-patch-5.4.21.tar.gz)
* Cirrent Agent (cypress-cirrent-1.60.tar.gz)
* Documents (docs/)
* README
Part 2: cypress-patch-v6.1.19-2023_1128.zip
* Cypress fmac patch files for Vanilla v6.1.19(cypress-patch-v6.1.19-2023_1128.tar.gz)
* Infineon-Vanilla-Kernel-v6.1.19-Bring-up-Reference_20201221.pdf
Checksum
cypress-fmac-v5.15.58-2023_1128 sha256sum:
990b5f6beeb9530525f254977569fd25936e09f9ef1bf36ca52118e73dff3e68 cypress-backports-v5.15.58-2023_1128-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55 cypress-cirrent-1.60.tar.gz
0c8da2efe289115f2242aa3f69de5bc616cb893ecd411e11194c4c008418bb2e cypress-custom-patch-5.4.21.tar.gz
c38cca05bb05db6198af7809c7a2e519cb33a06b02ebd4d626588c9038f7259b cypress-devicetree-2023-11-28.tar.gz
92608ceb4509cc02730833ce2119662b3c116a3956ca303245e97378186dc2a3 cypress-firmware-v5.15.58-2023_1128.tar.gz
771099830bd106307e77ebdd4d27a3e18de27bb60889c4db4bca81f44ade495d cypress-hostap_2_10-2023_1128.tar.gz
8fe7d8b677032fb04374615aae27c5a3131499956dc22ddb420847a3876974c6 cypress-patch-v5.15.58-2023_1128.tar.gz
cypress-patch-v6.1.19-2023_1128 sha256sum:
933ac3a50f0146b4078beb5e398c75a93ab0a1979a93d120a1c0ba2a06ab0ff7 Infineon-Kernel-v6.1.19-Bring-up-Reference.pdf
ac23fabed00e5c5ab0c3720fa0eb6fa135a589e009714f783701fe557abe3fe7 v6.1.19-2023_1128.tar.gz
Part 3: cypress-fmac-v5.15.58-2024_0118.zip
8ccbebf31bf69c85dc7d05fb7e3597fa282c3ba5373d76b2a65364191abb14d0 cypress-backports-v5.15.58-2024_0118-module-src.tar.gz
ce3bb31020e5ffe24fe549802440c137d14a05ad77af3e8e1fb9e184db96ed55 cypress-cirrent-1.60.tar.gz
92e7196a896fa65138c8297d4202a1811564605360f807faa2c8af310eddeb2e cypress-custom-patch-5.4.21.tar.gz
40dd314cee28149028a2d524ccd5d25f20336c7314e1e26654daecf4c9a796d2 cypress-devicetree-2024-01-18.tar.gz
739d1fae54d885e136847af2957821324c18c68622f204992e268b991172da53 cypress-firmware-2024_0118.tar.gz
2a411fb64818b054498645f64e3ef3b29e4db9a36b65987d9a3af76c2d60f765 cypress-hostap_2_10-2024_0118.tar.gz
8e43bc4487c5d4e77880e2fc9d3152a011063c5b0f3871e277561f0108a88304 cypress-patch-v5.15.58-2024_0118.tar.gz
[Change Log]
2023-12-18 Initial Post
2023-12-22 Add cypress-patch-v6.1.19 to support build brcmfmac on 6.1.19
2024-01-18 Fix for system crash post suspend and resume with CYW55572/55573 [PCIe]
The BT assets of AIROC Bluetooth Stack (Linux) Release are all on GitHub now.
Description:
AIROC Bluetooth Stack is Infineon's Bluetooth Host Protocol Stack implementation. The stack is optimized to work with Infineon Bluetooth controllers. The BTSTACK supports Bluetooth BR/EDR and BLE core protocols. This page provides the Github links to get started with application developments in Linux platform using AIROC Bluetooth Stack.
Please find the code examples :
Code Examples:
https://github.com/Infineon/linux-example-btstack-wifi-onboarding
https://github.com/Infineon/linux-example-btstack-wakeonle
https://github.com/Infineon/linux-example-btstack-bas
https://github.com/Infineon/linux-example-btstack-hello-sensor
https://github.com/Infineon/linux-example-btstack-alert-client
https://github.com/Infineon/linux-example-btstack-alert-server
https://github.com/Infineon/linux-example-btstack-headset
https://github.com/Infineon/linux-example-btstack-a2dp-source
https://github.com/Infineon/linux-example-btstack-a2dp-sink
https://github.com/Infineon/linux-example-btstack-spp
https://github.com/Infineon/linux-example-btstack-handsfree-unit
https://github.com/Infineon/linux-example-btstack-handsfree-ag
Show Less
The latest Infineon Linux Wi-Fi driver (FMAC) release can be accessed here:
Sr. No. | Driver release name | Release link |
1 | Backports v5.15.58-2023_1128 |
Public forum link: https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2023-11-28/td-p/662238 |
2 | 6.1 Latest kernel for RPI : RPI-6.1.21 IFXFMAC |
Github: https://github.com/Infineon/rpi-linux-kernel/releases/tag/6.1.21-hedorah-IFXFMAC-20231128 |
3 | 6.1 Kernel on BRCMFMAC |
Github: https://github.com/Infineon/ifx-wireless-drivers/tree/RTM/v6.1.19-hedorah |
Documentation is available in docs folder of cypress-fmac-v5.15.58-2023_1128.zip available at this link https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2023-11-28/td-p/662238
The older/archived Wi-Fi driver releases can be accessed here:
Show Less
Package Version
ahd-2022_1223
Release Date
2023-01-03
Description
Cypress Android release for the broad market.
This release has been qualified on Hikey 960 platform.
Customers wishing to leverage the Android Open Source Platform now have an out of the box Android solution for Cypress's connectivity parts.
The release package includes:
* ahd
* device
*hikey960
* firmware
* nvram
* 55572_AndroidBringup.pdf
Test Environment:
* Hikey 960
* 55572 Sanity and VTS
Change Log
[2022-12-23]
* Initial post
Show LessHi 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.
Show Less
Hi,
I am having trouble strating the bluetooth module on my board using a BCM4345C5 chip for bluetooth. The chip uses HCI UART interface and PCM interface for audio data.
I have successed running a program test that ensures that HCI UART interface works fine. But when I try the BSA server with this command : bsa_server -d /dev/ttyS0 -r 14 -p /firmware/BCM4345C5_003.006.006.0058.0135.hcd -u /var/run/
where :
d specifies the device, r specifies the baudrate and 14 stands for 3M (3MBits I suppose), p specifies the Bluetooth firmware and -u specifies the location of the generated Bluetooth node.
What I am getting :
First time, the run gets stuck here (after GKI timer has been disabled):
I cancelled the run and tried executing it again and this time I got this error :
Can anyone help with this please? I can give more info if needed!
@CarlosTirado @MichaelF_56 @GregG_16 @Chi-HsienL_21
Regards,
Honoré
Show Lesswithin wifi driver v5.4.18-backports/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c L898:
static void brcmf_sdiod_host_fixup(struct mmc_host *host)
{
/* runtime-pm powers off the device */
pm_runtime_forbid(host->parent);
/* avoid removal detection upon resume */
host->caps |= MMC_CAP_NONREMOVABLE;
}
Will it cause serious problems if I comment out this line of code?
In my suituation, there is a hotplug sdio wifi card insert to a SD Slot with card detect function.
Show Less
Hello Team,
My company is using LBEE5HY1MW in our product. According to the datasheet its support Bluetooth 5.0, However, the LMP version I read through hcitool is 4.1.
I would like to know, does the chip also supports the BLE security as specified in Bluetooth core specification 4.2?
Or does it support any of the Bluetooth 4.2 Core specifications?
The 1MW module in our product is involved in security-related compliance.
Any help is really appreciated.
Thanks,
Asma
Show LessAlthough document cypress-fmac-v5.4.18-2021_0527/README and cypress-fmac-v5.4.18-2021_0527/docs/Infineon_Wi-Fi_Software_UserGuide.pdf does not metioned it, but i really wana to known when this CONFIG_MAC80211 option be used?
This description doesn't make me clear:
CONFIG_MAC80211:
This option enables the hardware independent IEEE 802.11 networking stack.
Hi, I am having trouble programming the OTP memory on the CYW43364 (Murata 1FX). When I run cisdump, I get the following error:
# wl cisdump
Failed cisdump request: -45
wl: error -23
As I understand it, error 23 is BCME_UNSUPPORTED and indicates that the firmware does not support the operation. I also tried the sd_cis, nvram_dump, and otpdump commands with the same results. I am using the latest firmware as of today:
# wl ver
1.28 RC0.0
wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766
Do I need a special firmware which supports the above commands?
Additionally, I read through several application notes, and I was unable to determine what the hardware header for CYW43364 should be. I noticed several variations in which header to use, depending on the exact chipset. What should the hardware header be?
Show LessI can't find any nvram(parameters) file in cypress-fmac-v5.4.18-2021_0527.zip 's firmware directory, which downloaded form https://www.cypress.com/documentation/software-and-drivers-archive/wifi-bt-linux-archive.
I also notice AN232689 ( Wi-Fi software user guide) says:
NVRAM parameters might be included in the firmware image. Do a strings command in /lib/firmware/cypress/cyfmac43430-sdio.bin to check if the nvram parameters are included in the tail of
firmware image.
aw-nm372sm/firmware$ strings cyfmac43430-sdio.bin
this command output a lot of strings, how to check whether nvram is included in firmware image.
if NVRAM parameters already included in the firmware image, Why the brcmfmac driver still look for the corresponding nvram file ? look like:
"brcmfmac: brcmf_fw_request_firmware: no board-specific nvram available (err=-2), device will use cypress/cyfmac43430-sdio.txt"
if NVRAM parameters not included in the firmware image, , how to get one?
Show LessThe driver at https://www.cypress.com/documentation/software-and-drivers-archive/wifi-bt-linux-archive, is too new for me .
How can i find one suitable for linux kernel 3.10.
Any help is greatly appreciated
Show LessI face a issue about ‘HT Avail timeout’, which lead to exit the wifi driver probe.
I find servel related subject about this. But no one confirm the exact root cause of the issue. Some people say that the isuue is related to LPO_IN, which must be supplied with a 32.768KHz clock.
I search info about CYW43438's LPO and find that LPO is only a option iteam.
The AW-NM372SM uses an internal 26MHz xtal for normal operation and an external secondary low frequency clock for low-power-mode timing. Either the internal low-precision LPO or an external 32.768 kHz precision oscillator is required.
In my design, 32.768KHz clock is not supplied to LPO_IN. Can someone tell me if the issue is caused by this reason? or there are other reasons?
Is there any way to make the wifi module work normally without connecting the 32.768kHz LPO input?
Any help is appreciated.
Here is my wifi log:
[ 101.970000] Loading modules backported from Linux version v5.4.18-2021_0527-0-gc6ec8acef0b8
[ 102.000000] Backport generated by backports.git v5.4.27-1-0-gf6e8852f
[ 108.260000] brcmfmac_module_init No platform data available.
[ 108.300000] brcmf_ops_sdio_probe Enter
[ 108.350000] brcmf_ops_sdio_probe Class=0
[ 108.350000] brcmf_ops_sdio_probe sdio vendor ID: 0x02d0
[ 108.350000] brcmf_ops_sdio_probe sdio device ID: 0xa9a6
[ 108.390000] brcmf_ops_sdio_probe Function#: 1
[ 108.390000] brcmf_ops_sdio_probe Enter
[ 108.420000] brcmf_ops_sdio_probe Class=0
[ 108.420000] brcmf_ops_sdio_probe sdio vendor ID: 0x02d0
[ 108.460000] brcmf_ops_sdio_probe sdio device ID: 0xa9a6
[ 108.500000] brcmf_ops_sdio_probe Function#: 2
[ 108.500000] brcmf_ops_sdio_probe F2 found, calling brcmf_sdiod_probe...
[ 108.530000] brcmf_sdiod_probe set F2 blocksize to 512
[ 108.530000] brcmf_sdio_probe Enter
[ 108.530000] brcmf_chip_recognition found AXI chip: BCM43430/1
[ 108.560000] brcmf_chip_cores_check [1 ] core 0x800:49 base 0x18000000 wrap 0x18100000
[ 108.560000] brcmf_chip_cores_check [2 ] core 0x812:39 base 0x18001000 wrap 0x18101000
[ 108.570000] brcmf_chip_cores_check [3 ] core 0x829:21 base 0x18002000 wrap 0x18102000
[ 108.580000] brcmf_chip_cores_check [4 ] core 0x82a:9 base 0x18003000 wrap 0x18103000
[ 108.590000] brcmf_chip_cores_check [5 ] core 0x80e:22 base 0x18004000 wrap 0x18104000
[ 108.600000] brcmf_chip_cores_check [6 ] core 0x135:0 base 0x00000000 wrap 0x18105000
[ 108.610000] brcmf_chip_cores_check [7 ] core 0x240:0 base 0x00000000 wrap 0x18106000
[ 108.620000] brcmf_chip_set_passive Enter
[ 108.640000] brcmf_chip_get_raminfo RAM: base=0x0 size=524288 (0x80000) sr=65536 (0x10000)
[ 108.640000] brcmf_chip_setup ccrev=49, pmurev=24, pmucaps=0x39d25f18
[ 108.660000] brcmf_get_module_param Enter, bus=0, chip=43430, rev=1
[ 108.660000] brcmf_sdiod_sgtable_alloc nents=35
[ 108.670000] brcmf_sdio_kso_init Enter
[ 108.670000] brcmf_sdio_drivestrengthinit No SDIO driver strength init needed for chip BCM43430/1 rev 1 pmurev 24
[ 108.690000] brcmf_sdio_probe completed!!
[ 108.690000] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43430-sdio for chip BCM43430/1
[ 108.700000] brcmf_fw_get_firmwares enter: dev=mmc0:0001:1
[ 108.710000] brcmf_ops_sdio_probe F2 init completed...
[ 109.830000] brcmf_fw_complete_request firmware cypress/cyfmac43430-sdio.bin found
[ 165.600000] cfg80211: failed to load regulatory.db
[ 169.920000] brcmfmac: brcmf_fw_request_firmware: no board-specific nvram available (err=-2), device will use cypress/cyfmac43430-sdio.txt
[ 169.940000] brcmf_fw_complete_request firmware cypress/cyfmac43430-sdio.txt found
[ 169.960000] brcmf_fw_request_nvram_done enter: dev=mmc0:0001:1
[ 169.960000] brcmf_fw_request_nvram_done nvram c39ab000 len 684
[ 169.980000] brcmf_sdio_firmware_callback Enter: dev=mmc0:0001:1, err=0
[ 169.980000] brcmf_sdio_clkctl Enter
[ 170.000000] brcmf_sdio_htclk Enter
[ 170.000000] brcmf_sdio_htclk CLKCTL: turned ON
[ 170.000000] brcmf_sdio_clkctl 1 -> 3
[ 170.010000] brcmf_sdio_download_firmware firmware rstvec: 0
[ 170.020000] brcmf_sdio_download_code_file Enter
[ 170.030000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00000000
[ 170.040000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00008000
...
[ 170.170000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00058000
[ 170.180000] brcmf_sdiod_ramrw write 26582 bytes at offset 0x00000000 in window 0x00060000
[ 170.190000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x00000000; size=419798
[ 170.200000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00000000 in window 0x00000000
[ 170.210000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00000800 in window 0x00000000
...
[ 172.350000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00005800 in window 0x00060000
[ 172.360000] brcmf_sdiod_ramrw read 2006 bytes at offset 0x00006000 in window 0x00060000
[ 172.370000] brcmf_sdio_download_nvram Enter
[ 172.370000] brcmf_sdiod_ramrw write 684 bytes at offset 0x00007d54 in window 0x00078000
[ 172.380000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x0007fd54; size=684
[ 172.390000] brcmf_sdiod_ramrw read 684 bytes at offset 0x00007d54 in window 0x00078000
[ 172.400000] brcmf_chip_set_active Enter
[ 172.410000] brcmf_sdio_clkctl Enter
[ 172.410000] brcmf_sdio_htclk Enter
[ 172.410000] brcmf_sdio_htclk CLKCTL: turned OFF
[ 172.420000] brcmf_sdio_clkctl 3 -> 1
[ 172.420000] brcmf_sdio_clkctl Enter
[ 172.430000] brcmf_sdio_htclk Enter
[ 173.450000] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 173.450000] brcmf_sdio_clkctl 1 -> 1
[ 173.460000] brcmf_sdio_firmware_callback failed: dev=mmc0:0001:1, err=0
[ 173.460000] brcmf_ops_sdio_remove Enter
[ 173.470000] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[ 173.470000] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[ 173.480000] brcmf_ops_sdio_remove Function: 2
[ 173.490000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.490000] brcmf_ops_sdio_remove Enter
[ 173.500000] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[ 173.500000] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[ 173.510000] brcmf_ops_sdio_remove Function: 1
[ 173.510000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.520000] brcmf_sdio_remove Enter
[ 173.530000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.530000] brcmf_detach Enter
[ 173.540000] brcmf_sdio_clkctl Enter
[ 173.540000] brcmf_sdio_htclk Enter
[ 174.560000] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 174.560000] brcmf_sdio_clkctl 1 -> 1
[ 174.600000] brcmf_chip_set_passive Enter
[ 174.650000] brcmf_chip_reset_watchdog Enter
[ 174.650000] brcmf_sdio_clkctl Enter
[ 174.660000] brcmf_sdio_sdclk Enter
[ 174.660000] brcmf_sdio_clkctl 1 -> 0
[ 174.660000] brcmf_sdio_remove Disconnected
[ 174.670000] brcmf_ops_sdio_remove Exit
Hello Everyone,
We are using IMX7D with android 9.0 in our product with a 1MW module. I want to set a static random address for the device.
How can this be achieved in android, can someone please shed some on light on it?
Thank you
Show LessPlease find the below different cases we experimented and the issue we are facing :
case 1) BT Classic application and connecting using Android shutter Bluetooth symbol
When there is only a BT classic application running on the board, and an Android device is used to connect to the board. The shutter on Android device is swiped to touch upon the 'bluetooth symbol' to turn on the bluetooth, and then the device is selected, which upon touching, pops up a window for pairing, and subsequently upon entering the pass code the Android device connects to the board successfully. Absolutely no issue in this case.
case 2) BT Classic application and BLE application on target board and connecting using BLE scanner app on Android device
When there is BT Classic app and BLE app, two different applications running simultaneously on the board, and BLE scanner app on Android device is used to connect to the board. But this time, we used an Android application called "BLE scanner" to get connected to the board, and the connection was smooth and successful without any prompt for pass code [as we know, BLE does need pass code to get connected to any device]. Absolutely no issue in this case as well.
case 3) BT Classic application and BLE application on target board and connecting to board using Android shutter bluetooth symbol intending to connect to BT Classic only.
Now, When we run BT Classic app and BLE app, two different applications both simultaneously on our custom board, and an Android device is used to connect to the board. The same way as in case (1) we tried to connect to the board using 'bluetooth symbol' on shutter, intending to connect to BT app only on target board, but this time around the pop up on the Android device doesn't ask for pass code, it simply gives two options either to "PAIR" or "CANCEL" , upon selecting "PAIR' option the device gets connected successfully, and from the log on the target custom board, we found that, it is getting connected to the BLE application, but not to the BT application. Typically, when we connect to the BT Classic, the android device should produce a pop up for pass code, but it is not happening so.
We are curious to know, why is the device getting connected to the BLE but not to the BT Classic even when we select the 'bluetooth symbol' on the Android shutter, and to be noted that, we are not running the BLE android application [BLE scanner] on the Android device.
Even in the case when we have BLE enabled on the target board, the user should be prompted for pass code on the Android device when user tries to connect.
Kindly shed some light on this issue i.e., How BT classic can still send pass code to the client Android device even when there is BLE enabled on the target board.