nRF51822 not detected by nRF Connect

RE: nRF51822 not detected by nRF Connect

bjorn-spockeli — Mon, 24 Oct 2016 14:36:39 GMT

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

RE: nRF51822 not detected by nRF Connect

Sergio — Mon, 24 Oct 2016 14:18:53 GMT

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?

RE: nRF51822 not detected by nRF Connect

bjorn-spockeli — Mon, 24 Oct 2016 09:25:33 GMT

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)

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

RE: nRF51822 not detected by nRF Connect

Sergio — Mon, 24 Oct 2016 09:08:47 GMT

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 !

RE: nRF51822 not detected by nRF Connect

bjorn-spockeli — Mon, 24 Oct 2016 08:54:52 GMT

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)

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