MSX Game Library - Recent changes [en]

NEO mapper

Aoineko — Thu, 02 Jul 2026 03:04:37 GMT

‎MSXgl

Build tool/InstallRAMISR

Aoineko — Wed, 01 Jul 2026 13:18:43 GMT

‎RAMISR_SEGMENT0

SDCC

Aoineko — Fri, 26 Jun 2026 09:44:37 GMT

‎SDCC 4.5.0

Roadmap

Aoineko — Thu, 25 Jun 2026 09:02:40 GMT

‎Build tool

Modules/arkos/Usage

Aoineko — Mon, 15 Jun 2026 21:10:02 GMT

@@ 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.

@@ Line 1: / 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.
@@ Line 5: / 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).
-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.
-<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:
-== 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.
 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).
-<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"
 ! Mapper !! Segments
@@ Line 44: / Line 47: @@
 [[Samples#Software_Sprite|s_swsprt]] sample (software sprite) showcase the use of this option.

@@ Line 2: / Line 2: @@
 Supported version:
-* Embedded: <tt>SDCC 4.2.0</tt>
+* Embedded: <tt>SDCC 4.6.0</tt>
-* Last tested: <tt>SDCC 4.5.0</tt> (Windows) and <tt>SDCC 4.4.0</tt> (Linux)
+* Last tested: <tt>SDCC 4.6.0</tt>
 == Assembler ==
@@ Line 52: / Line 52: @@
 === <tt>SDCC 4.2.0</tt> ===
 * ⭐ '''Main features:'''
@@ Line 123: / Line 122: @@
 * ⚠️ '''Known issues:'''
 ** Major code generation [https://sourceforge.net/p/sdcc/bugs/3834/ bug] in specific condition
 == Links ==

@@ Line 51: / Line 51: @@
 == [[Build tool]] ==
-* ⏳ Add native support for SDCC 4.5.0 ''(done but waiting for SDCC fix release)''
+* ⏳ Add native support for SDCC 4.6.0
 * Add an option to compile the source files in parallel.
 * Add IPS generator (to create a Patch for a given binary).

← Older revision		Revision as of 21:10, 15 June 2026
Line 1:		Line 1:
−	⚠️ Arkos tracker working area address in RAM is hardcoded. You must manually ensure that this area does not overlap any other content in RAM. Default value is 0xF000 but can be change in library configuration (see [[#Settings]]).	+	⚠️ Arkos tracker working area address in RAM is hardcoded. You must manually ensure that this area does not overlap any other content in RAM. Default value is 0xF000 but can be change in library configuration (see [[#Settings]]). The memory buffer size is 275 bytes, but it is recommended to allow for a little more in case the player is updated later.

	=== Music address ===		=== Music address ===