wl18xx warning - any resolution?

132 views
Skip to first unread message

ags

unread,
Dec 7, 2020, 6:12:52 AM12/7/20
to BeagleBoard
Has there been any progress in understanding the cause, and cure, for the warning message being written to the system log every second (BBBW)?

kernel: wlcore: WARNING no fw rx ba on tid <n>


Is there a firmware/driver update available? I just re-flashed my eMMC on a

uname -a

Linux beaglebone 4.14.108-ti-r113 #1 SMP PREEMPT Wed Jul 31 00:01:10 UTC 2019 armv7l GNU/Linux



jose...@gmail.com

unread,
Dec 7, 2020, 10:22:38 AM12/7/20
to BeagleBoard
TI has released recently an updated driver and firmware:

ags

unread,
Dec 7, 2020, 3:43:28 PM12/7/20
to BeagleBoard
@RobertCNelson are there any plans to provide this update as part of a BBBW package? (any reason to believe it addresses the issue cited above?)

Robert Nelson

unread,
Dec 7, 2020, 3:50:50 PM12/7/20
to Beagle Board
On Mon, Dec 7, 2020 at 2:43 PM ags <alfred.g...@gmail.com> wrote:
>
> @RobertCNelson are there any plans to provide this update as part of a BBBW package? (any reason to believe it addresses the issue cited above?)

Have you tried booting v4.19.x-ti? Upgrading firmware isn't going to
do too much for your current v4.14.x-ti install..

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ti-connectivity

Mainline only has: firmware 8.9.0.0.83

Regards,

--
Robert Nelson
https://rcn-ee.com/

Robert Nelson

unread,
Dec 7, 2020, 3:53:24 PM12/7/20
to Beagle Board
On Mon, Dec 7, 2020 at 2:43 PM ags <alfred.g...@gmail.com> wrote:
>
> @RobertCNelson are there any plans to provide this update as part of a BBBW package? (any reason to believe it addresses the issue cited above?)
>

ps you have a different issue:

Please run and report this output:

sudo /opt/scripts/tools/version.sh

ags

unread,
Dec 8, 2020, 1:42:24 AM12/8/20
to BeagleBoard


git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5]

eeprom:[A335BNLTBWA51650BBWG0378]

model:[TI_AM335x_BeagleBone_Black_Wireless]

dogtag:[BeagleBoard.org Debian Image 2019-08-03]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gbb4af0f50f]:[location: dd MBR]

kernel:[4.14.108-ti-r113]

nodejs:[v6.17.0]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[disable_uboot_overlay_audio=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]

pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801]

pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]

pkg:[kmod]:[23-2rcnee1~stretch+20171005]

pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]

pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]

groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide]

cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]

dmesg | grep remote

[    1.313264] remoteproc remoteproc0: wkup_m3 is available

[    1.528468] remoteproc remoteproc0: powering up wkup_m3

[    1.528581] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168

[    1.532865] remoteproc remoteproc0: remote processor wkup_m3 is now up

dmesg | grep pru

[ 5566.578557] Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep hci_uart btqca bluetooth cfg80211 ecdh_generic uio_pruss usb_f_mass_storage usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite bc_example(O) pvrsrvkm(O) iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter snd_usb_audio snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device wlcore_sdio evdev uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables

[39794.273196] Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep hci_uart btqca bluetooth cfg80211 ecdh_generic uio_pruss usb_f_mass_storage usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite bc_example(O) pvrsrvkm(O) iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter snd_usb_audio snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device wlcore_sdio evdev uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables

dmesg | grep pinctrl-single

[    0.949178] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

dmesg | grep gpio-of-helper

[    0.961436] gpio-of-helper ocp:cape-universal: ready

lsusb

Bus 001 Device 002: ID 0d8c:0014 C-Media Electronics, Inc.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

END

~                                                                                                                                   

~                                                                                                                                   

                                                                                                                  26,592        All


On Monday, December 7, 2020 at 1:53:24 PM UTC-7, RobertCNelson wrote:

jose...@gmail.com

unread,
Dec 8, 2020, 3:48:36 AM12/8/20
to BeagleBoard
I would suggest upgrading to the v4.19.x-ti kernel and then upgrade the firmware to TI's latest (8.9.0.0.85):

Upgrading the firmware to 8.9.0.0.85 solved some issues in my specific use case.

If that does'nt solve your issue, you can try also to upgrade the wl18xx driver.

For that, pick Robert's scripts and patches to build a BB kernel:


add to them TI's wl18xx R8.8 driver patches:


and build a custom kernel with:

./build_deb.sh

