Hacking Game Boy - Revision history

MathUser: /* Using BGB's Debugger */

2008-12-04T16:38:52Z

Using BGB's Debugger

← Older revision		Revision as of 16:38, 4 December 2008
Line 97:		Line 97:


			{{EnHacklopedia}}

	{{Template: EnHacklopedia_Legal}}		{{Template: EnHacklopedia_Legal}}
	[[Category: EnHacklopedia]]		[[Category: EnHacklopedia]]

Ace at 14:27, 3 December 2008

2008-12-03T14:27:13Z

← Older revision		Revision as of 14:27, 3 December 2008
Line 1:		Line 1:
	{{Template:EnHacklopedia Header}}		{{Template:EnHacklopedia Header}}


	==Game Genie==		==Game Genie==

Ace at 14:26, 3 December 2008

2008-12-03T14:26:50Z

← Older revision		Revision as of 14:26, 3 December 2008
Line 84:		Line 84:
	[[Image:bgbcheat.png\|center\|BGB's Cheat Searcher]]		[[Image:bgbcheat.png\|center\|BGB's Cheat Searcher]]

	[[Tools#BGB\|BGB]] is a Game Boy and Game Boy Color emulator with Game Genie and GameShark code support as well as code searching and debugger ~~functionability~~. To use the cheat search, first open up the emulator and load a game. Once loaded, right click and go to "cheat search" inside the "other" option. The cheat search provides 8 and 16-bit searches, both known and unknown. Search values need to be entered in hexadecimal.		[[Tools#BGB\|BGB]] is a Game Boy and Game Boy Color emulator with Game Genie and GameShark code support as well as code searching and debugger functionality. To use the cheat search, first open up the emulator and load a game. Once loaded, right click and go to "cheat search" inside the "other" option. The cheat search provides 8 and 16-bit searches, both known and unknown. Search values need to be entered in hexadecimal.


Line 92:		Line 92:
	[[Image:bgbdis.png\|center\|none\|550px\|BGB's Disassembler]]		[[Image:bgbdis.png\|center\|none\|550px\|BGB's Disassembler]]

	BGB's debugger is accessed by choosing "debugger" under the "other" menu. The main part of the window shows the assembly, with the instruction PC points to on top. 24 instructions are shown at a time. However, scrolling up and down to see others is possible. On the bottom, a memory viewer is shown. The top right area shows the values of all the registers and status flags, and on the right a scrollable memory viewer is available, showing 16-bits per line. On the memory viewer in the bottom middle of the screen, memory can be copied, ~~editted~~, and inserted depending on the option chosen after right clicking on that area. The "modify code" instruction allows the memory address specified to be overwritten with assembly code entered into the message box. These same options are provided when right clicking on the disassembly section. Under the "File" menu, there are the normal "Load ~~Rom~~", "Save State" and "Load State" options. Additionally, there is a "Save ROM" option, which will save the ROM with any changes that have been made to the assembly code. A "fix checksum" option is also provided, which recalculates the checksum byte for the ROM header. Memory and ASM dump options are provided as well. Under "Options", a "Search String" option is given. This searches the assembly code for an instruction that matches the search string provided. For instance, searching for "ld a," will find any instructions that load any value in a, such as "ld a, (ff00+91)" and "ld a, (bc)". Under the "Run" menu, the normal "Run" and "Reset" options are provided. The "trace" option is effectively a "step" instruction - it executes the next instruction. The "Run to next line" option is similar. The instruction that succeeds the current instruction in memory is executed. This means that all jumps are skipped. The "Animate" options runs the game with the disassembler highlighting the instruction being executed. The "run to cursor" option runs the game until the highlighted instruction is executed. The "step out" instruction executed assembly code until the code returns from a subroutine. Finally, the last option jumps to the instruction SP points to and then increments the stack pointer.		BGB's debugger is accessed by choosing "debugger" under the "other" menu. The main part of the window shows the assembly, with the instruction PC points to on top. 24 instructions are shown at a time. However, scrolling up and down to see others is possible. On the bottom, a memory viewer is shown. The top right area shows the values of all the registers and status flags, and on the right a scrollable memory viewer is available, showing 16-bits per line. On the memory viewer in the bottom middle of the screen, memory can be copied, edited, and inserted depending on the option chosen after right clicking on that area. The "modify code" instruction allows the memory address specified to be overwritten with assembly code entered into the message box. These same options are provided when right clicking on the disassembly section. Under the "File" menu, there are the normal "Load ROM", "Save State" and "Load State" options. Additionally, there is a "Save ROM" option, which will save the ROM with any changes that have been made to the assembly code. A "fix checksum" option is also provided, which recalculates the checksum byte for the ROM header. Memory and ASM dump options are provided as well. Under "Options", a "Search String" option is given. This searches the assembly code for an instruction that matches the search string provided. For instance, searching for "ld a," will find any instructions that load any value in a, such as "ld a, (ff00+91)" and "ld a, (bc)". Under the "Run" menu, the normal "Run" and "Reset" options are provided. The "trace" option is effectively a "step" instruction - it executes the next instruction. The "Run to next line" option is similar. The instruction that succeeds the current instruction in memory is executed. This means that all jumps are skipped. The "Animate" options runs the game with the disassembler highlighting the instruction being executed. The "run to cursor" option runs the game until the highlighted instruction is executed. The "step out" instruction executed assembly code until the code returns from a subroutine. Finally, the last option jumps to the instruction SP points to and then increments the stack pointer.

	The "Debug" menu controls breakpoints and similar options. F2 ("Toggle Breakpoint") toggles a BPX on the highlighted instruction. An "evaluate expression" options attempts to evaluate an inputted instruction. The "breakpoint" option allows a BPX to be added or removed. To add a BPX, input the address of the instruction that should be broken upon into the "PC =" box, and add any necessary condition in the other box. If no condition is needed, leave it empty. The "Access Breakpoints" allows the addition and removal of BPR's and BPW's. Choose "read" and/or "write" to choose the break option, and put the address or address range into the "addr range" box.		The "Debug" menu controls breakpoints and similar options. F2 ("Toggle Breakpoint") toggles a BPX on the highlighted instruction. An "evaluate expression" options attempts to evaluate an inputted instruction. The "breakpoint" option allows a BPX to be added or removed. To add a BPX, input the address of the instruction that should be broken upon into the "PC =" box, and add any necessary condition in the other box. If no condition is needed, leave it empty. The "Access Breakpoints" allows the addition and removal of BPR's and BPW's. Choose "read" and/or "write" to choose the break option, and put the address or address range into the "addr range" box.

Ace: Hacking Gameboy moved to Hacking Game Boy

2008-12-03T11:39:27Z

Hacking Gameboy moved to Hacking Game Boy

← Older revision	Revision as of 11:39, 3 December 2008
(No difference)

Ace: /* Using BGB's Debugger */

2008-12-03T08:21:46Z

Using BGB's Debugger

← Older revision		Revision as of 08:21, 3 December 2008
Line 90:		Line 90:
	==Using BGB's Debugger==		==Using BGB's Debugger==

	[[Image:bgbdis.png\|center\|BGB's Disassembler]]		[[Image:bgbdis.png\|center\|none\|550px\|BGB's Disassembler]]

	BGB's debugger is accessed by choosing "debugger" under the "other" menu. The main part of the window shows the assembly, with the instruction PC points to on top. 24 instructions are shown at a time. However, scrolling up and down to see others is possible. On the bottom, a memory viewer is shown. The top right area shows the values of all the registers and status flags, and on the right a scrollable memory viewer is available, showing 16-bits per line. On the memory viewer in the bottom middle of the screen, memory can be copied, editted, and inserted depending on the option chosen after right clicking on that area. The "modify code" instruction allows the memory address specified to be overwritten with assembly code entered into the message box. These same options are provided when right clicking on the disassembly section. Under the "File" menu, there are the normal "Load Rom", "Save State" and "Load State" options. Additionally, there is a "Save ROM" option, which will save the ROM with any changes that have been made to the assembly code. A "fix checksum" option is also provided, which recalculates the checksum byte for the ROM header. Memory and ASM dump options are provided as well. Under "Options", a "Search String" option is given. This searches the assembly code for an instruction that matches the search string provided. For instance, searching for "ld a," will find any instructions that load any value in a, such as "ld a, (ff00+91)" and "ld a, (bc)". Under the "Run" menu, the normal "Run" and "Reset" options are provided. The "trace" option is effectively a "step" instruction - it executes the next instruction. The "Run to next line" option is similar. The instruction that succeeds the current instruction in memory is executed. This means that all jumps are skipped. The "Animate" options runs the game with the disassembler highlighting the instruction being executed. The "run to cursor" option runs the game until the highlighted instruction is executed. The "step out" instruction executed assembly code until the code returns from a subroutine. Finally, the last option jumps to the instruction SP points to and then increments the stack pointer.		BGB's debugger is accessed by choosing "debugger" under the "other" menu. The main part of the window shows the assembly, with the instruction PC points to on top. 24 instructions are shown at a time. However, scrolling up and down to see others is possible. On the bottom, a memory viewer is shown. The top right area shows the values of all the registers and status flags, and on the right a scrollable memory viewer is available, showing 16-bits per line. On the memory viewer in the bottom middle of the screen, memory can be copied, editted, and inserted depending on the option chosen after right clicking on that area. The "modify code" instruction allows the memory address specified to be overwritten with assembly code entered into the message box. These same options are provided when right clicking on the disassembly section. Under the "File" menu, there are the normal "Load Rom", "Save State" and "Load State" options. Additionally, there is a "Save ROM" option, which will save the ROM with any changes that have been made to the assembly code. A "fix checksum" option is also provided, which recalculates the checksum byte for the ROM header. Memory and ASM dump options are provided as well. Under "Options", a "Search String" option is given. This searches the assembly code for an instruction that matches the search string provided. For instance, searching for "ld a," will find any instructions that load any value in a, such as "ld a, (ff00+91)" and "ld a, (bc)". Under the "Run" menu, the normal "Run" and "Reset" options are provided. The "trace" option is effectively a "step" instruction - it executes the next instruction. The "Run to next line" option is similar. The instruction that succeeds the current instruction in memory is executed. This means that all jumps are skipped. The "Animate" options runs the game with the disassembler highlighting the instruction being executed. The "run to cursor" option runs the game until the highlighted instruction is executed. The "step out" instruction executed assembly code until the code returns from a subroutine. Finally, the last option jumps to the instruction SP points to and then increments the stack pointer.

Ace at 08:15, 3 December 2008

2008-12-03T08:15:08Z

@@ Line 1: / Line 1: @@
 {{Template:EnHacklopedia Header}}
 {{Template: EnHacklopedia_Legal}}
 [[Category: EnHacklopedia]]

Ace: New page: {{Template:EnHacklopedia Header}} {{Template: EnHacklopedia_Legal}} Category: EnHacklopedia

2008-12-03T02:10:49Z

New page: {{Template:EnHacklopedia Header}} {{Template: EnHacklopedia_Legal}} Category: EnHacklopedia

New page

{{Template:EnHacklopedia Header}}

{{Template: EnHacklopedia_Legal}}
[[Category: EnHacklopedia]]