From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: "ppcdev" <linuxppc-dev@ozlabs.org>
Subject: Re: Calling the kernel from a mini-bootloader
Date: Tue, 22 Jul 2008 12:49:49 +0200 [thread overview]
Message-ID: <048601c8ebe8$acbfcc50$ad289e86@LPSC0173W> (raw)
In-Reply-To: 007a845ba2b60b02a256b58632490b27@bga.com
Thank you Milton for the detailed explanation. It'll take me quite a while
to digest it.
As a follow up to my previous messages, I now have a working kernel and a
working bootloader... but not when they are both together.
Case in point:
- load zImage.elf to DRAM 0x400000 with JTAG debugger. Run it. It runs fine.
- Load Bootloader.elf to BRAM 0xFFFF0000 with JTAG debugger. Run it. It runs
fine (but it doesn't do much yet).
- Now load both of the previous ones, and have the bootloader perform a jump
to kernel:
typedef void tFunc(void);
((tFunc *)0x400000)();
The kernel seems to start:
loaded at: 00400000 004EA19C
board data at: 004E8120 004E819C
relocated to: 0040405C 004040D8
zimage at: 00404E48 004E7A7E
avail ram: 004EB000 08000000
Linux/PPC load: console=ttyUL0,115200 rw root=/dev/nfs ip=bootp
Uncompressing Linux...done.
Now booting the kernel
But then it hangs for exactly 3 minutes, nothing on the serial port, before
the bootloader restarts.
Why should the behavior be different whether it's started from the debugger
or from my bootloader ?
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2008-07-22 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 16:14 Calling the kernel from a mini-bootloader Milton Miller
2008-07-18 3:47 ` David Gibson
2008-07-18 17:47 ` Milton Miller
2008-07-18 8:43 ` Guillaume Dargaud
2008-07-18 18:38 ` Milton Miller
2008-07-22 10:49 ` Guillaume Dargaud [this message]
2008-07-22 16:01 ` Guillaume Dargaud
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 13:22 Guillaume Dargaud
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='048601c8ebe8$acbfcc50$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@ozlabs.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).