Port-arm archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Debugging efiboot
OK, it seems that the solution is to avoid efiboot altogether. The following u-boot commands boot the kernel successfully:
setenv bootargs "root=ld0a"
setenv bootcmd "fatload mmc 0:1 $kernel_addr_r netbsd-GENERIC.ub; fatload mmc 0:1 $fdt_addr_r dtb/am335x-boneblack.dtb; bootm $kernel_addr_r - $fdt_addr_r"
run bootcmd
However, I cannot yet get that to work automatically. The u-boot environment is a labyrinth of branches covering lots of cases.
Next task: determine what happens when the main entry point in the default environment, bootcmd, is run and inject the commands above into the sequence.
Any suggestions to streamline that process are welcome.
Thanks.
Brook
Home |
Main Index |
Thread Index |
Old Index