How to Program RF-BM-ND01 (nrf51822) BLE4.0

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

saiteja — Wed, 20 Feb 2019 18:31:02 GMT

Hi Einar Thorsrud,

Thank you very much for the support, finally, I made it.

issue is with both clock frequency and ld file.

Now its works perfectly by changing ld file by

MEMORY

{

FLASH (rx) : ORIGIN = 0x1b000, LENGTH = 0x25000

RAM (rwx) : ORIGIN = 0x20002080, LENGTH = 0x1f80

}

Thanks for the support

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

Einar Thorsrud — Wed, 20 Feb 2019 08:46:28 GMT

Hi,

There is no fundamental difference between the nRF51 DK and any nRF51 module, so it should be the same. Have you tried looking at older threads with this error?

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

saiteja — Wed, 20 Feb 2019 05:17:56 GMT

Hi,

I am able to debug nrf51 development kit. it is working fine for me and I am able to run all example applications.

if I am trying to debug RF-BM-ND01 with j-Link debugger it is throwing the exception No source available for "0xfffffffe"

One thing I observed is whatever applications flashing on NRF51822QFAC is working fine.But RF-BM-

ND01 which is NRF51822QFAA is giving trouble(softdevice and application downloading successfully but not running)

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

Einar Thorsrud — Tue, 19 Feb 2019 14:50:17 GMT

Hi,

This did not tell me much, other than that you are using GDB to successfully (?) debug the device. If you are unfamiliar with GDB then I recommend using a more modern and user friendly IDE such as Keil. If you have a Makefile project and don't want to migrate it, then you can still use a modern debugger, such as Segger Ozone, which works very well with GCC.

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

saiteja — Tue, 19 Feb 2019 12:04:33 GMT

When i am trying to debug i am getting issues like

No source available for "0xfffffffe"

where as NRF51 development board is working fine with the same soft device and application but RF-BM-ND01 is not.

i am unable to find datasheet reagarding RF-BM-ND01

and here is the log for RF-BM-ND01:-

SEGGER J-Link GDB Server V6.12i Command Line Version

JLinkARM.dll V6.12i (DLL compiled Feb 3 2017 15:29:31)

-----GDB Server start settings-----

GDBInit file: none

GDB Server Listening port: 2331

SWO raw output listening port: 2332

Terminal I/O port: 2333

Accept remote connection: localhost only

Generate logfile: off

Verify download: on

Init regs on start: on

Silent mode: off

Single run mode: on

Target connection timeout: 0 ms

------J-Link related settings------

J-Link Host interface: USB

J-Link script: none

J-Link settings file: none

------Target related settings------

Target device: nRF52

Target interface: SWD

Target interface speed: 1000kHz

Target endian: little

Connecting to J-Link...

J-Link is connected.

Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41

Hardware: V1.00

S/N: 682403177

Checking target voltage...

Target voltage: 3.30 V

Listening on TCP/IP port 2331

Connecting to target...WARNING: Identified core does not match configuration. (Found: Cortex-M0, Configured: Cortex-M4)

Connected to target

Waiting for GDB connection...Connected to 127.0.0.1

Reading all registers

Read 4 bytes @ address 0x00000000 (Data = 0x000007C0)

Read 2 bytes @ address 0x00000000 (Data = 0x07C0)

Target interface speed set to 1000 kHz

Resetting target

Halting target CPU...

...Target halted (PC = 0x000006D0)

R0 = FFFFFFFF, R1 = FFFFFFFF, R2 = FFFFFFFF, R3 = FFFFFFFF

R4 = FFFFFFFF, R5 = FFFFFFFF, R6 = FFFFFFFF, R7 = FFFFFFFF

R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF

R12= FFFFFFFF, R13= 000007C0, MSP= 000007C0, PSP= FFFFFFFC

R14(LR) = FFFFFFFF, R15(PC) = 000006D0

XPSR C1000000, APSR C0000000, EPSR 01000000, IPSR 00000000

CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Reading all registers

Read 4 bytes @ address 0x000006D0 (Data = 0x4C174916)

Read 2 bytes @ address 0x000006D0 (Data = 0x4916)

Select auto target interface speed (1000 kHz)

Flash breakpoints enabled

Semi-hosting enabled (Handle on BKPT)

Semihosting I/O set to TELNET Client

SWO disabled succesfully.

SWO enabled succesfully.

Read 4 bytes @ address 0x000006D0 (Data = 0x4C174916)

Read 2 bytes @ address 0x000006D0 (Data = 0x4916)

Downloading 15952 bytes @ address 0x0001B000 - Verified OK

Downloading 6608 bytes @ address 0x0001EE50 - Verified OK

