From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] minimum bdi config to read flash on 85xx
Date: Thu, 06 Sep 2007 15:12:29 -0700 [thread overview]
Message-ID: <46E07B4D.4010803@ovro.caltech.edu> (raw)
In-Reply-To: <46E06F0C.4080301@qstreams.com>
Hi Ben,
> I'm not sure if this has been mentioned or not.
> You should be able to read/write the flash from
> the BDI-2000, regardless of whether you connect
> the LA or LBA address bits. The difference comes
> into play when you want to boot from the flash chip.
> During the very early boot process, only the special
> LSbits toggle.
Yeah, I'd read that in some corner of the processor
reference manual, and fired up the MDS board with a
logic analyzer just to confirm it. I wondered at the
time how many people would miss that subtle requirement!
> On one spin of our board we missed this as well, and
> had to do some funny business with an I2C EEPROM to boot
> the board. Thankfully it was easy with our CPU (MPC8349)
> because it only involved programming a couple of
> configuration words and no UPM programming like Dave H.
> has suggested.
Ah-ha, so it is possible - cool :)
(crossed fingers it won't happen to me though ...)
> Have you tried asking Freescale for help through their
> website? I've found their tech support in these matters
> to be responsive and useful.
Yep, I second that. Freescale's design support is
great. Sometimes they confirm what you don't want to
hear ... but they do respond quickly :)
Cheers,
Dave
next prev parent reply other threads:[~2007-09-06 22:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 18:11 [U-Boot-Users] minimum bdi config to read flash on 85xx robert lazarski
2007-09-04 18:26 ` David Hawkins
2007-09-04 19:45 ` Ben Warren
2007-09-04 20:50 ` robert lazarski
2007-09-04 21:12 ` Ben Warren
2007-09-04 21:15 ` David Hawkins
2007-09-05 15:05 ` robert lazarski
2007-09-05 16:35 ` David Hawkins
2007-09-05 19:53 ` robert lazarski
2007-09-05 21:19 ` David Hawkins
2007-09-06 21:03 ` Luiz Neto
2007-09-06 21:20 ` Ben Warren
2007-09-06 22:12 ` David Hawkins [this message]
2007-09-06 22:06 ` David Hawkins
2007-09-07 1:41 ` Luiz Neto
2007-09-07 2:00 ` David Hawkins
[not found] ` <50d8dde80709072035j3c066e81wab5216e78d47f89c@mail.gmail.com>
2007-09-08 3:46 ` David Hawkins
2007-09-12 17:23 ` robert lazarski
2007-09-12 18:00 ` David Hawkins
2007-09-12 18:13 ` Jerry Van Baren
2007-09-12 18:23 ` David Hawkins
2007-09-12 18:29 ` David Hawkins
2007-09-12 18:39 ` Jerry Van Baren
2007-09-12 18:44 ` David Hawkins
2007-09-12 19:19 ` robert lazarski
2007-09-12 19:41 ` David Hawkins
2007-09-12 20:06 ` Jerry Van Baren
2007-09-12 20:16 ` David Hawkins
2007-09-12 20:40 ` Jerry Van Baren
2007-09-12 21:39 ` David Hawkins
2007-09-14 18:21 ` robert lazarski
2007-09-14 18:34 ` Jerry Van Baren
2007-09-14 18:43 ` Ben Warren
2007-09-14 19:12 ` David Hawkins
2007-09-14 20:05 ` robert lazarski
2007-09-14 20:14 ` Ben Warren
2013-05-27 13:01 ` [U-Boot] " Monica
2013-05-27 13:37 ` Fabio Estevam
2013-05-28 5:35 ` Monica
2007-09-14 20:16 ` [U-Boot-Users] " Jerry Van Baren
2007-09-14 20:34 ` Leon Woestenberg
2007-09-14 21:04 ` Scott Mann
2007-09-14 20:31 ` David Hawkins
2007-09-06 22:43 ` Clemens Koller
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=46E07B4D.4010803@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--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