SEGGER + nRF51 = no SDK?

RE: SEGGER + nRF51 = no SDK?

Don — Tue, 29 Oct 2019 19:43:45 GMT

Just found the Short-Range Guides:

Looks like a good place to start!

RE: SEGGER + nRF51 = no SDK?

Don — Tue, 29 Oct 2019 19:32:46 GMT

Yes, thank you very much.

I was able to compile it successfully. I just had to undo a change or two that I had made before. My dev kit should be here tomorrow, and I will try running it.

Is there a tutorial or blog on using the softdevice/ble stack or is it just various threads in the devzone? It looks like there's a lot to learn.

RE: SEGGER + nRF51 = no SDK?

Hung Bui — Tue, 29 Oct 2019 12:57:19 GMT

Hi Don,

I attached here a SES project for nRF51 on SDK v12.3
It's the ble_app_blinky, and doesn't use peer manager (fstorage, fds) you may need to add the segment intothumb_crt0.s as instructed in the guide.

Could you please try and let me know if it works?

devzone.nordicsemi.com/.../experimental_5F00_ble_5F00_app_5F00_blinky.zip

RE: SEGGER + nRF51 = no SDK?

Don — Mon, 28 Oct 2019 18:17:00 GMT

Hi Hung Bui,

The link suggests changing the memory map file or the memory section definitions to change RAM to SRAM. Since the project does not have a memory map file, I went to the memory sections definition and changed

FLASH1 RX 0x00000000 0x00040000;RAM1 RWX 0x20000000 0x00008000

FLASH1 RX 0x00000000 0x00040000;SRAM RWX 0x20000000 0x00008000

This caused an undefined symbol error for RAM1. So instead I edited file 3324.ses_nrf51_startup.s and changed

ldr r0, =__SRAM_segment_end__

ldr r0, =__RAM1_segment_end__

This resolved the __SRAM_segment_end__ issue.

For __data_start__, adding thumb_crt0.s to the project does not resolve the issue because this file tries to use that symbol, but does not define it. It also causes a multiple definition of _start.

I found the definition of __data_start__ in the [sdk]/components/toolchain/gcc/nrf5x_common.ld file, and it's the beginning of RAM used by the linker. Below is a snippet of that file:

__etext = .;

.data : AT (__etext)
{
__data_start__ = .;
*(vtable)
*(.data*)

. = ALIGN(4);
/* preinit data */
PROVIDE_HIDDEN (__preinit_array_start = .);
KEEP(*(.preinit_array))
PROVIDE_HIDDEN (__preinit_array_end = .);

. = ALIGN(4);
/* init data */
PROVIDE_HIDDEN (__init_array_start = .);
KEEP(*(SORT(.init_array.*)))
KEEP(*(.init_array))
PROVIDE_HIDDEN (__init_array_end = .);

. = ALIGN(4);
/* finit data */
PROVIDE_HIDDEN (__fini_array_start = .);
KEEP(*(SORT(.fini_array.*)))
KEEP(*(.fini_array))
PROVIDE_HIDDEN (__fini_array_end = .);

KEEP(*(.jcr*))
. = ALIGN(4);
/* All data end */
__data_end__ = .;

} > RAM

Is there an equivalent way to do this in SES? I would guess it goes in the SEGGER_Flash.icf file.

RE: SEGGER + nRF51 = no SDK?

Hung Bui — Mon, 28 Oct 2019 09:06:52 GMT

Hi Don,

For the __SRAM_segment_end__ you can have a look here:

https://devzone.nordicsemi.com/f/nordic-q-a/22640/ses-sdk12-2-0-undefined-reference-to-__sram_segment_end__

For the __data_start__ have you made sure you included thumb_crt0.s located C:\Program Files\SEGGER\SEGGER Embedded Studio for ARM 4.18\source ? into the project ?

I saw here a similar case, not sure you will have to implement all what the customer had to do though.

RE: SEGGER + nRF51 = no SDK?

Don — Fri, 25 Oct 2019 21:00:43 GMT

Hi Hung Bui,

Thanks for the information. I got through the process today, and it compiles, but I get two errors in the linker. There are two undefined symbols, __SRAM_segment_end__ and __data_start__.

I can't figure out where these are supposed to be defined, and I can only guess at how they should be defined.

The first symbol is used in 3324.ses_nrf51_startup.s, and the second is used near the end of softdevice_handler.c. They don't seem to be defined within the SDK.

Any idea what I should do with these?

Is it possible that it would be easier to start from a nRF52 example in SDK 16.0.0 and work backward to nRF51?

I can't really change chips because the boards are sitting on my desk waiting to be programmed.

Thanks for your help.

RE: SEGGER + nRF51 = no SDK?

Hung Bui — Fri, 25 Oct 2019 12:00:00 GMT

Hi Don,

You can have a look here: https://devzone.nordicsemi.com/f/nordic-q-a/30945/is-there-a-tutorial-about-using-segger-embedded-studio-with-sdk-12-3-0-and-nrf51822

Another customer reported that he followed the tutorial and it worked for him.

Note that for new design, we suggest to use nRF52 series.