From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc83xx U-boot questions
Date: Fri, 26 Sep 2008 13:14:36 -0700 [thread overview]
Message-ID: <48DD42AC.1010500@ovro.caltech.edu> (raw)
In-Reply-To: <48DD3F4A.5030500@bnl.gov>
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
next prev parent reply other threads:[~2008-09-26 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 16:22 [U-Boot] mpc83xx U-boot questions Yuke Tian
2008-09-26 16:56 ` David Hawkins
2008-09-26 17:07 ` Yuke Tian
2008-09-26 17:24 ` David Hawkins
2008-09-26 17:37 ` Jerry Van Baren
2008-09-26 17:55 ` Yuke Tian
2008-09-26 18:05 ` David Hawkins
2008-09-26 18:33 ` Jerry Van Baren
2008-09-26 18:51 ` Yuke Tian
2008-09-26 18:55 ` David Hawkins
2008-09-26 18:05 ` Jerry Van Baren
2008-09-26 18:32 ` Yuke Tian
2008-09-26 18:51 ` David Hawkins
2008-09-26 19:02 ` Yuke Tian
2008-09-26 19:20 ` David Hawkins
2008-09-26 20:00 ` Yuke Tian
2008-09-26 20:14 ` David Hawkins [this message]
2008-09-26 18:55 ` Jerry Van Baren
2008-10-04 1:42 ` [U-Boot] U-boot Saveenv question Suresh Bhaskaran
2008-10-05 15:55 ` Andrejs Cainikovs
2008-10-06 17:02 ` Suresh Bhaskaran
2008-10-06 17:06 ` Jerry Van Baren
2008-10-06 18:17 ` Suresh Bhaskaran
2008-10-07 0:57 ` [U-Boot] U-boot Saveenv question --> final tested solution Suresh Bhaskaran
2008-10-07 22:24 ` Jerry Van Baren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48DD42AC.1010500@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox