← Older revision

Revision as of 13:18, 1 July 2026

(10 intermediate revisions by the same user not shown)

Line 1:

−

[[Build tool]] option '''InstallRAMISR''' is used to automatically select RAM in page 0 then copy data there at startup, so ROM cartridge can take advantage of (almost) 16 KB of additional RAM.

+

[[Build tool]] option '''InstallRAMISR''' is used mainly to automatically select RAM in page 0 then copy data there at startup, so ROM cartridge can take advantage of (almost) 16 KB of additional RAM.

This option requires MSX to have at least 64 KB of RAM (otherwise, no RAM will be available on page 0). So only some MSX1 may be compatible but all the MSX2, MSX2+ and MSX turbo R are.

This option requires MSX to have at least 64 KB of RAM (otherwise, no RAM will be available on page 0). So only some MSX1 may be compatible but all the MSX2, MSX2+ and MSX turbo R are.

Line 5:

As page 0 (addresses 0x0000-0x3FFF) is the place where MSX will search for interruption handler (ISR), the build tool will automatically copy the selected ISR (see [[Build tool/CustomISR|CustomISR]] option).

As page 0 (addresses 0x0000-0x3FFF) is the place where MSX will search for interruption handler (ISR), the build tool will automatically copy the selected ISR (see [[Build tool/CustomISR|CustomISR]] option).

−

InstallRAMISR can take 3 values:

+

InstallRAMISR can also be used to install ISR in page 3 and activate Interrupt mode 2 (IM2) so the system will no longer access to page 0 during interrupt and user can switch page 0 content freely.

−

* <tt>"RAM0_NONE"</tt>: Don't switch page 0 to RAM 

−

* <tt>"RAM0_ISR"</tt>: Switch page 0 to RAM then install ISR at 0x0038 (mandatory address)

−

* <tt>"RAM0_SEGMENT"</tt>: Switch page 0 to RAM, install ISR at 0x0038 , then copy segment data at 0x0100 (for mapped-ROM)

−

<u>Note</u>: In the past, this option was a Boolean. We recommend changing its value to one of the above strings, but note that if you keep a Boolean value, the 'true' will be interpreted as <tt>"RAM0_ISR"</tt> and the 'false' as <tt>"RAM0_NONE"</tt>.

+

InstallRAMISR can take those values:

+

* <tt>"RAMISR_NONE"</tt>: Don't switch page 0 to RAM 

+

* <tt>"RAMISR_PAGE0"</tt>: Switch page 0 to RAM then install ISR at 0x0038 (mandatory address)

+

* <tt>"RAMISR_SEGMENT0"</tt>: Switch page 0 to RAM, install ISR at 0x0038 , then copy segment data at 0x0100 (for mapped-ROM)

+

* <tt>"RAMISR_PAGE3"</tt>: Install ISR in RAM in page 3 and use interrupt mode 2 (IM2)

−

== RAM0_ISR ==

+

<u>Note</u>: In the past, this option was a Boolean. We recommend changing its value to one of the above strings, but note that if you keep a Boolean value, the 'true' will be interpreted as <tt>"RAMISR_PAGE0"</tt> and the 'false' as <tt>"RAMISR_NONE"</tt>.

−

When using <tt>RAM0_ISR</tt> option, you have additional RAM of be used from 0x0100 to 0x3FFF.

+

== RAMISR_PAGE0 ==

+

When using <tt>RAMISR_PAGE0</tt> option, you have additional RAM of be used from 0x0100 to 0x3FFF.

You can use SDCC's <tt>__at()</tt> directive to place variables in the memory space.

You can use SDCC's <tt>__at()</tt> directive to place variables in the memory space.

−

== RAM0_SEGMENT ==

+

== RAMISR_SEGMENT0 ==

−

When using <tt>RAM0_SEGMENT</tt> option, you have to define a source code file named <tt>{projectName}_p0.c</tt> (or <tt>.asm</tt> or <tt>.s</tt> to add assembler source) and it will be automatically added to your mapper data and copy at statup in page 0.

+

When using <tt>RAMISR_SEGMENT0 </tt> option, you have to define a source code file named <tt>{projectName}_p0.c</tt> (or <tt>.asm</tt> or <tt>.s</tt> to add assembler source) and it will be automatically added to your mapper data and copy at statup in page 0.

Code and data from your <tt>_p0</tt> file will be available starting from address 0x0100 (after the ISR) so you have a little less than 16 KB available in page 0 (16 KB - 0x100 = 16128 bytes).

Code and data from your <tt>_p0</tt> file will be available starting from address 0x0100 (after the ISR) so you have a little less than 16 KB available in page 0 (16 KB - 0x100 = 16128 bytes).

−

<tt>_p0</tt> will be place in segment after the 32 KB of your main program. Segment number depend of the mapper format your are using:

+

The 16 KB content of <tt>_p0</tt> will be place in segment after the 32 KB of your main program. Segment number depend of the mapper format your are using:

{| class="wikitable"

{| class="wikitable"

! Mapper !! Segments

! Mapper !! Segments

Line 44:

Line 47:

[[Samples#Software_Sprite|s_swsprt]] sample (software sprite) showcase the use of this option.

[[Samples#Software_Sprite|s_swsprt]] sample (software sprite) showcase the use of this option.

+

== RAMISR_PAGE3 ==

+

When using <tt>RAMISR_PAGE3</tt> option, the boot sequence activate Interrupt mode 2 (IM2) and setup a vector table so that, when an interrupt occurs, only page 3 will be accessed.

+

As page 0 is not used anymore by the system, the user can freely use it to have:

+

* A fixed chunk of 16 KB of ROM (for 48 KB plain-ROM),

+

* Freely switchable segments using [[NEO mapper]]:

+

** NEO-16: 1 bank of 16 KB (0x0000h~0x3FFF),

+

** NEO-8: 2 banks of 8 KB (0x0000~0x1FFF and 0x2000~0x3FFF).

+

* 16 KB of RAM (for MSX with at least 64 KB of RAM).

+

** For MSX computers equipped with a Memory mapper, you can freely change the segment displayed on page 0.

+

This option can only be used with <tt>ForceRamAddr=0xC000</tt> (or <tt>ForceRamAddr=0</tt> as it is equivalent).

+

In this case, C variables will be accumulated starting from address 0xC1C4.

+

Thus, 452 bytes are used for the vector tables (257 bytes) and the ISR code itself.

+

[[Samples#Graph_Mode_3|s_gm3]] sample (GM3 mode) showcase the use of this option.

@@ Line 123: / Line 123: @@
 === MSXgl ===
-Both NEO-8 and NEO-16 mappers are supported. Use respectively <tt>ROM_NEO8</tt> and <tt>ROM_NEO16</tt> as target format.
+Both NEO-8 and NEO-16 mappers are supported. Use respectively <tt>ROM_NEO8</tt> and <tt>ROM_NEO16</tt> as [[target|target format]].
 MSXgl uses macros to wrap quick bank switching mechanisms. It would therefore be totally transparent for a user to switch, for example, from an ASCII8 or even Konami-SCC mapper, to an NEO-8 mapper.

MSX Game Library - Recent changes [en]

NEO mapper

Build tool/InstallRAMISR