Products > Test Equipment
Just got a Tek 2465A, couple questions (how I screwed the calibration data)!!
usuthu65:
Hi all,
Glad my data is of some use!
Regarding the inability to compute the checksum, is it useful for me to repeat the Exerciser 02 video to see whether something has changed in the data (i.e. to get a handle on where or what the checksum is doing)? Or do we not expect any changes? I'm happy to repeat the process if you would like. Just let me know.
Cheers.
MarkL:
--- Quote from: usuthu65 on March 29, 2018, 09:29:08 pm ---Hi all,
Glad my data is of some use!
Regarding the inability to compute the checksum, is it useful for me to repeat the Exerciser 02 video to see whether something has changed in the data (i.e. to get a handle on where or what the checksum is doing)? Or do we not expect any changes? I'm happy to repeat the process if you would like. Just let me know.
Cheers.
--- End quote ---
I don't want to waste your time. The checksum program failed on two different data sets, so it's probably something I'm doing wrong.
The data should be the same from run to run, but if you find yourself with some spare time and you want to verify it, it would be good to know.
alpher:
I've played with my programmer/ cable-clip a little tonight and quite frankly I lost confidence in this whole setup, let me elaborate.
First thing I noticed is that even though programer complains about mismatch after just a few bytes (like 1D), it actually programms the whole chip, just with almost every second byte being higher by 1 (like LSB being stuck high but only every second or fourth location) ? :-//
Now is it happening during read or write is hard to determine, I know the programmer does work mostly fine using the zif socket, checked the cable/clip assembly a few times with a meter and they check out fine every time. I've programmed EEPROMS in circuit using this very clip mostly OK, (sometime it does error out).
I've jumped the CS2 to Vcc with 10 ohm resistor this time, the result is in the 2465A usuthu65 written-read zip file.
I've also tried Mark's test program in both locations 2160 and 2260, the resulting reads are the same as for direct writes with my programmer.
I've actually went full medieval with 2465a_test_1 , found an ancient 27512, erased with UV eraser that hasn't been used for ~10 years, programmed and voilla!! :) :) :) :) :)
Unfortunately when it was all said and done, still " TEST 04 FAIL 13 " >:(
I thing I'm going to wait fot the dallas chip that I've ordered, should be here after the weekend, at least I'll have a guarrantee that I'm reading the memory right.
Could be that the actual SRAM is defective? We'll see.
Attaching also firmware dump from my scope.
alpher:
Actually, I will read the very U2160/2260 through the cable/clip assy.
See if it matches, this way I will know if at least reading works right.
MarkL:
Bummer that didn't work.
So... When you tried 2465a_test_1, did it write the usuthu65 data correctly? Did you check it via your programmer or via the exerciser? Maybe try a spot check on some of the values via the exerciser without the programmer attached. Maybe it's interfering.
You can also use the exerciser to determine if the programmer is writing correctly.
It doesn't seem likely the SRAM is bad since you started with a working scope.
Another explanation is that there's more data somewhere besides this block that it's checking.
I will look at the firmware dump tomorrow.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version