Problem programming CoolRunner II xc2c256_tq144 CPLD using IMPACT

I was trying to program xc2c256_tq144 (CoolRunner II) CPLD using ISE
Project Navigator SW version 7.1.04i. I used parallel III cable
provided by Digilent to program the CPLD. But I am getting error
"iMPACT 583  - '1': The idcode read from the device does not match the
idcode in the BSDL file". I tried to view BSDL file but I don't have a
clue as to how to modify device IDCODE so device id and expect device
id matches. Does anybody know what's wrong here or know how resolve
this issue? Thanks in advance.

Best regards,
Nabin

Nabin,
leave the bsdl file alone, try first to reduce the speed of the cable, 
and if still doesn't work post the output of impact here to see how 
different they are (I mean in which way)

Aurash

nshrestha wrote:
> I was trying to program xc2c256_tq144 (CoolRunner II) CPLD using ISE
> Project Navigator SW version 7.1.04i. I used parallel III cable
> provided by Digilent to program the CPLD. But I am getting error
> "iMPACT 583  - '1': The idcode read from the device does not match the
> idcode in the BSDL file". I tried to view BSDL file but I don't have a
> clue as to how to modify device IDCODE so device id and expect device
> id matches. Does anybody know what's wrong here or know how resolve
> this issue? Thanks in advance.
> 
> Best regards,
> Nabin
> 

"nshrestha" <nshrestha@msn.com> schrieb im Newsbeitrag 
news:1133968595.585555.327370@g49g2000cwa.googlegroups.com...
>I was trying to program xc2c256_tq144 (CoolRunner II) CPLD using ISE
> Project Navigator SW version 7.1.04i. I used parallel III cable
> provided by Digilent to program the CPLD. But I am getting error
> "iMPACT 583  - '1': The idcode read from the device does not match the
> idcode in the BSDL file". I tried to view BSDL file but I don't have a
> clue as to how to modify device IDCODE so device id and expect device
> id matches. Does anybody know what's wrong here or know how resolve
> this issue? Thanks in advance.
>
> Best regards,
> Nabin
>

its an generic warning that usually doesnt tell you at all whats wrong
there is no need to touch the BSDL file, there is some JTAG problem
with your setup so you need to troubleshoot it

try reading the chain with chipscope does it show correct ID?

Antti