This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 + OpenOCD: Error: Could not initialize the debug port

Hi,

when trying to connect to a 51822 target, using for example OOCD I keep getting

.... Open On-Chip Debugger 0.10.0-rc1-dev-00001-gc404ff5-dirty (2016-12-29-19:45) Licensed under GNU GPL v2 For bug reports, read openocd.org/.../bugs.html cortex_m reset_config sysresetreq adapter speed: 1000 kHz Info : CMSIS-DAP: SWD Supported Info : CMSIS-DAP: Interface Initialised (SWD) Info : CMSIS-DAP: FW Version = 1.0 Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1 Info : CMSIS-DAP: Interface ready Info : clock speed 1000 kHz Info : SWD DPIDR 0x0bb11477 Error: Could not initialize the debug port

I have tried with various debug probes - of different types, same or similar result with any. This has worked till yesterday - and still works with another 51822 board.

The fact that the DPIDR was readable suggests that the 51822 is still alive (to some extent...)

Any ideas what's going on here?

Thanks.

Parents
  • As I said, i was using different debug probes, JLink (with both OOCD and the Segger GDB server), BlackMagic, CMSIS-DAP, presenting similar symptoms.

    I investigated this further and found a hint in the ARM ADIv5 reference manual. The probe is polling for a PoWeRUP event which never gets set, as the OOCD -d3 log revealed.

    But nevermind, I scrapped this module for another one which is working ok.

    Thanks.

Reply
  • As I said, i was using different debug probes, JLink (with both OOCD and the Segger GDB server), BlackMagic, CMSIS-DAP, presenting similar symptoms.

    I investigated this further and found a hint in the ARM ADIv5 reference manual. The probe is polling for a PoWeRUP event which never gets set, as the OOCD -d3 log revealed.

    But nevermind, I scrapped this module for another one which is working ok.

    Thanks.

Children
Related