From: Dan Malek <dan@netx4.com>
To: bsimon@ctam.com.au
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc embedded boot problems.
Date: Tue, 14 Dec 1999 23:11:04 -0500 [thread overview]
Message-ID: <385714D8.8AD74656@netx4.com> (raw)
In-Reply-To: 38570544.476D42C9@ctam.com.au
Brendan Simon wrote:
> What I don't understand is why it starts to boot (ie. uncompresses into
> memory) but then nothing happens.
Could be lots of things. I hope you can reset your board
without losing memory. If so, find the address of 'log_buf'
in the System.map and dump it out (convert the virtual address
to physical by masking the upper few bits). This is the staging
area for kernel printk messages, and lots of information is
here before the console is enabled.
> .... Are there things that the kernel expects
> to be setup besides the flash/dram memory ?
Considering you are doing your own UPM, the Linux kernel will
find lots of timing errors with it. It enables the MMU and
caches very early, so the bus timing will see something new
for the first time. I hope you are peforming the proper cache
initialization sequence and setting all of the necessary
processor registers in the boot rom.
You can disable the caches in arch/ppc/kernel/head.S. Try that.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-15 4:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 22:12 linuxppc embedded boot problems Brendan Simon
1999-12-15 2:58 ` Dan Malek
1999-12-15 3:04 ` Brendan Simon
1999-12-15 4:11 ` Dan Malek [this message]
1999-12-15 3:51 ` Brendan Simon
1999-12-15 19:04 ` Dan Malek
1999-12-15 22:49 ` linuxppc-embedded: NFS boot options Brendan Simon
-- strict thread matches above, loose matches on Subject: below --
1999-12-15 5:55 linuxppc embedded boot problems Brian Kuschak
1999-12-15 19:06 ` Dan Malek
1999-12-15 22:56 ` Brendan Simon
1999-12-16 5:03 ` Dan Malek
1999-12-16 4:08 Brian Kuschak
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=385714D8.8AD74656@netx4.com \
--to=dan@netx4.com \
--cc=bsimon@ctam.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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).