From: annamaya <annamaya@yahoo.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux using a PlanetCore BootLoader
Date: Mon, 11 Oct 2004 11:38:28 -0700 (PDT) [thread overview]
Message-ID: <20041011183828.93046.qmail@web53803.mail.yahoo.com> (raw)
In-Reply-To: <20041011181553.GC6871@smtp.west.cox.net>
Oops! Thanks for pointing that blooper. I am so used
to dealing with the U-Boot header of 64 bytes that I
misread the ELF header size as 64 bytes instead of 64
KBytes.
Anyways, it looks like I am much farther that I have
ever been before. Now, I see that the PC is stuck at
some address that I am not sure what to make off. Is
this before the MMU has been turned on? Also, it looks
like my BDI is not showing the "Debug entry cause"
correctly.
BDI>info
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : <reserved 0>
Current PC : 0x00401890
Current CR : 0x20002024
Current MSR : 0x00002040
Current LR : 0x0040084c
I am not sure how I can map this address to some
address in the kernel. Could this be due to the
unavailability of bdinfo? Do I have to put in support
in the kernel to pass bdinfo? Thanks much.
--- Tom Rini <trini@kernel.crashing.org> wrote:
> On Mon, Oct 11, 2004 at 10:50:54AM -0700, annamaya
> wrote:
>
> > I loaded a zImage into address 0x100000 in RAM and
> > verified that this was indeed an ELF file. I then
> said
> > "go 0x100040" which would start executing the code
> > after skipping the 64 bytes of ELF header. But
> this is
> > what I see happen.
>
> It's 64Kilobytes, so you'd want 0x00110000. You
> also might be loading
> yourself a bit too low. The default link address is
> (assuming this is
> 2.4 and I'm still recalling right) 0x00200000, so
> you might as well load
> things there.
>
> --
> Tom Rini
> http://gate.crashing.org/~trini/
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
next prev parent reply other threads:[~2004-10-11 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 16:04 Booting Linux using a PlanetCore BootLoader annamaya
2004-10-11 16:38 ` Dan Malek
2004-10-11 17:33 ` annamaya
2004-10-11 18:52 ` Dan Malek
2004-10-11 17:50 ` annamaya
2004-10-11 18:15 ` Tom Rini
2004-10-11 18:38 ` annamaya [this message]
2004-10-11 18:47 ` Tom Rini
2004-10-11 21:18 ` annamaya
2004-10-11 21:44 ` Tom Rini
2004-10-11 22:52 ` annamaya
2004-10-11 18:55 ` Dan Malek
[not found] <20041012003339.B1EB92BDDA@ozlabs.org>
2004-10-12 1:12 ` Sam Song
2004-10-12 21:02 ` annamaya
2004-10-12 21:26 ` Dan Malek
2004-10-13 14:49 ` annamaya
2004-10-13 16:07 ` Dan Malek
2004-10-13 18:06 ` annamaya
2004-10-13 19:21 ` annamaya
2004-10-13 21:19 ` Dan Malek
2004-10-13 21:23 ` annamaya
2004-10-13 22:47 ` Dan Malek
2004-10-14 15:53 ` annamaya
2004-10-14 16:45 ` Dan Malek
2004-10-14 18:10 ` annamaya
2004-10-14 20:54 ` Wolfgang Denk
2004-10-16 0:16 ` Sam Song
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=20041011183828.93046.qmail@web53803.mail.yahoo.com \
--to=annamaya@yahoo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).