Spartan® Family FPGAs

[ustaudinger]

Hello everybody,

I use the following command on my linux box to build my blinker.v file. 

echo "run -ifn blinker2.v -ifmt Verilog -p x3cs700an -ofn $TGT -opt_mode Speed -opt_level 1" | $ISE_HOME/xst

xst complains: 

ERROR:Xst:1817 - Invalid target architecture 'x3cs700an'.

Wich target architecture parameter do I have to pass in, to specify that I want to build for my spartan 3AN? 

Thanks

Ulrich

[eteam00]

The package type and speed grade need to be included.

And syntax needs to be (more or less) correct...

ERROR:Xst:1817 - Invalid target architecture 'x3cs700an'.

Try transposing the "3c" to "c3".  An example Spartan-3AN part number would be:  xc3s700an-4-ft256.  See DS706 for part number "fields" and available part vs. package vs. speed grade combinations.

-- Bob Elkind

[ustaudinger]

Pardon, but how do I set the package type and the speed grade? 

The XST use guide does not mention these in chapter 20/"XST Command Line Mode". The documentation mentions:

To run XST in script mode:
1.
Open a new file called design.xst in the current directory. Put the previously
executed XST shell command into this file and save it.
run
-ifn watchver.prj
-ifmt mixed
-ofn watchver.ngc
-ofmt NGC
-p xc5vfx30t-2-ff324
-opt_mode Speed
-opt_level 1
2.
From the tcsh or other shell, enter the following command to begin synthesis.
xst -ifn design.xst

My command line works, if I give another target architecture, but if i do this, then the map process complains that certain entries in my UCF file are invalid and do not exist in the specified target architecture. 

What could be wrong?

why do the package type and speed grade matter during at the xst step? 

Thanks

[eteam00]

Pardon, but how do I set the package type and the speed grade? 

The XST use guide does not mention these in chapter 20/"XST Command Line Mode". The documentation mentions:

Perhaps this is a good time to ask what version of ISE you are using.  I am looking at version 13.4of ISE and the ISE Command Line Tools User Guide.  From page 13:

Syntax
-p part_number

This option can specify an architecture only, a complete part specification (device, package, and speed), or a partial specification (for example, device and package only). The part number or device name must be from a device library you have installed on your system.

A complete Xilinx® part number consists of the following elements:

• Architecture (for example, spartan3e)
• Device (for example, xc3s100e)
• Package (for example, vq100)
• Speed (for example, -4)

In the example you list: -p xc5vfx30t-2-ff324  all 4 components of the complete Xilinx part number are included.

My command line works, if I give another target architecture, but if i do this, then the map process complains that certain entries in my UCF file are invalid and do not exist in the specified target architecture.

This suggests there is a mismatch between properties assigned in the .UCF file and the part or package specified in the command line.

ERROR:Xst:1817 - Invalid target architecture 'x3cs700an'.

Try transposing the "3c" to "c3".  An example Spartan-3AN part number would be:  xc3s700an-4-ft256.  See DS706 for part number "fields" and available part vs. package vs. speed grade combinations.

-- Bob Elkind

[ustaudinger]

thanks, i will try if this works.

[ustaudinger]

update: 

had to have a look into DS557.pdf (google)

have a spartan 3an fgg484

here my compile script for my linux: 

export ISE_HOME=/opt/Xilinx/13.4/ISE_DS/ISE/bin/lin/

initUSB (){
sudo sed $ISE_HOME/xusbdfwu.rules -e 's:TEMPNODE:tempnode:g' > /tmp/xusbdfwu.rules
sudo cp /tmp/xusbdfwu.rules /etc/udev/rules.d/
sudo rm /tmp/xusbdfwu.rules
sudo cp $ISE_HOME/xusb*.hex /usr/share/
sudo /etc/init.d/udev restart
}

TGT=aqfpga
echo "run -ifn blinker2.v -ifmt Verilog -p xc3s700an-4-fgg484 -ofn $TGT -opt_mode Speed -opt_level 1" | $ISE_HOME/xst
$ISE_HOME/ngdbuild -p xc3s700an-4-fgg484 -uc master.ucf $TGT.ngc
$ISE_HOME/map -detail -pr b $TGT.ngd
$ISE_HOME/par -w $TGT.ncd parout.ncd $TGT.pcf
$ISE_HOME/bitgen -w -g StartUpClk:CClk -g CRC:Enable parout.ncd bitfile.bit $TGT.pcf
$ISE_HOME/promgen -w -p bin -o $TGT.bin -u 0 bitfile.bit$ISE_HOME/impact -batch impact.batch

