si
is slow, especially when there are big loops. It might be better to add commands or code in DingusPPC to enter the DPPC debugger when the code at the PPC or 68K program counter matches some bytes (which you would grab from the Mac OS Loader file).
Another option would be to alter the code to enable instruction logging, and have it use get_name_OpenFirmware
to detect the very first Open Firmware code being executed. See the code that handles the debug_copland
option. Of course, you could just get the address of an early Open Firmware instruction (such as the address of @startvec
= 0xFF808000 or real address 0x00408000 or cold-load
at 0xFF80FF88 if that doesn't work) and use that with a until
command.
Then dump the instruction log. Maybe there's an interesting address in the instruction log that you could use with until
after rebooting. Then use si
from there.
We know nothing important is happening until the hard disk is being read. So that would be another good place to stop the debugger and start logging.