nRF51 DK - not possible to flash files to the board

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Mon, 02 May 2016 05:59:28 GMT

Hi, Sorry for late reply, I was sick all week. If it enabled it then the DK wil be marked with "Mbed Enabled" logo, if there is not logo then it means that it did not enable it.

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Tue, 26 Apr 2016 08:11:31 GMT

Is it possible to nRF51-DK doesn't enable the mbedOS ( mbed version of 3.0 ) ?

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Wed, 20 Apr 2016 07:47:14 GMT

I just know about merging two hex files into one using the mergehex tool

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Wed, 20 Apr 2016 07:25:52 GMT

You know what the different between the generated normal-combined.hex and the normal.hex?

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Wed, 20 Apr 2016 07:09:26 GMT

If you are not using any softdevice. (LENGTH depends on your device Flash size and RAM size, below example assumes your nrf51 have 256KB flash and 32 KB RAM)

MEMORY
{
  FLASH (rx) : ORIGIN = 0x0, LENGTH = 0x40000
  RAM (rwx) :  ORIGIN = 0x20000000, LENGTH = 0x8000
}

If you are using softdevice then the ORIGIN value changes for both and its value is given in the softdevice release notes. For example the S130_nrf51_2.0.0_release notes says

The combined MBR and SoftDevice memory requirements for this version are as follows: Flash: 108 kB (0x1B000 bytes). RAM: 4.9 kB (0x13C8 bytes) (minimum required memory - actual requirements are dependent upon the configuration chosen at sd_ble_enable() time).

Then the origin value for flash and ram changes as below

FLASH LENGTH = 0x40000 - 0x1B000 = 0x25000
RAM LENGTH    = 0x8000 - 0x13C8  = 0X6C38

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1b000, LENGTH = 0x25000
  RAM (rwx) :  ORIGIN = 0x200013c8, LENGTH = 0x6c38
}

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Wed, 20 Apr 2016 06:37:22 GMT

Hello Aryan, I have one more question, that you can answered, maybe. What is the optional setting for Memory in the Linker Script?

MEMORY { FLASH (rx) : ORIGIN = ?, LENGTH = ? RAM (rwx) : ORIGIN = ?, LENGTH = ? }

I am edited this few days ago, I have a vibe about the problem is here.

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Tue, 19 Apr 2016 08:43:15 GMT

Hi Polar, I am sorry, I was not aware that mbed needed the hex to be in specific format for the mount to work. I was thinking that the device flash is enumerated as the file system and any hex file should have worked normally. This is outside my expertise so I cannot help you further. Did you try to ask this in MBED forums? We at Nordic have little or no knowledge on mbed software or debug tools.

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Tue, 19 Apr 2016 08:37:38 GMT

Made .hex by the mbed online compiler works fine. But when I try it out local with mbed yotta, i got the "CORRUPT FILE" problem again. So I think, I don't need this software to work the flashing files to the board... Any suggestion?

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Tue, 19 Apr 2016 07:52:55 GMT

Download latest Segger software. Segger software needs to be installed for this tools to work.
www.segger.com/jlink-software.html

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Tue, 19 Apr 2016 07:29:20 GMT

I got the following error meassage:

ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM. But im using Linux.

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Tue, 19 Apr 2016 06:57:32 GMT

nrfjprog -f nrf51
nrfjprog -f nrf51 --program softdevice.hex

Does this work for you without any errors? You can download nrfjprog for linux here

RE: nRF51 DK - not possible to flash files to the board

polaroi8d — Tue, 19 Apr 2016 06:54:28 GMT

Hello Aryan, What does reflash mean in your sentence?

RE: nRF51 DK - not possible to flash files to the board

Susheel Nuguru — Mon, 18 Apr 2016 10:50:06 GMT

Hi, Are you able to reflash to the chip? I have not heard about this before probably some issue with Segger driver?