I have the nRF9160 DK and I've been able to program it without problems using Visual Studio Code by simply clicking the 'Flash' option in the 'ACTIONS' side menu. The problem is that I don't actually know what happens when I do that; is it strictly done using SWD interface? What has me a bit confused is that each reset cycle results in "*** Booting nRF Connect SDK v2.5.0 ***" being spit out the console UART, so I assume mcuboot came pre-flashed in the nRF9160 (starting at flash address 0) on the DevKit? Does the 'zephyr,code-partiton' section in the 'chosen' node of the board .dts file tell both the linker and the flash programmer where to write compiled binaries (when the 'Flash' menu is clicked)? In nrf9160dk_nrf9160_common.dtsi, slot0_ns_partition and slot0_partition have different addresses; does that mean that the pre-programmed MCUBOOT knows to look in both of these locations (0x10000 and 0x50000, plus secondary image locations 0x80000 and 0xc0000?) when it's searching for valid application code after reset? Finally (for now), if we only ever use SWD interface for programming flash, i.e. no over-the-air firmware update, is it okay to only define a slot0_partition in the flash0 section, i.e. can we get rid of the slot1_partition? And do we need partitions for both slot0_partition and slot0_ns_partition if all our code is nonsecure? And finally finally (for now), is there a reason why the secure image size partition is 0x40000 (256K) and the non-secure partition size is only 0x30000 (192K)? Or are those just example values to allow for 4 application images plus mcuboot within the 1 MB total flash space?
Thanks in advance.
