From: "Peter Ryser" <Peter.Ryser@xilinx.com>
To: James Campbell <jcampbell@omnigon.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Virtex II Pro/405GP
Date: Tue, 16 Apr 2002 12:44:27 -0700 [thread overview]
Message-ID: <3CBC7F1B.FF597841@xilinx.com> (raw)
In-Reply-To: 1018722334.3710.3.camel@skoll.omnigon.com
James,
I do have some experience with this chip :-)
As you said the Virtex-II Pro FPGA from Xilinx is a chip consisting of
programmable logic, embedded PPC405 core(s) and integrated multi-gigabit
transceivers. The smallest chip (2VP2) has zero CPUs and four 3.125 Gbit IOs.
The biggest chip (2VP50) has four CPUs and sixteen 3.125 Gbit IOs. The CPU is a
PPC405 core, it is not a 405GP. The user selects the peripherals he wants to
have and synthesizes them into the FPGA fabric. This results in a very flexible
solution that allows for a wide range of system design.
The developer's kit comes - besides HW IP and HW/SW design examples - with GNU
tools. These are cross-development tools for Windows and Solaris and consist of
GCC, binutils, GDB and newlib (with backend to the Parallel-3/Parallel-4 cable
attached to the BDM port/JTAG port for non-intrusive software debugging). The
kit also has simple device drivers and stand-alone/demo applications. The kit
does currently not have any direct support for any OS.
Internally, we tested the latest Linux development kernel and found that it
works just fine on our FPGA (2VP7FF672, one CPU, eight 3.125 Gbit IOs).
Regards,
- Peter
PS: For more information about the
- Virtex-II Pro FPGA: http://www.xilinx.com/virtex2pro/
- developer's kit: http://www.xilinx.com/ise/vii_pro/kit.htm
James Campbell wrote:
> Hello,
>
> Does anyone have any experiance with the new Xilinx Virtex II Pro chip?
> It is a million+ gate FPGA device with embedded 405GP cores on the die.
>
> We've recently consolidated our MPC8260 and Virtex II fpgas into this
> single chip, and I'm curious about getting linux up on it.
>
> I know the dev kit comes with GNU software, but I was just curious if
> anyone had any comments on it (good or otherwise).
>
> Cheers,
>
> James Campbell
>
> --
> James Campbell -|- Embedded Systems Engineer
> jcampbell@omnigon.com -|- Omnigon International
> pgp: DA57 E174 4769 1B9D D0DF 73E6 D639 D867 A576 A5AE
> work: +1.760.804.8884 x 332 cell: +1.760.803.8476
> --
> "Computer games don't affect kids; I mean if Pac-Man
> affected us as kids, we'd all be running around darkened
> rooms, munching magic pills and listening to repetitive
> electronic music."
> -Kristian Wilson, Nintendo, Inc. 1989
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-16 19:44 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 [this message]
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
[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=3CBC7F1B.FF597841@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=jcampbell@omnigon.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).