Hi Yuke,
What I am doing is to try to load RTEMS
Ok, that info helps.
It has a BSP for this board.
Thats good.
All the tools I used are targeting powerpc and tailed
for this board.
and those tools came from where?
But the final executable format is .exe. I am not sure if
this format
Yuke Tian wrote:
Hi David,
Thank you for your kind response. What I am doing is to try to load the
RTEMS (a kind of open source real time operating system) image to the
board. It has a BSP for this board. All the tools I used are targeting
powerpc and tailed for this board. But the final
Hi Yuke,
Sorry to ask the stupid question. I did study the RTEMS for a while and
am sure the tool set are correct (from ftp://www.rtems.com), otherwise
they will not build RTEMS. All the tools and development are done in
linux (RHLE5). I just got this board using U-boot and not sure about
Yuke Tian wrote:
Hi,
Sorry to ask the stupid question. I did study the RTEMS for a while and
am sure the tool set are correct (from ftp://www.rtems.com), otherwise
they will not build RTEMS. All the tools and development are done in
linux (RHLE5). I just got this board using U-boot and
Thanks.
To be specific, I followed the steps to build RTEMS:
1) Download a set of toolsets (gcc-4.2.3, binutils-2.18, newlib-1.16 and
RTEMS specific patches) and build them or use the pre-built rpm toolset
for RHLE5.
2) Download the RTEMS (4.9.0 for the latest version) and use the toolset
to
David Hawkins wrote:
Hi Yuke,
[snip]
You say that the development is done with RHLE5, but
then that a .exe is created. That seems to be a conflicting
statement. Perhaps you could explain ... are you running
the RTEMs tools under Wine??
The RTEMS quickstart example uses an .exe extension,
Jerry Van Baren wrote:
David Hawkins wrote:
Hi Yuke,
[snip]
You say that the development is done with RHLE5, but
then that a .exe is created. That seems to be a conflicting
statement. Perhaps you could explain ... are you running
the RTEMs tools under Wine??
The RTEMS quickstart example
Yuke Tian wrote:
Thanks.
To be specific, I followed the steps to build RTEMS:
1) Download a set of toolsets (gcc-4.2.3, binutils-2.18, newlib-1.16 and
RTEMS specific patches) and build them or use the pre-built rpm toolset
for RHLE5.
OK.
2) Download the RTEMS (4.9.0 for the latest
David Hawkins wrote:
Hi Yuke,
To be specific, I followed the steps to build RTEMS:
1) Download a set of toolsets (gcc-4.2.3, binutils-2.18, newlib-1.16 and
RTEMS specific patches) and build them or use the pre-built rpm toolset
for RHLE5.
2) Download the RTEMS (4.9.0 for the latest version)
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
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)
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
12 matches
Mail list logo
