Hi Alexandre! Thanks! Yes that would be great! Honestly, I don't know much of anything about MSX. Assuming we start with this as our baseline configuration 1. N8VEM 8 slot active termination S-100 backplane http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=S-100%20ba… ne 2. S100computers.com and N8VEM S-100 Z80 CPU board http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=S-100%20Z8… PU http://www.s100computers.com/My%20System%20Pages/Z80%20Board/Z80%20CPU%20Boa rd.htm 3. S100computers.com and N8VEM S-100 VDP http://n8vem-sbc.pbworks.com/w/browse/#view=ViewFolder&param=S-100%20VDP (caution, the S-100 VDP wiki is out of date) Are any changes necessary to the above boards to provide MSX and/or MSX2 compatibility? What else would be necessary to complete MSX and/or MSX2 compatibility? I assume some sort of S-100 board with 64K SRAM + IO. Probably a cartridge port, couple 8255 PPIs for control and ASCII keyboard and a serial port for a mouse? Is there any sort of interrupt controller or DMA controller? We can reuse the S-100 bus interface "glue" from other boards. What I am looking for is the components necessary for hardware compatibility. Thanks and have a nice day! Andrew Lynch

my right you bus. Hi Alexandre! Thanks! There are two objectives for the project Primary objective: To supply the necessary hardware to complete MSX compatibility at the hardware level on an S-100 bus system. I believe this would be a first. Secondary objective: a small general purpose SRAM and IO board to help with debugging a simple system when paired with only a CPU board. in from the V9938 VDP to the Z80 CPU clock to supply the 3.579545 MHz signal. It is emitted from the V9938 if I recall correctly. I am thinking an "over the top" style wire jumper with the Z80 CPU board next to the VDP on the S-100 bus. Also the ongoing design of the S-100 VDP V3 may need to be modified for cassette IO functions. How are those implemented? There are spare GPIO pins on the AY-3-8910 so it makes sense if we are talking about motor control, Push to Talk, etc. A simple 64K SRAM + IO (8255 PPI + UART) would be perfect for not just MSX compatibility but for builders in general as a CPU board debugging tool. Thanks and have a nice day! Andrew Lynch

Andrew could you give me a couple of days, I would like to see/be sure we could seat this board in an IEEE-696 bus and have the option of it being transparently being there unless ?activated? but once that is done it would have to phantom out any conflicts with other boards. John John Monahan Ph.D e-mail: <mailto:monahan at vitasoft.org> monahan at vitasoft.org Text: <mailto:monahan at txt.att.net> monahan at txt.att.net From: n8vem-s100 at googlegroups.com [mailto:n8vem-s100 at googlegroups.com] On Behalf Of Andrew Lynch Sent: Monday, August 12, 2013 6:30 AM To: n8vem-s100 at googlegroups.com Cc: cctalk at classiccmp.org Subject: RE: [N8VEM-S100:1801] Re: Looking for MSX2 expertise Hi, Thanks Antony! Great observation! This is precisely why I am asking for some peer review of the S-100 Utility board design. There are some truly strange things happening and they all seem centered around the 8255 PPI which drives the memory banking circuitry. I?ve not seen anything like it but it surely is a neat design. Yes good point on the U21B.5 connection. I?ve been scratching my head over it. I think in the schematic it refers to /Y5 or Y5* which is an output of the IO decoder 74LS138 pin 10. It connects to /CS which is in turn connected to the 8255 PPI chip select. Why they called it /Y5 instead of /CS makes no sense to me. It occurs nowhere else in the schematic AFAIK. I think what the two 74LS00s are doing is forming a flip-flop (S-R?) in front of the memory banking multiplexer. Once the 8255 is accessed, it toggles the multiplexer to get the next set of values. http://en.wikibooks.org/wiki/Digital_Circuits/Latches If you look at ?MSX hardware notes part 2? document on page 7 it more clearly spells out the set input (S?) to the flip flop is intended to be the 8255 chip select line. Regarding the 74LS682s, we could simplify the IO decoding by using a hard wired logic. However I?d like to keep the board general in nature. Although I?d like it to be MSX hardware compatible I suspect many (most) builders could care less about MSX and will want to move the IO block around to suit their particular machines. The 74LS682?s keep the design ?general? enough so that it can be customized without resorting to ?cuts and jumpers?. Although all the N8VEM builders just *love* cuts and jumpers! ? As a consequence of the separation of the V9938 and AY-3-8910 into its own board (S-100 VDP) and the rest on the S-100 Utility board there is a bit of redundant IO decoding between the two boards. For a final design I will eliminate the V9938 and AY-3-8910 unique IO decoding (U34 & U35 gates) since they are handled on the S-100 VDP. It will save us a chip! Woo Hoo! Thank you very much for the analytical and critical review of the S-100 Utility board. Please continue and hopefully others will join in. The better we scrub the schematic and PCB layout now, the more successful the follow on builders in build and test will be. Fewer ?cuts and jumpers? for everyone! Also there is less sending Leon and John on wild goose chases with my goofy prototype boards! Have a nice day! Andrew Lynch From: n8vem-s100 at googlegroups.com [mailto:n8vem-s100 at googlegroups.com] On Behalf Of Ants Pants Sent: Monday, August 12, 2013 2:56 AM To: n8vem-s100 at googlegroups.com Cc: cctalk at classiccmp.org Subject: [N8VEM-S100:1800] Re: Looking for MSX2 expertise Had a look over the schematic CrossRef with the msx tech manual and looks ok, U21B.5 i have connected to the PPICS* signal though, question: do we need the "board select" switches/682's ? is the board in reality more likely to just have straight address decoding via U33 to the PPI, Printer, UART? and the addresses fed straight to the various ROM, RAM, and I/O ? the only brains of the operation is the PPI which selects which chip select lines to get enabled at which addresses of 16KB blocks? the VDP and Sound board however will need the address decoding as we dont want to route out U33 pin(s) 11 and 12 to the PSG and VDP respectively. http://img855.imageshack.us/img855/5489/do2b.jpg [URL=http://imageshack.us/photo/my-images/855/do2b.jpg/][IMG]http://img855.imageshack.us/img855/5489/do2b.jpg[/IMG][/URL <http://img855.imageshack.us/img855/5489/do2b.jpg%5b/IMG%5d%5b/URL> ] looking forward to this board!! On Monday, 5 August 2013 10:31:49 UTC+12, lynchaj wrote: Hi As you may already know, at the N8VEM project we are working on an S-100 VDP. This board has a V9939 video display processor and a AY-3-8910 sound generator which should allow us to have some MSX2 compatibility when combined with a backplane, S-100 Z80 CPU board, and a memory board. There are more IO and memory features necessary for full MSX2 compatibility required though. I am considering a designing a board to provide the balance of MSX2 functions so that the combination of an S-100 backplane, S-100 Z80 CPU, and S-100 VDP. I envision such a board to be composed of SRAM memory, a couple of 8255 PPIs, a card slot plus whatever extra IO and memory we need. If anyone has detailed MSX2 experience and would like to help out on designing an S-100 MSX2 compatibility board to complement the S-100 VDP please contact me. S-100 and MSX seem like a neat combination but no one has tried it AFAIK. Thanks and have a nice day! Andrew Lynch -- You received this message because you are subscribed to the Google Groups "N8VEM-S100" group. To unsubscribe from this group and stop receiving emails from it, send an email to n8vem-s100+unsubscribe at googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "N8VEM-S100" group. To unsubscribe from this group and stop receiving emails from it, send an email to n8vem-s100+unsubscribe at googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.