-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
U-Boot section: Wrong command? #4
Comments
you have to change
to
|
@csukuangfj That's what I meant to type, actually |
hey i was just working through the arm-baremetal-ebook.pdf and came across this same issue. no biggie i thought i'd just bring it to your attention. excellent project tyvm |
^^ This project is super sweet. |
u-boot-2018.09/tools/mkimage -A arm -C none -T kernel -a 0x60000000 -e 0x60000000 -d better-hang.elf bare-arm.uimg later in test it's not ELF, but BIN |
Your suggestion work but i have now this problem... Booting kernel from Legacy Image at 60000000 ...Image Name: resetting ... |
Trying to run in qemu, and got the same message: boot sequence:bootm 0x60000000 Booting kernel from Legacy Image at 60000000 ...Image Name: resetting... With u-boot printenv gives:kernel_addr_r=0x60100000 I think it is supposed to start. Is it related somehow to fdtcontroladdr? or fdtfile? |
No, with the u-boot version explicitely mentioned in the doc (2018.09), it works. |
I am facing the same issue Booting kernel from Legacy Image at 60000000 ...Image Name: running ubuntu on Vbox.
|
Hi,
in doc/03_bootloader.md, you say to modify the U-Boot config, specifically setting
CONFIG_BOOTCOMMAND="run mmc_elf_bootcmd"
, while in the next paragraph, you add a bootcommand / environment variablebootcmd_bare_arm
.Is this intended? Shouldn't it be
CONFIG_BOOTCOMMAND="run bootcmd_bare_arm"
?Because this way, when I start U-Boot in qemu, I get an error
## Error: "mmc_elf_bootcmd" not defined
, i.e. the autoboot doesn't workThe text was updated successfully, but these errors were encountered: