Programming 3rd-Party nRF51822

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Tue, 14 Aug 2018 07:49:34 GMT

Hi,

If you take an untouched example, for instance ble_app_hrs, then do the following alterations:

1. Change the IRAM1 size from 0x5800 to 0x1800

2. Set the LFCLK to RC oscillator: SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_8000MS_CALIBRATION, NULL);

3. compile and load the firmware.

Do you still have issues?

If yes; try to erase the whole chip (nrfjprog -e) and reprogram the S130 softdevice v1.0 (This is the version used in SDK v10), then load your program again.

Still have issues? Enter debug mode in Keil, and see where it stops.

Kind regards,

Håkon

RE: Programming 3rd-Party nRF51822

Lu — Wed, 08 Aug 2018 22:29:31 GMT

Okay, so I tried many things now.. The RAM size seems to not be the problem.
I use the P09 now to get some Messages via UART out. So this is working and the code
does not stuck somewhere.
In my Opinion there is a problem about the clock, so here is what I did:

In the SDK_config:
#define CLOCK_CONFIG_XTAL_FREQ 255
#define CLOCK_CONFIG_LF_SRC 0

In this post (devzone.nordicsemi.com/.../16578 I read about HF Clock not working so I tried whats said there:

NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while (NRF_CLOCK->EVENTS_HFCLKSTARTED == 0)
{
// Wait for started event to occur. Note: will spin forever if crystal isnt working
__NOP();
}

So before I call that the HFCLKSTAT is 0x00010000, and after 0x00010001 like mentioned in the post,

but in a Bluetooth Scan I can still not see the device...

Any suggestions anymore?

Thank you for your help!

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Fri, 03 Aug 2018 13:55:12 GMT

The RAM length should be 0x1800, as the softdevice uses 0x2800 (0x4000 - 0x2800 = 0x1800). I suspect you're running out of RAM, which will cause a HardFault in the CPU.

RE: Programming 3rd-Party nRF51822

Lu — Fri, 03 Aug 2018 13:00:23 GMT

Yes I left the Flash the same and for RAM I changed the Lenght to 0x4000.

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Fri, 03 Aug 2018 07:33:46 GMT

Did you accommodate for the RAM size being smaller on your device? Your current device has 16k of RAM while examples assume it is the 32k RAM variant of the nRF51822 (QFAC)

RE: Programming 3rd-Party nRF51822

Lu — Thu, 02 Aug 2018 14:46:06 GMT

There are no errors or stucks.. But even with the XTAL-Clock it does not stuck. I guess there is something basicly wrong.

Complete erase did not work either..

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Thu, 02 Aug 2018 07:27:55 GMT

Where is the device stuck if you enter debug mode? It should be able to get past the SOFTDEVICE_HANDLER_INIT(..) with that input.

Try running from a "clean slate", by issuing a "nrfjprog -e" from command line.

After that, flash the softdevice ("nrfjprog --program <path/to/softdevice_s130...hex>"), then the application.

Best regards,

Håkon

RE: Programming 3rd-Party nRF51822

Lu — Wed, 01 Aug 2018 17:16:01 GMT

Im sorry, I really dont get the mistake fixed..

I tried your code, it didnt compile, so I search for the definitions of the oscillators and used it like this:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, NULL);

It compiles and I can flash, but it is the same as before, no errors but I cannot see the device in a bluetooth scan.

I was using the Keil, so I will show you my settings, maybe you can see the mistake directly..

Due to the cheap china hardware, I cannot find a good Documentation, but I guess the xtal on the board is 13,56MHz. With this setting it was not working either.

This ist SDK10 now, with S130 v1.0.0

Thank you for the previous help!

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Wed, 01 Aug 2018 08:40:28 GMT

In any ble_app_* example, there shall be a ble_stack_init() function, where you can initialize the softdevice with the clock configuration.

Use the below shown configuration for "clock_lf_cfg", and it shall use the 32k RC oscillator instead of the external one.

Cheers,

Håkon

RE: Programming 3rd-Party nRF51822

Lu — Tue, 31 Jul 2018 15:32:08 GMT

So just in the main.c of the Example-Project, I want to use?

Thank you very much for your help!

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Tue, 31 Jul 2018 12:04:20 GMT

Sorry, that is my fault! In newer SDKs, you can change this in a sdk_config.h file, while in older SDKs, you can explicitly set it, like the code snippet I showed in my previous reply.

RE: Programming 3rd-Party nRF51822

Lu — Mon, 30 Jul 2018 14:18:45 GMT

Sorry for the studip question, but I dont know where to put the code snipped.. Im not finding an sdk_config in my SDK folder..

RE: Programming 3rd-Party nRF51822

Lu — Mon, 30 Jul 2018 12:25:25 GMT

Thank you very much, I will try this!

RE: Programming 3rd-Party nRF51822

Håkon Alseth — Mon, 30 Jul 2018 09:25:34 GMT

Hi,

This module normally does not have an external 32k xtal mounted, so you'll need to adjust this in your sdk_config.h (for SDK 12 and newer) to use the 32kHz internal RC oscillator instead.

I assume you're using SDK 12.3 or older? Then you do not have to go through the config file. Here's a snippet that should be placed in ble_stack_init that will use the RC osc instead of the external xtal:

    nrf_clock_lf_cfg_t clock_lf_cfg = 
    {
        .source        = NRF_CLOCK_LF_SRC_RC,
        .rc_ctiv       = 16,                                
        .rc_temp_ctiv  = 2,                                
    };    

    // Initialize SoftDevice.
    SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL);

Another thing you have to think about is to alter the linker script to accommodate to the RAM size of your nRF51822 device (subtract 0x4000), but it looks like you already have thought about this.

Kind regards,

Håkon

RE: Programming 3rd-Party nRF51822

Lu — Mon, 30 Jul 2018 01:10:34 GMT

Im Student, so I dont have that much knowledge.. but I am using the PCA10018 as JLink Debugger, dont I?

And I guess there is no line of code that is failing, because in the linux terminal via make-command everything executes like it should.

And as you can see, I could flash the SoftDevice perfectly..

RE: Programming 3rd-Party nRF51822

Turbo J — Thu, 26 Jul 2018 21:22:05 GMT

You need a j-link to actually see this dialog. That is all you need for actual debugging hardware. Setup the IDE of your choice and check which line of code is failing.