nrf9160 can't jump (Secure Boot: prepare to jump to Non-Secure image)

[SuperAbe]

Hello,

I have a custom nrf9160 device which requires  

device stops at:

'Secure Boot: prepare to jump to Non-Secure image'

if I use this the following prj.conf:

CONFIG_BSD_LIBRARY=y
CONFIG_BSD_LIBRARY_TRACE_ENABLED=y
CONFIG_GPIO=n
CONFIG_STDOUT_CONSOLE=y
CONFIG_AT_HOST_LIBRARY=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_NETWORKING=y
CONFIG_NET_BUF_USER_DATA_SIZE=1
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_NET_RAW_MODE=y
CONFIG_LOG=n
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_HEAP_MEM_POOL_SIZE=1024

#Custom config
CONFIG_SERIAL=y
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_0_NRF_UARTE=y
CONFIG_UART_1_NRF_UARTE=y

# SPI
CONFIG_SPI=y
CONFIG_SPI_2=y
CONFIG_SPI_2_NRF_SPIM=y
CONFIG_SPI_2=y
CONFIG_SPI_NRFX=y

# Enable I2C
CONFIG_I2C=y
CONFIG_I2C_NRFX=y
CONFIG_I2C_3=y
CONFIG_I2C_3_NRF_TWIM=y
CONFIG_I2C_INIT_PRIORITY=60

if I use this prj.conf (delete everything before '#Custom config'). Everything works as expected but I need MQTT.

#Custom config
CONFIG_SERIAL=y
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_0_NRF_UARTE=y
CONFIG_UART_1_NRF_UARTE=y

# SPI
CONFIG_SPI=y
CONFIG_SPI_2=y
CONFIG_SPI_2_NRF_SPIM=y
CONFIG_SPI_2=y 
CONFIG_SPI_NRFX=y

# Enable I2C
CONFIG_I2C=y
CONFIG_I2C_NRFX=y
CONFIG_I2C_3=y
CONFIG_I2C_3_NRF_TWIM=y
CONFIG_I2C_INIT_PRIORITY=60

I assume that by adding CONFIGs to prj.conf that I am creating conflicts between UART instances but I dont know if that is the case.

I am using:

UART 0 for console (debug)

UART 1 connected to uart device.

SPI 2 used for display.

I2C 3 used for i2c sensors and drivers.

Really the core of my issue is that I don't know how nrf9160 communicates with its built in modem. Does is require UART? will adding UART 2 create conflict with SPI 2? 

Thank you

[AndreasF]

Hi.

 

I assume that by adding CONFIGs to prj.conf that I am creating conflicts between UART instances but I dont know if that is the case.

 This should not be a problem, prj.conf is suppose to overwrite the other configurations.

Really the core of my issue is that I don't know how nrf9160 communicates with its built in modem. Does is require UART? will adding UART 2 create conflict with SPI 2?

 nRF9160 and the modem communicates with eachother by using the interprocessor commuication (IPC) peripheral.

Which tag are you working on, do you have the latest modem firmware?

Best regards,

Andreas

[SuperAbe]

Thank you for the quick reply.

I don't have experience with IPC yet so I will study more.

I don't know what my modem firmware version is but I assume that I need to run new firmware. How do I do that?

I am using J-Link educational with a custom PCB. My device will not show up on nrf connect but I have been using Segger Embedded Studio so far so it didn't matter to me. 

[AndreasF]

Hi.

Check that you are using the latest ncs version by running:

cd ncs/nrf
git checkout master
git pull
git checkout v1.0.0
west update

SuperAbe said:

I don't know what my modem firmware version is but I assume that I need to run new firmware. How do I do that?

Can you take a look at this answer.

The latest modem firmware on nordicsemi.com does not have the nrf9160_mdm_dfu.zip folder, but you can download that here: nrf9160_mdm_dfu.zip

So just follow from step 3 in the link above and run nrf9160_mdm_dfu --update from the folder with the latest modem (mfwnrf9160100.zip).

Best regards,

Andreas

[SuperAbe]

I fixed it here: https://devzone.nordicsemi.com/f/nordic-q-a/50475/nrf-connect-j-link-no-detection

Note: if your nrf9160 won't jump to secure boot and does not return errors seemingly for no reason. Most likely you are trying to access something in the fimware that was not uploaded. 

This error will occur if you don't have secure_boot or you don't have latest modem firmware 

May all your code run predictably and economically. Namaste.