|
|
JTAGPROG to iMPACT Script Migration
This section is provided as a guide to help customers convert their 3.1i JTAGPROG .cmd script files for use with 4.1i iMPACT.
Getting Started
JTAGPROG and iMPACT are both case-insensitive. Uppercase syntax is used in this and other documents for the sake of clarity.
To invoke JTAGPROG in batch mode:
jtagprog –batch bat_file.cmd
To invoke iMPACT in batch mode:
impact –batch bat_file.cmd
The .cmd file is simply a text file which specifies the instructions to be performed in batch mode. All instructions that follow should be placed in this .cmd file.
Determining the Part Name
JTAGPROG and iMPACT both require the user to specify a part name for certain commands. This can cause confusion, as the required naming convention is not provided in the documentation for JTAGPROG or iMPACT.
When specifying the part name with the part command, the part name must exactly match the name of the BSDL file that is associated with that part, minus the file extension (examples provided in table C-2). BSDL files for all parts can be found in the $xilinx folder.
This applies to both JTAGPROG and iMPACT.
Note
Programming and Verifying a Device
You often need to perform five operations in your command (.cmd) file:
JTAGPROG
Autoconfigure
part part_type:[arbitrary part name]
program [arbitrary part name] -f [filename.bit/.jed/.mcs
verify [arbitrary part name]
quit
iMPACT
setmode -bscan
setcable -p auto
identify (optional)
addDevice -p [devicenumber] -file [filename.bit/.jed]
program - verify -p [device number]
quit
iMPACT (XC18V00 Family)
The iMPACT syntax varies slightly for 18v00 PROMs.
setmode -bscan
setcable -p auto
identify (optional)
addDevice –p [device number] –sprom [part name]3 –file [filename.mcs/.exo]
program -e -v -p [device number]
quit
iMPACT (when assigning a BSDL file)
Again, the syntax is slightly different when assigning a BSDL file to a device. This situation arises whenever third-party devices are used or when BSDL files are used to bypass Xilinx devices.
setmode -bscan
setcable -p auto
identify (optional)
addDevice –p [device number] –file [filename.bsd]
assignFile3 –p [device number] –file [filename.bsd]
bypass -p [device number]4
quit
Note
[device number] = 1,2,3...If the programming file does not reside in the working directory, the full path may be specified, e.g.: -file c:\test\filename.bit
[part name] = xc18v256, xc18v512, xc18v01, xc18v02, or xc18v04.
The bypass command is not needed in most cases, since devices with no action assigned are automatically placed in bypass. See the Examples, below.
Blank lines are not allowed in the iMPACT .cmd file.
Example: Programming a XC18v00 PROM
JTAGPROG
autoconfigure
part xc18v04_pc44:device1
program device1 -f c:\test\design.mcs
quit
iMPACT
setmode –bscan
setcable –p auto
identify
addDevice –p 1 –sprom xc18v04 –file design.mcs
program –p 1
quit
iMPACT (SVF mode)
setmode –bscan
setcable –p svf –file output.svf
addDevice –p 1 –sprom xc18v04 –file design.mcs
program -e -v –p 1
quit
Example: XC2v1000 Device (bypassed with a .bit file) in a Chain with an XC18v04 Device (programmed)
JTAGPROG
reset
autoconfigure
part xc2v1000_fg256:device1 xc18v04_pc44:device2
program device2 -f design.mcs
quit
iMPACT
setmode -bscan
setcable -p auto
identify
addDevice -p 1 -file design.bit
addDevice –p 2 –sprom xc18v04 –file design.mcs
program -e -v -p 2
quit
iMPACT (SVF mode)
setmode –bscan
setcable –p svf –file output.svf
addDevice -p 1 -file design.bit
addDevice –p 2 –sprom xc18v04 –file design.mcs
program -e -v –p 2
quit
Note No instruction is required to bypass the 2v1000. Devices that do not have instructions specified are bypassed automatically. Bypassed Xilinx devices can be assigned either a BSDL (.bsd) file or a programming file (.bit/.jed/.mcs/.exo). Bypassed third-party devices must be assigned a BSDL file.
Example: XC2v1000 (programmed) in a Chain with a XC18v04 (bypassed with a BSDL file)
JTAGPROG
reset
autoconfigure
part xc2v1000_fg256:device1 xc18v04_pc44:device2
program device1 –f design.bit
quit
iMPACT
setmode -bscan
setcable -p auto
identify
addDevice -p 1 -file design.bit
addDevice –p 2 –file xc18v04_pc44.bsd
assignFile –p 2 –file xc18v04_pc44.bsd
program -p 1
quit
iMPACT (SVF mode)
setmode –bscan
setcable –p svf –file output.svf
assignfile -p 1 -file design.bit
assignfile –p 2 –sprom xc18v04 –file design.mcs
program -p 1
quit
Example: Chain Consisting of XC18v04 (programmed), Third Party Device (bypassed), XC18v04 (programmed), XC18v04 (bypassed with a .bsd file)
JTAGPROG
reset
autoconfigure
part xc18v04_vq44:device1 thirdparty:device2 xc18v04_vq44:device3 xc18v04_vq44:device4
program device1 –f design.mcs
program device3 –f design.mcs
quit
iMPACT
setmode -bscan
setcable -p auto
identify
addDevice -p 1 -sprom xc18v04 -file design1.mcs
addDevice –p 2 –file thirdparty.bsd
assignFile –p 2 –file thirdparty.bsd
addDevice –p 3 –sprom xc18v04 –file design2.mcs
addDevice –p 4 –file xc18v04_vq44.bsd
assignFile –p 4 –file xc18v04_vq44.bsd
program -e -v -p 1
program -e -v –p 3
quit
iMPACT (SVF mode)
setmode -bscan
setcable -p svf -file output.svf
addDevice -p 1 -sprom xc18v04 -file design1.mcs
addDevice -p 2 -file thirdparty.bsd
assignFile -p 2 –file thirdparty.bsd
addDevice -p 3 -sprom xc18v04 -file design2.mcs
addDevice -p 4 -file xc18v04_vq44.bsd
assignFile –p 4 –file xc18v04_vq44.bsd
program -e -v -p 1
program -e -v -p 3
quit
|
|