Hi,
Please correct me if I am wrong. From what I understand, u-boot itself is
relocated to RAM by calling
the procedure: relocate_code at the end of the procedure: board_init_f .
There is a need for me to load an executable to a static address (say,
0x82xx_xxxx) in RAM such that
control could be passed to this executable from U-boot. How could this be
accomplished, with the
limitation that:
the executeable is to be downloaded together with u-boot.bin, zImage, ramdisk
and other images
that are to be be executed before u-boot etc, as a blob onto the eMMC?
Could u-boot be used to relocate the said executable to the address:
0x82xx_xxxx? u-boot does not
have the knowledge where this executable resides in eMMC. This also means that
it would not be possible
to use u-boot command: cp (memory copy) to do the relocation, as the command
itself requires knowledge
of the source address.
>From a u-boot user group, I have learned that by using the command: "mkimage"
>it would be able to package a raw
image into a blob understood by u-boot. I have discovered a few "mkimage"
files, such as mkimage.o, mkimage, other
than mkimage.c, mkimage.h and mkimage.l. But, I soon found out that I could not
execute the command: mkimage.
What should I do in order to execute the command? There isn't a file called
mkimage.bin generated!!
Any comment or suggestions would be greatly appreciated.
Thanks,
Ivan
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
