Changes

Jump to: navigation, search

FPGAmstrad

490 bytes removed, 15:40, 29 March 2015
/* TODO : more ROM and RAM */
In order to plug FPGAmstrad on TV, and help debugging. And also to test a simple scan-doubler.
=== TODO DONE : more More ROM and RAM === -- "001" dsk_A(19:0) DSK_A -- "0000000" "xx" ROMBase L U0 U7 U1 <= finally only L is used -- "0000001" "xx" ROMBase 4 5 6 7 <= finally not used -- "0000010" "xx" RAMBase -- "0000011" "xx" RAMBank page 0 -- "0000111" "xx" RAMBank page 1 -- "0001111" "xx" RAMBank page 3 -- "0101111" "xx" RAMBank page 7 -- "100000000" ROMBank 0-255
To check feasability in MiST-board, and do find a simple strategy about naming ROMs (a txt ROM files does finish with file should be so cool) Do try OrgAMS (that does use extended RAM and 3 ROM), shall be so coolextension from ==== Analyse ====Actually I do use only A(22e00 to ..0) of external RAM (I'm using them for 64KB ROM + 128KB RAM + 178KB DSK)eFF, and MiST-board has A(24..0), so I have at minimum... 64+128+178=370<512KB *2*2 -1 so I have... around 512KB+1024KB free ? 2^24=16777216 /1024=16384KB normaly ? So 256*16KB ROM= 4096KB ROM and 64KB lowerROM and 64K BaseRAM and 512KB RAM and 178KB dsk shall do 4914KB<16384KB so in theory it does pass. Last problem LowerROM is saying "here no ROM, do read RAM" : it does make a mask of 256 bits, why not. I have also to find a way to attach rom fixed name to placements, I think that a hexa number in extension can be fine, as myRom.R00 to myRom.RFF. And finally that has to enter in MiST-board plaform at compilation...
== Agile method ==
1,200
edits