Description
I currently have problems getting the Beagle Bone Black booted with the root pointing to a rootfs
on the SD card.
I initially tried to simply copy the ext4
rootfs on the host to the rootfs
partition on the SD card and boot that one. It failed with the following output
=> fatload mmc 0:1 0x80200000 zImage
9609728 bytes read in 603 ms (15.2 MiB/s)
=> fatload mmc 0:1 0x80f00000 am335x-boneblack.dtb
62852 bytes read in 6 ms (10 MiB/s)
=> setenv bootargs console=ttyO0,115200n8 root=/dev/mmcblk0p2
=> bootz 0x80200000 – 0x80f00000
data abort
pc : [<9ff6c820>] lr : [<9ff6c8f5>]
reloc pc : [<80813820>] lr : [<808138f5>]
sp : 9df38cb8 ip : 00000000 fp : 9df3c3e4
r10: 9ffc03d0 r9 : 9df38eb8 r8 : 9ffc03cc
r7 : 00000002 r6 : 9df3c3d0 r5 : 82000000 r4 : 9ffc0334
r3 : 56190527 r2 : 9df3c3d1 r1 : 00000002 r0 : 00000000
Flags: nZCv IRQs off FIQs on Mode SVC_32
Code: ffdaf7ff f85db003 0000fb04 4b0ab510 (46046802)
Resetting CPU ...
I then tried to follow the instructions in the book exactly, using
format-sd-card.sh
to set up the SD card, copying the bootloader to boot
,
and then generating rootfs.ext2
with
genext2fs -b 16384 -d initramfs -D device-table.txt -U rootfs.ext2
and finally sudo dd if=rootfs.ext2 of=/dev/<rootfspartition>
to flash the rootfs partition, but I get the same issue with a data abort. Does anyone have an idea what might cause this?
If I run
fatload mmc 0:1 0x80200000 zImage
fatload mmc 0:1 0x80f00000 am335x-boneblack.dtb
fatload mmc 0:1 0x81000000 uRamdisk
setenv bootargs console=ttyO0,115200n8 rdinit=/sbin/init
bootz 0x80200000 0x81000000 0x80f00000
I can boot the kernel from the initramfs in uRamdisk
without issues, so I assumed that the Linux kernel image and the *.dtb
file are not the issue