ustaudinger@lakegeneva:~/fpga/trunk$

my impact stuff doesn't work yet. But i will open another thread for this. 

thanks

[eteam00]

my impact stuff doesn't work yet.

Do you get the same error message with the updated part number declaration?

-- Bob Elkind

[ustaudinger]

the part number was just an issue during the initial steps.

in impact, i got the IDCODE mismatch error.

I did the following to solve this.

I started impact and programmed the jtag/fpga through the graphical GUI. The console window in the GUI will print the batch commands and plenty of other information. I removed everything but the batch commands and ended up with:

ustaudinger@lakegeneva:~/fpga/trunk$ cat impact.batch
setMode -bs
setCable -port auto
Identify -inferir
identifyMPM
assignFile -p 1 -file "/home/ustaudinger/fpga/trunk/bitfile.bit"
setCable -port auto
ReadIdcode -p 2
setMode -pff
setMode -pff
addConfigDevice -name "Untitled" -path "/home/ustaudinger/fpga/trunk"
setSubmode -pffserial
setAttribute -configdevice -attr multibootBpiType -value ""
addDesign -version 0 -name "0"
setAttribute -configdevice -attr compressed -value "FALSE"
setAttribute -configdevice -attr compressed -value "FALSE"
setAttribute -configdevice -attr autoSize -value "FALSE"
setAttribute -configdevice -attr fileFormat -value "mcs"
setAttribute -configdevice -attr fillValue -value "FF"
setAttribute -configdevice -attr swapBit -value "FALSE"
setAttribute -configdevice -attr dir -value "UP"
setAttribute -configdevice -attr multiboot -value "FALSE"
setAttribute -configdevice -attr multiboot -value "FALSE"
setAttribute -configdevice -attr spiSelected -value "FALSE"
setAttribute -configdevice -attr spiSelected -value "FALSE"
addPromDevice -p 1 -size 0 -name xcf04s
setMode -pff
setMode -pff
setSubmode -pffserial
setMode -pff
addDeviceChain -index 0
setMode -pff
addDeviceChain -index 0
addDevice -p 1 -file "/home/ustaudinger/fpga/trunk/bitfile.bit"
setMode -pff
setSubmode -pffserial
generate
setCurrentDesign -version 0
setMode -bs
setMode -bs
setMode -bs
assignFile -p 2 -file "/home/ustaudinger/fpga/trunk/Untitled.mcs"
setAttribute -position 2 -attr packageName -value ""
Program -p 1 -e -v
Program -p 2 -e -v
quit
ustaudinger@lakegeneva:~/fpga/trunk$


which I run from the command line with:

impact -batch impact.batch

works like a charm.

thanks

[ywu]

I unserstand that you are using the script flow. But sometimes it makes it easier to use Project Navigator to create a project first and then use some of the files genearted by the GUI as the starting point for your script. For example, the GUI will create [design].prj and [design].xst files for your project, where [design].xst file has all the settings for synthesis including the part number. I also want to point out that the GUI also create a file [design].cmd_log that has all the commands and their options used by the GUI.

---

ustaudinger wrote:

Pardon, but how do I set the package type and the speed grade? 

The XST use guide does not mention these in chapter 20/"XST Command Line Mode". The documentation mentions:

To run XST in script mode:
1.
Open a new file called design.xst in the current directory. Put the previously
executed XST shell command into this file and save it.
run
-ifn watchver.prj
-ifmt mixed
-ofn watchver.ngc
-ofmt NGC
-p xc5vfx30t-2-ff324
-opt_mode Speed
-opt_level 1
2.
From the tcsh or other shell, enter the following command to begin synthesis.
xst -ifn design.xst

My command line works, if I give another target architecture, but if i do this, then the map process complains that certain entries in my UCF file are invalid and do not exist in the specified target architecture. 

What could be wrong?

why do the package type and speed grade matter during at the xst step? 

Thanks

---