From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uboot on pq2fadsvr
Date: Fri, 1 Jul 2005 08:20:53 -0400 [thread overview]
Message-ID: <42C53525.6030405@smiths-aerospace.com> (raw)
In-Reply-To: <74499824050701044466e21088@mail.gmail.com>
eagle keeper wrote:
> Hi all,
> and sorry for my question. I have not very clear what to do to compile
> uboot for pq2fadsvr with mpc8275 processor. I mean: it is an
> evaluation board supported by uboot isn't it?
> And if so, why doesn't exist a configuration file?
> Is it enought to lighlty modify the 8260ads configuration file? And
> wich entries?
>
> Thank in advance
>
> Lele
In the top level directory, do the following:
$ grep PQ2FADS Makefile
PQ2FADS_config \
PQ2FADS_lowboot_config \
PQ2FADS-VR_config \
PQ2FADS-VR_lowboot_config \
PQ2FADS-ZU_config \
PQ2FADS-ZU_lowboot_config \
PQ2FADS-ZU_66MHz_config \
PQ2FADS-ZU_66MHz_lowboot_config \
I would expect PQ2FADS-VR_config or PQ2FADS-VR_lowboot_config would work
(if you don't have the "lowboot" version, you may want to update your
u-boot copy from the head of CVS).
The lowboot is configured to boot with the Boot Memory Space HWCW[BMS]
set to 1 (i.e. booting at 0x00000000) and is the recommended
configuration. In this case you _must_ use the HRCW from flash rather
than from the FPGA (sorry, I forgot what they called the registers in
the FPGA). I highly recommend using the HRCW from flash and lowboot.
If you live right ;-), you can actually make a "lowboot" and a "high
boot" version and program both into your board. Run with the lowboot
version and, if you screw up u-boot[low] (not that I've ever done that
;-), you can recover by switching the configuration to use the
FPGA-supplied HRCW to "boot high" out of the alternate u-boot image.
gvb
prev parent reply other threads:[~2005-07-01 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 11:44 [U-Boot-Users] uboot on pq2fadsvr eagle keeper
2005-07-01 12:20 ` Jerry Van Baren [this message]
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=42C53525.6030405@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