Is the bbb_debian, images search reporting 32-bit systems for aarch64?

everything but…

The PWR LED lives on!

You should be able to recover it.
Are you seeing any thing on debug port?

No, nothing on the debug port is showing up. I waited for an hour. Nothing.

No odd symbols or hexadecimal notation.


Maybe it is dead. You would see something immediately when powered up. Have you looked at the TI docs for the SoC to see how to start it up?

One of our ai64 died on the shelf, it was working, I am the one that powered it down. Went back a few months later and it is dead, no led. So, that has me a little suspicious…

1 Like

I have not looked at the TI docs.

Just grab the minimal flasher snapshot: ARM64 - Debian 11.x (Bullseye) - Monthly Snapshots - 2023-10-07

Use to flash a mciroSD.

Then insert microSD into bbai64, insert power, hold ‘user’, toggle ‘reset’ buttons…

Watch it flash over USART0


1 Like

I will try and return service once complete.

Okay. You are right.

I booted some random image…

I commanded it this way…

1. Install SD Card w/ random image
2. Hold down the "boot" button
3. Toggle the "reset" button

Thank you! It boots!


One last question on this subject matter before I reboot or boot again…

Will I need the UART0 TTL to USB cable adapter to handle booting each time?


The serial to USB adapter is not required for normal operation.

1 Like

Okay…so the toggle business is what to do no matter what in regards to the USB adapter and/or just USB-Ethernet connections. Okay.

I will test this later and return service just in case it is or is not the case.

Okay and Okay Again,

Sorry here but…

  1. USB to TTL converter cable works
  2. I cannot get the board booted w/ ssh access w/out the USB to TTL cable
  3. The board boots, it shows on my desktop as an icon, and the ssh access is denied each time

Is this something new w/ Debian Bookworm WSL2 instance?

The reason I think it is b/c of WSL2 changing hands over time w/ specific drivers is the fact that I read over this forum in posts about the lack there of specific NDIS drivers not being available on current images/kernels.

Anyway, hearsay or whatever, I am missing something…

Send rations of ideas pretty please!


I tried:

ssh debian@
ssh debian@MY_IP_ADDRESS
ssh debian@beaglebone.local

I also tried:

ssh beagle@
ssh beagle@MY_IP_ADDRESS
ssh beagle@beagleone.local

WSL with Windows 10 or Windows 11?


Windows 11 on WSL2/5.15.133

It seems the system is refusing ssh connections now…

I can try PuTTY if necessary.

which flasher file did you flash?


No clue. I will go and try the one you told me to use from the get-go.

The issue is that all my SD Cards for some reason keep not allowing to rewrite them, i.e. like they are locked or something w/out my permission on Balena Etcher.

I did read about 1.18.x of Etcher is giving people issues.

Downgrade to 1.18.12 : Releases · balena-io/etcher · GitHub

1.18.13 is broken…

Tons of issues on 1.18.13 : Unable to Flash Drive on Ubuntu 22.04 LTS · Issue #4126 · balena-io/etcher · GitHub

To be fair, they list 1.18.11 here: balenaEtcher - Flash OS images to SD cards & USB drives

so both 1.18.12 and 1.18.13 are pre-release…


1 Like

I know every so often some idiom takes place. So, I understand things take place.

Some transfer of people while workin’ or whatever. Who knows, really?

Anyway, thank you. You bring back memories of what I have been reading for some reason. Thank you for sticking around.



Okay. I think I figured out what took place. I am not goin’ to describe everything that I have witnessed here but…

  1. Some images run while other nightly builds do not run or run well or even boot. Understood.
  2. I think this is a mistake I have made in the past until today.
  3. W/ some firmware and images w/ firmware on the SD Cards already flashed, I find myself w/out a method for rebuking the already loaded firmware off the SD Card (Windows 11 and/or Linux Debian “Bullseye and/or Bookworm”)

I think testing images is beside me for now as I have run into some command issues I cannot describe for now. My issue. Not your issue. Understood.

Okay. Outside of my play on words w/ the rebuke word, I am basically trying to erase the SD Card, promote a new image on said SD Card, and then boot into glory. Off to keep trying…

If you read this garble, thank you. Please try to take time to advise me on what should transpire versus what I have already actually done. Blah.

Update Two

Balena Etcher says my SD Card is locked when it is not locked on 1.18.12 and 1.18.11.

Let me show you:


Update Three

BeagleBoard Docs
Release 1.0.20231007

This is the docs. release on my board…

Ubuntu 22.04 native.


The 1.18.11 version of Balena Etcher works on Debian Bookworm desktops for flashing images.

I was having trouble but not any more.