public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yuke Tian <ytian@bnl.gov>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc83xx U-boot questions
Date: Fri, 26 Sep 2008 15:02:14 -0400	[thread overview]
Message-ID: <48DD31B6.8000306@bnl.gov> (raw)
In-Reply-To: <48DD2F3D.8010100@ovro.caltech.edu>

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) and use the toolset
>> to build RTEMS.
>> 3) Compile a RTEMS application,  tailed for specific BSP.  That is where
>> I get .exe (it is ELF 32-bit MSB executable, PowerPC or cisco 4500,
>> version 1 (SYSV), statically linked, not stripped).  I just want to use
>> the vendor provided U-Boot to download the .exe and get it run. I didn't
>> expect to rebuilt U-Boot, but that might be educational :-)          
>
> Great, that is useful background information in which
> to pose your questions.
>
> It sounds like the Makefile puts a .exe extension on
> the ELF file, and that can safely be ignored.
>
> Does the RTEMs BSP for the MPC8313 board have a README
> that tells you how to boot RTEMs? The ELF file is
> not what will be executed by U-Boot. powerpc-linux-objcopy
> would most likely be used to convert the ELF into a binary
> image.  mkimage might be run on that image to add a header.
> However, I've only used U-Boot with standalone apps and
> Linux, so someone else would have to comment.
> (VxWorks/RTEMs users - any help here?)
>
> It does however sound like you have a reasonable tools
> setup, and the step you are looking for is
>
>  'what is necessary to convert the ELF file to a U-Boot
>   compatible format, and then what U-Boot command is needed
>   to execute it?'
>
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.

Thank you and sorry again for the unclear statement.

> Hopefully someone can help answer that. Please go and re-review
> the U-Boot README file too, there's a chance that there are
> some useful comments in there - now that you know what you
> are looking for.
>
> If someone on the RTEMs list answers your question, please
> post the results back to this list so that the solution
> is available in the archive.
>
> Cheers,
> Dave
>
>

  reply	other threads:[~2008-09-26 19:02 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 [this message]
2008-09-26 19:20                 ` David Hawkins
2008-09-26 20:00                   ` Yuke Tian
2008-09-26 20:14                     ` David Hawkins
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=48DD31B6.8000306@bnl.gov \
    --to=ytian@bnl.gov \
    --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