Wi-Fi Bluetooth for Linux Forum Discussions
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
Hello. I have recently come to know about the i.MX 8M Nano evk from NXP (i.MX 8M Nano Evaluation Kit | NXP ). It includes a Murata 1MW module, which I believe is using a Cypress chipset? Can someone let me know where can I donload the Wi-Fi driver from? I am planning to run Linux 4.14 on it.
Show LessIt seems that Cypress creates driver releases for the FMAC WiFi driver once in a while and the latest one (at the time of this post) is:
Cypress Linux WiFi Driver Release (FMAC) [2019-10-31]
My understanding of backports is that you have:
- a linux backports git repository (here's the standard linux one: kernel/git/backports/backports.git - Automatically backports the Linux kernel)
- a linux kernel git repository
Then you run gentree.py and it creates a backports source directory. This source directory is what is included in the release mentioned earlier in the post. Is the Cypress backports git repository public?
Show LessHello,
I am using the Jody-W1 chip. I want to use all available channels in 5Ghz (that are allowed in current country). Unfortunately, the only frequencies I see when setting country to US are:
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5745 MHz [149] (13.0 dBm)
* 5765 MHz [153] (13.0 dBm)
* 5785 MHz [157] (13.0 dBm)
* 5805 MHz [161] (13.0 dBm)
* 5825 MHz [165] (13.0 dBm)
Country DE gives me even only:
* 5745 MHz [149] (13.0 dBm)
* 5765 MHz [153] (13.0 dBm)
* 5785 MHz [157] (13.0 dBm)
* 5805 MHz [161] (13.0 dBm)
* 5825 MHz [165] (13.0 dBm)
These are the channels that do not use DFS or are not restricted to "indoors". I set my regdom in linux (iw reg set US), but that does not allow me to use DFS channels.
I even tried to use the commands in Cypress CLM regulatory manual 4.2.6 DFS (Dynamic Frequency Select ion), but At some commands, errors are returned:
wl down
wl ap 1
wl mpc 0
wl band a
wl mimo_bw_cap 1
wl dfs_preism 1
-> Unsupported
wl spect 1
wl txchain 3
wl chanspec 100/20
-> Bad channel
wl chanspec 100/80
-> Bad channel
wl up
wl radar 1
-> Unsupported
Are there any restrictions in the driver or programmed into the chip?
Best regards,
Michael
Show LessHi team,
We use Cypress chip BCM43455 based Wi-FI+BT module with this we successfully up running wifi and BT.
We are planning to go for regulation test. so we required wl utility to set different combination of power and channels.
Toolchain/system/kernel info:
WiFI Chip: CYW43455
linux 4.19.82
ARCH: arm64
libc : musl
gcc 7.x
Our toolchain is toolchain-aarch64_cortex-a53_gcc-8.3.0_musl
Can you please compile it and share it binary?
Please let's know if you need any further information.
Thanks,
Show LessHello.
We are trying to prepare Wi-Fi software test for the reference lab to certificate our device.( Linux machine)
Our Communication Module uses a CYW43455 Cypress Module,
we found out in our researches this package Cypress Linux WiFi Driver , is it the right package that includes the Certtification Firmware and the tool "wl" ?
Cypress Linux WiFi Driver Release (FMAC) [2019-10-31]
Show LessDear
I am using CYW4343W (Murata LBEE5KL1DX) in our IMX6 Android8 platform.
For FCC Certification we must be able to generate a Carrier into specific Channel or an Continuous Transmission.
Using WL commands we are be able to do all neccessary setting for WIFI.
For Bluetooth we are in trouble, we can not find a way to send HCI Command directly to chipset.
Which method recommend us?
Thanks
M.
Show Less
Hello Everyone,
My company has made a custom board based on imx6ul for EFTPOS applications. We are using 1MW module in our product. Our interface is SDIO based. Schematic is as below.
I get the following error after bootup.
root@imx6:~# dmesg | grep brcmfmac
root@imx6ulevk:~# dmesg | grep brcm
[ 3.111520] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.197038] brcmfmac mmc1:0001:1: direct-loading brcm/brcmfmac43455-sdio.bin
[ 3.250556] brcmfmac mmc1:0001:1: direct-loading brcm/brcmfmac43455-sdio.txt
[ 4.289794] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 5.299965] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
device tree is as follows:
regulators {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <0>;
wlreg_on: fixedregulator@100 {
compatible = "regulator-fixed";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-name = "wlreg_on";
gpio = <&pca9535_0 0 GPIO_ACTIVE_HIGH>;
startup-delay-us = <100>;
enable-active-high;
};
};
&usdhc1 {
#address-cells = <1>;
#size-cells = <0>;
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_wifi>;
pinctrl-1 = <&pinctrl_wifi_100mhz>;
pinctrl-2 = <&pinctrl_wifi_200mhz>;
bus-width = <4>;
non-removable;
vmmc-supply = <&wlreg_on>;
vqmmc-1-8-v;
pm-ignore-notify;
wifi-host;
status = "okay";
brcmf: bcrmf@1 {
reg = <1>;
compatible = "brcm,bcm4329-fmac";
interrupt-parent = <&gpio3>;
interrupts = ❤️ IRQ_TYPE_LEVEL_LOW>;
interrupt-names = "host-wake";
};
};
pinctrl_wifi: wifigrp {
fsl,pins = <
MX6UL_PAD_SD1_CMD__USDHC1_CMD 0x17019
MX6UL_PAD_SD1_CLK__USDHC1_CLK 0x10029
MX6UL_PAD_SD1_DATA0__USDHC1_DATA0 0x17019
MX6UL_PAD_SD1_DATA1__USDHC1_DATA1 0x17019
MX6UL_PAD_SD1_DATA2__USDHC1_DATA2 0x17019
MX6UL_PAD_SD1_DATA3__USDHC1_DATA3 0x17019
MX6UL_PAD_LCD_RESET__GPIO3_IO04 0x50 //host wake interrupt
>;
};
pinctrl_wifi_100mhz: wifigrp1 {
fsl,pins = <
MX6UL_PAD_SD1_CMD__USDHC1_CMD 0x17059
MX6UL_PAD_SD1_CLK__USDHC1_CLK 0x10069
MX6UL_PAD_SD1_DATA0__USDHC1_DATA0 0x17059
MX6UL_PAD_SD1_DATA1__USDHC1_DATA1 0x17059
MX6UL_PAD_SD1_DATA2__USDHC1_DATA2 0x17059
MX6UL_PAD_SD1_DATA3__USDHC1_DATA3 0x17059
MX6UL_PAD_LCD_RESET__GPIO3_IO04 0x50
>;
};
pinctrl_wifi_200mhz: wifigrp2 {
fsl,pins = <
MX6UL_PAD_SD1_CMD__USDHC1_CMD 0x170d9
MX6UL_PAD_SD1_CLK__USDHC1_CLK 0x100e9
MX6UL_PAD_SD1_DATA0__USDHC1_DATA0 0x170d9
MX6UL_PAD_SD1_DATA1__USDHC1_DATA1 0x170d9
MX6UL_PAD_SD1_DATA2__USDHC1_DATA2 0x170d9
MX6UL_PAD_SD1_DATA3__USDHC1_DATA3 0x170d9
MX6UL_PAD_LCD_RESET__GPIO3_IO04 0x50
>;
};
I checked my /lib/firmware/brcm folder as well,
root@imx6:~# ls /lib/firmware/brcm/
brcmfmac4339-sdio.bin brcmfmac43455-sdio.bin brcmfmac43455-sdio.txt
brcmfmac4339-sdio.txt brcmfmac43455-sdio.clm_blob
Binaries are present.
Could someone please help me to understand if anything is missing? Your help is much appreciated.
My bsp:
Linux imx6ulevk 4.19.35-04770-ge5eda1f8cba7-dirty
Regards,
Asma
Show LessHi there,
I am currently developing a Raspberry-Pi based product, which is using BLE (no Wifi). We need to CE-certify this product.
In order to do that, I need to be able to activate the direct test mode on the chip.
Which HCI command do I have to send? What are the OCF and the OGF and the payload for this command?
According to this document HCI Interface — Vendor Specific Guide 5.00.00 documentation this is part of the vendor-specific commands.
Which are the correct commands for the chip I am referring to? How can I trigger this mode?
I also need to be able to count the number of valid received BLE packets. How can I do that?
Thanks and best regards,
Caroline
Show LessOn running PI3B+ with Linux kernel 4.14.y as an AP (using wlan0), if protected management frame is enabled in the hostapd (ver : 2.9) with configurations as follow, the clients are not getting connected :
wpa=2
ieee80211w=2
key_mgmt=WPA-PSK
I could see the error in client that AP is not MFP capable. If ieee80211w=0 is used, STA is getting connected. Have anyone tried using protected management frame (ieee80211w=2) and get the client connected. Is this a known limitation or any firmware/kernel fix available. ?
Show LessHi all,
Evaluating the CYBT-483039-02 module for use in a new design, I have the CYBT-483039-EVAL board plugged into a TI Beagleboard X-15 (running a minimally customized Yocto Warrior OS to add necessary Bluetooth tools) with Bluez5.50
Set up:
I followed this blog post to get a Bluetooth PAN network running: https://blind.guru/tag/bluetooth-pan.html under Bluez5.
I paired with a cheap USB-dongle connected to my PC (Ubuntu 18.04) and have been running iperf3 UDP tests.
On PC:
iperf3 -s
On the BB x-15:
iperf3 -c <IP-address> -t 120 -u
(Setting the test time to 2 minutes as the error does not occur consistently)
Error encountered:
(Copied from Syslog - all messages that were printed during the test)
Sep 10 03:40:39 beagle-x15 systemd[1]: Starting Bluetooth Personal Area Network...
Sep 10 03:40:39 beagle-x15 bt-pan[358]: DEBUG:root:Using local device (addr: 20:71:9B:19:3E:41): /org/bluez/hci0
Sep 10 03:40:39 beagle-x15 bt-pan[358]: DEBUG:root:Registered uuid 'nap' with bridge/dev: pan / 20:71:9B:19:3E:41
Sep 10 03:40:39 beagle-x15 systemd[1]: Started Bluetooth Personal Area Network.
Sep 10 03:42:16 beagle-x15 systemd-udevd[361]: Using default interface naming scheme 'v240'.
Sep 10 03:42:16 beagle-x15 kernel: pan: port 1(bnep0) entered blocking state
Sep 10 03:42:16 beagle-x15 kernel: pan: port 1(bnep0) entered disabled state
Sep 10 03:42:16 beagle-x15 kernel: device bnep0 entered promiscuous mode
Sep 10 03:42:16 beagle-x15 systemd-networkd[146]: bnep0: Gained carrier
Sep 10 03:42:16 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:42:16 beagle-x15 kernel: pan: port 1(bnep0) entered blocking state
Sep 10 03:42:16 beagle-x15 kernel: pan: port 1(bnep0) entered forwarding state
Sep 10 03:42:16 beagle-x15 systemd-networkd[146]: pan: Gained carrier
Sep 10 03:42:16 beagle-x15 systemd-networkd[146]: pan: Could not enable IP masquerading: Operation not supported
Sep 10 03:42:16 beagle-x15 systemd-udevd[361]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 03:42:16 beagle-x15 systemd-networkd[146]: Failed to determine timezone: No such file or directory
Sep 10 03:42:16 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:42:16 beagle-x15 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): pan: link becomes ready
Sep 10 03:42:16 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:42:17 beagle-x15 systemd-networkd[146]: pan: Gained IPv6LL
Sep 10 03:42:17 beagle-x15 systemd-networkd[146]: bnep0: Gained IPv6LL
Sep 10 03:42:17 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:42:29 beagle-x15 systemd-networkd[146]: pan: Configured
Sep 10 03:42:29 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:43:50 beagle-x15 systemd[1]: Starting Cleanup of Temporary Directories...
Sep 10 03:43:50 beagle-x15 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Sep 10 03:43:50 beagle-x15 systemd[1]: Started Cleanup of Temporary Directories.
Sep 10 03:44:11 beagle-x15 kernel: ------------[ cut here ]------------
Sep 10 03:44:11 beagle-x15 kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x258/0x25c
Sep 10 03:44:11 beagle-x15 kernel: NETDEV WATCHDOG: bnep0 (): transmit queue 0 timed out
Sep 10 03:44:11 beagle-x15 kernel: Modules linked in: bnep hci_uart btbcm cdc_acm xhci_plat_hcd xhci_hcd usbcore pru_rproc irq_pruss_intc pruss dwc3 udc_core usb_common snd_soc_simple_card snd_soc_simple_card_utils ahci_platform libahci_platform libahci snd_soc_omap_hdmi omap_aes_driver omap_sham pruss_soc_bus omap_wdt phy_omap_usb2 libata ti_vpe ti_sc ti_csc dwc3_omap ti_vpdma rtc_omap omap_hdq omap_des des_generic crypto_engine omap_crypto wire rtc_palmas rtc_ds1307 extcon_palmas at24 snd_soc_tlv320aic3x omap_remoteproc remoteproc bridge stp llc sch_fq_codel
Sep 10 03:44:11 beagle-x15 kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.59-g50ceb3c6e7 #1
Sep 10 03:44:11 beagle-x15 kernel: Hardware name: Generic DRA74X (Flattened Device Tree)
Sep 10 03:44:11 beagle-x15 kernel: Backtrace:
Sep 10 03:44:11 beagle-x15 kernel: [<c020ca34>] (dump_backtrace) from [<c020cd6c>] (show_stack+0x18/0x1c)
Sep 10 03:44:11 beagle-x15 kernel: r7:c0e5d848 r6:600f0113 r5:00000000 r4:c1250ac0
Sep 10 03:44:11 beagle-x15 kernel: [<c020cd54>] (show_stack) from [<c0a38280>] (dump_stack+0x90/0xa4)
Sep 10 03:44:11 beagle-x15 kernel: [<c0a381f0>] (dump_stack) from [<c022deb0>] (__warn+0xdc/0xf8)
Sep 10 03:44:11 beagle-x15 kernel: r7:c0e5d848 r6:00000009 r5:00000000 r4:c1201cec
Sep 10 03:44:11 beagle-x15 kernel: [<c022ddd4>] (__warn) from [<c022daf4>] (warn_slowpath_fmt+0x50/0x6c)
Sep 10 03:44:11 beagle-x15 kernel: r9:ffffffff r8:c1203d00 r7:ec596294 r6:ec596000 r5:c0e5d80c r4:c1204c48
Sep 10 03:44:11 beagle-x15 kernel: [<c022daa8>] (warn_slowpath_fmt) from [<c08f13d4>] (dev_watchdog+0x258/0x25c)
Sep 10 03:44:11 beagle-x15 kernel: r3:ec596000 r2:c0e5d80c
Sep 10 03:44:11 beagle-x15 kernel: r5:ec5962a8 r4:00000000
Sep 10 03:44:11 beagle-x15 kernel: [<c08f117c>] (dev_watchdog) from [<c02a01a0>] (call_timer_fn+0x2c/0x9c)
Sep 10 03:44:11 beagle-x15 kernel: r10:00000001 r9:c08f117c r8:00000000 r7:00000200 r6:c08f117c r5:00000101
Sep 10 03:44:11 beagle-x15 kernel: r4:ffffe000
Sep 10 03:44:11 beagle-x15 kernel: [<c02a0174>] (call_timer_fn) from [<c02a02a0>] (expire_timers+0x90/0x9c)
Sep 10 03:44:11 beagle-x15 kernel: r6:c1201da4 r5:eed46540 r4:ec5962a8
Sep 10 03:44:11 beagle-x15 kernel: [<c02a0210>] (expire_timers) from [<c02a0358>] (run_timer_softirq+0xac/0x1ac)
Sep 10 03:44:11 beagle-x15 kernel: r9:00000101 r8:c1204c48 r7:c1203d00 r6:c1201da4 r5:eed46540 r4:c1201da4
Sep 10 03:44:11 beagle-x15 kernel: [<c02a02ac>] (run_timer_softirq) from [<c020215c>] (__do_softirq+0x124/0x28c)
Sep 10 03:44:11 beagle-x15 kernel: r8:40000001 r7:ffffe000 r6:c1203080 r5:c1203084 r4:00000020
Sep 10 03:44:11 beagle-x15 kernel: [<c0202038>] (__do_softirq) from [<c0232c90>] (irq_exit+0xd4/0x110)
Sep 10 03:44:11 beagle-x15 kernel: r10:c10694f0 r9:c1200000 r8:ee80c000 r7:00000001 r6:00000000 r5:00000000
Sep 10 03:44:11 beagle-x15 kernel: r4:c1069cfc
Sep 10 03:44:11 beagle-x15 kernel: [<c0232bbc>] (irq_exit) from [<c0287f88>] (__handle_domain_irq+0x68/0xbc)
Sep 10 03:44:11 beagle-x15 kernel: [<c0287f20>] (__handle_domain_irq) from [<c0559504>] (gic_handle_irq+0x44/0x80)
Sep 10 03:44:11 beagle-x15 kernel: r9:c1200000 r8:fa213000 r7:c1201eb0 r6:fa212000 r5:fa21200c r4:c1205100
Sep 10 03:44:11 beagle-x15 kernel: [<c05594c0>] (gic_handle_irq) from [<c02019f8>] (__irq_svc+0x58/0x8c)
Sep 10 03:44:11 beagle-x15 kernel: Exception stack(0xc1201eb0 to 0xc1201ef8)
Sep 10 03:44:11 beagle-x15 kernel: 1ea0: 00000000 0009c058 fe600000 00000000
Sep 10 03:44:11 beagle-x15 kernel: 1ec0: ffffe000 c1204c7c c1204cc4 00000001 00000000 00000000 c10694f0 c1201f0c
Sep 10 03:44:11 beagle-x15 kernel: 1ee0: c1201eec c1201f00 c0221cfc c0208e94 600f0013 ffffffff
Sep 10 03:44:11 beagle-x15 kernel: r9:c1200000 r8:00000000 r7:c1201ee4 r6:ffffffff r5:600f0013 r4:c0208e94
Sep 10 03:44:11 beagle-x15 kernel: [<c0208e6c>] (arch_cpu_idle) from [<c0a5220c>] (default_idle_call+0x30/0x34)
Sep 10 03:44:11 beagle-x15 kernel: [<c0a521dc>] (default_idle_call) from [<c025a238>] (do_idle+0x20c/0x2b4)
Sep 10 03:44:11 beagle-x15 kernel: [<c025a02c>] (do_idle) from [<c025a5cc>] (cpu_startup_entry+0x20/0x24)
Sep 10 03:44:11 beagle-x15 kernel: r10:c104ba38 r9:c12541c0 r8:ffffffff r7:c12541c0 r6:00000000 r5:00000002
Sep 10 03:44:11 beagle-x15 kernel: r4:000000c6
Sep 10 03:44:11 beagle-x15 kernel: [<c025a5ac>] (cpu_startup_entry) from [<c0a4c4f4>] (rest_init+0xd0/0xd4)
Sep 10 03:44:11 beagle-x15 kernel: [<c0a4c424>] (rest_init) from [<c1000dfc>] (start_kernel+0x448/0x470)
Sep 10 03:44:11 beagle-x15 kernel: r5:00000000 r4:c1254218
Sep 10 03:44:11 beagle-x15 kernel: [<c10009b4>] (start_kernel) from [<00000000>] ( (null))
Sep 10 03:44:11 beagle-x15 kernel: ---[ end trace 85e7b9e4ab5c2312 ]---
Sep 10 03:47:27 beagle-x15 systemd-networkd[146]: bnep0: Lost carrier
Sep 10 03:47:27 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:47:27 beagle-x15 kernel: pan: port 1(bnep0) entered disabled state
Sep 10 03:47:27 beagle-x15 kernel: device bnep0 left promiscuous mode
Sep 10 03:47:27 beagle-x15 kernel: pan: port 1(bnep0) entered disabled state
Sep 10 03:47:27 beagle-x15 systemd-networkd[146]: pan: Lost carrier
Sep 10 03:47:27 beagle-x15 systemd-timesyncd[202]: Network configuration changed, trying to establish connection.
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: command 0x0c1a tx timeout
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: hardware error 0x00
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Sep 10 03:47:29 beagle-x15 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
After this, the module is unresponsive until power is cycled.
The module seems to work with TCP tests or at least I have not been able to reproduce the error.
I have tried to reproduce the issue with the CYBT module plugged into my PC (and generic USB dongle on the BB x-15) but have been unable to successfully establish a PAN network to even run a test.
Anyone have advice on why this is happening or how to fix?
Show Less