gba: add support for mGBA debugging

[zowhoey]

Implements putchar when mgbadebug build tag is set which outputs
text through the mGBA debugging output interface.

mGBA allows the games running in the emulator to output debug text
The process to do so is:

1. set 0x4FFF780 to value of 0xC0DE
2. write text in memory 0x4FFF600 to 0x4FFF700
3. set 0x4FFF700 to the desired log level value from 0x100 (fatal) to
   0x104 (debug)

Once this is done mGBA will output the text in its logs view as well as
through stdout. (Setting the log level to fatal also produces a dialog
box with the text)

The text output in the CLI is prefixed with [DEBUG] GBA Debug: so I
modified the regex used for address matching in panic messages to be
able to read the address when the output line doesn't start with
panic.

After the change

func main() {
	println("hello world")
	// fake panic with an address in it for demo purposes
	panic("runtime error at 0x08000000: ")
}

results in output such as:

This makes debugging much easier as panic messages are shown and we can also do
debug prints.

[jwetzell]

Nice! I was looking at adding this too except I was going to add it to https://github.com/tinygo-org/tinygba . I like the ability to just use println though.

[zowhoey]

Hmm I didn't realize tinygba is a thing. I've been doing a fair bit of GBA development with tinygo slowly over several years (it's my fallback project when I get tired of everything else) so I have a fair bit of GBA functionality implemented.
No bitmap modes, no gamepak stuff, no DMA sound, but most other stuff is either fully or partially implemented. I'm not sure my code would mash well with the existing tinygba code, but I should probably look into publishing the code publicly as it could be useful for others.

I've had the code for mGBA debug printing in my code for at least 2 years as a custom log package. Eventually as the scale grew I started running into mysterious crashes very often that were really annoying to debug without seeing runtime panics, so having this code in the actual runtime has been pretty helpful.

[deadprogram]

@zowhoey do please publish whatever code you have for gba. It would be amazing to have more support implemented, however we get it out there. If we can merge some of that into tinygba, great. If not, also fine. Just having a way to see working code that does things will be very helpful I'm sure!

[jwetzell]

@zowhoey nice! When I get bored of other things I've been messing with getting a good link cable API going mostly following this repo!

[deadprogram]

I just wonder if it might be better to add this to https://github.com/tinygo-org/tinygo/blob/dev/src/device/gba/gba.go what do you think?

[zowhoey]

I was a bit split on whether I should put the registers in the gba.go file or in runtime_mgba.go, I've decided to put it in the runtime_mgba.go file as it'd keep all mGBA specific code behind a build tag so it's easy to avoid using it on real hardware.

Although I suppose having it in gba.go makes it easier for people to implement their own logging if they want different log levels in the output.

[deadprogram]

Actually you are right. Never mind, my suggestion was incorrect.

[zowhoey]

Shall I revert the commit then?

[deadprogram]

Yes, please. Sorry about that.

[zowhoey]

No problem at all, thank you for reviewing!

[deadprogram]

Thank you for the improvement @zowhoey now merging.