• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Unable to unbrick uboot: timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS  (Read 2599 times)
jeffball
Newbie
*

Karma: 0
Posts: 1


View Profile
« on: June 18, 2010, 11:46:35 AM »

I'm attempting to reflash my bricked openrd-client through openocd.  I've attached the output below.  I've been searching for a while now and the two other posts I've found who have gotten the error:  "timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0" both claim that the issue was a hardware problem.  My questions are, could there be another cause, how can I tell if it is actually my openrd-client that is the issue, and does anyone know what this error means.  I have 4 of these devices and the other three worked fine while following the exact same process.  I've been following this guide whenever I have to unbrick one of them.

Code:
Open On-Chip Debugger
> halt
target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled
> load_image /uboot.elf
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
Command handler execution failed
in procedure 'load_image' called at file "command.c", line 654
called at file "command.c", line 365
> version
Open On-Chip Debugger 0.5.0-dev-snapshot (2010-06-10-15:10)
Logged

Pages: [1]
Print
Jump to: