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!

Device IDCODE mismatch. Not possible to configure

Reply
Contributor
Posts: 30
Registered: ‎04-24-2014

Device IDCODE mismatch. Not possible to configure

Greetings!

I have a problem. I am trying to verify the contents of a XC18V04-VQ44 PROM, on my target board, using the Xilinx Program Cable USB II and the iMPACT software. I was given the configuration file in .EXO format and converted it to .MCS format using Promgen.

 

I have manually set up my scan chain ( in attached .PNG) and assigned the 145K874.MCS configuration file to the PROM device. When I try to run the VERIFY operation, it fails and says the iDCODE read from the device (05026093H) does not match the expected IDCODE (05036093H).

 

If I assign the default .bsdl file to the PROM device, the GET IDCODE operation passes.

 

QUESTION: Where is it getting the expected IDCODE of 05036093H that dosen't match the IDCODE read from the device of 05026093H?

 

QUESTION: Both IDCODES are acceptible for this PROM, why does iMPACT expect one over the other?

 

Thank You

Ken Grohman

 

WRA1_4 A9 scan chain.PNG
Moderator
Moderator
Posts: 1,468
Registered: ‎01-15-2008

Re: Device IDCODE mismatch. Not possible to configure

Which version of Impact tool you are using?

could you share the impact.log file here.

 

--Krishna

Contributor
Posts: 30
Registered: ‎04-24-2014

Re: Device IDCODE mismatch. Not possible to configure

Hi Krishna!

 

I am using ver. 14.7 of the standalone iMPACT tool. The first logfile entry is result of running the VERIFY operation with configuration file 145K874.MCS assigned to the XC18V04 device. The second logfile entry is result of running the GET IDCODE operation and the last entry is result of running GET IDCODE operation after assigning the default .bsdl file: XC18V04_VQ44 BSDL.bsd to the XC18V04 device.

 

iMPACT Version: Oct 13 2013 09:58:58

iMPACT log file Started on Wed Jun 03 10:27:01 2015

INFO:iMPACT - Current time: 6/3/2015 10:27:08 AM
// *** BATCH CMD : Verify -p 2
PROGRESS_START - Starting Operation.
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 :        00000101000000100110000010010011
INFO:iMPACT:1579 - '2': Expected IDCODE:    00000101000000110110000010010011
Please make sure that the version of the xc18v00 proms you are using aresupported in iMPACTPROGRESS_END - End Operation.
Elapsed time =      0 sec.

 

 

INFO:iMPACT - Current time: 6/3/2015 10:27:54 AM
// *** 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 :        00000101000000100110000010010011
INFO:iMPACT:1579 - '2': Expected IDCODE:    00000101000000110110000010010011
Please make sure that the version of the xc18v00 proms you are using aresupported in iMPACT

 

 

// *** BATCH CMD : assignFile -p 2 -file"C:/Users/kenneth.grohman/Desktop/WRA1-4 A9/XC18V04_VQ44 BSDL.bsd"
INFO:iMPACT:1777 -
   Reading C:/Users/kenneth.grohman/Desktop/WRA1-4 A9/XC18V04_VQ44 BSDL.bsd...
INFO:iMPACT:1777 -
   Reading C:/Xilinx/14.7/LabTools/LabTools/xc18v00/data/xc18v04_vq44.bsd...
INFO:iMPACT:501 - '2': Added Device XC18V04_VQ44 successfully.
----------------------------------------------------------------------
INFO:iMPACT:1777 -
   Reading C:/Users/kenneth.grohman/Desktop/WRA1-4 A9/XC18V04_VQ44 BSDL.bsd...
INFO:iMPACT - Current time: 6/3/2015 10:28:46 AM
// *** BATCH CMD : ReadIdcode -p 2
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'2': IDCODE is '00000101000000100110000010010011'
'2': IDCODE is '05026093' (in hex).
'2': : Manufacturer's ID = Xilinx xc18v04, Version : 0
Project: 'C:\Users\kenneth.grohman\Desktop\\auto_project.ipf' created.
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -ss
// *** BATCH CMD : setMode -sm
// *** BATCH CMD : setMode -hw140
// *** BATCH CMD : setMode -spi
// *** BATCH CMD : setMode -acecf
// *** BATCH CMD : setMode -acempm
// *** BATCH CMD : setMode -pff
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : saveProjectFile -file"C:\Users\kenneth.grohman\Desktop\\auto_project.ipf"
// *** BATCH CMD : setMode -bs
INFO:iMPACT - Launching WebTalk, please refer to the webtalk log at   C:\Users\kenneth.grohman\Desktop\webtalk.log for details.
ERROR:iMPACT - Failed to execute wbtc: Process crashed.
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : deleteDevice -position 1
----------------------------------------------------------------------
// *** BATCH CMD : deleteDevice -position 1
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -ss
// *** BATCH CMD : setMode -sm
// *** BATCH CMD : setMode -hw140
// *** BATCH CMD : setMode -spi
// *** BATCH CMD : setMode -acecf
// *** BATCH CMD : setMode -acempm
// *** BATCH CMD : setMode -pff

