Home Home
Product Product Product
Microcontrollers
PSoC™ 6 PSoC™ 4 PSoC™ 5, 3 & 1 CAPSENSE™ & MagSense XMC™ AURIX™ TRAVEO™ T2G MOTIX™ MCU Legacy microcontrollers
USB
USB low-full-high speed peripherals USB hosts hubs transceivers USB superspeed peripherals USB EZ-PD™ Type-C
Wireless Connectivity
AIROC™ Wi-Fi and Wi-Fi Bluetooth Combos AIROC™ Wi-Fi MCUs AIROC™ Bluetooth
Power
Power MOSFET IGBT Discretes Silicon Carbide Gate Driver IC's IGBT Modules LITIX™ Automotive LED Driver IC iMOTION™ controller, driver & IPM MADK MOTIX™ Bridge MOTIX™ Driver MOTIX™ SBC Intelligent Power Modules (IPM) Power Management ICs CoolGaN™
Sensors
CO₂ sensor 3D Hall (Magnetic sensor) Hall switches (Magnetic sensor) Radar sensor Angle (Magnetic sensor) Current (Magnetic sensor)
Memories
Nor Flash Hyper Flash Hyper RAM Non Volatile RAM (F-RAM & NVSRAM) Specialty Memory SRAM
Other Technologies
Clocks Other Technologies General
Security
OPTIGA™ Trust OPTIGA™ TPM
Radio Frequency (RF)
RF Transistors
Software Software Software
ModusToolbox™
PSoC™ 6 SDK Bluetooth SDK AWS IoT SDK Mbed SDK Any cloud SDK ModusToolbox™ General
WICED™ Studio
Wi-Fi Combo Studio Bluetooth Smart Bluetooth
CIRRENT™ Software Services
CIRRENT™ Product Analytics CIRRENT™ Cloud ID
DAVE™ PSoC™ Creator & Designer Wi-Fi Bluetooth for Linux AURIX™ Development Studio
General General General
Blogs
Community Manager Blog Security Bulletin University Alliance Blog Software on Silicon Blog ModusToolbox Blog Memory Solutions IoT Blog Blog4Engineers
Community Information Resource Library Knowledge Base Articles
Member Contributions & Content Member Contributions & Content Member Contributions & Content
Code Examples Community Translations
Community Sitemap Community Sitemap Community Sitemap

Ask the Community

Wi-Fi Bluetooth for Linux

Recent discussions

Sort by:

wl_tool cross compile (armv7l w/custom toolchain)

Solved

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... Show More

By hongkongkiwi

Apr 4, 2022

199

Wi-Fi Bluetooth for Linux

Pre Compliance tests for CYW43455 WiFi-BT chip on Android 11

Hi Cypress Team, We need to do Pre-compliance tests on CYW43455 module on Android 11 platform for WiFi and BT. Could you please provide us any tools... Show More

By Hrithik

May 17, 2022

Wi-Fi Bluetooth for Linux

1DX wi-fi driver issue with i.MX6ULL

Solved

We are using Murata LBEE5KL1DX (BCM4343W) as Wi-Fi module with i.MX6ULL. We have been able to compile BCMDHD driver for this chip inbuilt (in kernel) ... Show More

By Anonymous

Sep 20, 2017

433

Wi-Fi Bluetooth for Linux

SDIO -110 errors with CYW43012 WiFi chipset

Hi All, We are using CYW43012 chipset with the following details: Firmware version: 1.21 RC0.0wl0: Feb 21 2022 07:19:28 version 13.10.271.283 (211da63... Show More

Hi All,

We are using CYW43012 chipset with the following details:

Firmware version:

1.21 RC0.0
wl0: Feb 21 2022 07:19:28 version 13.10.271.283 (211da63 CY) FWID 01-18f4ac2

Driver Version:

Backported Linux Version v4.14.77-kong-RTM-rc8-0-ged6fa18

We have observed that after certain time, we are seeing SDIO -110 error as follows:

2022-05-04 02:44:53 SAMA5D2C3 kernel:[45542.850000] +++ should not come 470:atmel_i2s_switch_mck_generator
2022-05-04 02:45:01 SAMA5D2C3 crond[699]: pam_unix(crond:session): session opened for user root by (uid=0)
2022-05-04 02:45:01 SAMA5D2C3 CROND[700]: (root) CMD (/bin/date -u +%4Y%2m%2d%2H%2M%2S 2>/dev/null > /etc/timestamp)
2022-05-04 02:45:01 SAMA5D2C3 CROND[699]: pam_unix(crond:session): session closed for user root
2022-05-04 02:46:09 SAMA5D2C3 rsyslogd: -- MARK --
2022-05-04 02:46:15 SAMA5D2C3 kernel:[45624.750000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:46:58 SAMA5D2C3 kernel:[45667.480000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:48:58 SAMA5D2C3 kernel:[45787.500000] atmel_i2s f8050000.i2s: TX underrun on channel 0
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.300000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.320000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.330000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.350000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.360000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.370000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.390000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.400000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.420000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.440000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.440000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.560000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.570000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.580000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.700000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.720000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.730000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.950000] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.960000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x0a020, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.980000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F0@0x00003, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45809.990000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.010000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.020000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.040000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.050000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.070000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.080000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.100000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.110000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.120000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.140000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.160000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.170000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.190000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.200000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.220000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:20 SAMA5D2C3 kernel:[45810.220000] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.240000] brcmfmac: brcmf_sdiod_regrw_helper: failed to write data F1@0x1000d, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.260000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.270000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.290000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.300000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.320000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x1001a, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.340000] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x10019, err: -110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.340000] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-110
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.350000] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
2022-05-04 02:49:21 SAMA5D2C3 kernel:[45810.360000] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110

