Sorry guys, I thought the thread had gone dormant, and haven't looked in for a while.
(There are some serious distractions atm...)
What happened to the ceramic IC (U15 I think)? It's looks like it has modeling cement all over it.
Yes, the metal lid is a little corroded.
It's a 6844 DMA controller, and used for disk I/O.
I've left it out and it makes no difference in or out. It shouldn't be needed just to get a clear video screen with the monitor prompt.
Not sure at what point you took the pictures of the board, it appears dusty. Did you clean it and did you contact cleaned the sockets and re-seated the ICs?
It does look a little worse in the photos than it is. It's been brushed down and washed with IPA.
As I've replaced just about all the IC's that appear to be required for basic video operation, they have been reseated. The socket pins have oxidation where they are exposed, but clean where they contact the IC pins.
Which PAL read correctly and which do you only suspect did?
How do you know?
Can you provide those dumps so we can perhaps see if they make sense for address decoding?
I'm 99.9% sure of the address decoder PAL (U32) because it's outputs are chip select signals, and they match the memory map given in the documentation.
With the other PAL (40), it's much harder to tell, but I have no reason to believe it's not also good. Because:-
* U32 is good
* It's contents seem to be some orderly patterns of values
* These chips are robust TTL, programmed by burning metallic fuses.
Unlike more delicate MOS devices, or EPROMs that do eventually leak away the charges used to store the data.
Here are the PAL dumps:-
U32:
https://pastebin.com/k7SLcLCqU40:
https://pastebin.com/XeirNesjThe pin dumps at the end of these are probably the most useful parts.
I plan to do some more signal inspections with a CRO, but my next plan of attack is to come up with a ROM emulator using RAM.
With this I can store short test programs into the RAM, and have the processor run them as if from the ROM.
Starting out testing very basic things such as just the CPU, and then individual devices, building up to more complex subsystems such as the dynamic RAM, and the video. This should be much more orderly and systematic than using the monitor ROM which assumes all subsystems are operational.
Part of developing the ROM emulator will need a working system to test it on, and I have a Tandy CoCo to use for that, but it's not working either. (having a bad run with 6809 based systems atm!) I've just bought another CoCo, so I'm about to see if that works (seller said it had issues), and maybe use it to get the first CoCo going.