M. Dietrich wrote: > what would be the best way to figure out what happened?
The first thing I'd try is to connect a serial console. If the kernel is unhappy, maybe it can still print something. If the CPU is stuck somewhere, you could fire up OpenOCD, halt the CPU, and look at the PC. Likewise, you could use gdb get a call stack backtrace. Naturally, all this requires a debug board. I hope you have one :-) - Werner _______________________________________________ hardware mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/hardware
