Hugo Holden
Veteran Member
I think that we have a known hardware problem that would need to be eliminated/solved before the CPU could properly execute code. The fact that pin 30 of the CPU's data line was reported by Desperado as being stuck low. It could be a good idea to find the cause of that first.. Or at least check that again, with the current Kernal ROM program running, which in theory should show pulses on all the data lines as they strobe between 00 and FF in the process of writing to $8000, in case it was a bad measurement beforehand. But obviously it is equally important to check the address lines and the outputs of UD2 again.