Skip to content

Instantly share code, notes, and snippets.

@elsuizo

elsuizo/error_openocd_gdb

Created August 28, 2017 23:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save elsuizo/eecedf30c935aafee6b8c122f16a13a0 to your computer and use it in GitHub Desktop.
Save elsuizo/eecedf30c935aafee6b8c122f16a13a0 to your computer and use it in GitHub Desktop.
Download ZIP
Error gdb openocd in custom board with lpc4337 and ftdi connection
Raw
error_openocd_gdb
Info : lpc4337.m4: hardware has 6 breakpoints, 4 watchpoints
Info : lpc4337.m0: hardware has 2 breakpoints, 1 watchpoints
Info : accepting 'gdb' connection on tcp/3333
Info : JTAG tap: lpc4337.m4 tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Info : JTAG tap: lpc4337.m0 tap/device found: 0x0ba01477 (mfg: 0x23b (ARM Ltd.), part: 0xba01, ver: 0x0)
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1a002730 msp: 0x10008000
Error: timed out while waiting for target halted
TARGET: lpc4337.m0 - Not halted
in procedure 'reset'
in procedure 'ocd_bouncer'
Error: timeout waiting for flash to finish write/erase operation
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
Info : Halt timed out, wake up GDB.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment