I am trying to compile and upload https_client onto my Thingy91. I am compiling it in bash using 'west build -b thingy91_nrf9160ns --pristine -- -DCONFIG_BOOTLOADER_MCUBOOT=y'. Compilation process shows no errors and hex files are generated:
$ ls -l build/zephyr/*.hex
-rw-r--r-- 1 ( , )_( , ) 197609 1336581 Jul 29 22:31 build/zephyr/app_moved_test_update.hex
-rw-r--r-- 1 ( , )_( , ) 197609 337726 Jul 29 22:31 build/zephyr/app_signed.hex
-rw-r--r-- 1 ( , )_( , ) 197609 342196 Jul 29 22:31 build/zephyr/app_test_update.hex
-rw-r--r-- 1 ( , )_( , ) 197609 288334 Jul 29 22:31 build/zephyr/mcuboot_primary.hex
-rw-r--r-- 1 ( , )_( , ) 197609 288334 Jul 29 22:31 build/zephyr/mcuboot_primary_app.hex
-rw-r--r-- 1 ( , )_( , ) 197609 436665 Jul 29 22:31 build/zephyr/merged.hex
-rw-r--r-- 1 ( , )_( , ) 197609 151642 Jul 29 22:31 build/zephyr/zephyr.hex
When I try to upload 'app_signed.hex' using nRF Connect v3.7.0 - Programmer v1.4.11, I am getting the below message:
I have tried compiling a few other samples, and so far have only had success with 'asset_tracker_v2'. Am I missing a critical step in compiling samples?
