linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Ryser" <Peter.Ryser@xilinx.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Virtex II Pro/405GP
Date: Tue, 16 Apr 2002 14:58:43 -0700	[thread overview]
Message-ID: <3CBC9E93.F2F38B42@xilinx.com> (raw)
In-Reply-To: 1018722334.3710.3.camel@skoll.omnigon.com


Bob,


> 1) What sort of boot-loader did you use?

So far we did not use a boot-loader. We boot the system in one of the following
ways:
- for development by using an external debugger. In our case this is GDB. We
know that other external debuggers that support the PPC405 work, too (see
below).
- for production
    - we include a minimal boot stub in the FPGA bitstream. This initial boot
stub then boots the rest of the system
    - we load the program into flash
    - we use System ACE. System ACE is a companion chip that reads both
bitstream and program from a CompactFlash or MicroDrive, configures the FPGA,
loads the program into memory and boots the system. System ACE acts then as an
interface to the file system on the CompactFlash/MicroDrive.
    - we are working on PPCBoot


> 2) Will the GDB debugger work with the Multilinx cable or 3rd party
> emulators like the Abatron BDI-2000.

GDB currently works with the Parallel-3 and Parallel-4 cable. Multilinx is not
supported and will never be (performance). Additional external debuggers may be
added as backends for GDB.

3rd party debuggers that we know to be working are (not an exclusive list)
- VisionProbe-II from Wind River
- VisionICE from Wind River
- Abatron BDI-2000



> 3) Is Xilinx going to make the work of porting Linux to the platform
> available to the general community?

Yes.

>  Maybe you could put the source on
> your web site or sell a Linux version of the developer's kit.

Watch out for announcements.

> 4) Will Xilinx be making a reference platform or evaluation board
> available?

Yes, this work is in progress but is not yet publicly announced. You can expect
an evaluation board to be available in Q3.

> As you can see I am eager to get as much info as possible on this.  I
> have a project that I am currently working on that this would be perfect
> for.  Any info you can point me to would be helpfull.

We are willing to give as much info as we can. But, since some of this has not
been announced yet I cannot go into all the details. Please also consider
getting into contact with your closest Xilinx representative or FAE to get more
information and to tell them about your projects.

- Peter


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

  parent reply	other threads:[~2002-04-16 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 18:25 Virtex II Pro/405GP James Campbell
2002-04-16 19:44 ` Peter Ryser
2002-04-16 20:49   ` James Campbell
2002-04-16 22:03     ` Peter Ryser
2002-04-16 22:54       ` James Campbell
2002-04-16 21:58 ` Peter Ryser [this message]
     [not found] <2F62FF8D9BD6F647BD924E3889D0F6077F7BB0@prex1-fy.preston.cmst.csiro.au>
2002-04-18 15:40 ` James Campbell

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=3CBC9E93.F2F38B42@xilinx.com \
    --to=peter.ryser@xilinx.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).