I'm having trouble starting my application after power cycling after flashing it with the DFU app.

[mosi]

I'm having trouble starting my application after power cycling after flashing it with the DFU app.

I started nRFgo Studio. Erased the chip. Programmed the SoftDevice (s130_nrf51_2.0.0_softdevice.hex). Programmed the bootloader.

Now the bootloader is activated.

I sent my application to the board with the nRF Toolbox DFU app on my Iphone. All went well.

My application started. My application works.

Then I power cycled the board.

Now trouble

My application does not start and the bootloader does not start.

I restarted nRFgo Studio and verify the application against my application hex file and I also verify the SoftDevice. Both verify successfully.

There is no way to verify the bootloader against the hex-file? What if my application destroys the bootloader?

What could be the error?

The application has functioned without problems together with S130 V2.0.0 SoftDevice before when I didn't use a bootloader. I have made no changes to the application.

This is my Linker script:

/* Linker script to configure memory regions. */

SEARCH_DIR(.)
GROUP(-lgcc -lc -lnosys)

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1b000, LENGTH = 0x21000
  RAM (rwx) :  ORIGIN = 0x20001FE8, LENGTH = 0x6018
}

SECTIONS
{
  .fs_data :
  {
    PROVIDE(__start_fs_data = .);
    KEEP(*(.fs_data))
    PROVIDE(__stop_fs_data = .);
  } > RAM
} INSERT AFTER .data;

INCLUDE "nrf5x_common.ld"

Could it be my App Data that corrupts the DFU bootloader? Where is the App data memory region defined?

[mosi]

Resolved. I had not included all compiler and linker flags into my ecplise project (I'm not using the makefile). I looked at the makefile and included all missing flags. Now the bootloader works fine.