DOL (File format) - Revision history

Algoflash: /* Softwares */

2023-10-07T12:07:27Z

Softwares

← Older revision		Revision as of 14:07, 7 October 2023
Line 181:		Line 181:
	== Softwares ==		== Softwares ==

	~~This~~ softwares can handle dol files:		These softwares can handle dol files:
	* [https://github.com/Virtual-World-RE/NeoGF/tree/main/doltool doltool.py] - Virtual World RE.		* [https://github.com/Virtual-World-RE/NeoGF/tree/main/doltool doltool.py] - Virtual World RE.
	* [https://github.com/sup39/GeckoLoader GeckoLoader], - JoshuaMKW, sup32.		* [https://github.com/sup39/GeckoLoader GeckoLoader], - JoshuaMKW, sup32.

	[[Category:File format]]		[[Category:File format]]

Algoflash: /* SI - Serial Interface */

2023-10-07T12:07:05Z

SI - Serial Interface

← Older revision		Revision as of 14:07, 7 October 2023
Line 177:		Line 177:

	== SI - Serial Interface ==		== SI - Serial Interface ==
	[https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/Core/HW/SI/SI_Device.h Dolphin Emulator sources] show devices using SI. We found these devices: GBA (Game Boy Advance), CONTROLLER, KEYBOARD, STEERING, TARUKONGA. The Serial Interface ~~use~~ the [https://n64brew.dev/wiki/Joybus_Protocol Joybus] protocol.		[https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/Core/HW/SI/SI_Device.h Dolphin Emulator sources] show devices using SI. We found these devices: GBA (Game Boy Advance), CONTROLLER, KEYBOARD, STEERING, TARUKONGA. The Serial Interface uses the [https://n64brew.dev/wiki/Joybus_Protocol Joybus] protocol.

	== Softwares ==		== Softwares ==

Algoflash: /* SI - Serial Interface */

2023-10-07T12:06:50Z

SI - Serial Interface

← Older revision		Revision as of 14:06, 7 October 2023
Line 177:		Line 177:

	== SI - Serial Interface ==		== SI - Serial Interface ==
	[https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/Core/HW/SI/SI_Device.h Dolphin Emulator sources] show devices using SI. We found ~~this~~ devices: GBA (Game Boy Advance), CONTROLLER, KEYBOARD, STEERING, TARUKONGA. The Serial Interface use the [https://n64brew.dev/wiki/Joybus_Protocol Joybus] protocol.		[https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/Core/HW/SI/SI_Device.h Dolphin Emulator sources] show devices using SI. We found these devices: GBA (Game Boy Advance), CONTROLLER, KEYBOARD, STEERING, TARUKONGA. The Serial Interface use the [https://n64brew.dev/wiki/Joybus_Protocol Joybus] protocol.

	== Softwares ==		== Softwares ==

Algoflash: /* DI - DVD Interface */

2023-10-07T12:05:03Z

DI - DVD Interface

← Older revision		Revision as of 14:05, 7 October 2023
Line 169:		Line 169:

	== DI - DVD Interface ==		== DI - DVD Interface ==
	The driver handling DVD accesses ~~use~~ the chip [https://wiibrew.org/wiki/Hardware/Disc_Drive#Hardware MN102] documented on [https://www.gc-forever.com/yagcd/chap5.html#sec5.7 yagcd]. The Hitmen team has programmed a plugin for it: [http://hitmen.c02.at/html/gc_releases.html MN102 IDA Pro].		The driver handling DVD accesses uses the chip [https://wiibrew.org/wiki/Hardware/Disc_Drive#Hardware MN102] documented on [https://www.gc-forever.com/yagcd/chap5.html#sec5.7 yagcd]. The Hitmen team has programmed a plugin for it: [http://hitmen.c02.at/html/gc_releases.html MN102 IDA Pro].

	Some more documentation on [http://hitmen.c02.at/files/docs/gc/Ingenieria-Inversa-Understanding_WII_Gamecube_Optical_Disks.html disc reads].		Some more documentation on [http://hitmen.c02.at/files/docs/gc/Ingenieria-Inversa-Understanding_WII_Gamecube_Optical_Disks.html disc reads].

Algoflash: /* Sections */

2023-10-07T12:04:20Z

Sections

← Older revision		Revision as of 14:04, 7 October 2023
Line 166:		Line 166:
	* FST stuck to the end of memory (81800000)		* FST stuck to the end of memory (81800000)

	The SDK offers two functions for handling Arena: OSAllocFromArenaHi & OSAllocFromArenaLo. But the main program initializes a number of Heaps in it and Create / Destroy them as it ~~need~~.		The SDK offers two functions for handling Arena: OSAllocFromArenaHi & OSAllocFromArenaLo. But the main program initializes a number of Heaps in it and Create / Destroy them as it needs.

	== DI - DVD Interface ==		== DI - DVD Interface ==

Algoflash: /* Sections */

2023-10-07T12:03:57Z

Sections

← Older revision		Revision as of 14:03, 7 October 2023
Line 166:		Line 166:
	* FST stuck to the end of memory (81800000)		* FST stuck to the end of memory (81800000)

	The SDK ~~offer~~ two functions for handling Arena: OSAllocFromArenaHi & OSAllocFromArenaLo. But the main program ~~initialize~~ a number of Heaps in it and Create / Destroy them as it need.		The SDK offers two functions for handling Arena: OSAllocFromArenaHi & OSAllocFromArenaLo. But the main program initializes a number of Heaps in it and Create / Destroy them as it need.

	== DI - DVD Interface ==		== DI - DVD Interface ==

Algoflash: /* Sections */

2023-10-07T12:02:30Z

Sections

← Older revision		Revision as of 14:02, 7 October 2023
Line 147:		Line 147:
	* R0 when used with an offset don't care about its value. It allows to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).		* R0 when used with an offset don't care about its value. It allows to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).

	As said above SDA are used with a signed short offset (-0x8000 +0x7FFF). When we reach the entry_point then R1 R2 and R13 are ~~pointer~~ in the Bootrom/IPL. The first function __init_registers initialize them for executing the dol and we can see that it's set to the beginning of some .data and .bss sections.		As said above SDA are used with a signed short offset (-0x8000 +0x7FFF). When we reach the entry_point then R1 R2 and R13 are pointing in the Bootrom/IPL. The first function __init_registers initialize them for executing the dol and we can see that it's set to the beginning of some .data and .bss sections.

	We found this section originally build in the ELF32 file format:		We found this section originally build in the ELF32 file format:

Algoflash: /* Sections */

2023-10-07T12:01:31Z

Sections

← Older revision		Revision as of 14:01, 7 October 2023
Line 145:		Line 145:
	* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It corresponds to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).		* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It corresponds to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).
	* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It corresponds to the .sdata (initialized variables) or .sbss (uninitialized variables).		* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It corresponds to the .sdata (initialized variables) or .sbss (uninitialized variables).
	* R0 when used with an offset don't care about ~~it's~~ value. It ~~allow~~ to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).		* R0 when used with an offset don't care about its value. It allows to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).

	As said above SDA are used with a signed short offset (-0x8000 +0x7FFF). When we reach the entry_point then R1 R2 and R13 are pointer in the Bootrom/IPL. The first function __init_registers initialize them for executing the dol and we can see that it's set to the beginning of some .data and .bss sections.		As said above SDA are used with a signed short offset (-0x8000 +0x7FFF). When we reach the entry_point then R1 R2 and R13 are pointer in the Bootrom/IPL. The first function __init_registers initialize them for executing the dol and we can see that it's set to the beginning of some .data and .bss sections.

Algoflash: /* Sections */

2023-10-07T11:59:52Z

Sections

← Older revision		Revision as of 13:59, 7 October 2023
Line 143:		Line 143:
	The PowerPc Embedded Application Binary Interface (EABI) describes 4 special registers:		The PowerPc Embedded Application Binary Interface (EABI) describes 4 special registers:
	* R1 is the stack pointer. We subtract the space needed from it when entering in a function (Stack Frame). Terminal functions (those which don't call any functions) don't always need a frame.		* R1 is the stack pointer. We subtract the space needed from it when entering in a function (Stack Frame). Terminal functions (those which don't call any functions) don't always need a frame.
	* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It ~~correspond~~ to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).		* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It corresponds to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).
	* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It ~~correspond~~ to the .sdata (initialized variables) or .sbss (uninitialized variables).		* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It corresponds to the .sdata (initialized variables) or .sbss (uninitialized variables).
	* R0 when used with an offset don't care about it's value. It allow to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).		* R0 when used with an offset don't care about it's value. It allow to address 0x8000 first bytes of memory space and 0x7fff last bytes (signed short).

Algoflash: /* Sections */

2023-10-07T11:59:20Z

Sections

← Older revision		Revision as of 13:59, 7 October 2023
Line 142:		Line 142:

	The PowerPc Embedded Application Binary Interface (EABI) describes 4 special registers:		The PowerPc Embedded Application Binary Interface (EABI) describes 4 special registers:
	* R1 is the stack pointer. We ~~substract~~ the space needed from it when entering in a function (Stack Frame). Terminal functions (those which don't call any functions) don't always need a frame.		* R1 is the stack pointer. We subtract the space needed from it when entering in a function (Stack Frame). Terminal functions (those which don't call any functions) don't always need a frame.
	* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It correspond to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).		* R2 is the read only Small Data Anchor __SDA2_BASE__ addressed with a signed short offset. It correspond to the .sdata2 (initialized constants) or .sbss2 (uninitialized constants).
	* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It correspond to the .sdata (initialized variables) or .sbss (uninitialized variables).		* R13 is the Read / Write Small Data Anchor __SDA_BASE__ also addressed with a signed short offset. It correspond to the .sdata (initialized variables) or .sbss (uninitialized variables).