Compare function gives 'FF' for ROM

[Guest]

I load one 29040 EEPROM into RAM, then COmpare it with another. At 50012 it shows a difference which is correct, but at 50013 and onwards it says that the ROM has FF in it. However, if I DR (dump) the ROM, it does NOT have FFs in it and the next locations are in fact identical!
This happens whether I do it manually on the S4 or remotely. Any ideas what is going on!

[Dataman (Neil Parker)]

Hi,

Which version of the library are you using and what is the manufacturer of the chip?

Neil

[Guest]

Alg 74 ref 0207 is still visible on the S4 and it was lib 1.11.

I have not tried 1.12 but the 1.12 readme did not say there were any bugfixes.

I don't have the chips to hand now but the make had 3 letters A?? (don't think it was AMD)

[Guest]

1.11 lib
it was AMIC chip
ALg 74 ref 0207
lib 1.12 says bugfixes=none so I did not try it.

[Guest]

Hi
Try this...
Select 29040 device (AMIC)
LOAD it into RAM
Do COmpare and check it is all same.
EDit 3F000 in RAM to alter it to say 55
EDit 40001 in RAM to alter it to say 55

Now do COmpare ->>
00000-7FFFF=00000
3F000 RAM=55 ROM=8E (hit enter to cont.)
40001 RAM=55 ROM=62
40002 RAM=66 ROM=00
40003 RAM=BF ROM=02
40004 RAM=0F ROM=00 .. etc. always wrong now!

Seems to happen when modify any location above 40000, but OK below this. Seem to get FF if I try the same thing at 51000.

Does it do this on yours S4 or it it my S4 that is faulty?

[Dataman (Neil Parker)]

Hi,

COMPare shows correct result only on the first address after burn has failed. The following addresses are not correct for some devices, specifically for EEPROMs and Flash.
We will try to fix this for the COMPARE function.

Neil