Downloading 8 bytes @ address 0x00020820 - Verified OK

Downloading 148 bytes @ address 0x00020828 - Verified OK

Comparing flash [....................] Done.

Verifying flash [....................] Done.

Writing register (PC = 0x1cee0100)

Read 4 bytes @ address 0x0001EE1C (Data = 0x480A2103)

Read 2 bytes @ address 0x0001EE1C (Data = 0x2103)

Resetting target

Halting target CPU...

...Target halted (PC = 0x000006D0)

R0 = FFFFFFFF, R1 = FFFFFFFF, R2 = FFFFFFFF, R3 = FFFFFFFF

R4 = FFFFFFFF, R5 = FFFFFFFF, R6 = FFFFFFFF, R7 = FFFFFFFF

R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF

R12= FFFFFFFF, R13= 000007C0, MSP= 000007C0, PSP= FFFFFFFC

R14(LR) = FFFFFFFF, R15(PC) = 000006D0

XPSR C1000000, APSR C0000000, EPSR 01000000, IPSR 00000000

CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Reading all registers

Read 4 bytes @ address 0x000006D0 (Data = 0x4C174916)

Read 2 bytes @ address 0x000006D0 (Data = 0x4916)

Starting target CPU...

...Target halted (DBGRQ, PC = 0xFFFFFFFE)

Reading all registers

Read 4 bytes @ address 0xFFFFFFFE (Data = 0x02BCED00)

Read 2 bytes @ address 0xFFFFFFFE (Data = 0x0000)

Read 4 bytes @ address 0x20007FFC (Data = 0x00000000)

Reading 64 bytes @ address 0x20007FC0

Read 4 bytes @ address 0x00000000 (Data = 0x000007C0)

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

Einar Thorsrud — Tue, 19 Feb 2019 11:36:29 GMT

I see. Then some debugging is required:

Have you remembered to flash the SoftDevice as well as the application .hex?
Can you put a breakpoint in the beginning of the main function to verify that the application starts and you are able to debug?
...

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

saiteja — Tue, 19 Feb 2019 10:07:48 GMT

tried to change crystal frequency as

// Low frequency clock source to be used by the SoftDevice

#ifdef S210

#define NRF_CLOCK_LFCLKSRC NRF_CLOCK_LFCLKSRC_XTAL_20_PPM

#else

#define NRF_CLOCK_LFCLKSRC {.source = NRF_CLOCK_LF_SRC_RC, \

.rc_ctiv = 0, \

.rc_temp_ctiv = 0, \

.xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM}

#endif

in file location

/nRF5_SDK_12.3.0_d7731ad/components/boards/pca10028.h

still i am facing issue.

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

Einar Thorsrud — Tue, 19 Feb 2019 09:27:55 GMT

Hi,

The RF-BM-ND01 module is based on a nRF51822 chip, so you can use any SDK with support for it. The latest SDK for nRF51 is SDK 12.3, so you are using the correct SDK. A typical issue when using SDK examples with modules is that some modules does not include the optional 32.768 kHz crystal, but the SDK examples assume it is present out of the box. If that is the case, using a unmodified example will not work, as the SoftDevice will attempt to start the non-existing crystal oscillator.

Assuming this is the problem, you have to adjust the SoftDevice configuration so that it uses the internal LFRC oscillator instead. In most SDK examples, that means that you need to change the nrf_clock_lf_cfg_t instance which is passed to softdevice_handler_init(), for instance by setting it to something like this:

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_RC,              \
                                 .rc_ctiv       = 0,                                \
                                 .rc_temp_ctiv  = 0,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM}

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

saiteja — Tue, 19 Feb 2019 04:27:59 GMT

thanks for the Quick reply.

Actually, my module is RF-BM-ND01. i am able to download hex file on it. but it is not advertising at all. so is it possible to use nrf12.3 SDK for RF-BM-ND01 module?

I even tried to download s130 from SDK12.3 and downloaded BLE_app_uart example file inRF-BM-ND01, the download was successful but the application is not running(not observed any advertisements in nrf connect app).

RE: How to Program RF-BM-ND01 (nrf51822) BLE4.0

Einar Thorsrud — Mon, 18 Feb 2019 13:10:55 GMT

Hi,

There are three SoftDevice variants available for the nRF51:

S110 - peripheral only
S120 - central only
S130 - central and peripheral.

The S130 SoftDevice is the most resent and feature rich, so this is the recommended SoftDevice to use unless you are so limited in flash space that you have to use another one. SDK 12.3, which is the most recent SDK for the nRF51 targets S130 version 2.0.1.

Regarding programming there is no difference between any modules. You need to use a SWD debugger of some sort (Nordic tools support J-Link).