From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI2000 with ppc440epx.
Date: Thu, 1 May 2008 14:34:51 +0200 [thread overview]
Message-ID: <200805011434.52032.sr@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C0364A9BE@ehost011-3.exch011.intermedia.net>
On Wednesday 30 April 2008, Leonid wrote:
> I have some problem with AMCC PPC440epx CPU when it boots from NAND.
>
> I am using sequoia.cfg file. If I do "reset halt" on BDI and then "go",
> CPU doesn't boot. If I do "reset run" it boots OK.
>
> That points on some potential problem in .cfg file. OK, I removed entire
> [INIT] section, but situation didn't change.
Yes.
> Moreover, when I set breakpoint to the function which surely is invoked
> and do "reset run", I don't hit breakpoint (CPU boots till the end).
Right. This is because of the icache being used for the code read from NAND by
the IPL (see below).
> Do you have any idea what I may be doing wrong?
Not really. It is not easy to debug a NAND booting system. This is because of
the 4k code being loaded into the icache and run from there. What I am always
doing while debugging NAND booting 4xx systems is, integrate some infinite
loops after the suspicious code. Or just load different values into one
(unused) register in the very early starting phase to see how far the PPC
gets.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-05-01 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:02 [U-Boot-Users] BDI2000 with ppc440epx Leonid
2008-05-01 12:34 ` Stefan Roese [this message]
2008-05-01 15:31 ` Leonid
2008-05-02 7:19 ` Stefan Roese
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=200805011434.52032.sr@denx.de \
--to=sr@denx.de \
--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