nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Fri, 21 Apr 2017 12:46:39 GMT

That blog doesn't explain how to integrate buttonless DFU into custom application. Anyways, I got it working. Thanks for your support!

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sigurd — Fri, 21 Apr 2017 11:06:38 GMT

Great that you got it working! There is the blog post I linked to in my comment, the blog post is called "Getting started with Nordic's Secure DFU bootloader, a step by step guide". If you have any questions regarding this, or run into any problems feel free to create a new question here on Devzone.

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Thu, 20 Apr 2017 16:28:36 GMT

Got it working. I was flashing the bootloader using the 'LOAD' icon in Keil. Since Keil cannot directly write to the UICR registers, I had to use the nrfjprog command to flash the bootloader.

Now that I want to integrate DFU into my custom application, is there a step-by-step guide or a blogpost on how to do this?

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sigurd — Thu, 20 Apr 2017 12:19:17 GMT

Did the L6406E error go away? If the only problem is that it don't advertise, then try to follow the steps here: infocenter.nordicsemi.com/index.jsp

Also see the "Testing" steps here and this blog post for more informaton about Secure DFU bootloader.

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Wed, 19 Apr 2017 08:03:48 GMT

Tried those RAM settings already on the custom board and it doesn't start advertising. I also tried using the original IRAM and IROM settings on a PCA10028 and it starts advertising as "DfuTarg".

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sigurd — Wed, 19 Apr 2017 07:54:22 GMT

According to this devzone answer, you can for the bootloader_secure example for nRF51 16kB try to set the RAM settings to:

RAM start: 0x200025E0
RAM size/length: 0x1A20

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Tue, 18 Apr 2017 18:09:07 GMT

Continuing the errors due to lack of characters in the previous comment.

._build\nrf51422_xxac_s130.axf: Error: L6407E: Sections of aggregate size 0x9c bytes could not fit into .ANY selector(s).

Not enough information to list image symbols.

Not enough information to list the image map.

Finished: 2 information, 0 warning and 13 error messages.

"._build\nrf51422_xxac_s130.axf" - 13 Error(s), 0 Warning(s).

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Tue, 18 Apr 2017 18:08:44 GMT

Continuing the errors due to lack of characters in the previous comment.

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching app_util_platform.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching nrf_dfu_settings.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching nrf_dfu_flash.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching system_nrf51.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching fstorage.o(.data).

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Tue, 18 Apr 2017 18:07:35 GMT

Continuing the errors due to lack of characters in the previous comment.

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching softdevice_handler.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching nrf_dfu_flash.o(fs_data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching app_scheduler.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching nrf_ble_dfu.o(.data).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching nrf_drv_rng.o(.bss).

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Tue, 18 Apr 2017 18:06:25 GMT

That was a quick response! And thank you it worked. I tried to compile other applications like ble_app_proximity and the values of IROM and IRAM [IRAM base - 0x20001FE8 IRAM size(16 kB RAM) - 0x2018 and IROM base - 0x1B000 IROM size(256 kB Flash) - 0x25000] works perfectly fine. But, when I try to compile bootloader_secure for doing DFU with the following IROM and IRAM values, I get errors. IROM1 Start - 0x3AC00, Size - 0x5000 IRAM1 Start - 0x20002C00, Size - 0x1380

The errors are as follows:

linking... ._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching ble_conn_params.o(.bss).

._build\nrf51422_xxac_s130.axf: Error: L6406E: No space in execution regions with .ANY selector matching ble_conn_params.o(.data).

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sigurd — Tue, 18 Apr 2017 12:59:17 GMT

For the experimental_ble_app_blinky example the softdevice uses 1FE8(8168 bytes) RAM and the application with logging enabled uses 3920bytes (ZI-data + RW-data). That’s 11,8 kB RAM, so you have sufficient RAM with the nRF51 16kB RAM device for this example.

Do you have an external LF crystal(32 kHz) on your custom board? If not use the RC oscillator instead

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_RC,            \
                                 .rc_ctiv       = 16,                                \
                                 .rc_temp_ctiv  = 2,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sanjay Shreedharan — Tue, 18 Apr 2017 12:35:31 GMT

I tried the experimental_ble_app_blinky in SDK12 without making any changes to the code with the following values. IRAM base - 0x20002000 IRAM size(16 kB RAM) - 0x2000 These values didn't get it working. When I tried reducing it to IRAM base - 0x20001FE8 IRAM size(16 kB RAM) - 0x2018, then as well I don't see it working. Is the 16KB RAM on nRF51822_xxAA version sufficient to support SDK12 or SDK12 needs a minimum of 32KB RAM?

RE: nRF51822_xxaa SDK12 S130 v2.0.1 IROM and IRAM settings

Sigurd — Tue, 18 Apr 2017 09:22:27 GMT

Hi,

The IROM number is correct for S130 V2.0.1, The IRAM varies depending on how you configure the SoftDevice, how many services/characteristics you add, etc. For experimental_ble_app_blinky the default IRAM base should be 0x20001fe8 in SDK 12.1, if you add something extra to the default example, you need to increase the number.

Regarding you last question,0x20001870 did not work because this is not enough RAM for the SoftDevice to work, but when you increased it to 0x20002000 this was enough for the SoftDevice. If you enable logging in SDK 12.1 (NRF_LOG_ENABLED set to 1 in sdk_config.h) the function softdevice_enable() will print the correct RAM settings if you have not allocated enough RAM to the SoftDevice.