This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 not detected by nRF Connect

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 !

Parents
  • 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?

Reply
  • 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?

Children
No Data
Related