This issue is frequently reproducible and any need asap is deeply appreciated.

Attached the complete log file for your reference.

@Vinayak @GauravS_31 @raks_99

Regards,

Rupesh

Show Less

By rupesh_theatro

May 5, 2022

102

Wi-Fi Bluetooth for Linux

WiFi certified with the CM4 - How to ?

Solved

Hello, We are a manufacturer of gateways and intend to get the "WiFi Certified" approval of the WiFi Alliance with the Raspberry Compute Model 4 (https://www.raspberrypi.com/products/compute-module-4/?variant=raspberry-pi-cm4001000... Show More

By fischeor

Apr 14, 2022

131

Wi-Fi Bluetooth for Linux

Cypress Linux WiFi Driver Release (FMAC) [2022-03-31]

Package Version v5.10.9-2022_0331 Release Date 2022-03-31 Description This is Cypress's Linux brcmfmac driver and firmware support pack... Show More

By DoubleLo

Apr 1, 2022

1136

Wi-Fi Bluetooth for Linux

CYW43340 CE certification failed

Hello, 我们在针对CYW43340进行CE认证时，自适应测试失败，测试报告见附件；我们使用的固件及nvram文件也传到附件，请参考。 1. 我们使用的平台内核是2.6. 2. 我们使用的wl命令如下： wl outwl downwl ampdu 1wl country DEwl ba... Show More

By XiLo_1740121

May 4, 2022

Wi-Fi Bluetooth for Linux

CYW43012 WiFi Firmware becomes unresponsive after sometime

Hi All, We are using CYW43012 chipset with the following details: Firmware version: 1.21 RC0.0wl0: Sep 1 2021 22:33:32 version 13.10.271.273 (9278a6... Show More

Hi All,

We are using CYW43012 chipset with the following details:

Firmware version:

1.21 RC0.0
wl0: Sep 1 2021 22:33:32 version 13.10.271.273 (9278a67 CY) FWID 01-e6c8687a

Driver Version:

Backported Linux Version v4.14.77-kong-RTM-rc8-0-ged6fa18

We have observed that after certain time when we are using the device (going out of network and coming with in network zone), we observe that driver disconnects and remains offline permanently with the following errors:

2022-04-29 10:32:11 SAMA5D2C3 dropbear[697]: Child connection from 10.0.250.20:61214
2022-04-29 10:32:11 SAMA5D2C3 kernel:[ 307.050000] device wlan0 entered promiscuous mode
2022-04-29 10:32:14 SAMA5D2C3 dropbear[697]: Pubkey auth succeeded for 'root' with key md5 8f:1e:41:f8:30:7a:52:07:76:10:26:22:6a:24:53:b6 from 10.0.250.20:61214
2022-04-29 10:32:14 SAMA5D2C3 dropbear[697]: Exit (root): Disconnect received
2022-04-29 10:32:41 SAMA5D2C3 kernel:[ 336.430000] ## AIC32X4_STKY1STATUSREG JACKSTATUS 16
2022-04-29 10:32:41 SAMA5D2C3 kernel:[ 336.440000] ## AIC32X4_INT1STATUSREG STATUS 16
2022-04-29 10:32:41 SAMA5D2C3 kernel:[ 336.440000] atmel-sama5d2-sbc sound: ASoC: DAPM unknown pin Headset Mic
2022-04-29 10:32:41 SAMA5D2C3 kernel:[ 336.450000] atmel-sama5d2-sbc sound: ASoC: DAPM unknown pin Headphone
2022-04-29 10:32:41 SAMA5D2C3 kernel:[ 336.450000] ## AIC32X4_HP_DETECT Detected 16
2022-04-29 10:32:45 SAMA5D2C3 ntpd[311]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
2022-04-29 10:32:47 SAMA5D2C3 kernel:[ 342.650000] ## AIC32X4_STKY1STATUSREG JACKSTATUS 156
2022-04-29 10:32:47 SAMA5D2C3 kernel:[ 342.660000] ## AIC32X4_INT1STATUSREG STATUS 0
2022-04-29 10:32:47 SAMA5D2C3 kernel:[ 342.670000] atmel-sama5d2-sbc sound: ASoC: DAPM unknown pin Headset Mic
2022-04-29 10:32:47 SAMA5D2C3 kernel:[ 342.670000] atmel-sama5d2-sbc sound: ASoC: DAPM unknown pin Headphone
2022-04-29 10:32:47 SAMA5D2C3 kernel:[ 342.680000] ## AIC32X4_HP_DETECT Removed 0
2022-04-29 10:33:03 SAMA5D2C3 dropbear[715]: Child connection from 10.0.250.20:61268
2022-04-29 10:33:06 SAMA5D2C3 dropbear[715]: Pubkey auth succeeded for 'root' with key md5 8f:1e:41:f8:30:7a:52:07:76:10:26:22:6a:24:53:b6 from 10.0.250.20:61268
2022-04-29 10:33:06 SAMA5D2C3 dropbear[715]: Exit (root): Disconnect received
2022-04-29 10:33:59 SAMA5D2C3 ntpd[311]: Deleting interface #5 wlan0, 10.128.0.52#123, interface stats: received=13, sent=14, dropped=0, active_time=384 secs
2022-04-29 10:33:59 SAMA5D2C3 ntpd[311]: 10.0.250.3 local addr 10.128.0.52 -> <null>
2022-04-29 10:34:00 SAMA5D2C3 kernel:[ 415.310000] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
2022-04-29 10:34:00 SAMA5D2C3 kernel:[ 415.320000] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
2022-04-29 10:34:10 SAMA5D2C3 kernel:[ 425.330000] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
2022-04-29 10:34:10 SAMA5D2C3 kernel:[ 425.340000] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
2022-04-29 10:35:01 SAMA5D2C3 crond[744]: pam_unix(crond:session): session opened for user root by (uid=0)
2022-04-29 10:35:01 SAMA5D2C3 CROND[745]: (root) CMD (/bin/date -u +%4Y%2m%2d%2H%2M%2S 2>/dev/null > /etc/timestamp)
2022-04-29 10:35:01 SAMA5D2C3 CROND[744]: pam_unix(crond:session): session closed for user root
2022-04-29 10:38:23 SAMA5D2C3 shutdown[758]: shutting down for system reboot
2022-04-29 10:38:23 SAMA5D2C3 init: Switching to runlevel: 6
2022-04-29 10:38:23 SAMA5D2C3 shutdown[760]: shutting down for system reboot
2022-04-29 10:38:23 SAMA5D2C3 shutdown[762]: shutting down for system reboot
2022-04-29 10:38:23 SAMA5D2C3 shutdown[764]: shutting down for system reboot
2022-04-29 10:38:24 SAMA5D2C3 shutdown[766]: shutting down for system reboot
2022-04-29 10:38:24 SAMA5D2C3 shutdown[768]: shutting down for system reboot
2022-04-29 10:38:24 SAMA5D2C3 shutdown[770]: shutting down for system reboot
2022-04-29 10:38:24 SAMA5D2C3 shutdown[772]: shutting down for system reboot
2022-04-29 10:38:24 SAMA5D2C3 shutdown[774]: shutting down for system reboot

This issue is frequently reproducible and any need asap is deeply appreciated.

Attached the complete log file for your reference.

@Vinayak @GauravS_31

Regards,

Rupesh

Show Less

By rupesh_theatro

May 2, 2022

Wi-Fi Bluetooth for Linux

brcmfmac instant crash on Raspberry Pi

Solved

Hello, We get a very reproducible crash of the brcmfmac wifi driver under specific traffic conditions that I will detail below. Product info: Device: ... Show More

Hello,

We get a very reproducible crash of the brcmfmac wifi driver under specific traffic conditions that I will detail below.

Product info:

Device: Raspberry Pi 3B+

OS: Raspberry Pi OS 5.10.63

WLAN CHIP: BCM43455

Wireless firmware version: 7.45.206
We had the exact same crash almost 2 years ago with Raspbian 4.19.75 and wireless firmware 7.45.189, so the problem is not new.

Transmission parameters: channel 36 (5.18 GHz) - MCS3 - HT20.

dmesg crash report:

[ 6582.744261] device mon0 entered promiscuous mode
[ 6595.671916] ieee80211 phy1: brcmf_fw_crashed: Firmware has halted or crashed
[ 6599.210435] device mon0 left promiscuous mode
[ 6601.763640] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 6601.764088] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 6601.764297] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aabb0
                 cpsr 0x2000019f spsr 0x200001bf sp 0x0025fdb8
                 lr   0x001aad23 pc   0x001aabb0 offset 0x25fd60
                 r0   0x00218b58 r1   0x00218b58 r2 0x0025fe34 r3 0x00000000
                 r4   0x0022bbbc r5   0x0000ffff r6 0x00000000 r7 0xbe23f199
