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 On Thursday, January 14, 2021 at 12:56:54 PM UTC-5 Ren W wrote: > 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 > <https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/488702?Mysterious-warning-wlcore-WARNING-no-fw-rx-ba-on-tid-1-WL1831> > .) > > [ 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 > > > On Mon, Dec 14, 2020 at 7:31 AM [email protected] <[email protected]> > wrote: > >> I would go a setp further from Robert's sugestion and manually upgrade >> the firmware file, using the one at: >> >> https://git.ti.com/cgit/wilink8-wlan/wl18xx_fw/tree/ >> >> That FW should be retro-compatible with older drivers... >> >> A segunda-feira, 14 de dezembro de 2020 à(s) 15:10:36 UTC, RobertCNelson >> escreveu: >> >>> On Mon, Dec 14, 2020 at 9:03 AM ags <[email protected]> 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 >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/c463b99b-a4bc-42cb-8bcd-432a640f56a7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/c463b99b-a4bc-42cb-8bcd-432a640f56a7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/398eebb6-f916-46ca-86de-f1956cccb7f6n%40googlegroups.com.
