Preparing software for production

[droghio]

We are in the final stages of product development and are planning to enter the first batch of production by the end of January. We have a custom board tested, software written and tested, so all that is left are the final pre-production checks.

Particularly I was wondering if there was a guide on how to harden the devices before production? I.e. how to disable debug logic, apply the lock fuses (if they exist) and general guidance for preparing for production.

[Kenneth]

Hi,

The only thing you should need to do is to enable readback protection if you don't want anyone to readback your code. This can be done by calling: nrfjprog --rbp ALL

This will write to APPROTECT in UICR:
http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/uicr.html?cp=2_1_0_13_0_61#register.APPROTECT 

Best regards,
Kenneth

[droghio]

Thanks, will this also disable RTT logging or must I do that separately?

Also in a similar vein, but possibly worth another post, we are also using the example BLE bootloader with a couple modifications. I have been using the 10040_debug build scripts for SDK 14.2. Is there anything I should look to modify in those before releasing with these? From what I could tell the only differences between the debug and non-debug scripts are enabling logging.

[Kenneth]

Typically for release you disable DEBUG define to turn off for instance RTT logging and save some current consumption. RTT logging is not possible if readback protection is enabled no. For bootloader questions I suggest a new post yes.