Problem getting started with BLE Nano 2

RE: Problem getting started with BLE Nano 2

matbli — Thu, 14 Sep 2017 14:48:52 GMT

Hi,

In the tutorial I followed it said:

FLASH_START=0x1F000 SRAM_START=0x20002000

But I se now that it was a different version of the softdevice.

Your numbers was much better, it looks like I'm flying :-)

Thanks for your help!!

/Mats

RE: Problem getting started with BLE Nano 2

Jørgen Holmefjord — Thu, 14 Sep 2017 07:02:06 GMT

Did you use the FLASH_START and SRAM_START values from the tutorial, or did you modify these number to reflect the ROM/RAM requirements of the softdevice you are using? Correct numbers for the ble_app_beacon example from SDK v14.0.0 should be:

FLASH_START=0x23000
SRAM_START=0x20001720

You can check the default FLASH and RAM settings in the linker-file (.ld), found in the armgcc directory of each example.

RE: Problem getting started with BLE Nano 2

matbli — Wed, 13 Sep 2017 21:44:34 GMT

Thank you,

Tried the SES tutorial and built the beacon example - builds fine as it seams.

Since I have a Redbear BLE NANO 2 KIT I want to program it through dropping the hex file on DAPLINK drive. Tried to merge my application hex with the softdevice, but:

mergehex -m s132_nrf52_5.0.0_softdevice.hex ble_app_beacon_pca10040_s132.hex -o application.hex Parsing input hex files. Merging files. ERROR: The hex files cannot be merged since there are conflicts.

Am I doing some thing wrong?

/Mats

RE: Problem getting started with BLE Nano 2

Jørgen Holmefjord — Wed, 13 Sep 2017 09:04:00 GMT

Hi,

If you do not want to pay the license fee for Keil, you can switch to another free compiler. We support GCC, and you can find a tutorial on developing with GCC and Eclipse here.

Another alternative is to use Segger Embedded Studio (SES). This blog post tutorial show you how to import Keil projects into SES, and how to get started with the development.

Best regards,

Jørgen