[ 6601.764324] ieee80211 phy1: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[ 6604.323574] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 6604.324003] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 6604.324233] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aabb0
                 cpsr 0x2000019f spsr 0x200001bf sp 0x0025fdb8
                 lr   0x001aad23 pc   0x001aabb0 offset 0x25fd60
                 r0   0x00218b58 r1   0x00218b58 r2 0x0025fe34 r3 0x00000000
                 r4   0x0022bbbc r5   0x0000ffff r6 0x00000000 r7 0xbe23f199
[ 6604.324259] ieee80211 phy1: _brcmf_set_multicast_list: Setting allmulti failed, -110
[ 6606.883511] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 6606.883946] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 6606.884168] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aabb0
                 cpsr 0x2000019f spsr 0x200001bf sp 0x0025fdb8
                 lr   0x001aad23 pc   0x001aabb0 offset 0x25fd60
                 r0   0x00218b58 r1   0x00218b58 r2 0x0025fe34 r3 0x00000000
                 r4   0x0022bbbc r5   0x0000ffff r6 0x00000000 r7 0xbe23f199
[ 6606.884206] ieee80211 phy1: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110

[ 6609.443453] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 6609.443866] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 6609.444084] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aabb0
                 cpsr 0x2000019f spsr 0x200001bf sp 0x0025fdb8
                 lr   0x001aad23 pc   0x001aabb0 offset 0x25fd60
                 r0   0x00218b58 r1   0x00218b58 r2 0x0025fe34 r3 0x00000000
                 r4   0x0022bbbc r5   0x0000ffff r6 0x00000000 r7 0xbe23f199
