flash U-Boot on beaglebone black

General Discussion
1

Why I can’t update U-Boot on eMMC?
I tried to run the install.sh script but when I reboot u-boot is always at the previous version… what is missing?

root@devuan:/opt/u-boot/bb-u-boot-am335x-evm# ./install.sh
dd if=/opt/u-boot/bb-u-boot-am335x-evm/MLO of=/dev/mmcblk0 count=2 seek=1 bs=128k
0+1 records in
0+1 records out
92532 bytes (93 kB, 90 KiB) copied, 0.00851008 s, 10.9 MB/s
dd if=/opt/u-boot/bb-u-boot-am335x-evm/u-boot.img of=/dev/mmcblk0 count=4 seek=1 bs=384k
1+1 records in
1+1 records out
473472 bytes (473 kB, 462 KiB) copied, 0.0288175 s, 16.4 MB/s
dd if=/opt/u-boot/bb-u-boot-am335x-evm/MLO of=/dev/mmcblk1 count=2 seek=1 bs=128k
0+1 records in
0+1 records out
92532 bytes (93 kB, 90 KiB) copied, 0.530141 s, 175 kB/s
dd if=/opt/u-boot/bb-u-boot-am335x-evm/u-boot.img of=/dev/mmcblk1 count=4 seek=1 bs=384k
1+1 records in
1+1 records out
473472 bytes (473 kB, 462 KiB) copied, 0.118052 s, 4.0 MB/s

root@devuan:/opt/u-boot/bb-u-boot-am335x-evm# file u-boot.img

u-boot.img: u-boot legacy uImage, U-Boot 2019.04-g923f8b8 for am33\270, Firmware/ARM, Firmware Image (Not compressed), 473408 bytes, Sun Jan  2 19:05:15 2022, Load Address: 0x80800000, Entry Point: 0x00000000, Header CRC: 0xAD095BAA, Data CRC: 0x775613A7

but when the board boot I see: U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)

2

Its defaulting to fat load over raw load… You probably have an old fat partition with the old version of u-boot

1 Like
3

It is true!!!
:slight_smile: on the board I have:

/dev/mmcblk1p2 mounted on / (type ext4)
/dev/mmcblk1p1 mounted on /boot/uboot (type vfat)

I have to overwrite the /boot/uboot/u-boot.img with the newer u-boot.img file?
Have to overwrite MLO too?

Thank you

4

I have overwrited the two files with the newer and now it use the U-Boot 2019.04-g923f8b8