Contributor
Posts: 30
Registered: ‎04-24-2014

Re: Device IDCODE mismatch. Not possible to configure

Bump againm to keep this alive.

 

I looked at AR# 19208. This appears to be the same thing that is happening when I try to run the VERIFY operation. This AR says the problem was with version 6.2i of the iMPACT tool and was fixed by service pack 2. Did the fix not get incorporated in version 14.7 of the iMPACT tool?

 

Ken Grohman

 

 

AR# 19208 6.1i iMPACT - Programming User Code for XC1800 PROMs results in "ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File"

 

Description

General Description:

Programming User Code for XC1800 PROMs results in the following error; however, the user code does actually get programmed.

"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 : 00000000000000000000000000000000

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

'1': Setting usercode...

done."

Solution

This problem has been fixed in the latest 6.2i Service Pack available at:

http://support.xilinx.com/xlnx/xil_sw_updates_home.jsp The first service pack containing the fix is 6.2i Service Pack 2.

Visitor
Posts: 7
Registered: ‎04-11-2018

Re: Device IDCODE mismatch. Not possible to configure

I am facing below issues , can any one suggest me, i used imact 14.7 and Impact 11.1 version, still i am observing same issue.

 

 

 

INFO:iMPACT - Current time: 5/11/2018 6:11:23 PM
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: 00000011100001001110000010010011
PROGRESS_END - End Operation.
Elapsed time = 0 sec.

Moderator
Moderator
Posts: 1,468
Registered: ‎01-15-2008

Re: Device IDCODE mismatch. Not possible to configure

@hoyyoth,

 

there might be jtag interface issues this the reason the idcode has all '1's. Open a new thread under configuration with complete impact log file and schematic interface showing the jtag signals. 

 

Visitor
Posts: 7
Registered: ‎04-11-2018

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

Hi ,

 

Thanks for your reply.

Earlier while working on this board, due to voltage (2.5V and 1.2V ) rail shorted inside the FPGA this board stopped working. So we removed the non-working part and replaced with new FPGA  on this same board, part mounted on this board is with the same part number as earlier(P/N: XC3SD3400A-4FGG676C) but only date code(1701) is new, as we procured this part recently.

 

FYI.. recently we procured this part 10qty and mounted on 10 non-working board where FPGA chip is faulty.

when we try to program FPGA, we could able to program on only 3 boards successfully out of 10.  Remaining 7 boards are not programmable and the error message is same on all the 7 non-working boards. i.e...

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

 

Initially, I also douted about the Assembly issue on this 7 boards where, there might be a chance of FPGA not being soldered properly on the board. But, when I probed all JTAG signal lines and tried reading JTAG signal by performing Get Device ID details with help of impact V14.7 tool, I observed all JTAG lines are toggling. If the FPGA is not mounted correctly on this board, I should not see any one of the TDI/TDO/TMS/TCK line toggling. 

 

I  just collected JTAG signal data using a scope on both the Working and non-working board while Device ID ( Get Device ID) is getting read by impact V14.7 tool.

 

 

for your reference here i have attached Waveforms here collected on the non-working board where i am not able to program FPGA (P/N: XC3SD3400A-4FGG676C,  date code is 1701) and facing the Device ID code issue mentioned above. 

 

I also attached Waveforms here collected on the board where i am able to program FPGA (P/N: XC3SD3400A-4FGG676C,  date code is 1701) successfully.

 

 

 

 

 

 

JTGA Signal while reading Device ID on non working board-Complete Window from DSO scope- image1.png
Zoom of JTGA Signal while reading Device ID on non working board at 2us window-Image2.png
JTGA Signal while reading Device ID on working board-Complete window from DSO scope-Image3.png
Zoom of JTGA Signal while reading Device ID on working board at  2us window-image4.png