Dataman Forum

http://www.drivestar.biz/adapter-wlpl44 ... -1420.html

specified for the XC9536 etc


using the WL-PL44-U001 dip-44 to plcc44 adaptor I get

Device code unmatched !


Ok so i bought the adaptor online and it looks great.

Do you have a list showing how the pins should be mapped so I can verify the adaptor is right?

Hello chrisautosound,

The adaptor connection tables for the most popular sockets can be found on our website here: http://www.dataman.com/dataman-48xp48uxp-resources

If you have any further questions, please let me know.

Best regards,

Neil Parker
Dataman Programmers

thanks for the tip, I ohmed out the adaptor and it is straight 1 to 1, UNIV-44

but same failed result for all actions

read
blank check
program etc

Device code unmatched !

Hello chrisautosound,

Did the error message in the log window specify the expected Device ID and the ID as read from the device?

If you can provide all the codes from the top of the device we can check with Xilinx to see if they have changed the Device ID value on later devices.

If you have any further questions, please let me know.

Best regards,

Neil Parker
Dataman Programmers

Did the error message in the log window specify the expected Device ID and the ID as read from the device?

No, it does not. The only message is Device code unmatched !


If you can provide all the codes from the top of the device we can check with Xilinx to see if they have changed the Device ID value on later devices.

there are no bottom markings
top markings
XC9536XL
PC44CMN0401
F1291492A
10C


Chips supplied by Harman. Insert in socket.
Then select the IC, then load the 770498.jed file supplied by Harman.

blank test fails Device code unmatched !
program fails Device code unmatched !

so far I have used the succesfully use the 48LV for 27C eeproms and 18vc8 devices.

Thanks for the help, let me know what you find. chris

HMM I dont think it is the PLCC-> DIP adaptor.

I ordered a PLCC44 device for checking the adaptor and my 48LV

With the AT271024 in place there are no errors and the blank check works.


any news on your end?


Chris

Hello Chris,

I am afraid that we cannot offer a solution for this device. It may be a new version of the chip which is incompatible with the existing algorithm.
We have contacted Xilinx and requested updated information on the chip but we were informed that it is an old algorithm and chip and that Xilinx do not have the resources to continue supporting it any more.

I can only recommend that you contact Xilinx and ask for their recommended programming solution.

I regret that we could not be of more help on this occasion.

Best regards,

Neil Parker
Dataman Programmers