@User: It's the same one that puts code into RAM and runs it. The IRQ causes the program counter to be set to memory location zero, so the IRQ handler has to be placed in RAM at position 0. I have not debugged that yet, although I could just tarball it up and dump it in your lap if you want.