Getting stuff to work on PS2 wasn’t quite as easy as I probably made it sound in the last homebrew post. The problem with loading code from usb stick is that there is no way to debug anything, no remote debugging, no stdout – not even any way to render text unless you write your own program to do that.
The trick is to use the fact that we are rendering a CRT TV signal and that you can control what gets rendered in the overscan area (think 8bit loading screens). There is a register which directly sets the background colour of the scanline – this macro is all you need:
#define gs_p_bgcolor 0x120000e0 // Set CRTC background color #define GS_SET_BGCOLOR(r,g,b) \ *(volatile unsigned long *)gs_p_bgcolor = \ (unsigned long)((r) & 0x000000FF) << 0 | \ (unsigned long)((g) & 0x000000FF) << 8 | \ (unsigned long)((b) & 0x000000FF) << 16
Which you can use to set the background to green for example:
Its a good idea to change this at different points in your program. When you get a crash the border colour it’s frozen with will tell you what area it was last in, allowing you to track down errors.
There is also a nice side effect that this provides a visual profile of your code at the same time. Rendering is synced to the vertical blank – when the CRT laser shoots back to the top of the screen a new frame is started and you have a 50th of a second (PAL) to get everything done. In the screenshot below you can see how the frame time breaks down rendering 9 animated primitives – and why it might be a good idea to use some of these other processors: