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

Getting started, can't connect to nRF51 dev board

Hey guys,

Sorry to a basic question here, but it's been a few hours and I still can't get a connection to either of two brand new nRF51 dev boards, trying both on WindowsXP and MacOS.

See attached screenshot for Windows XP. JLink.exe seems to connect, but when I try to load the blinky .hex file via the Windows app J-Flash, it says "Error: Could not perform target reset"

Same in MacOS, typing JLinkExe... SEGGER J-Link Commander V4.96l ('?' for help) Compiled Feb 25 2015 10:24:59 DLL version V4.96l, compiled Feb 25 2015 10:24:52 Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 28 2014 10:32:04 Hardware: V1.00 S/N: 681313228 VTarget = 3.300V Info: Found SWD-DP with ID 0x0BB11477 Info: Found Cortex-M0 r0p0, Little endian. Info: FPUnit: 4 code (BP) slots and 0 literal slots Found 1 JTAG device, Total IRLen = 4: Cortex-M0 identified. Target interface speed: 100 kHz

Alright... this has got to be a simple answer here for something I'm missing. Pretty bad initial experience here with Nordic tools.

Thanks so much! Brian

image description

  • Ok... tried the command line, and it looks like the blinky demo was already programmed? But no blinky. This seems pretty basic, but no blinky.

    What am I missing?

    Thanks, Brian

    $JLinkExe -device nrf51822_xxaa -if swd -speed 4000

    SEGGER J-Link Commander V4.96l ('?' for help)

    Compiled Feb 25 2015 10:24:59

    Info: Device "NRF51822_XXAA" selected.

    DLL version V4.96l, compiled Feb 25 2015 10:24:52

    Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 28 2014 10:32:04

    Hardware: V1.00

    S/N: 681313228

    VTarget = 3.300V

    Info: Found SWD-DP with ID 0x0BB11477

    Info: Found Cortex-M0 r0p0, Little endian.

    Info: FPUnit: 4 code (BP) slots and 0 literal slots

    Cortex-M0 identified.

    Target interface speed: 1000 kHz

    J-Link>loadbin mbed_blinky_NRF51822.hex 0x16000

    Halting CPU for downloading file.

    Downloading file [mbed_blinky_NRF51822.hex]...Info: J-Link: Flash download: Flash download into internal flash skipped. Flash contents already match

    Info: J-Link: Flash download: Total time needed: 0.347s (Prepare: 0.087s, Compare: 0.252s,

    Erase: 0.000s, Program: 0.000s, Verify: 0.000s, Restore: 0.006s)

    O.K.

    J-Link>r

    Reset delay: 0 ms

    Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.

    J-Link>g

    J-Link>exit

  • If you are loading blinky at 0x16000 then that would indicate you are building to use with a softdevice, have you put a softdevice on? Or if you are building basic blinky with no softdevice then the code builds for, and goes at, 0x00000.

  • Hi

    As RK points out, you need to be aware of if you have an application that is supposed to be used with a softdevice, or without a softdevice. The streamlined way of flashing the softdevice and see what is going on is with nRFgo Studio. This method is also described in the getting started guide in the nRF51 SDK.

    This thread talks about applications with and without softdevice

Related