Beaglebone AI 64 cannot bootup and restore

General Discussion
1

My beaglebone AI 64 (BBAI64) are stuck after i changed dtbo uart1

[    4.785788] j721e-pcie 2920000.pcie:      MEM 0x4400011000..0x4407ffffff -> 0x0000011000
[    4.793871] j721e-pcie 2920000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[    4.802383] VFS: PARTUUID= is invalid.
[    4.802383] Expected PARTUUID=<valid-uuid-id>[/PARTNROFF=%d]
[    4.811767] Disabling rootwait; root= is invalid.
[    4.816575] VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6
[    4.824337] Please append a correct "root=" boot option; here are the available partitions:
[    4.832675] 0100            4096 ram0
[    4.832677]  (driver?)
[    4.838763] 0101            4096 ram1
[    4.838765]  (driver?)
[    4.844856] 0102            4096 ram2
[    4.844858]  (driver?)
[    4.850942] 0103            4096 ram3
[    4.850944]  (driver?)
[    4.857032] 0104            4096 ram4
[    4.857033]  (driver?)
[    4.863118] 0105            4096 ram5
[    4.863120]  (driver?)
[    4.869207] 0106            4096 ram6
[    4.869209]  (driver?)
[    4.875294] 0107            4096 ram7
[    4.875295]  (driver?)
[    4.881386] 0108            4096 ram8
[    4.881388]  (driver?)
[    4.887474] 0109            4096 ram9
[    4.887475]  (driver?)
[    4.893559] 010a            4096 ram10
[    4.893561]  (driver?)
[    4.899736] 010b            4096 ram11
[    4.899738]  (driver?)
[    4.905909] 010c            4096 ram12
[    4.905911]  (driver?)
[    4.912084] 010d            4096 ram13
[    4.912085]  (driver?)
[    4.918258] 010e            4096 ram14
[    4.918259]  (driver?)
[    4.924434] 010f            4096 ram15
[    4.924436]  (driver?)
[    4.930616] b300        15310848 mmcblk0
[    4.930618]  driver: mmcblk
[    4.937415]   b301          131072 mmcblk0p1 86066b37-01
[    4.937417]
[    4.944201]   b302        15178752 mmcblk0p2 86066b37-02
[    4.944202]
[    4.950984] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    4.959228] SMP: stopping secondary CPUs
[    4.963141] Kernel Offset: disabled
[    4.966616] CPU features: 0x8240022,20006008
[    4.970870] Memory Limit: none
[    4.973916] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

I try to restore, get image and restore but error throw out

done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
[   35.907986] tlv71033: disabling
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk1p2 does not exist.  Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
(initramfs)
(initramfs)
(initramfs)
(initramfs)

I’m now stuck with BBAI64 can’t boot and can’t restore,
Can anyone help restore BBAI64 back to default and booting it up

2

Grab the latest version from here

testing 2023-02-05

Write the image to an SD Card. Be careful as the BBAI64 currently has issue with some cards. Stick with an older 4-32GB card,

With power off, insert the card. While keeping the boot button pressed apply power. Give it a second or two then it is ok to release the boot button.

Depending on which version you have downloaded, it will either flash the eMMC or boot from SD.

Assuming you have the means to mount an SD card and edit its contents, while playing around with stuff that might break booting, it would be easier to just boot and run from SD card rather than flashing the eMMC.

1 Like
3

Thank you,

My BBAI-64 are back,