Hi Yuke, > 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)
Install the ELDK tools as per my document, and it'll get installed for you. You'll want to install whatever the latest version is ... ELDK-4.2 I think. > --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. Great! > 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 ? Its a binary for the development host (RHEL5), so it will get installed with the ELDK. As a bonus, once you boot a version of RTEMs built using their toolset, you should be able to set the compiler tools to those provided with the ELDK and build RTEMs with that toolset too. Cheers, Dave _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
