From: Alessandro Rubini <rubini-list@gnudd.com>
To: nvbolhuis@aimvalley.nl
Cc: linuxppc-dev@ozlabs.org, u-boot@lists.denx.de
Subject: Re: [U-Boot] NAND only (no NOR)
Date: Tue, 2 Dec 2008 10:31:14 +0100 [thread overview]
Message-ID: <20081202093114.GA25146@mail.gnudd.com> (raw)
In-Reply-To: <4934F7FC.2030105@aimvalley.nl>
Disclaimer: I'm not running ppc these days
> However, having no NOR flash means:
> - NAND should be programmable via JTAG (BDI3000 doesn't support
> this, Lauterbach/trace32 does)
My personal preference for bringing up a new board is placing u-boot
in RAM using the available information to setup SDRAM from the jtag
tool (or, better, place the initial boot code the manufacturer give
you in static memory, and jump to is with a breakpoint in the right
place).
While my debugger is able to write flash, I've always found it easier
to do that from u-boot itself. Besides, I can fix my u-boot in RAM
without the lengthy erase-reprogram cycles.
If you work like this, it's irrelevant whether it is nor, nand or dataflash
or whatever, as long as u-boot is able to manage it.
hope this helps
/alessandro
next prev parent reply other threads:[~2008-12-02 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 8:55 NAND only (no NOR) Norbert van Bolhuis
2008-12-02 9:31 ` Alessandro Rubini [this message]
2008-12-03 2:50 ` Sean MacLennan
2008-12-03 5:48 ` [U-Boot] " Stefan Roese
2008-12-03 6:38 ` Sean MacLennan
2008-12-03 7:40 ` Trent Piepho
2008-12-03 13:57 ` Leon Woestenberg
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=20081202093114.GA25146@mail.gnudd.com \
--to=rubini-list@gnudd.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nvbolhuis@aimvalley.nl \
--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;
as well as URLs for NNTP newsgroup(s).