From: Peter Ryser <Peter.Ryser@xilinx.com>
To: NARI_DHY <nari_dhy@nari-china.com>
Cc: Peter Ryser <Peter.Ryser@xilinx.com>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: bootstrap of virtex-ii pro eval board ML300
Date: Thu, 05 Jun 2003 08:16:41 -0700 [thread overview]
Message-ID: <3EDF5ED9.9C5A46AF@xilinx.com> (raw)
In-Reply-To: 001101c32b21$1bb5f2d0$4c44900a@hydingnb
System ACE CF.
- Peter
NARI_DHY wrote:
> > 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.
> System ACE CF reads one of the .ace files (at most 8) from the first partition of FAT16/FAT12 fs.
>
> > 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.
> >
> what is this "it"? Is it System ACE CF or other small executive edited by developper?
>
> -hyding
>
> best regards
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-05 15:16 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
2003-06-05 5:12 ` NARI_DHY
2003-06-05 15:16 ` Peter Ryser [this message]
-- 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=3EDF5ED9.9C5A46AF@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nari_dhy@nari-china.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).