Difference between revisions of "Minimig Expansion"

From OpenCircuits
Jump to navigation Jump to search
m (Minimig expansion PCI moved to Minimig Expansion PCI)
(Expansion obstacles)
Line 1: Line 1:
 
http://www.amiga.org/modules/newbb/viewtopic.php?topic_id=39358&forum=8&viewmode=flat&order=ASC&start=140<br>
 
http://www.amiga.org/modules/newbb/viewtopic.php?topic_id=39358&forum=8&viewmode=flat&order=ASC&start=140<br>
 +
<br>
 +
ATA (IDE), ZorroII, SCSI all wants a large number of I/O pins. There a currently 4 remaining. A few more possible by reusing boot configuration pins. Getting larger fpga means BGA and that is a path you don't want to go.<br>
 +
<br>
 +
But fpgas are capable of really fast communications, esp the standard spartan3. So a possibility is to use the leftover I/O to connect another fpga to hookup these things. Essentially a "south bridge" running on a pseudo serial bus.<br>
 +
<br>
 +
Not minding the cost of an extra fpga, special copper trace requirements, support circuitry, power, and connectors.<br>
 +
<br>

Revision as of 19:02, 27 July 2007

http://www.amiga.org/modules/newbb/viewtopic.php?topic_id=39358&forum=8&viewmode=flat&order=ASC&start=140

ATA (IDE), ZorroII, SCSI all wants a large number of I/O pins. There a currently 4 remaining. A few more possible by reusing boot configuration pins. Getting larger fpga means BGA and that is a path you don't want to go.

But fpgas are capable of really fast communications, esp the standard spartan3. So a possibility is to use the leftover I/O to connect another fpga to hookup these things. Essentially a "south bridge" running on a pseudo serial bus.

Not minding the cost of an extra fpga, special copper trace requirements, support circuitry, power, and connectors.