I have a nRF9160DK board running asset_tracker_v2 on a nRF9160 custom board. V1.7.0 loads and boots fine but when I use V2.5.0 the boot fails as shown below. The only change I have made to the V2.5.0 asset_tracker_v2 code was to change the 2 lines in prj.conf that had my AWS information. This code loads fine in a nrf9160DK board but fails when I use the V2.5.0 version in the custom board. The V1.7.0 version loads in the custom board and had been running for several years. any ideas what I am doing wrong? any way to get more information on why the boot is failing? any help would be greatly appreciated. We have V1.7.0 out in the filed in many sites for years and it is working perfectly. The decision was made to upgrade to V2.5.0 so I am stuck until I can get this to boot correctly.
I noticed there are 2 new lines in the V2.5.0 code that are not in the V1.7.0 code. since these related to boot I commented them out. below are the 2 extra lines in V2.5.0 and the error message.
CONFIG_SECURE_BOOT=y
CONFIG_BUILD_S1_VARIANT=y
when I tried to build with these commented out I got the following error message.
********************************************
C:/Nordic1/v2.5.0/nrf/modules/tfm/tfm/boards/common/assert.c:16:9: note: '#pragma message:
!!!Partition alignment error!!!
The non-secure start address in pm_static.yml or generated partition.yml is: 0x1be00
which is not aligned with the SPU region size.
Refer to the documentation section 'TF-M partition alignment requirements'
for more information.
'
16 | #pragma message "\n\n!!!Partition alignment error!!!"\
| ^~~~~~~
C:/Nordic1/v2.5.0/nrf/modules/tfm/tfm/boards/common/assert.c:22:2: error: #error "TF-M non-secure start address is not aligned on SPU region size"
22 | #error "TF-M non-secure start address is not aligned on SPU region size"
| ^~~~~
ninja: build stopped: subcommand failed.
[
************************************************************************
*** Booting nRF Connect SDK v2.5.0 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0xc0...9e
Firmware signature verified.
Firmware version 1
Booting (0x8200).