DFU image with gcc optimisation bricks device

RE: DFU image with gcc optimisation bricks device

Vidar Berg — Fri, 14 Aug 2020 08:43:40 GMT

Hi,

Yes, I agree, the best solution is to upgrade to SDK 17 as long as that's an option.

Best regards,

Vidar

RE: DFU image with gcc optimisation bricks device

AndoniV — Fri, 14 Aug 2020 08:39:22 GMT

Hi Vidar, thank you for your response, I will give this a try! But seems like a better solution would be to upgrade our whole system to the latest SDK version.

Once again, much appreciated!

Andoni

RE: DFU image with gcc optimisation bricks device

Vidar Berg — Thu, 13 Aug 2020 06:29:12 GMT

Hello,

Please try replacing the nrf_bootloader_app_start_final.c->jump_to_addr() function with the new one from SDK 17.0.0 below. I'm pretty sure it will fix the problem. Our old GCC assembly implementation would break when optimization was turned off and cause the program to jump to the wrong address.

/**@brief Function that sets the stack pointer and starts executing a particular address.
 *
 * @param[in]  new_msp  The new value to set in the main stack pointer.
 * @param[in]  addr     The address to execute.
 */
void jump_to_addr(uint32_t new_msp, uint32_t addr)
{
    __set_MSP(new_msp);
    ((void (*)(void))addr)();
}

Best regards,

Vidar