lilyjayd
commented
1 year ago Hello again,
I think I have found a root cause of this problem. The thing is that in the instruction we copy combined uboot and dtb file to SD card:
sudo mkdir -p /media/rootfs/opt/backup/uboot/
sudo cp -v ./u-boot/MLO /media/rootfs/opt/backup/uboot/
sudo cp -v ./u-boot/u-boot-dtb.img /media/rootfs/opt/backup/uboot/but the script is looking for u-boot.img, not u-boot-dtb.img which we copied to SD card:
if [ ! -f /opt/backup/uboot/u-boot.img ] ; then
mkdir -p /opt/backup/uboot/
wget --directory-prefix=/opt/backup/uboot/ http://rcn-ee.com/repos/bootloader/am335x_evm/${http_uboot}
mv /opt/backup/uboot/${http_uboot} /opt/backup/uboot/u-boot.img
fiand since it did not find u-boot.img, it will download and install image from rcn-ee.com, as we an see in my session log:
113246208 bytes (113 MB, 108 MiB) copied, 2.85152 s, 39.7 MB/s
Erasing: /dev/mmcblk1 complete
-----------------------------
--2022-09-17 19:26:00-- http://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img
Resolving rcn-ee.com (rcn-ee.com)... 45.33.2.10, 2600:3c00::f03c:91ff:fe37:6ad5
Connecting to rcn-ee.com (rcn-ee.com)|45.33.2.10|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img [following]
--2022-09-17 19:26:01-- https://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img
Connecting to rcn-ee.com (rcn-ee.com)|45.33.2.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 474352 (463K)
Saving to: ‘/opt/backup/uboot/u-boot-am335x_evm-v2019.04-r13.img’
u-boot-am335x_evm-v 100%[===================>] 463.23K 512KB/s in 0.9s
2022-09-17 19:26:02 (512 KB/s) - ‘/opt/backup/uboot/u-boot-am335x_evm-v2019.04-r13.img’ saved [474352/474352]
Writing bootloader to [/dev/mmcblk1]
dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128kwhich will ultimately end up in having my own MLO flashed with some u-boot-am335x_evm-v2019.04-r13.img instead of my u-boot-dtb.img. When I flashed manually my original MLO and u-boot-dtb.img, my target boots correctly from eMMC.
I can fix that problem in the script if that's ok for you. This can be also fixed by changing the instruction to:
sudo cp -v ./u-boot/u-boot-dtb.img /media/rootfs/opt/backup/uboot/u-boot.imgPlease let me know which option you prefer :)
RobertCNelson
Hello,
first of all, I'd like to thank you @RobertCNelson - what you are doing is amazing!
So I followed your instructions for BBB (I skipped only HDMI and u-boot Overlays sections) from here:
https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967
It booted completely fine from SD card. And at that time my BBB was also properly booting old u-boot and kernel on eMMC. So I booted again from SD card to flash the fresh software to eMMC via:
After the script finished, I did sync + remove SD card and restart BBB. It did not end well:
Below, you can find logs from the whole session: boot from SD card with software installed by following instruction on digikey forum, download and execution of bbb-eMMC-flasher-eewiki-ext4.sh script and then restart without SD card inserted.
After that I booted again from SD card and used the bbb-eMMC-flasher-eewiki-ext4.sh once more - with the same result unfortunately. Below logs doesn't cover that second try.
What can be wrong here? Any way to debug and fix that?