PAN1782 Bluetooth Module
4 Specification
Product Specification Rev. 1.0
Page 23 of 42
Locking the Device Debug Port and enabling the Access Port Protection
To ensure that the device debug port is locked during production programming and the access
port protection is enabled correctly, the following steps must be followed.
1. Use the Microcontroller Development Kit (MDK)
application development.
– If the application is based on
the application with the globally defined
ENABLE_APPROTECT
-define.
Open the project in
Segger Embedded Studio
. Set the define in
Project
options
>
Section
Code
>
Preprocessor Options
>
Preprocessor Definitions
.
– If the application is based on
nRF Connect SDK (version 1.8.0)
compile the application with the option set
CONFIG_NRF_APPROTECT_LOCK=y
, for
example in the project configuration file
prj.conf
.
nRF Command Line Tools (version 10.15.4)
Please make sure to use version 10.15.4 or later.
3. Execute
nrfjprog.exe --verify fast --sectorerase --program
application.hex
from a command line prompt to program an application HEX file:
Parsing image file.
Verifying programming.
Verified OK.
4. Execute
nrfjprog.exe --rbp ALL
from a command line prompt to enable the
access port protection:
Protected the device against read and debug. Only a
--recover, --debugreset, or --pinreset operations will work from
now on.
It is possible to disable the access port protection again using the
option
recover
, but the complete PAN1782 module is erased
including the built-in Bluetooth Device Address.
For details how to prevent this during application development, please
refer to the “PAN1782 EVB User Guide (“Bluetooth Address
Safeguard”)”.
For technical details please refer to
IN149 Informational Notice v1.1
https://infocenter.nordicsemi.com/
Once the access port protection is enabled, no further access including
debugging can be done anymore!