BBB-Wireless Upgrade to Bullseye

Let me know if you want me to move this to its own thread.

I ran into a problem corrupting the eemc on BBB-Wireless working through upgrading to blaster.

I updated /etc/apt/sources.list as recommended above, then apt update → apt upgrade.

I input yes to the 2 questions asking if I wanted to update to the new distribution files. Everything seemed fine.

I then ran apt autoremove which was recommended earlier in the upgrade process and the BBB froze up.

Upon restart the power, WL & BT leds came on, but nothing on the USR leds.

I backed up & reinstalled the 4.19.94-ti-r42 flasher image and that restored everything, but upon trying to update and upgrade that with latest buster I get the corruption again. During the upgrade using cloud9 I am getting an error “Failed to write state settings” flshing quickly and disappearing.

After the update the system does start, but the USR leds are dead.

I redid the whole process using VScode remote explorer. Nothing on problems screen, nothing on output.

Upon reboot the USR leds are not functioning. Update doesn’t produce anything upgradable except c9-core-installer which doesn’t get upgraded.

I went on and updated /opt/script/tools and updated the kernel to 4.19.94-ti-r64

You can see problems with LEDs related to pinctrl in the version output shown in the uname_dogtag_version.txt uploaded file which is taken after updating, upgrading, and upgrading kernel.

Did I break it? Is there something I can do to fix it?

Any suggestions would be welcomed.

Much Thanks,


uname_dogtag_version.txt (4.2 KB)
scripts_kernelupdate terminal screen.txt (10.0 KB)
update_upgrade terminal screen.txt (82.9 KB)

Hi @Patrick_Bolton did you do this on the 4GB eMMC?

What corruption are you seeing? i don’t see anything in the logs…

cloud9 is eol, there will not be a bullseye build…


I am just not seeing the usr leds working at all. On other posts this was indicated as a corruption problem. Perhaps I jumped the gun on that conclusion.

The board is booting and accessible the usr leds are all off and not their usual functions.

I can use vscode instead of cloud9. I did use cloud9 initially.

Best, Pat

Oh, looks like an mixup between kernel and overlays:

dmesg | grep pinctrl-single
[    0.954676] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    1.370693] pinctrl-single 44e10800.pinmux: pin PIN74 already requested by 481a6000.serial; cannot claim for leds
[    1.381151] pinctrl-single 44e10800.pinmux: pin-74 (leds) status -22
[    1.387583] pinctrl-single 44e10800.pinmux: could not request pin 74 (PIN74) from group pinmux_bt_pins  on device pinctrl-single
[    1.535784] pinctrl-single 44e10800.pinmux: pin PIN108 already requested by ocp:A15_pinmux; cannot claim for 0-0070
[    1.546340] pinctrl-single 44e10800.pinmux: pin-108 (0-0070) status -22
[    1.553016] pinctrl-single 44e10800.pinmux: could not request pin 108 (PIN108) from group nxp_hdmi_bonelt_pins  on device pinctrl-single

It’s looking for A15 pinmux, we need to just remove that pin… it needs to be set, but not set by any overlay…


Hi robert,
Is it fixed ? I have same issue on my BBBW. Or, Is there any solution ?

I encountered the same problem, put me on a wrong footing. I though the BBBW had died. After connecting a TTL-USB cable to the serial console I found the same error.

Would be nice to find out how to fix this. Is it kernel stuff, or should we do something else?

Kind Regards,

it was a kernel and overlay mixup…

On bullsye please run:

sudo beagle-version

and report what it output’s for debugging…


dogtag:[ Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-00002-g07d5700e21 (Mar 06 2020 - 11:24:55 -0600)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d5700e21]:[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:[]
UBOOT: Loaded Overlay:[]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
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
[   11.946497] remoteproc remoteproc0: is available
[   11.950282] remoteproc remoteproc1: is available
[   36.458758] Bluetooth: hci0: change remote baud rate command in firmware
[   43.412553] remoteproc remoteproc2: wkup_m3 is available
[   43.428661] remoteproc remoteproc2: powering up wkup_m3
[   43.428686] remoteproc remoteproc2: Booting fw image am335x-pm-firmware.elf, size 217148
[   43.428955] remoteproc remoteproc2: remote processor wkup_m3 is now up
dmesg | grep pru
[   11.946497] remoteproc remoteproc0: is available
[   11.946684] pru-rproc PRU rproc node pru@4a334000 probed successfully
[   11.950282] remoteproc remoteproc1: is available
[   11.950542] pru-rproc PRU rproc node pru@4a338000 probed successfully
dmesg | grep pinctrl-single
[    1.119015] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    1.636580] pinctrl-single 44e10800.pinmux: pin PIN74 already requested by 481a6000.serial; cannot claim for leds
[    1.647067] pinctrl-single 44e10800.pinmux: pin-74 (leds) status -22
[    1.653466] pinctrl-single 44e10800.pinmux: could not request pin 74 (PIN74) from group pinmux_bt_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[    1.137901] gpio-of-helper ocp:cape-universal: ready
Bus 001 Device 003: ID 0b95:772b ASIX Electronics Corp. AX88772B
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Oops. was Buster.

Still, beagle-version was available.

sudo apt update
sudo apt install bb-u-boot-am335x-evm
sudo /opt/u-boot/bb-u-boot-am335x-evm/
sudo reboot


1 Like

Thanks, that worked!

Kind Regards,