U-boot is normally used as Stage2 bootloader and used to setup cpu timmings and sdram. Stage1 bootloader is normally part of the hardware and it is loaded and executed from On Chip RAM (OCRAM).
The process of building u-boot is similar to build the kernel itself. Set a cross compile toolchain, make a .config using an already available defconfig and make to build. Normally (on imx at least) a little header is wrapped at the beginning of the binary and that is specific to your model DRAM configuration.
I don't know much about Kindle but the sources of Kobo's uboot ship with a helper script that
does exactly the steps mentioned above.
Quote:
|
Originally Posted by knc1
QEMU is a 'single program' loader, stock QEMU can not load two programs (u-boot and kernel).
|
I had no idea, I have no CS background and never played with QEMU but sounds to me as a normal bootstrap: stage1/qemu loads stage2 and jumps there, stage2 loads kernel and jumps there and so on. In any case I would like to see the link as my search skills suck and I can't found such info. Thanks in advance
But yeah, OP has a difficult task at hand. Good luck and keep us informed
edit: I found a
interesting link about the topic. Basically you can try the same but using a different device configuration. It seems that
i.MX6 Dual Lite SABRE is available on qemu 2 and should be a good place to start. Use that instead of "versatile"