even replacing all the ics in the board too allow for dual voltage 3.3 or 5v ram
will take i think about 8 added or changed ics and change out the mcu for vhdl or a dual cpld from another maker
at least 12ic's in total
just too be carefull .... a total redesign is needed and this is a years work and testing
ive unitated the mach210 code and have reworked it too an algurithm {pointed node register based } so porting too vhd is mega easy...
the code is mainly used for size detection and is quite bloated anyway for what it does
i think i could reduce it in half at least within the mach the compiler for it isnt free...!
but ill need also too work in extra choices and make use of PD2 and 3 on each simm
and also a 3.3v jumper
for perhaps each simm
then a pair of any types will do .... but carefully set!!! or boomb!!
is it worth it ???
twice the size of board
or i can mount a small daughter board as i/o control {and v sel}
easy done
but is it worth it ???
how many TT users are there compaired too how many good sets of 128MB simms 5v edo or fpm
i think there is plenty so 3.3 v isnt worth the extra effort
i need views
everyones saying nothing
as usual no feedback no advice
this makes it hard for me too choose for you
tell me the old story again
so this is what i am going too do
and thats that
pcb will be on its way too me tonight after i spend a few hours and finalise the design by alliging all tracks and bends etc
to be really nice and centered between pins etc
finishing touches
ill card a deal in china tonight
above all adding this choice gives rise to frying your TT or the magnum or the simms more often
sticking to the datasheet details of the ics and the simm module datasheet
is the best way and stick to 5v
just adds problems
so this this the final update too the magnum ill make
we need another name and more of an ide and some other stacks port added to a design that has perhaps an ssd or some nv RAM
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------#
all the mpu does is map this whole port like a massive can be upto 138GB space...... but at like 60ns access...
60ns timings is only the limit imposed on the 68030 MMU by the ram speed avalible
tos adjustment can speed it up
and drivers and tos does map it out
as we know and you can load the whole TT o.s and drivers and software to fast ram
or what we all want fast NVRAM so we can power down power fail etc etc etc
and still it works at max speed
there is heeps and stacks of space...
so.... i think ... we need to think along some added niceness..
and use the TTRAM port with more of a choice...
these days its a better choice too just use a couple of 16bit nvram chips to form like 256MB or 1GB TTram
cheep and chearful
say
sdcard fixed ... or removable on its own TTRAM address as a fixed slow access NVRAM {can be called}
usb stack and i<>o { stack fixed boot held on sdcard {fixed for this purpose to a memory range }}
ide {dual or quad} same as st and ste falcon ranges
LAN {dual port 100Mb direct too ram }
its what i would do perhaps an i2c interface and a decent LPT com port controller
and it takes 1VHDL and a CPLD for interface...bridge with a rasp pi...
ide is another matter so far the ide design for the TT uses TWO cpld
and its a bit hard to get your head round {im trying }
lan is easy
usb is in progress anyway and the port would just need to overlay back to the tos locations in slow ram ...
not sure what state the usb stack in mint etc is at???
obviously 256MB of SSD nvram is a good idea
turn on the TT tos is there.. after just a warm reset
so it becomes a warm boot machine
so sleep mode and hybernate is an easy choice
sdcard keeps the usb stack
and can also be used like lan too wake the machine up {psu enable }
and psu runs 3.3v too run the lan and usb controllers and shares sdcard power {so both machines can power the dedicated stack sdcard }
eeek so easy
cant wait too see what jookie is up too after what he posted he is up too im not keen to start a big project
better add an interface too what we have for expanssion
he is very quiet...????
would be nice too get a heads up if im gona work on something
its better we do it as groups with a topic added for the projects
in the project section
like
{ATARI HARDSOFT PROJECTS...
{OFFICAL PROJECTS LIST}
{
projects software
project hardware
projects available to join in with
}
known ATARI hardware projects + sources + details full done projects referance lib ONLY COMPLETE PROJECTS
}

There is too much bleed over from members wanting to fit a different floppy and problem hardware
to actual hardware project issues and details
this needs pruned and some grafts
its almost spring