Okay, instead of tracing I have been reading more so far today. Will get to the tracing, but, came across this and had some thoughts:
"The 2BL (bootloader2/secondary boot loader) is responsible for decrypting/decompressing the main KERNEL image and 'jumping' to it.
When 2BL starts, it is executing in a CPU address region from 090000-095FFF. It first sets up some simple page-tables (with what appears to be a one-to-one mapping of virtual to physical addresses), copies itself to CPU address region 400000-405FFF, enables paging, then 'jumps' to the copy of 2BL that it created based at 400000.
Next, the MCPX internal boot sector is 'hidden' (since it is no longer needed), and the PIC 'watchdog reset' is disabled (without doing this, the PIC chip will force a CPU reset after approximately 200ms of execution). The original decrypted copy of 2BL at CPU addresses 090000-095FFF is erased."
Now, based on the above, a FRAG Xbox lets say, could it, or is it that the PIC reset is not being disabled, and that maybe is the cause of the FRAG, it reboots twice, and upon 3rd attempt, if still not disabled, it stops trying and FRAG's.
Anyone have any thoughts on that???