nrf9160 GPS problem

[MiroslavP]

Hello. I have problem with GPS example for nrf9160

I have:

Dev Board: PCA100900 0.8.5 2019.7

Source code: 

mcuboot: v1.3.99 aebd4b96d2abbeea5a3392c623369dd61ddf40cb 

nrf: v0.4.0 f9251026121264abc980a6c1e7928a802e8ab6e6

nrfxlib: v0.4.0 09bdd47ce20fd0ef0721eeb7c2eed10b5a199e0d

zephyr: v1.13.99 6c9637972f54e39640420c1e6ae096ac214c587c

Embedded  studio: 4.16

I'm use this firmware https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

Build process will be fine for GPS sample code. But after uploading the source code to the MCU, I have this output on the UART interface. 

***** Booting Zephyr OS v1.13.99-ncs1-1823-g715d2df3dd *****
Secure Boot: configure flash
Secure Boot: SPU: set region 0 as Secure
Secure Boot: SPU: set region 1 as Secure
Secure Boot: SPU: set region 2 as Secure
Secure Boot: SPU: set region 3 as Secure
Secure Boot: SPU: set region 4 as Secure
Secure Boot: SPU: set region 5 as Secure
Secure Boot: SPU: set region 6 as Secure
Secure Boot: SPU: set region 7 as Secure
Secure Boot: SPU: set Flash region 8 as Non-Secure
Secure Boot: SPU: set Flash region 9 as Non-Secure
Secure Boot: SPU: set Flash region 10 as Non-Secure
Secure Boot: SPU: set Flash region 11 as Non-Secure
Secure Boot: SPU: set Flash region 12 as Non-Secure
Secure Boot: SPU: set Flash region 13 as Non-Secure
Secure Boot: SPU: set Flash region 14 as Non-Secure
Secure Boot: SPU: set Flash region 15 as Non-Secure
Secure Boot: SPU: set Flash region 16 as Non-Secure
Secure Boot: SPU: set Flash region 17 as Non-Secure
Secure Boot: SPU: set Flash region 18 as Non-Secure
Secure Boot: SPU: set Flash region 19 as Non-Secure
Secure Boot: SPU: set Flash region 20 as Non-Secure
Secure Boot: SPU: set Flash region 21 as Non-Secure
Secure Boot: SPU: set Flash region 22 as Non-Secure
Secure Boot: SPU: set Flash region 23 as Non-Secure
Secure Boot: SPU: set Flash region 24 as Non-Secure
Secure Boot: SPU: set Flash region 25 as Non-Secure
Secure Boot: SPU: set Flash region 26 as Non-Secure
Secure Boot: SPU: set Flash region 27 as Non-Secure
Secure Boot: SPU: set Flash region 28 as Non-Secure
Secure Boot: SPU: set Flash region 29 as Non-Secure
Secure Boot: SPU: set Flash region 30 as Non-Secure
Secure Boot: SPU: set Flash region 31 as Non-Secure
Secure Boot: configure SRAM
Secure Boot: SPU: set SRAM region 0 as Secure
Secure Boot: SPU: set SRAM region 1 as Secure
Secure Boot: SPU: set SRAM region 2 as Secure
Secure Boot: SPU: set SRAM region 3 as Secure
Secure Boot: SPU: set SRAM region 4 as Secure
Secure Boot: SPU: set SRAM region 5 as Secure
Secure Boot: SPU: set SRAM region 6 as Secure
Secure Boot: SPU: set SRAM region 7 as Secure
Secure Boot: SPU: set SRAM region 8 as Non-Secure
Secure Boot: SPU: set SRAM region 9 as Non-Secure
Secure Boot: SPU: set SRAM region 10 as Non-Secure
Secure Boot: SPU: set SRAM region 11 as Non-Secure
Secure Boot: SPU: set SRAM region 12 as Non-Secure
Secure Boot: SPU: set SRAM region 13 as Non-Secure
Secure Boot: SPU: set SRAM region 14 as Non-Secure
Secure Boot: SPU: set SRAM region 15 as Non-Secure
Secure Boot: SPU: set SRAM region 16 as Non-Secure
Secure Boot: SPU: set SRAM region 17 as Non-Secure
Secure Boot: SPU: set SRAM region 18 as Non-Secure
Secure Boot: SPU: set SRAM region 19 as Non-Secure
Secure Boot: SPU: set SRAM region 20 as Non-Secure
Secure Boot: SPU: set SRAM region 21 as Non-Secure
Secure Boot: SPU: set SRAM region 22 as Non-Secure
Secure Boot: SPU: set SRAM region 23 as Non-Secure
Secure Boot: SPU: set SRAM region 24 as Non-Secure
Secure Boot: SPU: set SRAM region 25 as Non-Secure
Secure Boot: SPU: set SRAM region 26 as Non-Secure
Secure Boot: SPU: set SRAM region 27 as Non-Secure
Secure Boot: SPU: set SRAM region 28 as Non-Secure
Secure Boot: SPU: set SRAM region 29 as Non-Secure
Secure Boot: SPU: set SRAM region 30 as Non-Secure
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 2002c790
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS kitprod_w49 *****
Application started
LTE LC config ...
[00:00:00.929,809] <err> net_if.net_if_init: There is no network interface to work with!

