Hi David,
After email some people in RTEMS community, I got the solutions:
--- To prepare the U-boot image for RTEMS application (with os built in for RTMES) in host pc (RHEL5) powerpc-rtems4.9-objcopy -O binary test.ext test.bin (the powerpc-rtems4.9-objcopy is provided from rtems toolset) gzip -9 test.bin mkimage -A ppc -O rtems -T kernel -C gzip -a 100 -e 10000 -n "RTEMS Test" -d test.bin test.img (I am still looking for mkimage software)
--To load through U-boot (pre-installed by board vendor) setenv ethact TSEC1 (this board has 6 ethernet port, choose one) setenv ipaddr 123.345.123.1 (board ip) setenv serverip 123.345.123.2 (tftp server ip) tftp 1000000 test.img (load image to this RAM address) bootm (then run)
This is the recommended step to boot the board into RTEMS through U-boot.
I guess to get mkimage for this board, I need to rebuilt U-boot anyway. Or this mkimage is a standard utility from U-boot ?
Thanks for the discussion.
Yuke
David Hawkins wrote:
Hi Yuke,
That is exactly what I want now (I need to pick up U-boot later :-) ). I will try powerpc-linux-objcopy and let you know.
Well, powerpc-linux-object copy will give you a binary blob, but thats useless to you unless you know how to use/load the blob.
I'm a little confused as to why you say you have a BSP, and none of this is explained in the BSP.
Where did this BSP come from? Got a link?
Cheers, Dave