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: 
Visitor joe.kuchman
Visitor
1,307 Views
Registered: ‎07-20-2018

The idcode read from the device does not match the idcode in the bsdl File

We have built several hundred of these boards and have never previously experienced this issue.

 

I have verified all of the voltages and all of the JTAG pull-up resistors are in place. Is there anything else I can try short of reflowing and or replacing the PROM and or FPGA?

 

Error from Impact:

INFO:iMPACT - Current time: 7/17/2018 1:38:14 PM

// *** BATCH CMD : Program -p 1 -e -v

PROGRESS_START - Starting Operation.

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 :       00001111111111111111111111111110

INFO:iMPACT:1579 - '1': Expected IDCODE:       00000101000001000110000010010011

Please make sure that the version of the xc18v00 proms you are using are supported in iMPACTPROGRESS_END - End Operation.

Elapsed time =     0 sec.

 

 

 

0 Kudos
5 Replies
Explorer
Explorer
1,276 Views
Registered: ‎05-08-2018

Re: The idcode read from the device does not match the idcode in the bsdl File

j.k,

 

Looks like the parts are not what expected (wrong ID code implies they are not what you designed it for).  Need to contact your distributor and verify what they shipped was/was not correct.  Then either remove and replace them, or investigate if its possible to re target your design for these different parts, creating a new bitstream and/or new programming for the EPROM.

 

Not a solder or PCB issue ...

 

0 Kudos
Xilinx Employee
Xilinx Employee
1,248 Views
Registered: ‎08-25-2010

Re: The idcode read from the device does not match the idcode in the bsdl File

Hi @joe.kuchman,

 

Device ID(impact log) is same for all tested boards?  Or the same ID reading for every time on the same board?

 

Thanks

Simon

Thanks
Simon
-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Visitor joe.kuchman
Visitor
1,240 Views
Registered: ‎07-20-2018

Re: The idcode read from the device does not match the idcode in the bsdl File

The device ID Is the same for this particular board. All previous boards have not had an issue. The same board design has been used for quite some time without any programming issues.

 

Also, the error occurs on both the PROM and the FPGA which indicates to me that it is not an issue with a mismatched part and is more likely the PCB or a solder issue.

 

Here is the PROM:

INFO:iMPACT - Current time: 7/17/2018 2:12:54 PM

// *** BATCH CMD : ReadIdcode -p 1

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 :       00001111111111111111111111111110

INFO:iMPACT:1579 - '1': Expected IDCODE:   00000101000001000110000010010011

Here is the FPGA:

// *** BATCH CMD : ReadIdcode -p 2

INFO:iMPACT:583 - '2': The idcode read from the device does not match the idcode in the bsdl File.

INFO:iMPACT:1578 - '2': Device IDCODE :       00001111111111111111111111111100

INFO:iMPACT:1579 - '2': Expected IDCODE:   00000001010000101000000010010011

 

(These are both consistent but notice the results are not exactly the same:

00001111111111111111111111111110 (PROM)

00001111111111111111111111111100(FPGA)

 

I would think that if the TDO line were stuck then the DEVICE ID would have just been all 1s. Perhaps I need to investigate more on what to expect on the JTAG signals when reading device ID. I would assume it should at least contain the expected ID code shown above.

 

I've already verified all of the required JTAG pull-up resistors are installed I compared board impedances to a good board and everything on the JTAG lines matched up. The voltages are all good. The only other thing I could think of was replacing the PROM then reflowing the FPGA and then possible replacing the FPGA. Hoping for another suggestion as neither of these options are ideal.

 

 

Example of a good ID code read:

// *** BATCH CMD : ReadIdcode -p 1

Maximum TCK operating frequency for this device chain: 15000000.

Validating chain...

Boundary-scan chain validated successfully.

'1': IDCODE is '11010101000001000110000010010011'

'1': IDCODE is 'd5046093' (in hex).

'1': : Manufacturer's ID = Xilinx xcf04s, Version : 13

 

0 Kudos
Xilinx Employee
Xilinx Employee
1,231 Views
Registered: ‎08-10-2008

回复: The idcode read from the device does not match the idcode in the bsdl File

Hi j,

"00001111111111111111111111111100 " this is a typical JTAG chain not-correctly-recognized issue. The IDCODE you got telling that the chain is not correctly scanned or bypassed.
You have more than one part in the JTAG chain right? Now the tool cannot identify all the parts, this could be a hardware connection issue or SI issue.
For SI, you can lower down TCK for a test;
For HW, you need to double check all the connections. TDI->TDO path has issues so cannot shift all the IDs of each part as expected.

Thanks,
Ivy
------------------------------------------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
---------------------------------------------------------------------------------------------------------
0 Kudos
Observer chenj15
Observer
1,025 Views
Registered: ‎08-14-2016

回复: The idcode read from the device does not match the idcode in the bsdl File

Hi Ivy,

 

I have the same issue with " INFO:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File." the read back device code is "00001111111111111111111111111110", and expected is "00000100000000000000000010010011"

 

my board has only one device, xc6slx4CSG255. Jtag signals are  clean, and  TDO responds to the call.  How should I resolve this issue?  The board was assembled overseas, do I have bad chips? (XC6SLX4CSG255BIV1809 D5581035A)

 

Jim 

 

0 Kudos