Control: tags 966186 moreinfo On 2020-07-24, rah wrote: > I've successfully installed u-boot to an SD card and set my BeagleBone > Black to not boot from MMC. However, when u-boot runs, it cannot > boot the kernel:
I've just booted a beaglebone black using the am335x_boneblack target and the am335x_evm target, and both work fine for me. > ====================================================================== > U-Boot SPL 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +0000) > Trying to boot from MMC1 > > > U-Boot 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +0000) > > CPU : AM335X-GP rev 2.1 > Model: TI AM335x BeagleBone Black > DRAM: 512 MiB > WDT: Started with servicing (60s timeout) > NAND: 0 MiB > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > Loading Environment from FAT... Unable to use mmc 0:1... <ethaddr> not set. > Validating first E-fuse MAC > Net: eth0: ethernet@4a100000 > Warning: usb_ether MAC addresses don't match: > Address in ROM is de:ad:be:ef:00:01 > Address in environment is c8:df:84:dc:f1:6a > , eth1: usb_ether > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > SD/MMC found on device 0 > ** Unrecognized filesystem type ** > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:1... > Found U-Boot script /boot/boot.scr > 1634 bytes read in 7 ms (227.5 KiB/s) > ## Executing script at 80000000 > 4260352 bytes read in 277 ms (14.7 MiB/s) > SCRIPT FAILED: continuing... > ... > ====================================================================== > > > For some reason, the u-boot environment has `board_name=BBG1` so it > thinks the board is a BeagelBone Green. If I reset the environment, > the board_name variable is set to: Have you used saveenv in the past on either or both the microSD or eMMC? If so, you may have to wipe the environment from the media, as saveenv may have saved incompatible values from an old u-boot version. In general, I don't recommend using saveenv for this reason. > ====================================================================== > => env default -a - > ## Resetting to default environment > => pri > ... > board_name=am335x > ... > ====================================================================== > > Which likewise fails to boot: > > ====================================================================== > => boot > WARNING: Could not determine device tree to use > ... > ====================================================================== Unfortunately, even "env default -a" may not reset the values to the same state as an uninitialized environment, as it may run additional code to update the environment at boot... this is another reason I don't recommend using saveenv. > If I set the board_name variable to `A335BNLT` then it can boot OK. > However, I cannot save the environment using an ext2 root: > > ====================================================================== > => setenv board_name A335BNLT > => saveenv > Saving Environment to FAT... Unable to use mmc 0:1... Failed (1) > ====================================================================== > > > If I try to build an image using a vfat /boot partition then > flash-kernel causes an error while installing the kernel: > > ====================================================================== > Installing /usr/lib/linux-image-4.19.0-9-armmp/am335x-boneblack.dtb into > /boot/dtbs/4.19.0-9-armmp/./am335x-boneblack.dtb > Installing new am335x-boneblack.dtb. > /usr/bin/ln: failed to create symbolic link '/boot/dtb-4.19.0-9-armmp': > Operation not permitted > run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code > 1 > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 > dpkg: error processing package linux-image-4.19.0-9-armmp (--configure): > installed linux-image-4.19.0-9-armmp package post-installation script > subprocess returned error exit status 1 > ====================================================================== Yes, vfat /boot is not supported by flash-kernel (or Debian in general). You might be able to save the environment to a different partition than the one used for /boot, but I don't have much experience with the pitfalls of using a saved environment. > So the package is unfortunatley unusable on the BeagleBone Black. I can't reproduce your problem with my BeagleBone Black, so I'm guessing there is something specific to your environment or configuration. Do you have any capes hooked up, or is it just a bare board? live well, vagrant
signature.asc
Description: PGP signature
