XGecu T48 Programmer issue - NEWBIE

[CAjoe]

Newbie here. I've been using my XGecu T48 Programmer to read and program EPROM's for over a year now without any issues. Last night, I tried to read a AT27256 EPROM and I received "Check ID Error! Checked ID is:0x 8F 04". I tried other model EPROM's and received the same error. I updated the software and firmware last night. That didn't help. Then I sprayed DeoxIT into the disconnected programmer, and left it upside to dry for the night.

This morning, I tried again and got the same error on several model chips. In the Xgpro V12.66 software I'm using, if I uncheck the "Check ID" box, I can read the chips just fine. I never had to do this before. This setting is on by default every time you change the chip model in the software.

Is there a connector in the T48 that is used to perform the Check ID function that might be faulty? Or is it something else? I'm tempted to just buy another one from Amazon so that I can see if the new one does it too.

Any help is appreciated!

Joe

[coromonadalix]

i think

1st you should try to contact the company, and ask  if your programmer is genuine or not and behave correctly upon eeprom insertion / detection

[CAjoe]

I tried. But their website is in Chinese.

Joe

[CAjoe]

I just tried it on another Windows PC, and it did the same. I wonder if it has always been there and I never noticed since I'm usually burning EPROM's and not reading them. Hey, I'm old.

[oPossum]

The EPROM you have may be a remarked National NM27C256

[oPossum]

Atmel AT27C256 is 29 8C

[CAjoe]

Thank you for that information! I decided to try every 27256 28pin option in the software with a ST M27C256B inserted. Four options worked. Catalyst CAT27256, Fujitsu MBM27256, Greenwich GR27256, and NEC UPD27256. Even though the markings on the chip have ST brand, the ST selection didn't work.

So I tried a blank check on a new ATMEL AT27C256R using all possible 27256 28 pin options in the software. The result was the same as above. The same four worked. The ATMEL selection also didn't work.

What the heck? Oh well, at least I found a way to make things work.

Thank you!

Joe

[oPossum]

I decided to try every 27256 28pin option in the software with a ST M27C256B inserted. Four options worked. Catalyst CAT27256, Fujitsu MBM27256, Greenwich GR27256, and NEC UPD27256.

Those parts all appear to not support reading the product ID, so the T48 probably doesn't check the ID when one of those parts is selected.

As a general rule 27xxx parts do NOT support ID and 27Cxxx parts DO support ID.

AT27C256R is 1F 8C


I have attached a list of manufacturer ID codes. That will be the first byte of the product ID.

[oPossum]

So I tried a blank check on a new ATMEL AT27C256R using all possible 27256 28 pin options in the software. The result was the same as above. The same four worked. The ATMEL selection also didn't work.

Did it have the 8F 04 ID or something else?

[CAjoe]

Thank you for that list. How does the list work with the 1F 8C? When I search the text for "1F", I find it by Atmel. But the 8C?

I just ran a ID Check on the ATMEL AT27C256R and it returned "1E 8C". I also ran the ID Check on the ST M27C256B, and it returned "8F 04".

Joe

[oPossum]

Oh, that's interesting. When I looked at the datasheet for the AT27CR256R it showed the mfg ID as 1E.  I assumed that was an error in the datasheet because 1E does not have correct parity for the mfg ID. Fixing the parity makes if 9E - that is for Exel. Changing bit 0 to 1 makes it 1F. That is correct for Atmel, so I incorrectly said the ID is 1F 8C. Since you have read 1E 8C from an actual part the datasheet must be correct despite the parity being wrong.

I have never been able to find a list of device codes for EPROMs. So I look at datasheets based on the mfg ID.

[CAjoe]

Just because I could, I purchased a second T48 from Amazon. I used my other computer like before. When I connected the T48, I was prompted to reflash the firmware, which I did. Then I pulled a ST chip I know was seen as ST brand before because I had just burned something to it. The device gave me the same odd error. When I changed to the Fujitsu, it worked. I think they screwed up their chip ID tables somehow.

I can't rollback the software because the firmware update won't allow it.

I found an email address for contacting them for support, so I'm going to try that and see what happens.

Joe