Build tool/InstallRAMISR - Revision history

Aoineko: /* RAM0_SEGMENT */

2025-01-04T18:03:32Z

‎RAM0_SEGMENT

2025-01-04T18:03:08Z

2025-01-04T18:01:16Z

2025-01-04T18:01:03Z

2025-01-04T18:00:16Z

2025-01-04T17:53:48Z

‎RAM0_ISR

2024-12-03T22:17:04Z

2024-12-03T00:32:22Z

2024-12-03T00:32:08Z

2024-12-03T00:30:30Z

@@ Line 35: / Line 35: @@
 |-
 | NEO-16 || #3
 |-
 | ASCII16-X || #2

@@ Line 35: / Line 35: @@
 |-
 | NEO-16 || #3
 |}

@@ Line 10: / Line 10: @@
 * <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 following 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>.
+<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>.
 == RAM0_ISR ==

@@ Line 10: / Line 10: @@
 * <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 belowing 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>.
+<u>Note</u>: In the past, this option was a Boolean. We recommend changing its value to one of the following 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>.
 == RAM0_ISR ==

@@ Line 6: / Line 6: @@
 InstallRAMISR can take 3 values:
-* <tt>RAM0_NONE</tt>: Don't switch page 0 to RAM
+* <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_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)
+* <tt>"RAM0_SEGMENT"</tt>: Switch page 0 to RAM, install ISR at 0x0038 , then copy segment data at 0x0100 (for mapped-ROM)
 == RAM0_ISR ==

@@ Line 12: / Line 12: @@
 == RAM0_ISR ==
 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 variable in the memory space.
+You can use SDCC's <tt>__at()</tt> directive to place variables in the memory space.
 == RAM0_SEGMENT ==

@@ 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.
 This option requires MSX to have at least 64 KB of RAM (otherwise, no RAM will be available on page 0).
 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).

← Older revision		Revision as of 00:32, 3 December 2024
Line 35:		Line 35:

	When you use this option, these segments are reserved for code and data to be copied on page 0 and cannot be used for anything else.		When you use this option, these segments are reserved for code and data to be copied on page 0 and cannot be used for anything else.
		+
	[[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.

@@ Line 17: / Line 17: @@
 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 your main program. Segment number depend of the mapper format your are using:
+<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