Quote:
Originally Posted by Slothie
I've made a small change to the diagnostic program on request, if the zero page and stack tests are OK it will then test the memory, when it finds an error it will loop continually reading that bad memory location. (This will be the first error address - $4000 on a fully working 16k PET, $8000 on a 32k PET, $2000 on a 8k PET, or the first invalid memory address over $0300 on PET with a bad memory chip).
Otherwise identical to v0.1
|
It might help debug using a scope if it would loop writing and reading, so the R/w controls can be verified. Also if it could do the same for zero page and stack.
Possibly with some way to flag if it passed during retest.
Colin’s PET seems to have a zero page fault, but he has a problem testing if that is a write fail or a read fail.