@MockyLock
package has been received..
Code: Select all
the good news:
i can communicate with the chip...
i think your programmer may be working properly...
the bad news:
your soldering job was part of the communication issue...
this chip might not be compatible...(unsure why not)
during testing i received the same IDCODE mismatch error..
i checked pwr/gnd and everything seemed ok..
i checked jtag points and noticed a few pins did not have proper contact with the pads...
this can be tricky to discover because if you apply pressure to the pin, then it will make contact and appear to have proper continuity...
if you use light pressure on the pin, then the circuit appears open.
after adding a bit more solder to those points i tried again with the same IDCODE error...
i then applied a new layer of solder to all pins and issue was resolved...
communication established with the chip...
notice the difference in IDCODE (hex) and version detected between the two chip types:
XC95144XL-10TQ
G100C
Code: Select all
// *** BATCH CMD : ReadIdcode -p 1
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': IDCODE is '01011001011000001000000010010011'
'1': IDCODE is '59608093' (in hex).
'1': : Manufacturer's ID = Xilinx xc95144xl, Version : 5
XC95144XL-10TQ100C
Code: Select all
// *** BATCH CMD : ReadIdcode -p 1
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': IDCODE is '00101001011000001000000010010011'
'1': IDCODE is '29608093' (in hex).
'1': : Manufacturer's ID = Xilinx xc95144xl, Version : 2
if anyone else has ability to jtag their chip, please post this data above for comparison....
i am able to perform the following actions with no issues as shown below:
ERASE, BLANK CHECK, READBACK, GET DEVICE ID, GET CHECKSUM (0000), and GET DEVICE SIGNATURE
Code: Select all
INFO:iMPACT - Current time: 11/29/2012 10:15:17 PM
// *** BATCH CMD : Erase -p 1
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Erasing device...
'1': Erasure completed successfully.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
INFO:iMPACT - Current time: 11/29/2012 10:15:22 PM
// *** BATCH CMD : BlankCheck -p 1
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Putting device in ISP mode...done.
'1': Putting device in ISP mode...done.
'1': Performing blank check on device ...
'1': Device is blank.
'1': Blank check completed successfully.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
INFO:iMPACT - Current time: 11/29/2012 10:15:33 PM
// *** BATCH CMD : ReadbackToFile -p 1 -file "C:/Documents and Settings/megalomaniac/Desktop/gcide3-10TQG/blah.jed"
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Putting device in ISP mode...done.
'1': Putting device in ISP mode...done.
'1': Performing readback on device...
'1': Writing to file C:/Documents and Settings/megalomaniac/Desktop/gcide3-10TQG/blah.jed ...
'1': Read back completed successfully.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
INFO:iMPACT - Current time: 11/29/2012 10:15:41 PM
// *** BATCH CMD : ReadIdcode -p 1
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': IDCODE is '01011001011000001000000010010011'
'1': IDCODE is '59608093' (in hex).
'1': : Manufacturer's ID = Xilinx xc95144xl, Version : 5
INFO:iMPACT - Current time: 11/29/2012 10:15:45 PM
// *** BATCH CMD : Checksum -p 1
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Putting device in ISP mode...done.
'1': Putting device in ISP mode...done.
'1': Reading device contents...
'1': Calculated checksum is 0000
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
INFO:iMPACT - Current time: 11/29/2012 10:15:49 PM
// *** BATCH CMD : ReadUsercode -p 1
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Usercode is ''
programming appears to fail upon reaching a certain point anywhere under ~15%...it will then either get hung during programming or fail immediately...
sometimes during programming the initial erase cycle will also hang...
i rewired all pwr/gnd just to make sure but still no luck...
tried to program with v2 code, no luck...
tried to rebuild the jed in Project Navigator specifying 10TQ (instead of default 5TQ) and still no luck...
next i went into debug mode and performed an IDCODE loop to verify it can read the IDCODE successfully 10,000 times...no problems, chip performed as expected
then i went into the main debug and bitset TDI and TMS thru different sequences and combinations of 0 and 1 to confirm the chip followed thru the debug graph as expected...no problems, chip performed as expected...
this chip is the Pb free version and according to the spec sheets should be completely compatible with non-Pb free...this chip is fully recognizable by IMPACT, yet fails to program...
i highly doubt this chip is damaged from any of your troubleshooting as it is performing as expected in terms of standard communications thru IMPACT...
not sure what else i can do for you unless someone else has experienced and resolved this exact failure to program issue...