App does not start from bootloader when it is programmed via jlink

RE: App does not start from bootloader when it is programmed via jlink

Aravinth — Fri, 18 Nov 2016 09:52:37 GMT

That's right. It was in different place in older SDKs while the blogpost was written and it could be compiled only on Keil because of Keil ARM specific code.

RE: App does not start from bootloader when it is programmed via jlink

Aymen Rejeb — Thu, 17 Nov 2016 16:23:21 GMT

Hi Aravinth,

Sorry to tell you that, but Nordic have absolutely right ;)

Actually, I was editing the wrong file! it is not bootloader_util_arm.c as mentioned here but the bootloader_settings.c

Kind Regards

RE: App does not start from bootloader when it is programmed via jlink

Aravinth — Thu, 17 Nov 2016 14:41:08 GMT

First option was suggested by Nordic and it didn't work out for me as well because i'm compiling with GCC SDK8. I was always manually writing the bootloader setting page, that is 255th page of 256 KB ROM. So it worked out for you as well. Please mark it as a correct answer by clicking the grey circular tick next to the answer.

RE: App does not start from bootloader when it is programmed via jlink

Aymen Rejeb — Thu, 17 Nov 2016 14:31:04 GMT

Hi Aravinth,

The first option, editing the bootloader settings in bootloader_util_arm.c (m_boot_settings <== BANK_VALID_APP) doesn't work for me, the p_bootloader_settings->bank_0 flag still zero initialized! However, doing it manually worked fine! see attached screen-shots.

Please note that I'm using SDK10 on nRF51822 (256 Ko Flash /16 Ko RAM).

Do you have any other suggestions that could fix this?

Thanks.

RE: App does not start from bootloader when it is programmed via jlink

Aravinth — Thu, 17 Nov 2016 09:19:48 GMT

If my answer works for you, please mark it as a correct answer by clicking the tick.

RE: App does not start from bootloader when it is programmed via jlink

Aravinth — Wed, 16 Nov 2016 17:12:35 GMT

If you have erased the chip completely and flash everything, then you have to manually write VALID_APP after flashing. It could be done writing to bootloader settings using J-Link/nrfjprog or you can add it as a default bootloader setting in your firmware as

const uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((at(BOOTLOADER_SETTINGS_ADDRESS))) attribute((used)) = {BANK_VALID_APP};.

Have a look at this for more info.

If you flash only the firmware (bootloader and softdevice flashed separately) with --sectorerase, then bootloader setting will not be erased.

For example my bootloader settings are at 0x3fc00 and i do nrfjprog --memwr 0x3fc00 --val 0x01 -f NRF51 to booloader settings to have VALID_APP flag, if i have erased whole chip and flashed everything fresh.