linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ryser <Peter.Ryser@xilinx.com>
To: Scott Anderson <sanders@mvista.com>
Cc: "Kerl, John" <John.Kerl@avnet.com>, ??? <nari_dhy@nari-china.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: bootstrap of virtex-ii pro eval board ML300
Date: Wed, 04 Jun 2003 09:45:31 -0700	[thread overview]
Message-ID: <3EDE222B.38CBF@xilinx.com> (raw)
In-Reply-To: 384EB15A-953C-11D7-85A6-000A959CAB7C@mvista.com


As Scott describes correctly the preferred method of booting ML300 is through
System ACE CF. System ACE CF reads ACE files and programs the FPGA and the
PowerPC processor through the JTAG chain.

The ACE file is a concatenation of zero or one bitstream with zero to n ELF
files. Typically, it is one bitstream and one ELF file.
On power-up or reset System ACE CF reads the ACE file from the MicroDrive or
CompactFlash card and in a first step programs the FPGA. Then, in a second
step, from the same ACE file, it programs the processor, i.e. similar to an
external debugger it loads code and data contained in the ELF file into the
processor memories, sets the PC to the start address, and starts executing the
program.

For Linux, you will use the Linux kernel as the ELF file.

You can generate ACE files easily by using EDK by running the command
$ xmd genace.tcl implementation/system.bit arch/ppc/boot/images/zImage.embedded
top.ace
in your hardware project directory.

- Peter

-----
Some useful links:
System ACE CF: (http://www.xilinx.com/isp/systemace/systemacecf.htm
EDK: http://www.xilinx.com/edk
ML300: http://www.xilinx.com/ml300


Scott Anderson wrote:

> On Monday, June 2, 2003, at 01:48  PM, Kerl, John wrote:
> > You're saying that the entire zvmlinux.initrd file
> > (2-3 MB, say) is contained in the FPGA bitstream??
>
> I am saying that the entire zImage.embedded (without
> an initrd) is in the FPGA bitstream.  Its root partition
> is an ext2 partition on the IBM MicroDrive.
>
>    Scott
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-04 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 20:48 bootstrap of virtex-ii pro eval board ML300 Kerl, John
2003-06-02 20:53 ` Scott Anderson
2003-06-04 16:45   ` Peter Ryser [this message]
2003-06-05  5:12     ` NARI_DHY
2003-06-05 15:16       ` Peter Ryser
  -- strict thread matches above, loose matches on Subject: below --
2003-06-02 20:52 Kerl, John
2003-06-02 20:41 Kerl, John
2003-06-02 20:49 ` Scott Anderson
2003-06-01  1:14 丁厚永
2003-06-02 20:36 ` Scott Anderson

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=3EDE222B.38CBF@xilinx.com \
    --to=peter.ryser@xilinx.com \
    --cc=John.Kerl@avnet.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nari_dhy@nari-china.com \
    --cc=sanders@mvista.com \
    /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).