Can't boot from the custom built image

Summary

The official image boots fine, but the custom build image fails to run.

Detail

Accroding to the blog post, booting from SD card fails.

I am trying to boot a device tree built with 5.10 according to the blog post

To boot on U-Boot on the microSD card, press the USER button next to the USB host connector, when you power-up the board. Note that this is needed only once, until the board is completely switched off again. The board will continue to boot from the microSD card across reboots and resets. Make sure that the U-Boot prompt shows a 2021.07 U-Boot version.

However, when I try to boot from the SD card, I get nothing back from UART. Is there anything I should check?

What did you write to the uSD card?

writing official image via balenaEtcher works fine (checked with AM3358 Debian 10.3 2020-04-06 4GB SD IoT)

Isn't this what you were supposed to write to the uSD card? Is the issue the dd operation? Did you verify on your computer which device the uSD was on? Maybe it is better just to use balenaEtcher?

initializing "sdx" itself with FAT without cutting pertion, it boots up to U-Boot, but then error occurs.

[error message on the debug UART]
U-Boot SPL 2021.07 (Aug 06 2021 - 19:39:08 +0200)
Trying to boot from MMC1
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

It looks to me like it booted from eMMC and then tried to read the uSD and didn't find the next stage bootloader. If it works fine to boot a uSD written with balenaEtcher, why are you trying to boot an image where you haven't created partitions? What steps are you following to "initialize sdx itself"?

[Method in the blog] If I create partition 1 and write on it, nothing will be returned from UART.

I don't see where it says to create a partition. I'm only seeing it say to dd a disk image.

[operation log on my desktop]

$ sudo fdisk /dev/sdd
o -> n -> 1 -> Enter -> +1GB -> w
$ sudo mkfs.vfat -v -c -F 32 -n boot /dev/sdd1mkfs.fat 3.0.28 (2015-05-16)
gpioblink@gpiocentre:~/myoss/linux$ sudo mount /dev/sdd1 /mnt/sdcard
gpioblink@gpiocentre:~/myoss/linux$ cd /tmp && mkdir beagledl cd beagledl/ && wget https://bootlin.com/pub/2021/dt-> overlays/bbb-boot.tar.xz && tar xf bbb-boot.tar.xz && rm bbb-boot.tar.xz 
gpioblink@gpiocentre:/tmp/beagledl$ ls
am335x-boneblack-uboot.dtb  MLO       src        u-boot.img
dtb                         overlays  uboot.env  zImage
gpioblink@gpiocentre:/tmp/beagledl$ sudo cp -r * /mnt/sdcard/
gpioblink@gpiocentre:/tmp/beagledl$ ls
am335x-boneblack-uboot.dtb  MLO       src        u-boot.img
dtb                         overlays  uboot.env  zImage
gpioblink@gpiocentre:/tmp/beagledl$ sudo umount /dev/sdd1
# then I inserted the sdcard to BBB and turn on the device, the debug UART doesn't response anything...

Where in the blog post does it say to do this? Where does it say to grab these tarballs?

I performed the same operation of 3 on the 3 SD cards I have but god same results.

I copied and pasted what I wrote in Slack for now. I will check the situation again and I will write more details.

It isn't clear what you are trying to accomplish. Starting from the latest nightly builds will show something closer to what we are trying to "fix". The blog posts are intended to give a view of how things have been and how we'd like them to ultimately be. If you are trying to simply reproduce them to understand, it seems you'll need to be clearer in the steps you are following and why.

@gpioblink any updates?

Hello...let me try w/ these three links:

I know that may be a bit to take in at first, i.e. since there are many examples, ideas, and set up commands.

I will test it and reply again.

Seth

P.S. The 2/15 is a starter and then next the 3/31 example, and finally use the 6/06 for finalization.

That's right. Thanks.

Sorry for the very long delay. Thank you for your answer.

What did you write to the uSD card?

I use this image: https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz

Isn't this what you were supposed to write to the uSD card? Is the issue the dd operation? Did you verify on your computer which device the uSD was on? Maybe it is better just to use balenaEtcher?

The build was not an img file, but multiple file chunks. I have to mount the SD card normally and then boot.

I formated the partition to FAT and placed the required files as follows.

It looks to me like it booted from eMMC and then tried to read the uSD and didn't find the next stage bootloader. If it works fine to boot a uSD written with balenaEtcher, why are you trying to boot an image where you haven't created partitions? What steps are you following to "initialize sdx itself"?

Yes, u-boot.img is not loaded properly. U-Boot SPL 2021.07, so it should be booted from the SD card, not the BBB internal eMMC. (internal one is U-Boot SPL 2016.01-00001-g4eb802e)

Steps:

This is the case when/dev/sdx is entirely formated instead of the patition /dev/sdx1. Both is using mkfs.vfat.

The files are copied using sudo cp -r * /mnt/sdcard/, the same as when placed in sdx1.

I don't see where it says to create a partition. I'm only seeing it say to dd a disk image.

I was working on the blog post "Example usage on BeagleBone Black - Board setup".

I was doing the part of the description sudo mkfs.vfat -F 32 -n boot /dev/mmcblkp1.

Where in the blog post does it say to do this? Where does it say to grab these tarballs?

Yes. My first goal was to be able to control LEDs based on the blog post.

I built the kernel myself, but since I didn't have a file system, I was booting based on the contents of tarballs for a quick test.

added help wanted label

mentioned in issue #2

changed milestone to %Prework (delayed)

mentioned in issue #7

If I cannot do this, I will not be able to activate the compatibility layer. Tomorrow, I will first try to do the following so that I can somehow move on to the next step. Please let me know if you have any suggestions .

