From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Low-boot configuration for MPC8272ADS
Date: Wed, 02 Nov 2005 17:20:06 -0500 [thread overview]
Message-ID: <43693B96.3000208@smiths-aerospace.com> (raw)
In-Reply-To: <436935CE.9080707@rftechnology.com.au>
Dmytro Bablinyuk wrote:
>>
>> Yesterday I was on holidays, so "monday morning effects" also in
>> wednesday. The link to my submmit to Wolfgang with the patch
>>
>> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/19108
>>
>
> Hi Alex,
> Sorry for delay, in Sydney we have 8.40am - just came to work.
> YES, IT'S WORKING (after applying your patch) WITH AND WITHOUT BDI!!
>
> Thank you very much Alex and thank you very much Yuli - you were right
> all my problems were due to wrong value of HRCW
>
> One more question, so it looks like BDI was depending on HRCW - on
> target board we would have a blank flash - how do we burn it using BDI
> (at first time we will not have a HRCW in it)?
>
> > As you say "the classical" ads8272 without BCSR, do you mean same
> > flash module, SDRAM specs, phytters, etc.?
> Apart from flash, everyting else will be the same. We will use P30 flash
> from Intel. I expected that I will need to do some work on it. Most of
> the worries were about BCSR. So, I just was wondering how easy would be
> to make u-boot not to use BCSR. eg. CS0 - flash, CS1 - SDRAM ...
For blank flash, you need to pull up the RSTCONF* line (8260UM 5.4.2.1
"Single MPC8260 with Default Configuration") which will set your HRCW to
all zeros rather than read it from memory (I'm assuming you are not
implementing the BCSR).
This will require a different BDI2000 config file because the ISB will
be set to 0x0000_0000 - if the first line in your special BDI config
file sets the ISB back to your prefered value (0xF000_0000?), you should
be able to leave all the rest of your config file the same.
At this point, you should be able to program flash. After programming
flash, I go back to normal mode (RSTCONF* pulled low) and _power cycle_
the board. Note that the HRCW is only read on a power cycle, not on a
software reset.
YMMV (Your Magic May Vary ;-)
gvb
next prev parent reply other threads:[~2005-11-02 22:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 8:28 [U-Boot-Users] Re: Low-boot configuration for MPC8272ADS Bastos Fernandez Alexandre
2005-11-02 9:56 ` Dmytro Bablinyuk
2005-11-02 14:59 ` Alexandre BASTOS
[not found] ` <12783.4063292996$1130942654@news.gmane.org>
2005-11-02 21:55 ` Dmytro Bablinyuk
2005-11-02 22:20 ` Jerry Van Baren [this message]
2005-11-02 22:58 ` Dmytro Bablinyuk
2005-11-02 23:14 ` Jerry Van Baren
2005-11-02 23:43 ` Dmytro Bablinyuk
2005-11-02 23:33 ` Wolfgang Denk
2005-11-02 23:49 ` Dmytro Bablinyuk
2005-11-03 0:05 ` Wolfgang Denk
2005-11-03 0:22 ` Dmytro Bablinyuk
2005-11-03 1:41 ` Dmytro Bablinyuk
2005-11-02 22:20 ` Dan Malek
2005-11-04 3:39 ` [U-Boot-Users] Re : " Sam Song
2005-11-04 17:39 ` Dan Malek
2005-11-08 4:44 ` Sam Song
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 3:16 [U-Boot-Users] " Dmytro Bablinyuk
2005-11-02 5:39 ` [U-Boot-Users] " Dmytro Bablinyuk
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=43693B96.3000208@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--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