From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc83xx U-boot questions
Date: Fri, 26 Sep 2008 14:33:42 -0400 [thread overview]
Message-ID: <48DD2B06.2060201@ge.com> (raw)
In-Reply-To: <48DD245D.5080604@ovro.caltech.edu>
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, so it looks like
Yuke's toolset is braindamaged.
<http://www.rtems.com/wiki/index.php/Quick_Start>
Example:
bash-3.1$ sparc-rtems4.9-gdb `find . -name ticker.exe`
(bleah!)
The RTEMS example is running on a simulator via gdb, which is a far cry
from running on real hardware, booting either on bare metal (very big
ouch) or using u-boot to start it (much less ouch - I would start by
running your RTEMS build as a u-boot "application" - that gets you
things like fairly painless serial support).
Note to Yuke: this will be a learning experience for you - please keep
us informed so we can learn vicariously with you. I'm not aware of
anybody using u-boot to boot RTEMS, so you may have some useful stuff
when you get to the end of your journey. We will help as much as we can...
> Anyway, a good suggestion is to install ELDK and rebuild
> U-Boot and update it, even get Linux booted. It may not be
> your main goal, but consider it educational :)
Note to Yuke: you should also have a JTAG debugger to recover from
failed u-boot reprogramming if you rebuild and reflash u-boot. You may
want to use a JTAG debugger even if you *don't* reflash u-boot.
Note that the Abatron BDI3000 supports "gdb remote target".
<http://www.abatron.ch/products/bdi-family/bdi3000.html>
<http://www.abatron.ch/products/debugger-support/gnu-support.html>
I think most of the competitors do too now, but I don't know.
Definitely ask about their linux (as the host) and gdb (remote target
over ethernet) support before you buy.
USB-attached JTAG debuggers tend to be Windows-only. Bleah! On a
positive note, I have a whole collection of single-board computers
(curiously labeled "USB TAP" ;-) with a MPC866, usb, and JTAG interface.
If only I had the time to port u-boot to them and make them useful... :-D
> Cheers,
> Dave
Best regards,
gvb
next prev parent reply other threads:[~2008-09-26 18:33 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 [this message]
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
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=48DD2B06.2060201@ge.com \
--to=gerald.vanbaren@ge.com \
--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