RE: Does NRgo studo program BOOTLOADERADDR?

Hung Bui — Wed, 28 Jan 2015 12:02:20 GMT

You are correct,

When you compile with that line in the code, the compiler will add into the generated hex file at the address in "NRF_UICR_BOOT_START_ADDRESS" the value REMOTE_BOOTLOADER_ADDR.

nRFGo Studio doesn't know if the address is there or not when programming.

But when it reads there is an address in the UICR, it will display that address as the start of the bootloader.

RE: Does NRgo studo program BOOTLOADERADDR?

Charles Manning — Wed, 28 Jan 2015 03:59:26 GMT

Ok, to answer my own question...

You need to have something like the following in the code:

uint32_t m_uicr_bootloader_start_address 
    __attribute__((at(NRF_UICR_BOOT_START_ADDRESS))) = REMOTE_BOOTLOADER_ADDR;

This creates a record that ends up in the hex file for programming the UICR BOOTLOADERADDR.

It appears that when NRF studio sees this, it knows it is a bootloader.

I think it would be a good idea if NRF Studio was to warn that there is no such record in the hex file.