Guys before we go to C code etc., is the a simple chip initialization routine such that at least one line or character can be placed on the screen to check out the hardware. Preferably in Z80 or 8086 code.
From: n8vem...@googlegroups.com [mailto:n8vem...@googlegroups.com] On Behalf Of yoda
I think if you are going to be an earlier tester of this board you need to be able to do hardware support as well. This board "should work" as it is based on the N8VEM ECB design. There will probably be some complications. Porting the software is the least of the work - transcribing from one language to another is not that hard with software that already works. It is also much easier if the software is written in a somewhat higher language than assembler. My plan is I will write my code in C that will run on the 68K using gcc cross compiler, Z80 with SDCC and could run on x86 with gcc cross compiler though I don't plan to test that as I don't have any plans for using or supporting x86 as I just don't like the architecture of x86 in general. I believe there is a C compiler for 6502 as well but have not delved into that yet. It is fun to write assembler once but it is not productive to do it much more. The monitor I have written for the 68K is > 99% C is a derivative of John's monitor but I am doing in a way that should be portable. My next target will be to port this to z80. The monitor is straight forward for z80 I think - the interface to CPM may be a little more challenging. I am not done yet still getting s-record load and IDE disk running. Also I need to do some more refactoring - not happy with it yet. I will post the portable version when it is further along, i.e., boots CPM 68K.
So the net of this is - this board is more of a hardware bring up not a software driver project, so if you are not comfortable with hardware bring up you probably should not be one of the early users of the board and wait till the board is debugged and a second round of boards are produced with any changes.
I'm re-posting in case you missed my earlier post.
We have 3 volunteers to work on software for 3 different processors for the Prototype S100 uPD7220 GDC Board,
I'd just like to clarify if your offer to provide hardware support is still open, if so how many PCB's would you need ?
I anticipate this being a longer term project so hopefully shouldn't call on you too often :-)
Todd has offered to co-ordinate the PCB procurement and distribution.
I have uploaded the modified KiCad files to the Wiki, the only changes were to replace the 15 pin Dsub connector for a 2 x 8 IDC connector wired the same as the console i/o board, and updated the board identifier text (bottom right corner) Andrew has checked the schematic change and has given it the OK
So if everyone is happy then I guess we are ready to order.
regards and thanks