Way to wake up an old thread I spent a few hours reading the full thread, since the links to part 2 and 3 of the Demo Dev PDFs are dead. There were also some dead links here, especially the ones near the end, when you had solved some issues with Exit to menu etc. and I was hoping to have a look at the finished framework v6b. Darn! :angry: I guess it's on archive.gp32x.de somewhere? I'm a scene coder with a bit of spare time on my hands, and was inspired by the Nom demo when I was at Breakpoint this Easter. Dwelch's suggestion to 'turn off Linux' and have my way with the hardware was appealing to me, since it's the first thing I do when I start coding demos for any platform. Nicely own resources, nicely stop processes, then set my own ints and let the OS have a break I just translated SDL's gp2x_joystick_read to pascal, using /dev/mem and mmap to read the hw regs. I would like to go all Assembler shortly. But doesn't mmap essentially hide the physical hw reg addresses from me? I'd like to, once I own the system, to access them without any table lookups or similar. (An include was mentioned in an SDK, but the link was dead.) - So: Is there a list of physical hw reg addresses, their bits, and their names? I think I will also follow dwelch's advice regarding caching and communication; is there also advice / examples you guys could point me to, on how to nicely fire Linux and rehire him on exit? Thankful for any advice, checking rlyeh's hello world example... Edit: Found the SDK. What I'm after is how to access the hw regs in an OS friendly way. Is it safe, if I own the machine, to just go CODE ldr r0, nMSP_TCOUNT mov r0, [r0] ?