4.6.1. Troubleshooting
Actual layout of loaded modules could be seen in ROM Map screen.
4.7. Internals
4.7.1. Module Loader
This section describes procedure for ROM address assignment.
Each time module is plugged or unplugged Module Loader assigns locations of ROMs to active
modules.
For each step number below are all active modules processed in order specified in Active Modules
screen:
Pass 0
ROMs assigned in .mod files to fixed pages go exactly there.
Pass 1
Others ROMs are assigned to pages 8-F in order of appearance - first those with prescribed
mutual relative positions (in single .mod file).
Pass 2
Finally ROMs using single pages with no other requirements are placed at free pages.
Note that in above-mentioned steps ROM refers to item in .mod file which can
actually represent also RAM page.
4.7.2. RAM pages
Any module can define its own RAM (in .mod file) and subsequently access it using WROM(WMLDL)
and CXISA(FETCH S&X). HEPAX instructions WPTOG and BLKMOV are implemented too.
If you are going to use RAM pages in multiple modules or you want to change modules which
uses RAM pages:
The contents of RAM pages are internally linked to the order of RAM pages
requested during module load. That means these contents are strictly tied to a
particular configuration of modules containing RAM pages. We recommend you
make RAM backup (or full backup) whenever you change configuration of RAM
modules unless you really understand the consequences.
RAM pages are initialized when the module is used (plugged-in) for the first time after loading
Flash from FAT; RAM page contents are loaded with data from the appropriate RAM page of the
.mod file. In most cases this means the RAM is cleared, however this allows the user to create a
module with pre-filled RAM contents. Otherwise the contents is preserved during all plug/unplug(s)
of modules. Note that changes to these RAM pages are not saved to the .mod file, however you can
20
To Next Page
Loading...
