Congrats', Dwight. Nicely done!

Now to make the changes to the PC boards. The adapter
could be used for some other 6530 application but that would most
likely need the EEROM programmed and the PAL programmed for that
particular application. The PAL isn't as much of a problem as the
EEROM.
I program the EEROM on the KIM-1, in place. I don't have adapters to
do SOT parts. The PAL is a DIP so not as much an issue.
Another issue with the EEROM is that the address and data lines are
scrambled. This was done because routing of traces were first priority.
Things like getting D0 to the D0 pin were not as important.
Any file would need the proper address and data scrambled.
I has two jumpers to select -002 or -003 I/O decoding and the
other is for the programming enable. You don't want to accidentally
write over the EEROM ( although it is easy to restore ).
The entire thing is about 0.65 inches thick, including a socket on the
KIM and a socket for the 6532. One could use lower profile socket or no
socke at all on the KIM but the top socket could only be lowered a
little with a low profile socket. I've used machine pin sockets for both.
You can see that my 6502 is also on a machine pin.
I've got a relatively complete diagnostic code for the debug board.
The first two diagnostic programs were the most difficult. These needed to
be written with no usage of the RAM. Not that easy on a 6502. The first
test just sees if the processor is running. The second is a simplified
RAM test for the 2102's. At least it shows the failing bit with a blink
code on an LED but I ran out of register to show the address. All of
the there diagnostic programs expect the page0 and page1 RAM to
be working.
I'm not planning on doing any audio or TTY test but will do a check
sum test of -003.
Each diagnostic fits in a 1K window. Most of these are quite small
and leave a lot of extra space that one could add other ROMable
code. The diagnostic board supports a 27128 so there are 32 1K
possible blocks to use.
Dwight