Page 4 of 4
Re: DFB1X any use for a expansion port ?
Posted: 25 Sep 2026 13:44
by Badwolf
exxos wrote: 25 Sep 2026 11:58
So basically this design has a clone of the Falcon RAM expansion port built on. As said before it had to go "above" the existing connectors. And then the third small connector on the bottom left holes the rest of the address and data bus bits. I also routed the CPUCLK to pin 24 of the "extra" IO connector.
Cool. Any spare pins on the bottom one in the end? I'm thinking about STERM in particular.
BW
Re: DFB1X any use for a expansion port ?
Posted: 25 Sep 2026 13:51
by exxos
Badwolf wrote: 25 Sep 2026 13:44
Cool. Any spare pins on the bottom one in the end? I'm thinking about STERM in particular.
Ah yes very good point that.
There are some "random" free pins. mostly routed to GND.
- Capture.PNG (734.1 KiB) Viewed 19 times
The middle connector is the original Falcon connector.. The one above it is the through expansion port. And the bottom one holds the extra address and data lines.. The likely STERM needs to get added to that.. *somehow* :)
Re: DFB1X any use for a expansion port ?
Posted: 25 Sep 2026 13:55
by Badwolf
exxos wrote: 25 Sep 2026 13:51
The middle connector is the original Falcon connector.. The one above it is the through expansion port. And the bottom one holds the extra address and data lines.. The likely STERM needs to get added to that.. *somehow* :)
TBH, thinking about it, direct DTACK[0|1] access is probably the better choices than STERM as, whilst slower, does allow different bus sizing.
BW
Re: DFB1X any use for a expansion port ?
Posted: 25 Sep 2026 14:05
by exxos
Badwolf wrote: 25 Sep 2026 13:55
TBH, thinking about it, direct DTACK[0|1] access is probably the better choices than STERM as, whilst slower, does allow different bus sizing.
All 3 it is then :P
Don't think up any more because we are fast running out of pins :lol: