Boot BBB stalls? All 4 USR LEDs on...

[martva]

Hi all,

I'm new at the beagleboard black and after trying ubuntu, I want to try Archlinux.
So I looked up the how to for the BBB (http://archlinuxarm.org/platforms/armv7/beaglebone-black) and created the SD card.

But when I put the SD card in the BBB and hold down the Boot button and plugin the power adapter 5V/2A, the board starts with first only Power and then one by one Light up the USR LEDs. After which they stay on.

On my router I do not see extra devices coming online.

Here's what I did:

Create partitions:
$this->bbcode_second_pass_code('', 'Disk /dev/sdb: 7742 MB, 7742685184 bytes
239 heads, 62 sectors/track, 1020 cylinders, total 15122432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x73acd872

Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 133119 65536 e W95 FAT16 (LBA)
/dev/sdb2 133120 15122431 7494656 83 Linux
')

Format partitions:
$this->bbcode_second_pass_code('', '
# mkfs.vfat -F 16 /dev/sdb1
mkfs.vfat 3.0.14 (23 Jan 2023)
# mkfs.ext4 /dev/sdb2
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
468640 inodes, 1873664 blocks
93683 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1920991232
58 block groups
32768 blocks per group, 32768 fragments per group
8080 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
')

After which I downloaded beagleboard en archlinux tarballs.

$this->bbcode_second_pass_code('', '
# wget http://archlinuxarm.org/os/omap/BeagleBone-bootloader.tar.gz
...
Connecting to os.archlinuxarm.org (os.archlinuxarm.org)|67.23.118.182|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 249088 (243K) [application/x-gzip]
Saving to: ‘BeagleBone-bootloader.tar.gz’

100%[======================================>] 249,088 306KB/s in 0.8s

# wget http://archlinuxarm.org/os/ArchLinuxARM-am33x-latest.tar.gz
...
Connecting to os.archlinuxarm.org (os.archlinuxarm.org)|67.23.118.182|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 173964378 (166M) [application/x-gzip]
Saving to: ‘ArchLinuxARM-am33x-latest.tar.gz’

100%[======================================>] 173,964,378 2.30MB/s in 85s
')

And tar these to the sd card and umounted the card.

Am I doing something wrong?
What am I missing?

I've repeated the above steps several times and with several SD cards (kingston, samsung, all 8GB).

Board revision I have is A5A.

[Geoff]

I had success on the first try with a Lexar 16GB microSD chip. I'm sure you remembered to un-tar the partitions as root, not just sudo. The only thing I can think of that might cause this problem is inserting the chip upside down, as it seems the BBB isn't detecting the chip.

$this->bbcode_second_pass_quote('Geoff', 'I') had success on the first try with a Lexar 16GB microSD chip. I'm sure you remembered to un-tar the partitions as root, not just sudo.

[cbcs01]

I've had the same problem on 2 different cards. Also an A5A board.

[chisleu]

I had this happen today when changing back to arch.

I had to hold the button near the SD card while I powered it on to force it to boot from SD card correctly.

[PLyttle]

I had this happen too. When you connect the serial terminal you find out why. The u-boot from your Agstrom installation on your eMMC insists on reading the SSD and finds that the u-boot versions don't match and halts the boot.

(I strongly suggest obtaining an FTDI or similar interface. It makes life a lot easier and helps greatly in understanding the boot process)

Somehow the u-boot of angstrom messes up the documented boot cycle. the Arch installation works as it should. Maybe that is due to the included uEnv.txt bootscript.

success. LP