• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 25 subscribers
  • Views 118 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289202
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

production optimisation build

user89911

Hi Nordic,

My firmware is done and v1 beta is release, i will use it to flash my final production first batch with it.

What are the several good pratices  to create the final .hex file ( or merged because i'm using Softdevice+bootloader for dfu ota) ?

Is here a way to improve size and consumption by removing during the build the debug, SEGGER _Print or NRF_LOG message?

Thanks a lot !

  • +1

    Hi,

    It's sufficient to set NRF_LOG_ENABLED to '0' to disable everything related to logging. You should also make sure you use the "Release" build configuration. This configuration enables code optimization and limits the number of assert strings that need to be kept in flash.

    What are the several good pratices  to create the final .hex file ( or merged because i'm using Softdevice+bootloader for dfu ota) ?

    You can use mergehex to combine everything into a single hex file for production (i.e. softdevice + application + bootloader + bootloader settings page).

    Best regards,

    Vidar

  • 0 in reply to user4240

    Thanks Vidar, if NRF_LOG_ENABLED to 0 is the own tips, i'm almost good ;)

Related
Terms of service