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: 
Adventurer
Adventurer
7,384 Views
Registered: ‎12-16-2010

Impact in batch mode not working as expected

Hello.

I have a JTAG chain with 6 devices, in this order:

 

TPO -> Xilinx S6-100 -> iMX253 -> STV0903 -> STV0903 -> STV0903 -> STV0903 -> TDI

 

I have BSDL files for all devices, and I can operate flawlessly in Impact in GUI mode.

I can check chain integrity, check IDCODE, read eFuse keys, IDCODEs and so on from the Spartan6

device without problems.

 

Now I'm trying to do the same from batch file:

 

setlog -file c:\temp\xc6slx100_readefuse.log

setmode -bscan
setcable -port auto
setcablespeed -speed 1500000

identify

addDevice -p 1 -part xc6slx100
assignFile -p 2 -file iMX25_BSDL.bsd
assignFile -p 3 -file Stb0903c3_BAC_patched.bsd
assignFile -p 4 -file Stb0903c3_BAC_patched.bsd
assignFile -p 5 -file Stb0903c3_BAC_patched.bsd
assignFile -p 6 -file Stb0903c3_BAC_patched.bsd

CheckIntegrity
CheckIdcode -p 1
CheckIdcode -p 2
CheckIdcode -p 3
CheckIdcode -p 4
CheckIdcode -p 5
CheckIdcode -p 6

ReadEfuse -aeskey -p 1
ReadEfuse -dna -p 1
readdna -p 1

quit

 

 

Something goes wrong, I receive the following log:

 

Release 13.4 - iMPACT O.87xd (nt)
Copyright (c) 1995-2011 Xilinx, Inc.  All rights reserved.
Preference Table
Name                 Setting
StartupClock         Auto_Correction
AutoSignature        False
KeepSVF              False
ConcurrentMode       False
UseHighz             False
ConfigOnFailure      Stop
UserLevel            Novice
MessageLevel         Detailed
svfUseTime           false
SpiByteSwap          Auto_Correction
AutoInfer            false
SvfPlayDisplayComments false
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_xp2.sys found.
 Driver version: src=2301, dest=2301.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010
Build Date: Aug 31 2010 X86 32bit SYS
14:35:41, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 300 mA.
Type = 0x0005.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 2401.
File version of C:/Xilinx/13.4/ISE_DS/ISE/data/xusb_xp2.hex = 2401.
Firmware hex file version = 2401.
PLD file version = 200Dh.
 PLD version = 200Dh.
Type = 0x0005.
ESN option: 000013E2093F01.
Identifying chain contents...INFO:iMPACT:1588 - '0':The part does not appear to
be Xilinx Part.
'0': : Manufacturer's ID =Unknown , Version : 9
INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT:1588 - '1':The part does not appear to be Xilinx Part.
'1': : Manufacturer's ID =Unknown , Version : 9
INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT:1588 - '2':The part does not appear to be Xilinx Part.
'2': : Manufacturer's ID =Unknown , Version : 9
INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT:1588 - '3':The part does not appear to be Xilinx Part.
'3': : Manufacturer's ID =Unknown , Version : 9
INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT:1588 - '4':The part does not appear to be Xilinx Part.
'4': : Manufacturer's ID =Unknown , Version : 0
INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
'5': : Manufacturer's ID = Xilinx xc6slx100, Version : 2
INFO:iMPACT:1777 -
   Reading C:/Xilinx/13.4/ISE_DS/ISE/spartan6/data/xc6slx100.bsd...
INFO:iMPACT:501 - '1': Added Device xc6slx100 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
Elapsed time =      2 sec.
Elapsed time =      0 sec.
INFO:iMPACT:501 - '1': Added Device xc6slx100 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT:1777 -
   Reading iMX25_BSDL.bsd...
INFO:iMPACT:1777 -
   Reading iMX25_BSDL.bsd...
INFO:iMPACT:1777 -
   Reading Stb0903c3_BAC_patched.bsd...
INFO:iMPACT:1777 -
   Reading Stb0903c3_BAC_patched.bsd...
 Attribute TAP_SCAN_CLOCK is not found in Device 7 BSDL file.
Warning: Chain frequency (1000000) is less than the current cable speed
(1500000).
 Adjust to cable speed (1000000).
Maximum TCK operating frequency for this device chain: 1000000.
Validating chain...
INFO:iMPACT:477 - The bsdl for device 'UNKNOWN' is out of date. Please check
   your installation.
INFO:iMPACT:490 - Boundary-scan chain validation terminated.
Elapsed time =      0 sec.
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------

 

 

I don't understand why it is searching for device 7 (non-existant).

I suppose this would be a bug of impact in batch mode.

How to fix it?

 

Please some Impact expert take a look on this, thanks!

 

Thanks

Andrea

0 Kudos