From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can a BDI2K be used with a bare/erased 834x based system?
Date: Tue, 19 Jun 2007 15:01:09 -0500 [thread overview]
Message-ID: <46783605.2070206@freescale.com> (raw)
In-Reply-To: <864ec6740706191251y3eaef764l67741bbc5a15df6a@mail.gmail.com>
Joe Grisso wrote:
> You know, that's interesting. We're using a BDI2000 with an mpc8343
> here, and have to set the processor to a pre-defined mode to initially
> flash a RCW in, then set it back to loading from local bus after we
> have a valid word programmed. We've followed Freescale's guides on how
> to connect the COP port to the CPU, but have never gotten past
> switching modes to program the RCW.
I'm not a hardware guy, so I can't tell you if you're doing something wrong or even if
Freescale's guides (which I have not read) are complete.
I can say that I haven't had any real problems with the BDI-2000 on any Freescale
reference board I've used. However, creating a BDI-2000 configuration file is tricky,
especially if you're debugging U-Boot. U-Boot will generally not boot on a board that has
had some BDI-2000 pre-programming (i.e. stuff in the [INIT] section). So I usually have
two configuration files: one just for flashing, and the other for debugging early U-Boot.
The one for flashing will initialize the CPU, DDR, and flash memory.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-06-19 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 21:05 [U-Boot-Users] Can a BDI2K be used with a bare/erased 834x based system? Bruce_Leonard at selinc.com
2007-06-15 21:13 ` Timur Tabi
2007-06-15 22:31 ` Dan Malek
2007-06-15 22:36 ` Timur Tabi
2007-06-19 19:51 ` Joe Grisso
2007-06-19 20:01 ` Timur Tabi [this message]
2007-06-19 23:11 ` Wolfgang Denk
2007-06-19 19:46 ` Bruce_Leonard at selinc.com
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=46783605.2070206@freescale.com \
--to=timur@freescale.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