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: 
Explorer
Explorer
8,192 Views
Registered: ‎06-22-2011

why reading device id fail

The JTAG chain on my board consists of 3 no-xilinx devices and xc5vlx110 and xc2c512.

If I let iMPACT to scan the chain, only xc2c512 was found. But when I tried to read the device ID, it said:

 

INFO:iMPACT:583 - '5': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '5':  Device IDCODE :        00001111111111111000111111111110
INFO:iMPACT:1579 - '5': Expected IDCODE:    00000110110101111000000010010011

Then I set up the whole JTAG chain manually with coresponding bsdl files. But reading back ID of xc5vlx110 and xc2c512 all failed.

 

INFO:iMPACT - Current time: ��һ ���� 8 10// *** BATCH CMD : ReadIdcode -p 3
INFO:iMPACT:583 - '3': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '3':  Device IDCODE :        00001111111111111111111111111111
INFO:iMPACT:1579 - '3': Expected IDCODE:    00000010100011010110000010010011
INFO:iMPACT - Current time: ��һ ���� 8 10// *** BATCH CMD : ReadIdcode -p 5
INFO:iMPACT:583 - '5': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '5':  Device IDCODE :        00001111111111111000111111111110
INFO:iMPACT:1579 - '5': Expected IDCODE:    00000110110101111000000010010011

Why this happened? where can I get the real device ID of them?

 

regards

 

0 Kudos
6 Replies
Scholar austin
Scholar
8,179 Views
Registered: ‎02-27-2008

Re: why reading device id fail

p,

Something is wrong with the signal integrity of your JTAG chain: the signals are not at the right levels, there is too much over-shoot, or under-shoot, or there are multiple transitions in the clock edges (caused by bad termination, ...).

Check all your signals on the board with an oscilloscope.

The bad ID code means Impact can't figure out what bits are what ....

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Explorer
Explorer
8,168 Views
Registered: ‎06-22-2011

Re: why reading device id fail

But this board was bought from Curtis-wright, and it was tested before shipping.

I can't probe JTAG signals on the board, only signals near the cable header can be monitored.

0 Kudos
Xilinx Employee
Xilinx Employee
8,161 Views
Registered: ‎01-03-2008

Re: why reading device id fail

Have you called Curtis-Wright technical support?   Since they sold you the board they should answer your quesions.

------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
Explorer
Explorer
8,148 Views
Registered: ‎06-22-2011

Re: why reading device id fail

Curtis-wright hasn't answer me yet. I scoped the JTAG signals near the header.

JTAG TDO

This is the TDO where reading back device ID. The waveforms look fine. But the TDO is not the actual device ID(xc2c215). Actually iMPACT can find it with auto scaning. The other non-xilinx devices are added to the chain manually.

No matter adding those devices or not, reading device ID always failed with the same error.

Reading device IDs of the non-xilinx devices (device id test) always get the result with all 1 bits.

I'm using platform cable USB, will it help to try with platform cable parallel III?

 

0 Kudos
Highlighted
Observer rho88
Observer
8,134 Views
Registered: ‎06-22-2011

Re: why reading device id fail

You won't be able to read back idcodes of the non-xilinx devices, unless impact supports this now, but you should only be able to put them in bypass mode.  

 

-Did you define the Instruction register length for your non-xilinx devices or provide the BSDL file for them?  

-You sure there are no jumpers or switches on your board that change the JTAG chain?

-It seems like there is something missing from the JTAG chain.  Are all devices showing up in the boundary scan window? Can you provide a screenshot of that?

0 Kudos
Contributor
Contributor
2,943 Views
Registered: ‎07-04-2016

Re: why reading device id fail

had same error on ML605 - https://goo.gl/photos/DQVgW9kHiEJLhhkdA

 

 

jumpers should be like that to bypass FMC module. 

https://goo.gl/photos/yJR9emwTSr27gGMz6

https://goo.gl/photos/27r6snN4mCRwcLUQ9

 

 

0 Kudos