cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
stalha
Newbie
Newbie
15,711 Views
Registered: ‎09-11-2008

error iMPACT 583-'1': idcode mismatch between bsdl file and read from device

Hi 

While configuring my virtex-4 (sx35) using Platform cable USB (with XilinxISE7.1i), I get following message off and on.

 

error iMPACT 583-'1': The idcode read from the device does not match the idcode in the bsdl file

 

By off and on I mean that one-day this problem comes (and goes after wiggling of some wires and/or re-booting of computer and/or turning off & on the PC monitor), then for many days there's no problem (device configuring perfectly well) and then suddenly, this problem comes back again. Today is that day and since morning, I'm busy with it but the problem is still there. I 've also downloaded latest bsdl files for xc4vsx35 into the folder xilinx/virtex4/data and xilinx/xpla3/data, but of no use. Could anyone help please ?

0 Kudos
16 Replies
mcgett
Xilinx Employee
Xilinx Employee
15,697 Views
Registered: ‎01-03-2008

What this indicates is that the JTAG chain on the board has some signal integrity issues most likely on the TCK (clock) line.  This is causing incorrect data to be read out of the board occasionally.

 

JTAG may be a slow interface, but it is just as susceptible to clock glitches as any other interface.

------Have you tried typing your question into Google? If not you should before posting.
Too many results? Try adding site:www.xilinx.com
0 Kudos
stalha
Newbie
Newbie
15,679 Views
Registered: ‎09-11-2008

Hi

Thanks for the reply.

 

This problem that I'm getting is with our project-circuit1 which is housing xc4vsx35. However when I use the same setup (same ISE, Platform cable USB) to configure the 'Xilinx® Virtex™-4 SX Evaluation Kit (which is housing xc4vsx35)', there has never been any problem at all. Similarly, when I use the same setup (same ISE, Platform cable USB) to configure our another project-circuit2 housing Xilinx CPLD, there too has never been any problem at all. So, does it show that there's problem in our project-circuit1 (the one housing xc4vsx35) ? 

 

"What this indicates is that the JTAG chain on the board has some signal integrity issues most likely on the TCK (clock) line.  This is causing incorrect data to be read out of the board occasionally."

 

Could it be related to the PCB-quality of the project-circuit1 ?         

 

0 Kudos
mcgett
Xilinx Employee
Xilinx Employee
15,666 Views
Registered: ‎01-03-2008

Since the same software and cable works on 2 out of 3 different boards then the problem is on the board that doesn't work.

 

The board that you are calling the "project-circuit1" board has a problem with the way that it was designed.  I would suggest that you get out an oscilloscope and probe the TCK lines at each device on the board to see if you can determine where the problem(s) is.  Depending on what you find you may be able to fix the signal integrity problem with the capacitor or a resistor.

------Have you tried typing your question into Google? If not you should before posting.
Too many results? Try adding site:www.xilinx.com
0 Kudos
iffy2002
Newbie
Newbie
14,472 Views
Registered: ‎03-05-2009

I'm having a similar problem, but looking at the device  idcodes ... I can see that they're just shifted by 2 bits.  How would I fix this?

 

Cable connection established.
Firmware version = 1301.
File version of /home/matt/Xilinx92i/data/xusb_xlp.hex = 1301.
Firmware hex file version = 1301.
ESN Family Code: 00
ESN: 000000000000
CPLD file version = 0012h.
CPLD version = 0012h.
ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000111000010001000001001001100
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000001110000100010000010010011
 

0 Kudos
akleica
Explorer
Explorer
14,352 Views
Registered: ‎11-13-2007

How many devices are on your board? 3 perhaps?
0 Kudos
borisq
Xilinx Employee
Xilinx Employee
14,303 Views
Registered: ‎08-07-2007

ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000111000010001000001001001100
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000001110000100010000010010011

 

 

use iMPACT to identify the jtag chain "automatically", don't choose "manually"

------------------------------------------------------------------------------
Don't forget to reply, give kudo and accept as solution
------------------------------------------------------------------------------
0 Kudos
ddaadd
Newbie
Newbie
13,542 Views
Registered: ‎04-29-2009

^.^....  i'v solved..

 

iMPACT 10.1.03

usb download cable...

 

my board list..

 

 

#20 set
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000010101101100000100000010011
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110110110001000000010010011
#13
INFO:iMPACT:1578 - '1':  Device IDCODE :        00001111111111111000111111110011
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110110110001000000010010011
#4
INFO:iMPACT:1578 - '1':  Device IDCODE :        00001111111111111000111111110011
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110110110001000000010010011
#3
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000010101101100000100000010011
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110110110001000000010010011

 

 

 It took three days to resolve

 

TMS : 1K PULL DOWN

TDI, TDO, TCK : 1K PULL DOWN...

 

altera application... 

 

 

0 Kudos
hfsitu
Newbie
Newbie
12,381 Views
Registered: ‎11-10-2009

My solution for this is just slow down the cable speed to 200KHz, act as Parallel III. It works for me.
0 Kudos
delbotero
Explorer
Explorer
11,681 Views
Registered: ‎03-25-2010

Hello,

 

I am using a SPARTAN 3 starter kit.

 

I developped my first project with BSB, but I have one error, according with this thread is due to the board. How to solve it?

 

 

 

INFO:iMPACT:501 - '1': Added Device xc3s200 successfully.
INFO:iMPACT:583 - '1': The idcode read from the device does not match the idcode
   in the bsdl File.
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000000000000000000000000010001
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000001010000010100000010010011
make: *** [download] Error 1
Done!

 

