Build tool/BIOSReleaseEvent - Revision history

Aoineko at 11:07, 19 April 2026

2026-04-19T11:07:13Z

Aoineko at 11:06, 19 April 2026

2026-04-19T11:06:59Z

Aoineko at 10:58, 19 April 2026

2026-04-19T10:58:36Z

Aoineko at 10:58, 19 April 2026

2026-04-19T10:58:04Z

Aoineko at 10:17, 19 April 2026

2026-04-19T10:17:44Z

Aoineko at 10:17, 19 April 2026

2026-04-19T10:17:28Z

Aoineko at 10:11, 19 April 2026

2026-04-19T10:11:27Z

Aoineko at 10:11, 19 April 2026

2026-04-19T10:11:18Z

Aoineko: Created page with "Build tool option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switch out from page 0."

2026-04-18T17:54:12Z

Created page with "Build tool option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switch out from page 0."

New page

[[Build tool]] option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switch out from page 0.

@@ Line 20: / Line 20: @@
 ** mapper initialization will take place immediately after the return from the BIOS_OnRelease function and will overwrite any changes made in the callback;
 * Only page 1 of memory space points to the program in ROM
 === RAM in page 0 ===

@@ Line 9: / Line 9: @@
 <syntaxhighlight lang="c">void BIOS_OnRelease();</syntaxhighlight>
-== Call Context ==
+== Call context ==
 You must be fully aware of the program's initialization context at the time the BIOS_OnRelease callback function is executed. This context depends on the type of target format.
@@ Line 20: / Line 20: @@
 ** mapper initialization will take place immediately after the return from the BIOS_OnRelease function and will overwrite any changes made in the callback;
 * Only page 1 of memory space points to the program in ROM
 === RAM in page 0 ===
@@ Line 26: / Line 27: @@
 * The mapper has been initialized (see [[Create_a_mapped_ROM#Initial_slot_configuration|Initial slot configuration]])
 * Pages 1 and 2 of memory point to the program in ROM

@@ Line 14: / Line 14: @@
 === ROM in page 0 ===
-The global variables have been initialized (so they have their predefined values)
+* The global variables have been initialized (so they have their predefined values)
-The main() function has not yet been called (so no program-specific initialization has taken place yet)
+* The main() function has not yet been called (so no program-specific initialization has taken place yet)
-The mapper has not yet been initialized;
+* The mapper has not yet been initialized;
-the selected segments are those selected by default by the hardware at the physical level (see https://www.msx.org/wiki/MegaROM_Mappers);
+** the selected segments are those selected by default by the hardware at the physical level (see https://www.msx.org/wiki/MegaROM_Mappers);
-mapper initialization will take place immediately after the return from the BIOS_OnRelease function and will overwrite any changes made in the callback;
+** mapper initialization will take place immediately after the return from the BIOS_OnRelease function and will overwrite any changes made in the callback;
-Only page 1 of memory space points to the program in ROM
+* Only page 1 of memory space points to the program in ROM
 === RAM in page 0 ===
-The global variables have been initialized (so they have their predefined values)
+* The global variables have been initialized (so they have their predefined values)
-The main() function has not yet been called (so no program-specific initialization has taken place yet)
+* The main() function has not yet been called (so no program-specific initialization has taken place yet)
-The mapper has been initialized (see [[Create_a_mapped_ROM#Initial_slot_configuration|Initial slot configuration]])
+* The mapper has been initialized (see [[Create_a_mapped_ROM#Initial_slot_configuration|Initial slot configuration]])
-Pages 1 and 2 of memory point to the program in ROM
+* Pages 1 and 2 of memory point to the program in ROM

← Older revision		Revision as of 10:58, 19 April 2026
Line 8:		Line 8:
	Function prototype:		Function prototype:
	<syntaxhighlight lang="c">void BIOS_OnRelease();</syntaxhighlight>		<syntaxhighlight lang="c">void BIOS_OnRelease();</syntaxhighlight>
		+
		+	== Call Context ==
		+
		+	You must be fully aware of the program's initialization context at the time the BIOS_OnRelease callback function is executed. This context depends on the type of target format.
		+
		+	=== ROM in page 0 ===
		+	The global variables have been initialized (so they have their predefined values)
		+	The main() function has not yet been called (so no program-specific initialization has taken place yet)
		+	The mapper has not yet been initialized;
		+	the selected segments are those selected by default by the hardware at the physical level (see https://www.msx.org/wiki/MegaROM_Mappers);
		+	mapper initialization will take place immediately after the return from the BIOS_OnRelease function and will overwrite any changes made in the callback;
		+	Only page 1 of memory space points to the program in ROM
		+
		+	=== RAM in page 0 ===
		+	The global variables have been initialized (so they have their predefined values)
		+	The main() function has not yet been called (so no program-specific initialization has taken place yet)
		+	The mapper has been initialized (see [[Create_a_mapped_ROM#Initial_slot_configuration\|Initial slot configuration]])
		+	Pages 1 and 2 of memory point to the program in ROM

@@ Line 3: / Line 3: @@
 This applies to [[target]] formats that place the ROM on page 0 (ROM_48K_ISR, ROM_64K_ISR, ROM_NEO8, and ROM_NEO16), as well as ROM formats that place RAM on page 0 (via the [[Build_tool/InstallRAMISR|InstallRAMISR]] option).
 To use this option, the user must provide a function that will be called by the boot process just before the BIOS is removed from page 0 (to make room for the cartridge or memory).
 Function prototype:
 <syntaxhighlight lang="c">void BIOS_OnRelease();</syntaxhighlight>

← Older revision		Revision as of 10:17, 19 April 2026
Line 1:		Line 1:
−	[[Build tool]] option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switched out from page 0.	+	[[Build tool]] option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switched out from page 0. It allows you to have an initialization code that runs while the BIOS is still accessible at page 0. For example, to detect the presence of an MSX-Music device using the BIOS routines for cross-slot reading.

	This applies to [[target]] formats that place the ROM on page 0 (ROM_48K_ISR, ROM_64K_ISR, ROM_NEO8, and ROM_NEO16), as well as ROM formats that place RAM on page 0 (via the [[Build_tool/InstallRAMISR\|InstallRAMISR]] option).		This applies to [[target]] formats that place the ROM on page 0 (ROM_48K_ISR, ROM_64K_ISR, ROM_NEO8, and ROM_NEO16), as well as ROM formats that place RAM on page 0 (via the [[Build_tool/InstallRAMISR\|InstallRAMISR]] option).
		+
		+	To use this option, the user must provide a function that will be called by the boot process just before the BIOS is removed from page 0 (to make room for the cartridge or memory).
		+
		+	Function prototype:
		+	<syntaxhighlight lang="c">void BIOS_OnRelease();</syntaxhighlight>

← Older revision		Revision as of 10:11, 19 April 2026
Line 1:		Line 1:
−	[[Build tool]] option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switched out from page 0. This applies to [[target]] formats that place the ROM on page 0 (ROM_48K_ISR, ROM_64K_ISR, ROM_NEO8, and ROM_NEO16), as well as ROM formats that place RAM on page 0 (via the [[Build_tool/InstallRAMISR\|InstallRAMISR]] option).	+	[[Build tool]] option '''BIOSReleaseEvent''' is used to add a callback function to be called just before BIOS is switched out from page 0.
		+
		+	This applies to [[target]] formats that place the ROM on page 0 (ROM_48K_ISR, ROM_64K_ISR, ROM_NEO8, and ROM_NEO16), as well as ROM formats that place RAM on page 0 (via the [[Build_tool/InstallRAMISR\|InstallRAMISR]] option).