On Tue, Jun 9, 2009 at 6:13 PM, David Brownell <davi...@pacbell.net> wrote:
> Tweak the csb337 code so that it doesn't enable alignment traps when > it completes the "reset init" sequence. > > It turns out that the current CFI code reliably triggers such traps. > I don't have time now to sort out what flavor bug that is; I just > need flash reading/writing to work. > --- > tcl/board/csb337.cfg | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > What do these alignment traps look like when they happen? I just updated to the latest OpenOCD (SVN 2177) and when I do reset init ... it thinks my target isn't halted and times out: hu...@hutch-laptop:/$ !telnet telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger > reset init JTAG tap: pc205.cpu tap/device found: 0x079263a9 (mfg: 0x1d4, part: 0x7926, ver: 0x0) JTAG Tap/device matched PC was not 0. Does this target need srst_pulls_trst? target state: halted target halted in ARM state due to breakpoint, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled fast memory access is enabled dcc downloads are enabled 3000 kHz target not halted Runtime error, file "/usr/local/share/openocd/scripts/board/tess.cfg", line 38: timed out while waiting for target halted Runtime error, file "embedded:startup.tcl", line 226: expected return code but got 'TARGET: pc205.cpu - Not halted' in procedure 'ocd_process_reset' called at file "embedded:startup.tcl", line 208 called at file "embedded:startup.tcl", line 209 called at file "embedded:startup.tcl", line 225 Runtime error, file "command.c", line 453:
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development