nRF51822 not detected by nRF Connect

[Sergio]

Hi,

I'm trying to program a nRF51822 board following this tutorial (chisight.wordpress.com/.../) using OpenOCD in a Raspberry PI.

I have been able to burn the compilated ble_app_proximity example code (in .hex format) that the SDK contains, and in that case the nRF51822 is detected correctly by the nRF Connect iOS app. However, if I compile the main.c code contained in the same example of the SDK with Segger Embedded Studio, and I burn the .hex output in the same way that I did before, the burn is successful, but nothing is detected by the nRF Connect iOS app.

I'm using the following section placement macros:

FLASH_START=0x1C000 FLASH_SIZE=0x24000 SRAM_START=0x20000000 SRAM_SIZE=0x1800

Thanks in advance !

[bjorn-spockeli]

I think the section placement macros for the SRAM is wrong. If you're using the S110 v8.0.0, then they should be set to

SRAM_START=0x20002000 SRAM_SIZE=0x2000 (16kB RAM variant)

or

 SRAM_START=0x20002000 SRAM_SIZE=0x6000 (32kB RAM variant)

[Sergio]

Thanks so much for your response. I had a mistake while writing the tag of the question, I'm not using s110, but s130. I also think the problem is with the placement macros, but I don't know which values should I write for this softdevice. Thanks again !

[bjorn-spockeli]

Which version of the S130 are you using? And which nRF51822 variant are you using, 16kB or 32kB RAM? If you're using the S130 v2.0.0, then you should use the following settings

SRAM_START=0x20002080 SRAM_SIZE=0x1F80 (16kB RAM variant)

or

 SRAM_START=0x20002080 SRAM_SIZE=0x5F80 (32kB RAM variant)

[Sergio]

I'm using S130 v2.0.0, and the nRF51822 16 kB variant. However, if I compile with the SRAM_SIZE configured to 0x1F80 I get a RAM overflowed error, and if I compile with the SRAM_SIZE configured to 0x5F80 nothing happens when I burn the code. If I burn the compilated file contained in the SDK, it works perfect. I've tried using gcc instead of Segger but the result is the same. Could it be the flash address?

[bjorn-spockeli]

Yes, you are right, the FLASH_START should be set to 0x1B000 not 0x1C000. However, 0x1F80 is correct if you only have 16kB RAM.