UPDATE:

Everything has moved now...

Repository: https://github.com/WolfNet-Computing/WolfNet-65C02-WBC
Website and Docs: https://wolfnet-computing.github.io/WolfNet-65C02-WBC/

Will be looking through alternate UARTs as a lot of people have recommended it.
I've not used it... I've stuck with the FTDI devices, as they've always worked for me and they have drivers for Windoze, Linux and OSX (I use OSX).
The MCP2200 is also Linux and MacOS compatible as it uses the native ...

Just out of curiosity, does anyone have anyone here have any experience with the MCP2200 SOIC? It takes 3.3 or 5v logic depending on the voltage source. Seems like a good chip to use but haven't seen anyone mention it yet. Datasheet here: https://ww1.microchip.com/downloads/en/ ... 22228A.pdf

Last... are you really sure on using the W65C51? You have to code around the problem, so why not use a more modern and better UART/DUART. As you're also using a RS-232 level converter to interface to a DB-9 serial port, exactly what are you planning to use that port for? Driving some older device ...

As promised, version 2.6 in colour and monochrome for schematics and monochrome for the PCB layout.

So, 2.6 is done now and the sound card has been updated to 1.2. Now in the process of devising a breadboard expansion card.
Another question that may spark friendly debate is: What patterns can you recommend for pre-routed traces on a breadboard? (Pictures if possible...)

As always very grateful for the help and floobydust especially for giving me food for thought and being patient. Prime example of what people on this forum are like as I have only had the best help and advice from all of you. Many thanks.

P.S. The documentation, even though incomplete, should be ...

In your application, I see no value in hardware IRQ priority. You don't have anywhere near enough I/O to justify it. I suggest you spend your chip budget on useful features, not bells and whistles.

BTW, everything you are trying to do in discrete logic can be accomplished in a single Microchip ...

I was looking at what you had on GitHub 3 days ago, you since changed it.

Ah, I change a lot so I don't remember all of my commits but I do now remember changing it along with the CS_DEV address.

This defeats the lower chip count claim.

I meant lower than the previous design but I do have ...

I wanted this to be simple to understand and learn as well as simple to build and I'm trying to find the balance. The 138s simply allowed for a lower chip count while having a simple logic table. This should be the kind of thing that could be used at work but built in school. I hope that better ...

Many thanks for all the help from everyone and any pointers/constructive criticisms. I have had a lot of ideas and help from you all.

Having examined your latest schematic (2.5), you should take a closer look at your I/O decode and chip selects for the various I/O devices.
Thanks floobydust, I ...

As requested, the latest version.

I may have missed it somewhere, but a memory map would be very useful.

May be a bit diffucult to find, it's in HTML so I would assume it has to be viewed in GitHub Pages here: https://thealmostgenius.geekgalaxy.com/WolfNet-6502-WBC/memory_map.html (Sorry about all the colour, I tried to make them ...

I think it would be a good idea to read through some of the datasheets on the various chips. You still need a pull-up resistor on the BE line for the CPU. Also, if you're not planning to use a non-WDC processor, you can delete the jumper for VP going to ground.

I'm not too sure what version the ...

I was redesigning the address decoding using the 138s and it occurred to me that the 65C22 could drive the extra address pins on larger chips rather than using is as a chip select. As for the existing bus design, could anyone recommend one that has a similar pinout that would be compatible? (I don't ...