I Reunited with my Board, BBAI-64, and Ruined it... I think sudo blkdiscard was the culprit

General Discussion
1

Debugging Ideas…

I have a board, i.e. the BBAI-64. I used some commands on some unsuspecting files and blaw. The booting got mixed up in the trials.

Now, when I apply the command tio /dev/ttyUSB0 on an Ubuntu development machine with an Armbian image newly ported via micro SD Card, the board boots in the serial instance but not with ssh so far.

Also, when I try a kernel 6.12.x image with the bb-imager source, I received initramfs prompts at the console.

I am not quite sure what to do right now, i.e. as I am fresh to debugging this issue.

This is the output before the initramfs prompt: [ 6.490732] Buffer I/O error on dev mmcblk1, logical block 7633648, async page read .

I tried to custom write via u-boot prompt some root rules to boot from various places, i.e. none of which are correct so far.

Seth

P.S. I know…why should I have used blkdiscard on the machine in question? Well, I am not quite sure. I think I got upset and the 6.1.x kernel was not upgrading via micro SD Card to kernel 6.12.x via image writing. I think this was the start.

So, if anyone has a surefire way of handling initramfs, Armbian, beagleboard.org images, and/or TTL-to-USB debugging, please let me know. I am almost out of ideas…

2

L

3

Dont use blkdiscard again. Use the flasher image that will install everything.

1 Like
4

Would I need to use the serial debug cable to install the eMMC version?

Here is a new thing: https://youtu.be/uZ1MICjhr-s?si=ufQOxlxf8Krxz0HD

The LEDs not only show the PWR LED but also has a new LED that keeps blinking.

5

UPDATE!

I got it finally… It seems it was being peculiar in a manner I was unfamiliar with during the time of trying to get it to boot.

It works! The image from the beagleboard.org website works just fine.

Seth