FPGARelated.com
Forums

Xilinx Webpack

Started by RealInfo June 18, 2008
This is a multi-part message in MIME format.

------=_NextPart_000_0010_01C8D134.08D23E80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all=20

What are the limitations of the free Xilinx Webpack ?=20

Does any one know ?=20

Thanks=20
EC

------=_NextPart_000_0010_01C8D134.08D23E80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=3D2>Hi all </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>What are the limitations of the <STRONG><FONT =
size=3D3>free=20
Xilinx Webpack</FONT></STRONG> </FONT><FONT size=3D3><STRONG>?=20
</STRONG></FONT></DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV>
<DIV>Does any one know ? </DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks </FONT></DIV>
<DIV><FONT size=3D2>EC</FONT></DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0010_01C8D134.08D23E80--

RealInfo <therightinfo@yahoo.com> wrote:

> Hi all
> What are the limitations of the free Xilinx Webpack ?
> Does any one know ?
> Thanks > EC
Did you search for that on teh Xilinx website? -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
http://www.xilinx.com/ise/logic_design_prod/webpack.htm

RTWP*,

Austin

* try 'reading the web pages'
"austin" <austin@xilinx.com> wrote in message 
news:g3b5pt$sra1@cnn.xsj.xilinx.com...
> http://www.xilinx.com/ise/logic_design_prod/webpack.htm > > RTWP*, > > Austin > > * try 'reading the web pages'
RTFM would have been appropriate, here, but I understand that your position mandates some self control. 8} Bob -- == NOTE: I automatically delete all Google Group posts due to uncontrolled SPAM ==
"austin" <austin@xilinx.com> wrote in message 
news:g3b5pt$sra1@cnn.xsj.xilinx.com...
> http://www.xilinx.com/ise/logic_design_prod/webpack.htm > > RTWP*,
Some suggest support for SXT; some say there is no such support. Which is correct?
Pete,

Do you have a specific part number?

I will look into it for you.

I know there are some very small omissions/confusions regarding some
parts and/or speed grades.  For these there are "corrective actions"
being worked (to make documentation consistent and accurate).

Austin
"austin" <austin@xilinx.com> wrote in message 
news:g3bhpv$ss01@cnn.xsj.xilinx.com...
> Pete, > > Do you have a specific part number?
I was going to develop using the ML506, so that would be the XC5VSX50T FFG1136. Although the actual product might use the FF665C. http://www.xilinx.com/ise/logic_design_prod/webpack.htm mentions support for SXT, but http://www.xilinx.com/publications/prod_mktg/pn0010867.pdf doesn't.
> I will look into it for you.
Thanks, Pete
Pete,

There are no V5 SX devices in webpack.

Austin
"Pete Fraser" <pfraser@covad.net> wrote in message 
news:6fmdnedUUsw6zsTVnZ2dnUVZ_tfinZ2d@supernews.com...
> > "austin" <austin@xilinx.com> wrote in message > news:g3bhpv$ss01@cnn.xsj.xilinx.com... >> Pete, >> >> Do you have a specific part number? > > I was going to develop using the ML506, so that would be > the XC5VSX50T FFG1136. Although the actual product > might use the FF665C. > > http://www.xilinx.com/ise/logic_design_prod/webpack.htm > mentions support for SXT, but > http://www.xilinx.com/publications/prod_mktg/pn0010867.pdf > doesn't.
I have the webpack installed. I compared the PDF to device selections for V2P, V4, and V5. The Webpack does not support any SXT. The following devices are selectable in Webpack, but missing in the PDF list: XC5VLX20T XC2VP20 VC2VP30 The V4 device list matches available selections. The Spartan3 list also looks correct.
Mike,

Thank you.  I have forwarded this off the the folks responsible.  It is
important that we get the documentation as accurate as possible.

I think the original post concerned itself with "we don't document what
we don't have" which is a more generic problem.  I have two blogs on the
subject in the mill for the Xilinx blog spot:

http://forums.xilinx.com/xlnx/blog?blog.id=pld

So, stay tuned.

Ken's latest blog is pretty interesting, too.

Austin