• State Not Answered
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 1147 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 230214
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf52 does not reset after DFU

chaitz

Hi,

From this link https://devzone.nordicsemi.com/f/nordic-q-a/34224/device-does-not-reset-after-dfu I understand that the compiler option flto caused reset issues. Is this still an issue and is this a problem with nRF52832 too?

Apologies for starting a similar thread. But the above is over a year old and on a different processor.

Parents
  • 0

    Which SDK version are you using?

    The Link Time Optimization(LTO) issue occured when using a GCC version that was not production tested with the nRF5 SDK, e.g. using GCC ARM Embedded 7 instead of GCC ARM Embedded 6.3. We also do not see any issues with LTO when using the correct GCC version. 

    The latest SDK(v15.3.0) has been production tested with GCC ARM Embedded 7.2018q2.update and as far as I know we have not seen any issues with enabling LTO when compiling the SDK examples. 

    Best regards

    Bjørn

Reply
  • 0

    Which SDK version are you using?

    The Link Time Optimization(LTO) issue occured when using a GCC version that was not production tested with the nRF5 SDK, e.g. using GCC ARM Embedded 7 instead of GCC ARM Embedded 6.3. We also do not see any issues with LTO when using the correct GCC version. 

    The latest SDK(v15.3.0) has been production tested with GCC ARM Embedded 7.2018q2.update and as far as I know we have not seen any issues with enabling LTO when compiling the SDK examples. 

    Best regards

    Bjørn

Children
No Data
Related
Terms of service