QUOTE
No booting details known. [if you could connect to JTAG-pins and figure out how to use on-chip debugging features, you might be able to single step the boot code, bypass the boot loader altogether and get direct access to hardware and memory etc. You might also be able to create your own modified boot loader into RAM. As the boot ROM resides on-chip, the mods may need always some kind of hardware solution, for example a simple FPGA with an external Flash containing a modified boot monitor which will be downloaded using the JTAG interface during power-up by the FPGA. Once the boot sequence and protection is RE'd one may be able to find a software-only solution to circumvent the protections.]
This is why he use is Laptop:
QUOTE
[Also, it might be possible to arrange a remote access over Internet to this JTAG interface/debugger for selected skillful persons: Those persons might even use some kind of messenger conference call to use debugger together and see in real-time what's going on. Messenger with a secured remote desktop access might do the job.]
And there is very like very good information that lead me to this:
QUOTE
Disassembling old kernel - it accesses a serial port
SERIAL PORT!!: debug info written to on debug box, 115k
boot monitor: send special character '@' -> talk to boot monitor
plaintext interface
you can read/write memory, execute code
bootloader runs before hypervisor setup
boot monitor works on physical memory
write to pci config space possible, read memory, write memory
c000xxxx: THE interesting stuff is HERE!!!! can't be accessed - hangs
c8xxxxxx NAND - bootloader reads from there, copies to RAM
hack: use network to dump in boot monitor, just didn't work :- (something might not be configured yet
* read
* write
* init ram
everything before uses no ram
in bootloader: 1010101010 patterns - bus/memory training?