I agree 100% Gary.
One of the great advantages of the S100 bus is that you can add (or remove) components in stages to get things working.
As Gary stated, start with a Z80 CPU board preferably one with its own onboard ROM.
Show you can on reset get it to HALT. 76H in ROM, first at 0h, later at the “boot” address. No RAM is required.
Add whatever board you are using for character displays (e.g. our Console-IO board).
In ROM continuously output a character to the screen. Again no RAM is required
Add whatever console input board you are using.
Continuously output the last keyboard character entered. No RAM is required.
Next add RAM board.
Either use my “stackless” monitor Gary mentioned below or write a routine to place 76H in RAM and jump to there. Then a routine to display the keyboard character…
Next add the Z80 Master monitor (or your own) and thoroughly check hardware. Copy, move memory etc.
To bring up CPM, by far, the easiest is a non-banked version of CPM3 on the Dual IDE board. The web page shows how to do it.
I know this is a long process but believe me it’s the fastest in the end. Plopping in 4 or 5 new boards and hoping to get everything working at once is difficult. Not impossible BTW, if you know your electronics and use a logic probe an experienced hardware guy can quickly nail a problem. The reason I have so much “bling” LED’s is they quickly focus in on where problems are.
From: yoda [mailto:yo...@r2d2.org]
trying the big bang approach never has much success - good luck. You need to do this piece meal. I actually have done this as I had no S100 system prior to building the boards. My approach was to first write a simple loop in ROM that did an out to the serial port in a loop. I plugged in the CPU board populated and the minimal parts on serial board and made sure the CS was pulsing on the SIO chip. Next I proceeded to write a hand initialization of the SIO chip and a simple loop to output a character in a loop - I call that my scream test. Once I have that working I know the CPU and SIO board are working. Next I took John's RAM test that is unrolled and does not use a stack to bring up the memory board. Again simple loops on memory addresses are useful for making sure basic address decoding in working on the memory board. Once memory is working get the Monitor loaded in ROM. I don't have the floppy board but John has pretty good bring up notes on his page. Bringing up any board is a similar process - populate the bus and control logic and use simple loops to make sure address decode and CS functions work - them populate more of the board and write small exercisers to test new function added. This may seem to take longer but in the long run it is shorter and less chance of damaging chips. Also it is a lot of fun debugging and building this way.
All of the software is on the S100Computers web site Gary. Go to the software section. I don’t have a CPM 2.2 version (only 3.0). While I could copy a disk for you the console IO ports would not match up unless you are using the Console-IO board. You really have to modify the code for own BIOS. Easy to do.
From: n8ve...@googlegroups.com [mailto:n8ve...@googlegroups.com] On Behalf Of gek...@gmail.com
I'll hopefully soon have a Z80 CPU card, a ZFDC floppy controller, 4mb SRAM and Serial IO cards.