SS-50 1MB RAM board

One of the really cool things about the SWTPC 6809 CPU board is the ability to extend the 64K memory map to a full megabyte by use of Dynamic Address Translation (DAT). I’m not convinced many people actually had more than 64K back when SWTPC was making their CPU board, but when I designed the Corsham Tech 6809 one of the features added was 128K of RAM.

It seemed natural that people with either our CPU board or the original SWTPC board would want to use the extended memory scheme, so it didn’t take long for us to design this 1 MB board.

There were no existing memory boards to model the design after so this was done based on looking at the CPU board schematics and the crude description of how DAT worked. A number of customers have confirmed this board works well in OS/9 systems, as well as our XMEMTEST extended memory test program.
Features

• Fully compatible with the DAT design.
• Supports A16-A19.
• If not all four extended address bits are desired, any of them can be ignored.
• Each of the sixteen 64K memory banks can be enabled/disabled via switches.
• RAM chips are static. No refresh logic.

SS 50 1MB RAM




SS-30 USB Serial Board

As are most of our designs, this board was meant to address something that we wanted a better solution to. RS-232 interfaces with DB-9 connectors always need a USB-to-RS-232 converter for use with any laptop and most desktops at this point, so having a pure USB serial interface got rid of some messy cabling on our systems.
This board is fully software compatible with the original SWTPC MP-S board as well as our SS-30 Serial Board. It uses an MC68B50 ACIA just like the other two boards, so software can’t detect any difference between this board and a more traditional serial board.

Features

• Fully software compatible with more traditional serial boards.
• On-board baud rate generator provides 1200, 2400, 4800 and 9600 baud.
• Uses an FTDI USB/serial chip. Supported by all major OSes (Windows, OS X, Linux).
• Connection to your computer is via a USB B connector.
• CTS can be hard-wired or taken from the serial port.
• Jumper for NMI or IRQ interrupts (not normally used).

SS-30_USB_Serial


SS-50 65C02 CPU Board

