Secure Bootloader🔗

Introduction🔗

The PAN B611 module supports a secure bootloader chain as explained in nRF Connect SDK: Secure bootloader chain.

The implementation requires a certain amount of One-Time Programmable (OTP) memory as explained in nRF Connect SDK: nRF54L One-Time Programmable memory map for nRF Connect SDK.

However, if you use this feature in your application it clashes with the pre-programmed Bluetooth Device Address which is stored in the same location.

Validation🔗

If you are unsure if your application uses the secure bootloader chain, you can check if the file sysbuild.conf exists in your project space and if it contains the line SB_CONFIG_SECURE_BOOT_APPCORE=y.

If the file does not exist or the line is not included in it, your application does not use the secure bootloader chain and you don't need to do anything.

Solution🔗

If your application uses the secure bootloader chain, you can change the configuration of your application to have consideration for the pre-programmed Bluetooth Device Address.

Create the file pm_static.yml and add the following contents to the file.
pm_static.yml
```
panasonic:
  address: 0xffd500
  end_address: 0xffd508
  region: otp
  size: 0x08
```
This configuration reserves the first 8 bytes of the OTP memory and prevents the application from using it.