Device does not reset after DFU

RE: Device does not reset after DFU

Einar Thorsrud — Mon, 14 May 2018 06:59:34 GMT

I am not aware of any other issues, but we have not done extensive testing with GCC 7. As mentioned, the latest SDK (version 15.0.0) was tested with GCC 6.3 2017-q2-update because of the LTO issue. SDK 12.3 which you are using was tested with GCC 4.9 2015q3.

RE: Device does not reset after DFU

Einar Thorsrud — Mon, 14 May 2018 06:55:40 GMT

I have not seen any issues with -flto using GCC 6, but if you don't need it to make the bootloader fit, then you could just as well not use it. More recent SDK versions do not use it by default (the flag is included in the Makefile, but on a separate line that is commented out).

RE: Device does not reset after DFU

pmantri0412 — Fri, 11 May 2018 16:37:51 GMT

Hi Einar,

Can you let me know if there are any another problems associated with GCC 7,

Thanks,

RE: Device does not reset after DFU

pmantri0412 — Fri, 11 May 2018 14:13:03 GMT

Hi, With GCC 6 should I use the -flto option or should I remove it ?

Thanks,

RE: Device does not reset after DFU

Einar Thorsrud — Fri, 11 May 2018 13:46:02 GMT

I am glad to hear that this was the issue. I recommend you stick with GCC 6 for now (SDK 15 was tested with GCC ARM Embedded 6.3 2017-q2-update).

The combination of bootloader and application is not supported. You should use two separate upgrade images instead. (You can see a list of valid combinations by calling "nrfutil pkg generate --help").

RE: Device does not reset after DFU

pmantri0412 — Fri, 11 May 2018 13:29:29 GMT

Hi Einar,

After removing the -flto option, I don't see the issue. I will test this on the other devices on which I have programmed the boot loader and see if the problem resurfaces. Thanks for your help.

On a side note do you know how I can create one .zip DFU file with both the application and the boot loader.

Thanks,

RE: Device does not reset after DFU

Einar Thorsrud — Fri, 11 May 2018 12:20:49 GMT

Hi,

We have seen some issues with GCC version 7 when link time optimization (LTO) is enabled. Are you building the bootloader with the "-flto" option? If so, can you see if removing it helps?