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,

Pat

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…

Regards,

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…

Regards,

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