[ 6612.003397] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 6612.003804] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 6612.004023] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aabb0
                 cpsr 0x2000019f spsr 0x200001bf sp 0x0025fdb8
                 lr   0x001aad23 pc   0x001aabb0 offset 0x25fd60
                 r0   0x00218b58 r1   0x00218b58 r2 0x0025fe34 r3 0x00000000
                 r4   0x0022bbbc r5   0x0000ffff r6 0x00000000 r7 0xbe23f199

How to reproduce this crash:

It basically involves injecting three "small enough" frames back-to-back. We use nexmon to configure the BCM43455 in monitor mode, and pcap_inject() to inject frames. We forge our own 802.11 frames with radiotap headers.

When making three calls in a row to pcap_inject() with frames of any size smaller than about 600 bytes, the Broadcom driver crashes upon the third call, while the first two frames are transmitted correctly and received by a nearby machine.

On the other hand, making these three calls in a row with frames bigger than about 650 bytes never produces a crash. Making only two back-to-back calls to pcap_inject(), even with frames below 600 bytes, also never crashes the driver.

When inserting a small delay between the second and third call, here is what we get :

with a delay any smaller than 500 µs: the driver crashes upon the third injection for any frame size below about 600 bytes. For frames above about 650 bytes, no crash;
with a delay bigger than 600 µs: no crash whatever the frames size, whether big or small.

When repeating the experience on different machines, we noted that the delay above could take other values, possibly due to different radio transmission parameters. However the behavior was always the same as described above.

It looks like some sort of traffic shaping mechanism is acting up inside the driver - and failing under particular circumstances.

Are we doing something wrong ?

If you feel that more extensive tests under various conditions could help sort out this thing, please do not hesitate to ask, as the manipulation is really immediate.

Thanks for help!

Show Less

By xsutter

Jan 3, 2022

507

Wi-Fi Bluetooth for Linux

WL Tool & MFG Firmware for ARM64 Platform + Linux5.4.70 Kernel for RF Te...

Solved

Hi, I need WL tool & MFG Firmware for ARM aarch64 Platform with Linux5.4.70 Kernel + iMX8MMini Processor Supported WL Tool. Kindly provide the wl too... Show More

By Kumaresan

Apr 12, 2022

214

Wi-Fi Bluetooth for Linux

fmac 2022-3-31 release modifies public nl80211 API

Solved

Patch 0109 in the fmac 2022-03-31 release modifies nl80211.h by defining a new extended feature NL80211_EXT_FEATURE_ROAM_OFFLOAD. There is a correspo... Show More

By DeRa_4514941

Apr 12, 2022

157

Download the new Linux Driver

Download Now