As many of you know, I started my journey in microcomputers with a KIM-1 in 1978 which was a 6502 based system. My next machine was an OSI SuperBoard, then an Atari 800, and Apple ][, and my first full-time job was at Franklin Computer Corp where I spent most every day doing 6502 programming., etc.

There was at least one commercial board for the SS-50 bus with a 6502, but it was never very popular. Given my interest in this processor I decided to create my own CPU board:

Basic specifications:

  • WDC65C02 processor running at 2 MHz. This is a genuine WDC chip, nothing with an unknown history that came from who knows where.
  • Full memory map of RAM. 0000-7FFF is always RAM while each 4K block in the upper 32K can be turned on or off.
  • EEPROM from F000 to FFFF.
  • Optionally, EEPROM can be enabled from E200-EFFF via a DIP switch.
  • We include a 28C64 (8K) EEPROM with CTMON65, but the socket can support 32K EEPROMs and two jumpers select which 8K region is visible.
  • A single-step switch is on top of the board. When an opcode fetch occurs outside of the EEPROM, an NMI is generated. Great for writing a single-step monitor.
  • The baud rate generator products x16 clock for 1200, 2400, 4800 and 9600 baud.
  • Power-on reset.
  • The monitor source code CTMON65 is available on our Github repository

This is an experimenter’s board as there was no code that I am aware of for a 6502 on the SS-50 bus. It uses the standard SS-30 I/O bus and most of those devices have plenty of example code for the 6800 and/or 6809 to use as templates for writing 65C02 code.



SS-30 Serial Board

Most of us use our PCs/MACs/Linux machines with a terminal emulator program to connect to our SS-50 systems, usually with a USB serial port. That works great, but adds an extra signal conversion that doesn’t need to happen. With our new USB based serial board, your SS-50 machine can directly plug into the USB port of your main computer.

Uses a 68B50 ACIA: Fully software compatible with SWTBUG, SBUG and any other vintage software. The B version runs at 2 MHz (6809 use).
Uses a well established FTDI serial chip, not a lesser brand part. Drivers for all major operating systems are either already in the OS or easily installed from the FTDI site.
USB A port to plug into your computer.
Includes a USB A to B cable.
Board rate generator on-board for 1200, 2400, 4800 and 9600 baud. Those signals on the bus can be used for other things (like extended address lines for the 6809 based systems).
USB power from the USB bus, so when you shut down your SS-50 system the main computer doesn’t lose the com port.
The bare board option has the surface mount parts and USB connector pre-soldered onto the board, and includes the 2.4576 MHz oscillator. Remaining parts are common and easy to find.
Just set the baud rate, swap this board for your existing serial board, plug it into your computer and you’ll be up and running. For most machines it takes a minute or two for the OS to properly identify the port, but then it is always available. The board shows up as a normal serial (COM) port, just select the new port and you’re good to go.

SS-30 Serial Board Manual rev 3
SS-30 Serial Board Manual rev 4

Rev 3 schematics


Rev 3

Rev 4 schematics

SS-30 Parallel Board

SS-30 Parallel Board Manual

SS-30 bus extender

For those of you using one of our SS-50 motherboards and find yourself needing more I/O ports, this board will add an additional six SS–30 ports via a connector already on your motherboard. This extender simply plugs in and you’ll have the full eight slots available for more I/O boards. As you can deduce from this picture, each slot has a fixed address unlike the two slots present on the motherboard:

SS-30 Prototype board

Two versions were produced of the SS-30 Prototype board, small and large.


Yet another experiment that we needed to develop our own products. This is meant to allow someone to experiment with building their own SS-30 (I/O) boards. The two connectors on the left have +5 and ground, while all the SS-30 pins have connectors on the bottom to make it easy to build a circuit with. Trying to accommodate both the SS-30 and SS-30C busses, this board has labels for both. Due to a lack of double-checking, the board pictured above has a bizarre error… all the lettering below the CORSHAM logo is on the back side of the board in a mirror image! Details, details, details.
UPDATE The board above works fine for our system since we don’t have a chassis, but didn’t work well in a real SWTPC chassis without removing the back panel. A new version was laid out that fits entirely in a genuine SWTPC chassis but I’ve yet to order any blank PC boards for it.

Large board
2019: Customers often come up with good ideas for new products or improvements to existing ones, and this was certainly one of those cases! Basically, he suggested adding more breadboard space, and adding a spring loaded connector on top for running wires to external circuitry. The resulting product is our new board:


SS-30 SS-50 technical notes

On this page:
– SS-50 6800 CPU Power-On Reset
– SS050 FAQs
– SS-50 and SS-30 standards

SS-50 6800 CPU Power-On Reset

Update (2/7/2021): Rather than using a 220uf electrolytic, use a 47 uf tantalum capacitor instead.

Update (2/5/2021): A previous version of this page said to add the capacitor to U1… that was incorrect! It is definitely on U4, the MC6875!

All existing versions, including up to 3A, of the SS-50 6800 CPU Board have a problem where power-on reset does not work. A part is missing. This is not a severe problem, as the user can press the RESET button on the board or the motherboard to do the reset, but it can be easily fixed.

You’ll need to solder a 47 uf, 16v (or higher) tantalum capacitor to the back of the board. The negative side of the capacitor goes to U4 pin 8 (ground) and the positive side goes to U4 pin 12. This is a picture from when I was using a much larger electrolytic capacitor, but I’ve switched to a 47 uf tantalum cap for all new boards:

All future revisions of the board will include this fix.

SS-50 FAQs

Q: Where can I get a copy of the SS-50 standard?
A: There is no standard, just a loose specification manufacturers followed when designing boards. The first SS-50 machine was from SWTPC and had a 6800 processor, so the buss was closely designed around that processor’s architecture. When SWTPC added a 6809 board they more-or-less followed the previous use of most pins on the buss, but also changed the purpose of others. Other companies began making compatible boards based on what was already on the market. To paraphrase Dr. McCoy of Star Trek fame, “Dammit Jim, I’m a buss, not a standard!”

Q: I keep hearing SS-50 and SS-30. Are they the same thing?
A: No, but closely related. The SS-50 buss is the main processor buss which includes all the address, data, and control signals needed to control the buss or respond to the processor board. It has 50 pins. The SS-30 buss is meant only for I/O. Decoding addresses takes a few chips that chew up real estate on a peripheral board and add cost, so SWTPC does the decoding on the motherboard and runs only essential signals to the peripheral boards. This is the SS-30 buss, and has 30 pins. Only a few address lines, data lines, and very few control signals.

Q: What are those strange connectors?
A: Those are Molex connectors which SWTPC used on other, non-computer, products. Hey, use what you’ve got in stock to save development time and stocking cost! They are still available from many sources, but the cost has gone up tremendously since they aren’t widely used anymore. The male connector with 10 pins, as used on motherboards is AMP/ TE Connectivity part number 1-640384-0, while the female connector used on plug-in boards is Molex/Waldom 09-48-2101. There is also a polarizing plug that goes into the female connectors and is Molex part number XXXXXXX.

Q: Which pin is pin 1 on both the SS-30 and SS-50 busses?
A: Technically, there were no pin numbers. SWTPC simply used the name of the line and never referenced a pin number. Many companies use http://www.cs.unc.edu/~yakowenk/swtpc/ss50.html as a guide, but I am aware of at least one board where the pin numbers were exactly the opposite direction.

Q: Boards don’t seem to plug in without a lot of force. Are you sure they are meant to plug into the motherboard?
A: Yes, the Molex connectors offer a lot of resistance at first but eventually get looser with insertions and removals. Make sure the polarizing plug is aligned properly with the missing pin on the motherboard. Some people insert a small screwdriver or used dental tool into each of the female connectors to loosen them up, but be very careful not to over-loosen them or else some of the pins might not make contact.

Q: Why are there so many pieces to build a complete system?
A: This is a clone, so it has an SS-50 buss for the CPU and memory, and an SS-30 buss for the peripheral devices. The original systems had a motherboard, CPU board, memory board(s), serial console board, terminal, etc, which means our system does too. Back in the day, people were driven by cost (just like now) so systems were modular, allowing someone to buy exactly what they wanted (or could afford) while building their system.

Q: What is the bare minimum to get started?
A: The motherboard contains the framework for the other boards to plug into, and is required. To use a terminal for a console, a serial board is required. We have two CPU boards, one having a 6800 and 16K of RAM, and a 6809 CPU with 128K. Only one CPU board is required.

Q: What can the bare minimum systems do?
A: Actually quite a lot, thanks to all the available software on the net. If you want to re-live the early days of the microcomputer revolution, there is plenty of RAM on either CPU board to load up Tiny BASICs, play games, write assembly language code, etc.

Q: How about mass storage?
A: We use our SD Card System. Our CPU boards include the low-level code providing drivers for the SD system, along with monitor commands to boot an operating system.

Q: What OS do you provide?
A: For the 6800, we use FLEX. For the 6809 we use FLEX/9 but have talked to various groups about multi-tasking operating systems. A different (still not released) I/O board is being developed to add additional capabilities for some OSes.

Q: An OS is great, but is there any software for those old systems?
A: Absolutely! Try looking at the FLEX User Group site: www.flexusergroup.com. They also have a large FTP site with a bunch of disk images. Drop those DSK files onto the SD card, mount the file as a disk drive, and you’ve got the disk contents for your use.

Q: So what do you guys do with YOUR systems?
A: I’ve got both 6800 and 6809 systems on the bench, both of which run FLEX, and are both a lot of fun to just program. I enjoy assembly language programming, so I’ve been working on some better tools for writing code.

Q: This stuff is all old technology, so shouldn’t it be cheap?
A: Sorry, this has a long answer. Some vintage parts are getting harder to find, demanding higher prices, or available in small quantities which have higher shipping costs. Some of these parts haven’t been manufactured since the early 1980s. Another big cost factor is that a lot of parts are needed, so while a more modern part might cost a few dollars more, the “more vintage” design sometimes requires several dozen of the older technology devices. Yet another factor is that the cost of printed circuit boards is based on the size of the board and the number being ordered. Ordering a single board might have a $70 set-up fee, and then $50 for the single board. Bumping up to 30 boards still has the $70 set-up fee, but the per-board cost might drop to $10. Given the size of the boards and the fact that each board has only limited functionality (as per the original design), the fixed prices are fairly high. This is a slightly political issue, but keep in mind the 25% US tax (it’s a tax paid by every American) on goods purchased from China, which is where a large percentage of electronic parts come from. Invoices from major US based suppliers show the dollar amount I had to pay in “tariffs” (it’s a tax) for that order.

Q: What else is needed, really?
A: Just a terminal and an RS-232 cable OR a personal computer with a serial port, cable, and a terminal emulator program. At shows we always use Wyse 30 terminals as they are available nicely refurbished for about $200.

Q: If I buy one, how hard is it to get running?
A: Before we ship a complete system, everything is plugged in, the system is brought up, then it is disassembled, packaged, and shipped. It’s really quite simple to plug in the boards and get running. Our suggestion is to set up just the motherboard, power supply, CPU board and serial board. Once your terminal is talking to the system, then it’s easy to plug in the parallel card, connect the SD card system, and boot into FLEX.

Q: Can I use Corsham Tech boards in a real SWTPC system or use SWTPC boards in a Corsham Tech system?
A: Absolutely! I sometimes bring several real SWTPC boards to demos, but they tend to draw a lot of current. Their 8K RAM board draws more than our complete 6809 system with a meg of RAM.

Q: Is there a case to put a system in?
A: No. It is expensive to have a case built unless we buy in very large numbers which we will probably never sell most of.

SS-50 Specification

This isn’t really any definitive definition of the SS-50 bus, as boards were simply produced that worked with other SS-50 boards. When SWTPC devised the bus, they just made things work and other manufacturers made compatible boards. Years ago I found two sites that gave a clear description of the pins for both the SS-50 and SS-50C versions, and since they haven’t been touched in decades, I decided to copy the information here just in case the original pages ever go away.

The SS-50 bus

The SS-50 was the main backplane in 6800 based SWTPC machines, and connected the CPU board with memory, disk controllers, and so on. As was common in that era, a board usually did just one thing, and did it well, so a system would have a CPU board, one or more memory boards, a serial board connecting to a terminal, and either a cassette I/O or disk controller board for program/data storage. Physically, the SS-50 bus consisted of rows of male Molex connectors, spaced 0.156 inches apart. The boards that plugged into it had the corresponding female connectors along one edge, rather than the more modern (and cheaper) printed-circuit contacts. The SS-50 bus had all signals from the processor. For I/O, see the section below about the SS-30 bus.

All signals starting with “/” are active low.

  1. /D0 – (complement) data bus line 0
  2. /D1 “
  3. /D2 “
  4. /D3 “
  5. /D4 “
  6. /D5 “
  7. /D6 “
  8. /D7 – (complement) data bus line 7
  9. A15 – address bus line 15
  10. A14 “
  11. A13 “
  12. A12 “
  13. A11 “
  14. A10 “
  15. A9 “
  16. A8 “
  17. A7 “
  18. A6 “
  19. A5 “
  20. A4 “
  21. A3 “
  22. A2 “
  23. A1 “
  24. A0 – address bus line 0
  25. GND – ground
  26. GND – ground
  27. GND – ground
  28. +8V – power line
  29. +8V – power line
  30. +8V – power line
  31. -12V – power line
  32. +12V – power line
  33. INDEX – no pin – prevents backwards insertion
  34. /M.RST – (complement) manual reset
  35. /NMI – (complement) non-maskable interrupt
  36. /IRQ – (complement) interrupt request
  37. UD – user-defined
  38. UD – user-defined
  39. /Phase 2 – (complement) processor clock 2
  40. /VMA – (complement) Valid Memory Address
  41. R/W – Read / (complement) Write
  42. /RESET – (complement) Reset or power-up
  43. BA – Bus Available for DMA
  44. /Phase 1 – (complement) processor clock 1
  45. /Halt – (complement) halts the processor
  46. 110b – 110 baud clock signal
  47. 150b – 150 baud clock signal
  48. 300b – 300 baud clock signal
  49. 600b – 600 baud clock signal
  50. 1200b – 1200 baud clock signal

The SS-30 Bus

I/O was handled on a distinct 30-pin bus (the SS-30), which was generally similar to the SS-50 but had a “board select” signal instead of the address bus. The logic to select individual I/O boards in the SS-30 was hardwired to memory-map them into four-byte slots starting with board 0 at address $8000. Very few address lines from the SS-50 bus were present, usually only A0 and A1 (called RS0 and RS1) but the two UD (user defined) pins could have A2 and A3 connected to them.

  1. UD – user-defined
  2. UD – user-defined
  3. -12V – power line
  4. +12V – power line
  5. GND – ground
  6. GND – ground
  7. INDEX – no pin – prevents backwards insertion
  8. /NMI – (complement) non-maskable interrupt
  9. /IRQ – (complement) interrupt request
  10. RS0 – register select – like A0
  11. RS1 – register select – like A1
  12. D0 – data bus line 0
  13. D1 “
  14. D2 “
  15. D3 “
  16. D4 “
  17. D5 “
  18. D6 “
  19. D7 – data bus line 7
  20. /Phase 2 – (complement) processor clock 2
  21. R/W – Read / (complement) Write
  22. +8V – power line
  23. +8V – power line
  24. 1200 baud clock signal x 16
  25. 600 baud clock signal x 16
  26. 300 baud clock signal x 16
  27. 150 baud clock signal x 16
  28. 110 baud clock signal x 16
  29. /RESET – (complement) Reset or power-up
  30. /Board Select

Microchess for the KIM clone

(see also the Microchess page)

Downloads:

The hex file MicroChessOut can be loaded directly into the KIM CLONE and run from $2000
Archive with source.

Following the header "Peter Jennings, www.benlo.com" I was pleasantly surprised to see the website still active:
http://benlo.com/microchess/index.html
http://benlo.com/files/Microchess6502.txt
The source code Microchess6502.txt contains the additional note on line 35:
"; Updated with corrections to earlier OCR errors by Bill Forster, August 2005."
Line 73 comments on the cross-assembler used:
"BMCC    =    $E5         ; was BCC (TASS doesn't like it as a label)"
Looking for information about TASS led me to:
https://www.c64-wiki.com/wiki/Cross_Assembler
Reading from "64Tass/6502Tass: Another native "Turbo Assembler", developed for DOS (6502Tass), later also for Unix, Linux and Windows32 (64Tass)," I suspect the 1996-2002 code by Peter Jennings used the DOS version, but I am running Windows 10 on a modern laptop and I can't find a way to run 16-bit applications without using third party tools like DosBox or an emulator in VirtualBox.
So I decided to try out Tass64.  I found a link to the Windows version on sourceforge, https://sourceforge.net/projects/tass64/.  The documentation is included in the zip file, and also here http://tass64.sourceforge.net/.
Without really reading the documents, I just ran Microchess through the Assembler and got errors.  Below are the errors I got, and how I fixed/hacked/patched each one.
First Attempt:
Error messages:    31
Warning messages:  3
Passes:            2
....Oof.....
Error Group 1:
MicroChessSource:37:8: error: general syntax
cpu 65c02
^
MicroChessSource:38:9: error: general syntax
page 0,132
^
Correction:
Change 37 to: .cpu "65c02"
Change 38 to ; page 0,132
Line 38 is commented out because 'page' "gives an error on page boundary crossing, e.g. for timing sensitive code" and I am simply going to put my faith in Peter Jennings and hope for the best here.
Line 37 can be changed to reflect the CPU you are using.  I got my parts assembled by Bob, and leaving "65c02" as the cpu version works for me on the KIM CLONE.  
Error Group 2:
MicroChessSource:729:6: error: general syntax
db      $2c             ; used to skip over LDA #$20
^
MicroChessSource:859:12: error: general syntax
Hexdigdata     asc     "0123456789ABCDEF"
Correction:
For all the lines that use "db" or "asc," change the pseudo-op to ".text"
Now I got:
-----------------------------------------------------------------------------
C> 64tass.exe -o MicroChessOut MicroChessSource
64tass Turbo Assembler Macro V1.55.2200
64TASS comes with ABSOLUTELY NO WARRANTY; This is free software, and you
are welcome to redistribute it under certain conditions; See LICENSE!
Assembling file:   MicroChessSource
Error messages:    None
Warning messages:  None
Passes:            2
Memory range:      $1000-$1524   $0525
Memory range:      $1580-$15dc   $005d
-----------------------------------------------------------------------------
I think I'd like to run Microchess from $2000 up in one block, so I will modify line 95 and 869:
Change line 95 to ";*= $1580"
and comment out line 869.
-----------------------------------------------------------------------------
Memory range:      $2000-$2581   $0582
-----------------------------------------------------------------------------
Now the source will assemble, but it won't work yet.  The Peter Jennings code with TTY was written for the "6551 Asynchronous Communications Interface Adapter (ACIA)," not the "standard TTY" routines built into the KIM monitor that we see in the First Book of KIM etc.  
http://archive.6502.org/datasheets/mos_6551_acia.pdf
https://en.wikipedia.org/wiki/MOS_Technology_6551
First, I comment out the ACIA addresses from line 42.
;ACIADat    =     $7F70
;ACIASta    =    $7F71
;ACIACmd    =    $7F72
;ACIACtl    =    $7F73
Then, I add in the addresses of the KIM monitor TTY routines for getting (blocking) and outputting 1 character.
; http://www.zimmers.net/cbmpics/cbm/kim1/kim-hints.txt - See "KIM SUBROUTINES"
TTY_GETCH = $1E5A  ; Register States: In to A, X preserved, Y = FF
TTY_OUTCH = $1EA0  ; Register States: X preserved, Y = FF, A = FF
Now, I move to line 822 and start making changes to the I/O Routines.
(1) Comment Out the Init function 825-829, don't need.  I leave the label and rts to allow it to work as a dummy sub routine rather than deleting all references to it in the code.
(2) Replace the meat of "syskin" on 833 with code to push the affected registers, call TTY_GETCH, and restore affected registers.
(3) Replace the meat of "syschout" on 842 to push the affected registers, call TTY_OUTCH, and restore affected registers.
Now the code after line 822 looks like:
;
; 6551 I/O Support Routines
; Replaced with KIM Monitor Routines for KIM Clone - Neil 2020
;
;
Init_6551      ;lda   #$1F               ; 19.2K/8/1
;sta   ACIActl            ; control reg
;lda   #$0B               ; N parity/echo off/rx int off/ dtr active low
;sta   ACIAcmd            ; command reg
rts                      ; done
;
; input chr from ACIA1 (waiting)
;
syskin         ;lda   ACIASta            ; Serial port status             
;and   #$08               ; is recvr full
;beq   syskin             ; no char to get
;Lda   ACIAdat            ; get
PHY
JSR TTY_GETCH
PLY      
RTS                    ;
;
; output to OutPut Port
;
syschout       ;PHA                      ; save registers
ACIA_Out1      ;lda   ACIASta            ; serial port status
;and   #$10               ; is tx buffer empty
;beq   ACIA_Out1          ; no
;PLA                      ; get chr
;sta   ACIAdat            ; put character to Port
PHA
PHY
JSR TTY_OUTCH
PLY
PLA
RTS                      ; done
IMPORTANT: I make use of the 6502 commands to push X and push Y, pop X, pop Y - PHX, PHY, PLY, PLX which work on the 65c02 but not the old-school 6502.  This probably won't be an issue for the KIM Clone, but if it is, it will be necessary to change the way you push and pop using your favorite method from back in the day, of one of the examples here:
http://6502.org/tutorials/register_preservation.html
Now I re-assemble the source code, adding the flag to output INTEL HEX format.  This is because Bob added support for intel hex to the [L] command on the KIM-1.  There are programs on-line (somewhere) for converting and dealing with the KIM paper tape format, but being allowed to Load in INTEL HEX format allows us to output something the KIM CLONE can read without no trouble at all.
-----------------------------------------------------------------------------
C> 64tass.exe --intel-hex -o MicroChessOut MicroChessSource
64tass Turbo Assembler Macro V1.55.2200
64TASS comes with ABSOLUTELY NO WARRANTY; This is free software, and you
are welcome to redistribute it under certain conditions; See LICENSE!
Assembling file:   MicroChessSource
Error messages:    None
Warning messages:  None
Passes:            2
Memory range:      $2000-$256e   $056e
-----------------------------------------------------------------------------
Now, I could use SecureCRT or Tera Term or some other fancy terminal to send the file as ASCII when I press the [L]oad command on the KIM-1.  Today, however, I will use the humble PuTTy terminal emulator.  And simply copy the hex to my clipboard, and paste it in PuTTy after pressing the [L] command.
KIM Clone v1.0B
237A 24 0000
:00000001FF52250D45350455220643330FCC8F02020299250B25010033250736340D3434CD
KIM Clone v1.0B
0000 00 2000
2000 A9 G
MicroChess (c) 1996-2005 Peter Jennings, www.benlo.com
00 01 02 03 04 05 06 07
-------------------------
|BP|**|  |**|BP|**|  |**|00
-------------------------
|**|  |**|  |**|  |**|  |10
-------------------------
|BB|WP|  |**|  |**|  |**|20
-------------------------
|BP|  |**|  |**|  |**|  |30
-------------------------
|BP|**|  |**|  |**|  |**|40
-------------------------
|**|  |**|  |**|  |**|  |50
-------------------------
|  |**|  |**|  |**|  |**|60
-------------------------
|**|  |**|  |**|  |**|  |70
-------------------------
00 01 02 03 04 05 06 07
20 00 00
?C
MicroChess (c) 1996-2005 Peter Jennings, www.benlo.com
00 01 02 03 04 05 06 07
-------------------------
|WR|WN|WB|WK|WQ|WB|WN|WR|00
-------------------------
|WP|WP|WP|WP|WP|WP|WP|WP|10
-------------------------
|  |**|  |**|  |**|  |**|20
-------------------------
|**|  |**|  |**|  |**|  |30
-------------------------
|  |**|  |**|  |**|  |**|40
-------------------------
|**|  |**|  |**|  |**|  |50
-------------------------
|BP|BP|BP|BP|BP|BP|BP|BP|60
-------------------------
|BR|BN|BB|BK|BQ|BB|BN|BR|70
-------------------------
00 01 02 03 04 05 06 07
CC CC CC
Personal Notes:
-The extended monitor on the KIM Clone has extra for string printing and more, so if I was doing a serious "KIM CLONE" port, I might look at rewriting a lot of the drawing functions.  
-It is really clunky how the screen re-draws after every CHARACTER -- which means I have to sit through 4 board redraws just to enter a move.  I want to update that code, because I don't have pre-digital age patience.
-My cross compiler of choice is ca65, part of the cc65 C compiler for the 6502.  Maybe a ca65 port of the syntax is something I might try.
There are great usage notes for this version of the game here:
https://obsolescence.wixsite.com/obsolescence/kim-uno-microchess
Too late now, but I notice he went through the exact same process changing the UART routines for his version of MicroChess for the Arduino KIM-1 emulator.

KIM Monitor KIM clone

KIM monitor as modified for the Corsham Tech KIM Clone board.

Notable changes:
* Removal of the code to save/load from cassette tape.
* Lunar Lander (First Book of KIM) added.
* Famer Brown (First Book of KIM) added.
* New X command from TTY to enter the Corsham Technologies xKIM extended monitor.

See also the Corsham github page.

Download the KIM Monitor repository copy here.

Note that you can use the standard KIM ROMs also, the KIM Clone is a KIM-1.