UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor bilbaena
Visitor
4,510 Views
Registered: ‎12-15-2011

Creating a project for XC4VSX25, but using the 35

Jump to solution

Theoretical question:

 

Say I didn't want to upgrade to the Logic Edition and just wanted to use the WebPACK.

If I have created a project in the Xilinx ISE that has the XC4VSX25 selected, but have a 35...

Would I be able to pull this off? (provided that my code does not excede the specs of a 25)

 

Is the XC4VSX35 strictly not supported by the WebPACK edition because the ISE doesn't know how to configure it?

Or could the ISE try to configure a 35 thinking it was a 25?

 

Edit ----- Not trying to cheat the system here. We will be upgrading if necessary.

 

Thanks for your time,

Anton

0 Kudos
1 Solution

Accepted Solutions
Advisor eilert
Advisor
5,768 Views
Registered: ‎08-14-2007

Re: Creating a project for XC4VSX25, but using the 35

Jump to solution

Hi Anton,

simply no.

 

The resulting bitfile will not be accepted by a different device.

Apart from device identifiers, the contents just won't match the different structure.

 

Have a nice synthesis

  Eilert

 

0 Kudos
2 Replies
Advisor eilert
Advisor
5,769 Views
Registered: ‎08-14-2007

Re: Creating a project for XC4VSX25, but using the 35

Jump to solution

Hi Anton,

simply no.

 

The resulting bitfile will not be accepted by a different device.

Apart from device identifiers, the contents just won't match the different structure.

 

Have a nice synthesis

  Eilert

 

0 Kudos
Visitor bilbaena
Visitor
4,491 Views
Registered: ‎12-15-2011

Re: Creating a project for XC4VSX25, but using the 35

Jump to solution
Eilert,

Thanks for the quick reply.

I assumed there was no way... the different FPGAs must have different architectures, different pin locations etc.

Thanks again,
Anton
0 Kudos