From: Wolfgang Denk <wd@denx.de>
To: Bryan Rittmeyer <bryan@ixiacom.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: bootloader for deeply embedded 405CR
Date: Tue, 10 Apr 2001 23:16:44 +0200 [thread overview]
Message-ID: <20010410211649.9C41328417@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 10 Apr 2001 13:44:26 PDT." <3AD370AA.93F59622@ixiacom.com>
*** Please send PPCBoot related messages to the PPCBoot mailing list ***
In message <3AD370AA.93F59622@ixiacom.com> you wrote:
>
> > For the Walnut it should be a simple thing to do:
> > make WALNUT405_config
> > make
>
> I have built a CVS ppcboot as you suggest, however
> it appears to expect being burned into flash
> memory.
Right. That's what most of the people do.
> What I would like to do is GDB-load an ELF ppcboot
> into the Walnut's 32MB SDRAM mapped at address 0,
> then execute it in place. Then I want to GDB load a
> kernel at another higher address, and use ppcboot
> to boot it. Is this already possible or will I have
> to modify Makefiles, linker scripts, and possibly
> code?
You have to modify the link address at least; but most probably you
have to modify other code as well - for instance to prevent the
exception handlers to be installed, etc.
Why don't you do what everybody does, and write the image to flash?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Here's a fish hangs in the net like a poor man's right in the law.
'Twill hardly come out." - Shakespeare, Pericles, Act II, Scene 1
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-10 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010407220120.85706281E2@denx.denx.de>
2001-04-10 20:44 ` bootloader for deeply embedded 405CR Bryan Rittmeyer
2001-04-10 21:16 ` Wolfgang Denk [this message]
2001-04-07 20:09 Bryan Rittmeyer
2001-04-07 20:50 ` Wolfgang Denk
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=20010410211649.9C41328417@denx.denx.de \
--to=wd@denx.de \
--cc=bryan@ixiacom.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ppcboot-users@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.