Kaos Kidd
01-03-2006, 09:55 AM
Ok... I'm sure someone else has thought of this idea, but I cant seem to see it listed here and about...
An Overlay Memory approch to BS2's memory limitations..
Remember bback in the days of DOS... where all DOS could see and use was 1 Meg
(Sounds like the 8K limit in the BS2)... Anyway, we used a program to manage that..
and software would do something like this...
load in some code... stuff in into a page in upper memory...
load in some more code... stuff into a page in upper memory...
Now I know my BS2P's got 8 slots... and when the code gets just so large...
the idea is to take the "tokenized code" from a slot and offload it into an eeprom..
and then download "tokenized code" into the "freed" slot then execute it...
I could see it would require a "loader" program in the BS2...
... INIT...
... Get Source Code slot and Length...
... Open EEProm MemoryMap bytes, get the next available byte..
... start writing the code from slot one for XX length into eeprom starting at available byte...
... update the eeprom memorymap bytes to indicate the next available byte...
And I could invision the code in each program...
Something with a map of the routines stored in EE, and their size...
Reading that into a Slot... executing it... then returning back...
Ok bosses and gods of the stamps... is this "dooable" or pipe dreams?
It would be a ...
I could well imagin... with good memory managment skills, one could literly create a self modfying program...
as long as the code, offsets, locations are correct...· Gosh, I remember doing that on the C64...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---------------------------------------------
Until our bytes cross again, may your chips never smoke, your bits never fall off, your parts bin never be empty and your jumpers never fall off.
---------------------------------------------
KK
·
An Overlay Memory approch to BS2's memory limitations..
Remember bback in the days of DOS... where all DOS could see and use was 1 Meg
(Sounds like the 8K limit in the BS2)... Anyway, we used a program to manage that..
and software would do something like this...
load in some code... stuff in into a page in upper memory...
load in some more code... stuff into a page in upper memory...
Now I know my BS2P's got 8 slots... and when the code gets just so large...
the idea is to take the "tokenized code" from a slot and offload it into an eeprom..
and then download "tokenized code" into the "freed" slot then execute it...
I could see it would require a "loader" program in the BS2...
... INIT...
... Get Source Code slot and Length...
... Open EEProm MemoryMap bytes, get the next available byte..
... start writing the code from slot one for XX length into eeprom starting at available byte...
... update the eeprom memorymap bytes to indicate the next available byte...
And I could invision the code in each program...
Something with a map of the routines stored in EE, and their size...
Reading that into a Slot... executing it... then returning back...
Ok bosses and gods of the stamps... is this "dooable" or pipe dreams?
It would be a ...
I could well imagin... with good memory managment skills, one could literly create a self modfying program...
as long as the code, offsets, locations are correct...· Gosh, I remember doing that on the C64...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---------------------------------------------
Until our bytes cross again, may your chips never smoke, your bits never fall off, your parts bin never be empty and your jumpers never fall off.
---------------------------------------------
KK
·