Programming nRF52 with OpenOCD

RE: Programming nRF52 with OpenOCD

dimka-rs — Fri, 15 Jun 2018 13:22:59 GMT

    $(OPENOCD)/src/openocd -s $(OPENOCD)/tcl -f interface/stlink.cfg -f target/nrf52.cfg -c init -c "reset init" -c halt -c "nrf5 mass_e    rase" -c "program $< verify" -c reset -c exit

RE: Programming nRF52 with OpenOCD

chbereh — Tue, 10 Apr 2018 09:33:20 GMT

Can you tell how the .cfg and openocd command looks like?

RE: Programming nRF52 with OpenOCD

Matt Pfenninger — Tue, 27 Mar 2018 21:04:53 GMT

FYI - As of 3/27/2018, it looks like nrf52 support has been moved into the main openocd trunk (merged with nrf51 support as the 'nrf5' command set). I was just able to program an nrf52832 (Rigado) device.

RE: Programming nRF52 with OpenOCD

drahnr — Fri, 19 Jan 2018 12:15:48 GMT

Is that patch still relevant? I get the same issue regarding nrf52 not being a valid command

RE: Programming nRF52 with OpenOCD

amartin — Thu, 13 Jul 2017 05:51:26 GMT

This problem has probably been solved already, but for those peaple who will stumble here while struggling with their own version of the same, don't forget to check whether the instance of "openocd" you are using is really the one you have patched and installed. "which openocd" might prove useful.

RE: Programming nRF52 with OpenOCD

Shriram — Thu, 01 Dec 2016 09:21:23 GMT

Hello, I've applied patch manually for nrf52 as suggested by ubicore, I've applied patch to these following files src/flash/nor/Makefile.am 1 src/flash/nor/drivers.c 2 src/flash/nor/nrf52.c 1056 tcl/target/nrf52.cfg

but still it is showing error

ac2@ac2:~/openocd_new$ openocd -s /home/ac2/openocd_new/tools/scripts/ -f board_nrf52.cfg -c init -c "reset init" -c halt -c "nrf52 mass_erase" -c "program /home/ac2/test_nrf52/nRF5_SDK_12.1.0_0d23e2a/examples/peripheral/blinky/pca10031/blank/armgcc/_build/nrf51422_xxac.out verify" -c reset -c exit Open On-Chip Debugger 0.10.0-dev-00419-gbcaf775-dirty (2016-11-29-13:32) Licensed under GNU GPL v2 For bug reports, read openocd.org/.../bugs.html Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD adapter speed: 10000 kHz Info : Unable to match requested speed 10000 kHz, using 4000 kHz Info : Unable to match requested speed 10000 kHz, using 4000 kHz Info : clock speed 4000 kHz Info : STLINK v2 JTAG v21 API v2 SWIM v4 VID 0x0483 PID 0x3748 Info : using stlink api v2 Info : Target voltage: 3.248372 Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints nrf52.cpu: target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x000008e4 msp: 0x20000400 invalid command name "nrf52"

Can you help me figure out now which steps I am missing?

RE: Programming nRF52 with OpenOCD

Abhishek — Thu, 01 Dec 2016 07:33:04 GMT

Hi,

Even I am facing similar issue. As suggested by ubicore I checked that patch related to nrf52 target is correctly applied. Following is the error,

MS-7817:~/workarea/Projects/ble_door_lock/open/openocd-code$ openocd -s /home/ac1/workarea/Projects/ble_door_lock/open/openocd-code/ -f board_nrf52.cfg -c init -c "reset init" -c halt -c "nrf52 mass_erase" -c "program blinky_pca10031.hex verify" -c reset -c exit
Open On-Chip Debugger 0.10.0-dev-00419-gbcaf775-dirty (2016-11-30-17:06)
Licensed under GNU GPL v2
For bug reports, read
	openocd.org/.../bugs.html
Error: The specified debug interface was not found (hla)
The following debug interfaces are available:

PS: But it does not show any interfaces under 'following interfaces are available'. Although we have installed, STlink 'github.com/.../compiling.md', since we are using ST LinkV2 progammer for programming nrf52 module

