Problem programming flash MX29F002T

[Guest]

Hi Neil

well i finally managed to get a 40PRO to replace my S4! but i have a problem

I am trying to program a MX29F002T in a adaptor, the 40PRO finds the chip fine, but when i try and read it the programmer refuses to comming up with 'bad contact at pin 1 of programmed chip'

So i remove the whole adaptor and put it in my S4, this again finds the correct flash chip, only this time this programmer reads the content fine and indeed programs another chip just great! no problem!

Trying these 2 GOOD programmed chips still in the adaptor back in the 40PRO and it still comes up with the same error on both chips 'bad contact at pin 1 of programmed chip'

Now there cannot be anything wrong with my adaptor as it works perfectly in the S4 and has done so for a good few years

Now i have tried the diagnostic using the diagnostic pod on the 40PRO and it reports back just fine as no problems

So my question is, why is my old old discontuned S4 reading/programming the chips fine, when the 40PRO wont even read them comming up with error on pin1

Would you like a 40PRO fault log?

I have just put pictures up (please expand pics to full size once loaded otherwise you cant read them)

40PRO showing read error AFTER doing diagnostics with pod and passing

Here


S4 showing selecting same device, loading into S4 memory, programming and verify ok

Here


An SST39SF020 works fine in the adaptor in the 40Pro and S4

An ST29F002T works fine in S4, but also has problems in 40PRO, this time write error is 'programming device error ADDR=6A94h, DO=D7h, DI=27h'

Many thanks
Andrew

[Dataman (Neil Parker)]

Hello Andrew,

Can I ask you to create a problem report of the situation and email it to neil@dataman.com. Hopefully this will contain enough information to resolve the problem. If you could also include a selftest and selftest plus in the log it would help.

Regards,

Neil Parker
Dataman Programmers

[Guest]

Hi Neil

I have done some reasearch and think i have found the cure! Pin 1 on the MX29F002T is a reset (inverted) pin, BUT there is also an MX29F002NT which has NO INTERNAL CONNECTION TO PIN 1, and i am thinking this could possibly be the problem as the 40PRO is doing pin checking and of course it is open circuit and kicking off the error.

So i set the 40PRO for the MX29F002NT and low and behold it worked perfectly! no errors! programmed and verified fine!

I am guessing i had no problem with the S4 set to MX29F002T as that doesnt do pin checking and the status of there not being a intetrnal connection to pin 1 does not affect it programming the MX29F002NT when it is set to MX29F002T

Thanks for your help, I still find the S4 brill! i personally am still not convinced the 40PRO at the moment is better, I have a Intel N28F020 the 40PRO identifies as 89/BD a P28F020 and takes 64(hex) times to erase, but the S4 identifies it as 0D07 an intel 28F020 and again it works and erases perfectly 1st time (and quicker than the 40pro 64h erase tries), so am still not convinced i have made a good move with getting a 40PRO, am disapointed in it so far

Cheers
Andrew

[Dataman (Neil Parker)]

Hello Andrew,

The Macronix MX29F002T & MX29F002NT devices are identical, the only difference being that with the MX29F002NT device (pin 1 is NC - not connected) but with the MX29F002T (pin 1 is pin RESET). So you basically selected the wrong device. Of course the control program will report a problem on pin 1 - it is waiting for contact on this pin. These devices have the same ID codes and the same programming algorithm.

The S4 programmer doesn't provide the insertion test, so whether the MX29F002T or the
MX29F002NT is selected - it doesn't matter, as you have discovered.

I have a Intel N28F020 the 40PRO identifies as 89/BD a P28F020 and takes 64(hex) times to erase, but the S4 identifies it as 0D07 an intel 28F020 and again it works and erases perfectly 1st time (and quicker than the 40pro 64h erase tries),

- 89/BD are the right ID codes for the P28F020 and N28F020 flash devices
(P and N marks the package type). I don't understand what the 0D07 means?
- Your information about the erase function is unclear.
Max. number of erase attemts for the device is 3000 (from Intel's programming specification). PG4UW software displays the number of erase attempts in the INFO window. S4 doesn't display this info, so there is no way to know that the erase action was successful on the first attempt? The number of erase attempts is a problem of the device, not a problem of the programmer!
- What do you mean by: "quicker than the 40pro 64h erase tries"? Please provide the timing of the erase action on the S4 and Dataman-40Pro programmers exactly and we will look at it.

I think the only problem with your Dataman-40Pro is the programing error on the SST29F002T
device. But I need the complete content of the LOG window in order to solve the problem. This can be obtained using "Help > Create problem report" from within the control software after the error is displayed.

Regards,

Neil Parker
Dataman Programmers