I don't have much to add other than that I get the exact same results and I would love to know what's going on. I updated all the repos in the nRF Connect SDK to latest, built this with the following command line, and flashed to the board with "ninja flash".
I have figured out what needs to be done, more or less, to get the asset_tracker and the at_client apps running properly on the DK. In a nutshell, the SPM example, and the asset_tracker application, must be built and loaded separately. To do this, edit proj.conf and add CONFIG_SPM=n
Here's why:
The merged asset_tracker, which is the default type of executable built, and what is loaded with ninja flash, contains an asset tracker binary that is located at flash address 0x8000, but the SPM that is also built and merged into it is likely not jumping to that location (probably to 0x40000, see below).
In the "unmerged" asset tracker build (when CONFIG_SPM=n is set), the binary is located not at 0x8000, but at 0x40000. Hmmm, that is interesting.
When the samples/nrf9160/spm project is built (with -DBOARD=nrf9160_pca10090), then loaded with ninja load, then the "unmerged" asset tracker is built and also loaded with ninja load, it all works. Finally. Make sure you build the spm project with the secure board nrf9160_pca10090, and the asset_tracker project with the non-secure board.
I have figured out what needs to be done, more or less, to get the asset_tracker and the at_client apps running properly on the DK. In a nutshell, the SPM example, and the asset_tracker application, must be built and loaded separately. To do this, edit proj.conf and add CONFIG_SPM=n
Here's why:
The merged asset_tracker, which is the default type of executable built, and what is loaded with ninja flash, contains an asset tracker binary that is located at flash address 0x8000, but the SPM that is also built and merged into it is likely not jumping to that location (probably to 0x40000, see below).
In the "unmerged" asset tracker build (when CONFIG_SPM=n is set), the binary is located not at 0x8000, but at 0x40000. Hmmm, that is interesting.
When the samples/nrf9160/spm project is built (with -DBOARD=nrf9160_pca10090), then loaded with ninja load, then the "unmerged" asset tracker is built and also loaded with ninja load, it all works. Finally. Make sure you build the spm project with the secure board nrf9160_pca10090, and the asset_tracker project with the non-secure board.