RE: Programming nRF52 with OpenOCD

ubicore — Wed, 30 Nov 2016 11:54:47 GMT

Possible that the patch (which that add nrf52 target) has not been correctly applied...

RE: Programming nRF52 with OpenOCD

Shriram — Wed, 30 Nov 2016 11:19:16 GMT

Hello, I have followed the steps you have posted, But when I flash my nrf52832 board I find following errors:

Preparing: _build/nrf51422_xxac.hex
Flashing: _build/nrf51422_xxac.hex
/home/ac2/test_nrf52/openocd-code/src/openocd -s /home/ac2/test_nrf52/openocd-code/tcl -f /home/ac2/test_nrf52/openocd-code/board_nrf52.cfg  -c init -c "reset init" -c halt -c "nrf52 mass_erase" -c "program _build/nrf51422_xxac.hex verify" -c reset -c exit
Open On-Chip Debugger 0.10.0-dev-00419-gbcaf775-dirty (2016-11-29-13:32)
Licensed under GNU GPL v2
For bug reports, read
	openocd.org/.../bugs.html
Error: flash driver 'nrf52' not found

Makefile:182: recipe for target 'flash' failed
make: *** [flash] Error 1

Can you help me figure out which steps I am missing?

RE: Programming nRF52 with OpenOCD

ubicore — Thu, 09 Jun 2016 14:58:47 GMT

Hi,

I work from a few day with openOCD to program and debug on nRF52. For this I'm using a patched version of openocd.

1 - Clone openocd from git from sourceforge.net/.../

git clone git://git.code.sf.net/p/openocd/code openocd-code
cd openocd-code

2 - Apply patch for nrf52 : openocd.zylin.com/

git pull openocd.zylin.com/openocd refs/changes/15/3215/2

If need merge conflict manually

gedit src/flash/nor/drivers.c
gedit src/flash/nor/Makefile.am

3 - Build OpenOCD (change prefix) :

./bootstrap # (when building from the git repository)
./configure \
    --prefix=/Your-path/openocd-git_install \
    --enable-aice \
    --enable-amtjtagaccel \
    --enable-armjtagew \
    --enable-cmsis-dap \
    --enable-dummy \
    --enable-ftdi \
    --enable-gw16012 \
    --enable-jlink \
    --enable-jtag_vpi \
    --enable-opendous \
    --enable-openjtag_ftdi \
    --enable-osbdm \
    --enable-legacy-ft2232_libftdi \
    --enable-parport \
    --disable-parport-ppdev \
    --enable-parport-giveio \
    --enable-presto_libftdi \
    --enable-remote-bitbang \
    --enable-rlink \
    --enable-stlink \
    --enable-ti-icdi \
    --enable-ulink \
    --enable-usb-blaster-2 \
    --enable-usb_blaster_libftdi \
    --enable-usbprog \
    --enable-vsllink

make
make install

4 - Create a new board_nrf52.cfg config file with :

source [find interface/jlink.cfg]
transport select swd
source [find target/nrf52.cfg]

5 - Debug !

openocd -s /Your-path/openocd-git_install/share/openocd/scripts/ -f board_nrf52.cfg -c init -c "reset init" -c halt -c "nrf52 mass_erase" -c "program _build/nrf52832_xxaa.out verify" -c reset -c exit

RE: Programming nRF52 with OpenOCD

Gordon — Fri, 13 May 2016 09:18:30 GMT

This seems to be because Rigado set the memory protection bit.

Thanks to Rigado's support, it seems you can do nrfjtool --recover to remove this (or you can manually poke the relevant registers).

As it happens you can program an nRF52 from the nRF52DK by connecting it up to P20. The devkit switches over automatically (no jumpers needed). nrfjtool is also available for Linux now, so there's very little reason (IMO) to have to use OpenOCD now.

Of course it still doesn't work for me after all that, but I've created a new issue for that as it appears that OpenOCD would have worked, if it weren't for the memory protection bit being set.

New issue: devzone.nordicsemi.com/.../