Is the problem that it is recognized as sd and not mmcblk?
- Try the same operation with the internal SD card terminal
Try to use a tool that creates a FAT file image
- Referring to the MELP book, it looks like I can use the genimage command
Give up booting on one partition and try to divide it into multiple partitions
- Look up how to make an image, and try booting the U-Boot or zImage you are using into separate partitions
Since the essence of this project is to create a compatibility layer, give up and try a nightly build

for instance: use loopback device

@gpioblink ,

Hello Again...anyway. So, it seems one must compile the zImage, dtbs, and the modules. Using u-boot and a cross-compiler will get you there partially.

I saw what was posted in the new links from the blog. I think making an image is far more complicated than just building u-boot. Now, I can be wrong from time to time (especially with all the new remarkable tech. out).

Seth

P.S. Look here: https://forum.beagleboard.org/t/building-with-the-linux-kernel-u-boot-and-debian-minimal/32217 .

That is me complaining about not understanding and going to the forums for assistance. I think what I was missing is building the modules and dtbs. So, I will try once more and return service.

@gpioblink ,

Okay. So, I am going to make some notes here to help you, me, and anyone else looking over these items of interest.

wget https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--glibc--bleeding-edge-2021.11-1.tar.bz2
tar -xvf armv7-eabihf--glibc--bleeding-edge-2021.11-1
cd u-boot
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- distclean
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- am335x_evm_defconfig
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- menuconfig if needed?
Go to / in the u-boot prompt
Type in CMD_EXTENSION
Find in the GUI where exactly CMD_EXTENSION is located in the menuconfig
We need to have CONFIG_EXENTION_CMD=y and we can now build u-boot
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf-
cp MLO u-boot.img /media/$USER/boot/

Now, for the building of zImage, dtbs, and modules...

wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.4.197.tar.xz
tar -xvf linux-5.4.197.tar.xz
cd linux-5.4.197
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=~/YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- menuconfig if needed?
Within the GUI find, by /, OF_OVERLAY. a. Also, the rootfs.cpio build needs to be put in INITRAMFS_SOURCE by searching with / b. So, something like ../rootfs.cpio goes in the box in the GUI after the download
make ARCH=arm CROSS_COMPILE=YOUR_DIR/armv7-eabihf--glibc--bleeding-edge-2021.11-1/bin/arm-buildroot-linux-gnueabihf- zImage modules dtbs
cp zImage /media/$USER/boot/
zImage can be found once the kernel has been built in /arch/arm/boot/
cp am335x-boneblack.dtb /media/$USER/boot/
am335x-boneblack.dtb can be found in /arch/arm/boot/dts/

Now, if anyone wants to chime in here, please do. B/c, for some reason, I have not got this specific build to work just yet.

Seth

P.S. Everything builds correctly but I think my toolchain is outdated. For Bullseye, there is an updated gcc for cross-compilation. Anyway...this is the update so far. It may or may not work due to dependencies.

OKAY. I see what works and does not work so far. With the current bleeding-edge toolchain from bootlin, their respective kernel to use, I THINK, is 5.4.x and u-boot needs to be newer than the kernel. BUT...the info. here, https://beagleboard.org/blog/2022-06-06-using-the-u-boot-extension-board-manager-beaglebone-boards-example, was not ported to u-boot until very recently b/c of beagleboard.org.

@gpioblink ,

Hello Again...Seth here. So, I think in fact it is the course of the partition making that is in the way.

I have done some research and I think using /dev/mmcblk1 for instance over /dev/sda1 for instance is preferable.

I will test tonight and reply once I configure something worth sharing.

Seth

P.S. If you have made it past this phase in your development, please disregard what I am typing. This link says differently, https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967 . So, I will keep trying to support this cause. BBL! https://toolchains.bootlin.com/ may help too...

Okay...so.

In Buildroot, try to use these commands:

cd buildroot
cd configs
nano BONE_defconfig
C & P https://bootlin.com/pub/2022/u-boot-extension-mgr/src/buildroot-2021.02.5.config in BONE_defconfig
make ARCH=arm CROSS_COMPILE=your_toolchain BONE_defconfig
go to /buildroot/output/images/
There should be a bunch of files for your disposal
Add those files to the /boot and /rootfs files in your partitioned SD Card.
WIP

I am still working on the finalization of this process. Bear w/ me.

Seth

P.S. Okay, so. I now have a rootfs file to show off but I am not sure exatly what to do w/ it thus far:

@silver2row Sorry I haven't been able to get back to you very often. Thank you for your advices! Actually, I haven't tried the build yet and time has passed without a reply. I will check the details tomorrow and get back to you with more information.

@jkridner Excuse me, I would like to use the Nightly Build image, can you please tell me where I can find the latest Nightly Build for BeagleBoneBlack?

@gpioblink ,

No issue. If you are busy, you are busy. No issue at all. Enjoy.

Seth

P.S. Here is another resource:

https://github.com/RobertCNelson/ti-linux-kernel-dev/ and...
If just found this online from the #beagle on IRC a. https://pastebin.com/eLhrp1Hg

@silver2row Sorry for the very late response, but thanks to Seth I was able to activate the device tree overlay.

I will keep working on it. https://gpioblink.notion.site/Jun-30-e45e0c2f87d24034b098fa3f665df28b

@gpioblink ,

Way to go. I saw the link you posted for the notion blog.

Seth

Can't boot from the custom built image

Summary

Detail

Close Conditions

Note

Child items

Activity

Summary

Detail

Admin message

Can't boot from the custom built image

Summary

Detail

Close Conditions

Note

Child items

Linked items

Activity

Summary

Detail