Thank you in advance.

 

DABG

 

 

0 Kudos
ddaadd
Newbie
Newbie
8,321 Views
Registered: ‎04-29-2009

TDI, TDO, TCK : 1K PULL DOWN...   --->  Pull Up

 

and change download speed 

0 Kudos
kresimir
Visitor
Visitor
8,160 Views
Registered: ‎06-03-2010

Hello, I have the same problem with this idcode. I use Jtag cable (coolrunner II). a) I reduced TCK (750 kHz) b) 1 K pull down for TDO, TCK, TDI I didn't helped.
Krešimir Popović
0 Kudos
kresimir
Visitor
Visitor
8,138 Views
Registered: ‎06-03-2010

Hello,

 

I will try this schematic for programming. It will be used for CoolRunner II CPLD XC2C32A (VQ44).

Krešimir Popović
5.6.2010.jpg
0 Kudos
kresimir
Visitor
Visitor
8,135 Views
Registered: ‎06-03-2010

This should be even better. I have included C = 0.1 microF.

Krešimir Popović
5.6.2010.jpg
0 Kudos
suchit_ee
Visitor
Visitor
7,454 Views
Registered: ‎02-15-2011

For anyone who runs into the IDCODE mismatch issue the first time they are programming their kit:

Before you do anything fancy, take a few minutes to read-up on the jumper settings necessary for successfully programming your kit. In my case I am configuring an ML605 which arrived yesterday. After I got the IDCODE mismatch, I checked the hardware user guide, and found out the correct jumper settings. Now my bitstreams are downloading.

 

Cheers!!

bassman59
Historian
Historian
7,450 Views
Registered: ‎02-25-2008

 


@suchit_ee wrote:

For anyone who runs into the IDCODE mismatch issue the first time they are programming their kit:

Before you do anything fancy, take a few minutes to read-up on the jumper settings necessary for successfully programming your kit. In my case I am configuring an ML605 which arrived yesterday. After I got the IDCODE mismatch, I checked the hardware user guide, and found out the correct jumper settings. Now my bitstreams are downloading.

 

Cheers!!


 

Ah, you Read The Fine Manual?

 

You must be new here :)

----------------------------Yes, I do this for a living.
0 Kudos
hongtay
Newbie
Newbie
6,803 Views
Registered: ‎01-16-2013

I used ISE 14.3 nt64bit

 

  with device : XC3S500E-PQG208

  USB JTAG : ALTERA XILINX Lattice Saleae USBee 5 in 1 USB blaster Download Cable JTAG FPGA CPLD Downloader Debugger

  from  http://www.canton-electronics.com/

 

 

   got  below error

   =====

    info:impact:1578 - '1':  device idcode :        00000011100001000100000100100110

    info:impact:1579 - '1': expected idcode:    00000001110000100010000010010011

 

   ====

 

  I soft by used Impact  just  click-> Boundary Scan --> right click on bank right side windows  --> Initialize chain CTRL + I

  you will found 2 device one device is first chain that you programing  and other one is XC??? is inside USB JTAG loader

 then you load program only first you device don't touch other one  then try  Get device ID will working normal

 

 

 

 

 


INFO:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000011100001000100000100100110
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000001110000100010000010010011
GUI --- Auto connect to cable...
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.3
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusbdfwu.sys found.
 Driver version: src=1027, dest=1027.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 280 mA.
Type = 0x0605.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 1100.
File version of D:/Xilinx-web/14.3/ISE_DS/ISE/data/xusbdfwu.hex = 1100.
Firmware hex file version = 1100.
PLD file version = 0012h.
 PLD version = 0012h.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
Type = 0x0605.
ESN not available for this cable.
Enumerating cables. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusbdfwu.sys found.
 Driver version: src=1027, dest=1027.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
ESN not available for this cable.
=======================================================
Found cable - > ESN not available for this cable.
No ESN.
=======================================================
Connecting to cable (Usb Port - USB22).
Checking cable driver.
 Driver file xusbdfwu.sys found.
 Driver version: src=1027, dest=1027.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
PROGRESS_END - End Operation.
Elapsed time =      3 sec.
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.3
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 1/16/2013 4:00:43 PM
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xcf04s, Version : 13
INFO:iMPACT:1777 -
Reading D:/Xilinx-web/14.3/ISE_DS/ISE/xcf/data/xcf04s.bsd...
INFO:iMPACT:501 - '1': Added Device xcf04s successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
'1': : Manufacturer's ID = Xilinx xc3s500e, Version : 4
INFO:iMPACT:501 - '1': Added Device xc3s500e successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
'1': Loading file 'X:/M-Power/MOTOR-500E/2013-01-16/main.bit' ...
done.
UserID read from the bitstream file = 0xFFFFFFFF.
----------------------------------------------------------------------
INFO:iMPACT:501 - '1': Added Device xc3s500e successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT - Current time: 1/16/2013 4:01:25 PM
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': IDCODE is '01000001110000100010000010010011'
'1': IDCODE is '41c22093' (in hex).
'1': : Manufacturer's ID = Xilinx xc3s500e, Version : 4
INFO:iMPACT - Current time: 1/16/2013 4:01:30 PM
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': IDCODE is '01000001110000100010000010010011'
'1': IDCODE is '41c22093' (in hex).
'1': : Manufacturer's ID = Xilinx xc3s500e, Version : 4
INFO:iMPACT - Current time: 1/16/2013 4:01:31 PM

 

 

 

Anan P.

Thailand

0 Kudos