ags

unread,
Dec 10, 2020, 1:29:01 PM12/10/20
to BeagleBoard
Posted the results of the script, curious as to what "the different issue" is. I am hoping to avoid an upgrade to 4.19 at the moment, if possible -- and particularly if the problem is known and has another fix available.


On Monday, December 7, 2020 at 1:53:24 PM UTC-7, RobertCNelson wrote:

Robert Nelson

unread,
Dec 10, 2020, 1:39:37 PM12/10/20
to Beagle Board
On Thu, Dec 10, 2020 at 12:29 PM ags <alfred.g...@gmail.com> wrote:
>
> Posted the results of the script, curious as to what "the different issue" is. I am hoping to avoid an upgrade to 4.19 at the moment, if possible -- and particularly if the problem is known and has another fix available.

Before you upgrade to 4.19, first step would be to "upgrade" the os..

sudo apt update
sudo apt upgrade

All your firmware *.deb blob packages are at least 2 years out of date..

ags

unread,
Dec 14, 2020, 10:03:05 AM12/14/20
to BeagleBoard
Does that mean that everyone running 4.14.x had these problems? I didn't find an outpouring of posts about this problem (although possibly simply a benign log entry) so thought it was a rarer problem that few others had.

Is it reasonable to update just the radio firmware(s), or would that pose a risk (greater than the upgrade)?

On Thursday, December 10, 2020 at 11:39:37 AM UTC-7, RobertCNelson wrote:

Robert Nelson

unread,
Dec 14, 2020, 10:10:36 AM12/14/20
to Beagle Board, Al Schmidt
On Mon, Dec 14, 2020 at 9:03 AM ags <alfred.g...@gmail.com> wrote:
>
> Does that mean that everyone running 4.14.x had these problems? I didn't find an outpouring of posts about this problem (although possibly simply a benign log entry) so thought it was a rarer problem that few others had.
>
> Is it reasonable to update just the radio firmware(s), or would that pose a risk (greater than the upgrade)?

pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]

sudo apt update
sudo apt install --only-upgrade firmware-ti-connectivity

jose...@gmail.com

unread,
Dec 14, 2020, 10:31:00 AM12/14/20
to BeagleBoard
I would go a setp further from Robert's sugestion and manually upgrade the firmware file, using the one at:


That FW should be retro-compatible with older drivers...

R W

unread,
Jan 14, 2021, 12:56:54 PM1/14/21
to beagl...@googlegroups.com
Alfred:
Were you able to resolve this issue? It seems harmless, but the message is annoying.

This means that the peer is trying to start BA sessions more than what the device can support and we are rejecting it. I think you can ignore the warning or downgrade it to DEBUG (per TI E2E support forums.)

[   60.933343] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   61.555139] wlcore: PHY firmware version: Rev 8.2.0.0.242
[   61.608600] wlcore: firmware booted (Rev 8.9.0.0.79)

Linux beaglebone 4.19.94-ti-r57 #1buster SMP PREEMPT Thu Nov 19 23:44:09 UTC 2020 armv7l GNU/Linux


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c463b99b-a4bc-42cb-8bcd-432a640f56a7n%40googlegroups.com.

Walter Cromer

unread,
May 4, 2021, 10:13:11 AM5/4/21
to BeagleBoard
I'm getting this same message on a BBB Wireless now and I agree its annoying.  Any suggestions to get this fixed would be greatly appreciated.

I've recently upgraded and here's the output of version.sh

debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLTBWA52027BBWG0227]
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.03-00002-gac9cce7c6a]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BBBW-WL1835-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-I2C2-RTC-DS3231]
UBOOT: Loaded Overlay:[BB-W1-P9.12-00A2]
kernel:[4.19.94-ti-r61]
nodejs:[v10.15.2]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-W1-P9.12-00A0.dtbo]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
uboot_overlay_options:[dtb_overlay=/lib/firmware/BB-I2C2-RTC-DS3231.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20210401.0-0~buster+20210401]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~buster+20200322]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   70.651413] remoteproc remoteproc0: wkup_m3 is available
[   70.697391] remoteproc remoteproc0: powering up wkup_m3
[   70.697422] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[   70.697706] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   72.927878] remoteproc remoteproc1: 4a334000.pru is available
[   72.940691] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[   72.927878] remoteproc remoteproc1: 4a334000.pru is available
[   72.928077] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[   72.940691] remoteproc remoteproc2: 4a338000.pru is available
[   72.940850] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
dmesg | grep pinctrl-single
[    0.951037] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[    0.964485] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Reply all
Reply to author
Forward
0 new messages