We received the nRF9160DK that included default firmware for the Asset Tracker v2. The default version appears to be an older version of the application.
We built the latest version of Asset Tracker v2 from the nRF Connect SDK v2.0.0. The build is successful. When we flash it to the nRF9160DK, we are required to do a full erase because of UICR changes. Upon reset, we see the bootloader logs, then it attempts to jump to the first image slot, but it does not run after that. The startup log is shown below.
Are we missing something to set or clear a security issue that is left over from the previous version?
*** Booting Zephyr OS build v3.0.99-ncs1 ***{0D}{0A} Attempting to boot slot 0.{0D}{0D}{0A} Attempting to boot from address 0x8200.{0D}{0A} {0D}Verifying signature against key 0.{0D}{0A} {0D}Hash: 0x27...2d{0D}{0D}{0A} Firmware signature verified.{0D}{0A} {0D}Firmware version 1{0D}{0D}{0A} Booting (0x8200).{0D}{0D}*** Booting Zephyr OS build v3.0.99-ncs1 ***{0D}{0A} I: Starting bootloader{0D}{0A} I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3{0D}{0A} I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3{0D}{0A} I: Boot source: none{0D}{0A} I: Swap type: none{0D}{0A} I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3{0D}{0A} I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3{0D}{0A} I: Boot source: none{0D}{0A} I: Swap type: none{0D}{0A} I: Bootloader chainload address offset: 0x28000{0D}{0A} I: Jumping to the first image slot{0D}