The MCU does not send any additional data. He should send the GPS position. SIM card is insert on the slot.

[Hakon]

SIM card is insert on the slot.

 And you have registered the SIM card as well?

[MiroslavP]

Yes, SIM card is registered and working. I have two sim card, and SIM card is working on the different GSM module.

But why if I use nrf9160_pca10090ns and AT_Client example or others examples, then module jump to memmory address EFFFFFFE and stay here ? 

[Hakon]

And are you sure that you are flashing the correct .hex file? Look at this post to see how it is done in SES.

[MiroslavP]

Yes, flashing is correct. But thank you. I understand why code jump to the wrong  the memory address for non secure firmware.

But still AT_client doesn't work for me. Does not respond to any AT command, and on the serial console I have output "The AT host sample started" so, MCU is running. Only GSM modem not responding ? I do not know, but maybe I have bad firmware on the MCU ? I'm use firmware 0.7.0-29 alpha

I do not understand why modem not responding on the AT command.

[Hakon]

Try pushing the reset button and see what happens.

[MiroslavP]

MCU only send 

***** Booting Zephyr OS v1.14.99-ncs1 *****
The AT host sample started

and then does not respond to any AT command. This is for AT client sample. 

[Hakon]

Just make sure your at the right tag, by doing

cd ncs/nrf
git checkout master
git pull
git checkout v0.4.0
west update

Then run the following commands

nrfjprog -e

west build -b nrf9160_pca10090ns -d new_build123

west flash -d new_build123

from inside the at_client folder.

[MiroslavP]

I have problem with build. 

C:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client>west build -b nrf9160_pca10090ns -d new_build123
source directory: C:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client
build directory: C:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client\new_build123 (created)
BOARD: nrf9160_pca10090ns
-- Using application from 'C:/Users/Miroslav/WORK/nRF/ncs/nrf/samples/nrf9160/at_client'
Zephyr version: 1.14.99
-- Found PythonInterp: C:/Python37/python.exe (found suitable version "3.7.2", minimum required is "3.4")
-- Selected BOARD nrf9160_pca10090ns
CMake Error at C:/Users/Miroslav/WORK/nRF/ncs/zephyr/cmake/toolchain/zephyr/host-tools.cmake:26 (message):
  The file 'C:/Users/Miroslav/WORK/nRF/ncs/zephyr/sdk_version' was not found.
  Is ZEPHYR_SDK_INSTALL_DIR=C:/Users/Miroslav/WORK/nRF/ncs/zephyr
  misconfigured?
Call Stack (most recent call first):
  C:/Users/Miroslav/WORK/nRF/ncs/zephyr/cmake/host-tools.cmake:3 (include)
  C:/Users/Miroslav/WORK/nRF/ncs/zephyr/cmake/app/boilerplate.cmake:237 (include)
  CMakeLists.txt:9 (include)


-- Configuring incomplete, errors occurred!
ERROR: command exited with status 1: 'C:\Program Files\CMake\bin\cmake.EXE' '-BC:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client\new_build123' '-SC:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client' -GNinja -DBOARD=nrf9160_pca10090ns
run as "west -v build -b nrf9160_pca10090ns -d new_build123" for a stack trace

C:\Users\Miroslav\WORK\nRF\ncs\nrf\samples\nrf9160\at_client>

and I use 

set ZEPHYR_TOOLCHAIN_VARIANT=zephyr

set ZEPHYR_SDK_INSTALL_DIR=C:\Users\Miroslav\WORK\nRF\ncs\zephyr