boot from eMMC not working after using bbb-eMMC-flasher-eewiki-ext4.sh #127
Comments
|
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: but the script is looking for u-boot.img, not u-boot-dtb.img which we copied to SD card: and 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: which 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: Please let me know which option you prefer :) |
|
Unfortunately, when I changed filename: and run bbb-eMMC-flasher-eewiki-ext4.sh again, target still can't be booted properly, with a different message this time: Logs from the flashing with script below: I pressed reset button couple of times. So to sum up, I have MLO and u-boot.img (which is renamed u-boot-dtb.img) in /opt/backup/uboot/ directory on a software booted from SD card. When I manually install this new u-boot via: (I do not install rootfs) then it is working fine - BBB is booted and looking for sources to boot: but when I run the script which I believe installs the same MLO and u-boot.img (plus rootfs), then this is not working and ends up with u-boot hangs at: |
|
Hi @lilyjayd sorry about this, with bullseye, i've rewritten the eMMC flasher to be more modular, i really need to go back on buster and remove all the old scripts.. The debian package is "bb-beagle-flasher" pushed out to buster, bullseye, focal, and jammy.. The main script is: https://github.com/rcn-ee/repos/blob/master/bb-beagle-flasher/suite/bullseye/debian/beagle-flasher to configure for your board, you copy one of the config files to: BBB: microSD -> eMMC
BBB: eMMC -> microSD
BBAI: microSD -> eMMC
BBAI: eMMC -> microSD
For the BBB it'll pull in the u-boot here: From debian userspace then just run: Regards, |
|
Thanks @RobertCNelson. It went smooth with default MLO and u-boot-dtb.img from package you've mentioned: Tomorrow I'll try with my own MLO and uboot image. And by the way, do you perhaps have some helper tools or instructions with modern approach for doing kernel + rootfs over tftp on BBB? Years ago I was doing that with dnsmasq and nfs version 2, but things changed a little bit since then, so maybe there's a better way now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
The text was updated successfully, but these errors were encountered: