Once the fresh image developed with the Yocto project was installed, the Beaglebone Black will not boot from the SD card.

I’m using this procedure: “https://www.youtube.com/watch?v=IVjFJlqmaYU&t=233s,” however when I try to boot from the SD card in beaglebone black industrial, after flashing the core-image-minimal-beaglebone-yocto20240125152951.rootfs.wic, it doesn’t boot.Why?

MACHINE=beaglebone-yocto was referenced in my local.conf file.Perhaps that is the cause of the booting problem.

post your boot serial output.

my Beaglebone Black cannot be booted with the serial boot.

but i can boot my beaglebone black with beaglebone’s own debian image using SD card.
i tried with 5.10

poster asked for your “boot log” over serial to help debug…

Regards,

Confirmed yocto build of beaglebone-yocto does not boot, hangs at “Starting kernel …”
not sure why it’s hanging.

yocto build of beaglebone-yocto
yocto version: kirkstone

extlinux.conf contains:

default Yocto
label Yocto
   kernel /zImage
   fdtdir /
append root=PARTUUID=92e09156-02 rootwait console=ttyS0,115200

U-Boot SPL 2022.01 (Jan 10 2022 - 18:46:34 +0000)
Trying to boot from MMC1

U-Boot 2022.01 (Jan 10 2022 - 18:46:34 +0000)

CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
WDT: Started wdt@44e35000 with servicing (60s timeout)
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT… Unable to read “uboot.env” from mmc0:1… <ethaC
Net: eth2: ethernet@4a100000, eth3: usb_ether
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: Yocto
Retrieving file: /zImage
append: root=PARTUUID=92e09156-02 rootwait console=ttyS0,115200
Retrieving file: /am335x-boneblack.dtb
Kernel image @ 0x82000000 [ 0x000000 - 0x77b718 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffec000, end 8ffff64e … OK

Starting kernel …

seems this has been an issue for some time
https://lists.yoctoproject.org/g/yocto/topic/beaglebone_black_wig_image/81771131?p=

@Sama
good news:

yocto nanbield
builds and boots beaglebone-yocto

U-Boot SPL 2023.10 (Oct 02 2023 - 14:39:59 +0000)
Trying to boot from MMC1

U-Boot 2023.10 (Oct 02 2023 - 14:39:59 +0000)

CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
Core: 160 devices, 18 uclasses, devicetree: separate
WDT: Started wdt@44e35000 with servicing every 1000ms (60s timeout)
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT… Unable to read “uboot.env” from mmc0:1…
not set. Validating first E-fuse MAC
Net: eth2: ethernet@4a100000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
, eth3: usb_ether
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: Yocto
Retrieving file: /zImage
append: root=PARTUUID=076c4a2a-02 rootwait console=ttyS0,115200
Retrieving file: /am335x-boneblack.dtb
Kernel image @ 0x82000000 [ 0x000000 - 0x7a21d8 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
Loading Device Tree to 8ffeb000, end 8ffff130 … OK
Working FDT set to 8ffeb000

Starting kernel …

Booting Linux on physical CPU 0x0
Linux version 6.1.20-yocto-standard (oe-user@oe-host) (arm-poky-linux-gnueabi-g3
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: TI AM335x BeagleBone Black
Memory policy: Data cache writeback
cma: Reserved 16 MiB at 0x9e800000

uname -a
Linux beaglebone-yocto 6.1.20-yocto-standard #1 PREEMPT Sat Mar 18 02:48:04

Wonder if they just dropped it in kirkstone due to age and will they continue on with it using nanbield?

Have you tried the play and ai64 in nanbield?

don’t own play or ai64, to many to fast.
got BVA, just not working on it as much as i should

Just pulled meta-ti and they are not even on mickledore, I am assuming you used meta-poky-bsp for the build.

I will build one for the BBB, been using mickledore and was looking for a good reason to try out nanbield.

poky and meta-openembeded are the directories, I can double check when i boot the beast in the morning.

It produced an odd sized image that would not allow RPI imager to burn it. Uboot did not work either.

Update.
I better stop doing this so late at night and learn how to read file extensions…

1 Like

locations where i got the yocto meta from
git://git.yoctoproject.org/poky.git
https://git.openembedded.org/meta-openembedded

1 Like