MECB Roadmap / Index (Read First!)

User avatar
epaell
Posts: 258
Joined: Mon Jan 08, 2024 10:06 pm
Location: Sydney

Re: MECB Roadmap / Index

Post by epaell »

That's a great idea - I had thought that it would be useful to have the Jed files available (though I did have another machine that I use just for programming PLD/ROMS so I ended up installing WinCupl anyway).
User avatar
epaell
Posts: 258
Joined: Mon Jan 08, 2024 10:06 pm
Location: Sydney

Re: MECB Roadmap / Index (Read First!)

Post by epaell »

Just a thought, as a part of the road-map is it worth having a page where all the ports for the various boards are defined? I'm currently finding myself constantly rummaging through various PLD files to remind myself where all the current boards sit so as to avoid any conflicts with new devices :-)

Something along the lines of:

Code: Select all

$xx00-$xx07 PTM
$xx08-$xx0F ACIA
$xx10-$xx17 PIA
$xx20-$xx23 IDE Interface
$xx78-$xx7F Z80 memory paging control
$xx80-$xx87 VDP
$xx88-$xx8F OLED Display
$xxC0 RTC
$xxC4 IO board
I think that is most of what I'm aware of so far (at least in the default configurations). Thankfully these all make use of the PLD and so it is highly configurable in case there are conflicts but it's probably worth avoiding them in the first place.
User avatar
Editor
Posts: 388
Joined: Fri Nov 17, 2023 10:36 pm
Contact:

Re: MECB Roadmap / Index (Read First!)

Post by Editor »

epaell wrote: Wed Mar 25, 2026 10:05 am Just a thought, as a part of the road-map is it worth having a page where all the ports for the various boards are defined? I'm currently finding myself constantly rummaging through various PLD files to remind myself where all the current boards sit so as to avoid any conflicts with new devices :-)
Excellent idea!

Based on your suggestion, I've now added a "Default I/O Port Allocation" section at the bottom of the MECB Roadmap / Index (first topic post).

It might just need some additional details for your IDE Card, and your I/O and RTC Card (to clarify the Device column).

Also, what are your thoughts on my upcoming WDC I/O + Sound Card Card port allocation? At first I was just thinking of replicating the same I/O allocation space as the Motorola I/O + Sound Card (on the basis that most systems probably won't use both?). But, with plenty of IO allocations available, perhaps I should just allocate it's own space (it will help with developing code for one, with the other). :thinking:
User avatar
epaell
Posts: 258
Joined: Mon Jan 08, 2024 10:06 pm
Location: Sydney

Re: MECB Roadmap / Index (Read First!)

Post by epaell »

Fantastic - that'll be a very useful post ... looking at it now, ah yes, I forgot about the prototype cards - it's good that you included those.

The IDE card uses the Intel 82C55A, the I/O+RTC card simply uses TTL devices (latches and buffers) for the I/O.

For the WDC I/O + Sound card - I agree, it's worth having the default use one of the spare slots as it makes testing easier and you may want to use both.
User avatar
Editor
Posts: 388
Joined: Fri Nov 17, 2023 10:36 pm
Contact:

Re: MECB Roadmap / Index (Read First!)

Post by Editor »

epaell wrote: Wed Mar 25, 2026 8:36 pm The IDE card uses the Intel 82C55A, the I/O+RTC card simply uses TTL devices (latches and buffers) for the I/O.
Devices column updated. Thanks.
epaell wrote: Wed Mar 25, 2026 8:36 pm For the WDC I/O + Sound card - I agree, it's worth having the default use one of the spare slots as it makes testing easier and you may want to use both.
Agreed.
User avatar
epaell
Posts: 258
Joined: Mon Jan 08, 2024 10:06 pm
Location: Sydney

Re: MECB Roadmap / Index (Read First!)

Post by epaell »

BTW, I've made a minor change to the IO board to shift it to $xxC1 so it is next to the RTC device (there wasn't really any reason to leave that gap).
User avatar
Editor
Posts: 388
Joined: Fri Nov 17, 2023 10:36 pm
Contact:

Re: MECB Roadmap / Index (Read First!)

Post by Editor »

epaell wrote: Wed Mar 25, 2026 11:06 pm I've made a minor change to the IO board to shift it to $xxC1 so it is next to the RTC device (there wasn't really any reason to leave that gap).
Makes sense. Table updated. :)
Post Reply