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!

Reply
Newbie
Posts: 1
Registered: ‎07-29-2010

xc2c256 programming error

[ Edited ]

Starting yesterday, when I attempt to program my CoolRunnerII xc2c256 CPLD via the JTAG port, I get this error consistently:

// *** BATCH CMD : Program -p 1 -e -v
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 : 00001111111111111000111111111111
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000110110101001000000010010011
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
PROGRESS_START - Starting Operation.
// *** 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 : 00001111111111111000111111111111
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000110110101001000000010010011
// *** BATCH CMD : assignFile -p 1 -file "[redacted]"
'1': Loading file [redacted]' ...
done.
INFO:iMPACT:501 - '1': Added Device xc2c256 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
// *** BATCH CMD : Program -p 1 -e -v
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 : 00001111111111111000111111111111
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000110110101001000000010010011
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
PROGRESS_START - Starting Operation.
// *** 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 : 00001111111111111000111111111111
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000110110101001000000010010011


I had to reprogram a different board from the same batch last month, and everything worked just fine. We use a DLC9G USB programmer. I've slowed the cable speed to 750MHz with no change in the result. There is only one device on the JTAG chain. Any ideas as to how I could resolve this would be a big help.

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

Re: xc2c256 programming error

Hello Zwilloh,

The IDCODE that is being read back has a lot of 1's or 0's so this indicates that there might be short or a bad connection on the JTAG lines in your board.  

How many devices are in the JTAG chain, if there are many then can you remove all of them except  the CPLD and do the readback the IDCODE.  Also can you debug the JTAG chain by stepping through each step of the tap controller using the Impact tool.

 

Thanks

Krishna

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

Re: xc2c256 programming error

do send me the complete part marking of the CPLD device in question

 

Thanks

Krishna

Newbie
Posts: 1
Registered: ‎11-05-2012

Re: xc2c256 programming error

Hi, expert:

     I have the same error, the situation is :

 

The idcode read from the device does not match the idcode:

INFO:iMPACT - Current time: Mon Nov 5 15:08:02 2012
// *** 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 :        00001111111111111000111111111110
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110110101001000000010010011
Enumerating cables. Please wait.

 

     I have checked the bsdl file, I think that is no problem.

     I think there are something wrong about signal interity(TDI,TCK&TMS),

     I checked the TCK signal, there was no frequce.

     So, I wanted to know in the normal mode, how those three signal needed to be?

Highlighted
Visitor
Posts: 11
Registered: ‎06-17-2015

Re: xc2c256 programming error

Did anyone have any luck? Stuck with the same problem here...