I’m using a Flyswatter to debug a custom ARM926ejs SoC with a recent version of OpenOCD from SVN. Loading an image to RAM seems to work, but a ‘resume 0xc0008000’ after loading the image generates an
Debug: 226 133638 arm926ejs.c:113 arm926ejs_catch_broken_irscan(): caught ARM926EJ-S invalid Capture-IR result after CP15 access
My understanding is that 926 support is somewhat new territory, so I backed up and tried a couple of basic 926 specific commands:
Open On-Chip Debugger
> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x60000093 pc: 0xc0025818
MMU: enabled, D-Cache: enabled, I-Cache: disabled
> arm926ejs cache_info
cache type: 0xe, separate caches
D-Cache: linelen 32, associativity 4, nsets 128, cachesize 0x4000
I-Cache: linelen 32, associativity 4, nsets 128, cachesize 0x4000
> arm926ejs cp15 0 0 0 0
0 0 0 0: 41069265
TAP dw52.cpu:
value captured during scan didn't pass the requested check:
captured: 0x00 check_value: 0x01 check_mask: 0x0f
in_handler reported a failed check
The cache_info command did not generate an error, the halt command generated the “invalid Capture-IR result” error listed above, and the cp15 command generated the warning shown in the listing. Do I need to worry about any of these messages? Are they indicating a problem with my configuration?