Hi We are trying to configure Nordic UE (NRF9160) at our local setup. In order to flash software we performed following steps: We used ' carrier_deploy_e7f4d5d4-f607-43a6-b383-cfdb6d725c82.zip ' to flash SW in secure boot mode. We used ' mosh_nrf9160dk_modem_uart_trace_v104.hex ' to install modem shell application Can you suggest what step is wrong at our end. If we are using wrong firmware files, then can you please share the required one. We took reference from file 'nRF9160_External_Test_tools_Flashing_and_USB_Modem_Tracing.pdf' (attaching for reference) to flash the SW in Nordic UE.. Thanks.

This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Modem shell hex file is not valid

We are trying to configure Nordic UE (NRF9160) at our local setup. In order to flash software we performed following steps:

We used 'carrier_deploy_e7f4d5d4-f607-43a6-b383-cfdb6d725c82.zip' to flash SW in secure boot mode.
We used 'mosh_nrf9160dk_modem_uart_trace_v104.hex' to install modem shell application

Can you suggest what step is wrong at our end. If we are using wrong firmware files, then can you please share the required one.

We took reference from file 'nRF9160_External_Test_tools_Flashing_and_USB_Modem_Tracing.pdf' (attaching for reference) to flash the SW in Nordic UE..

Thanks.

Parents

0 Albrecht Markus Schellenberger over 4 years ago

Hello Vishal,

VishalGujela said:
Will you please tell me the procedure that you followed while flashing the image and what you did before and after flashing it it.

Sure.

Since the debug image does not support MCUboot DFU, see picture below:

I flashed the application image to the Thingy:91 using my nRF9160 DK instead:

2021-07-29T11:32:48.336Z INFO Application data folder: C:\Users\marku\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-07-29T11:32:48.390Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-07-29T11:32:48.391Z DEBUG App path: C:\Users\marku\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-07-29T11:32:48.391Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-07-29T11:32:48.391Z DEBUG nRFConnect path: C:\Users\marku\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-07-29T11:32:48.391Z DEBUG HomeDir: C:\Users\marku
2021-07-29T11:32:48.391Z DEBUG TmpDir: C:\Users\marku\AppData\Local\Temp
2021-07-29T11:32:48.400Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-07-29T11:32:51.712Z INFO Using nrfjprog to communicate with target
2021-07-29T11:32:52.150Z INFO Using J-Link Software version 6.88
2021-07-29T11:32:52.761Z INFO Segger serial:  960053486
2021-07-29T11:32:52.761Z INFO Segger speed:  2000  kHz
2021-07-29T11:32:52.761Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Feb  2 2021 16:48:58
2021-07-29T11:32:52.883Z INFO Core probed: 960053486
2021-07-29T11:32:52.883Z INFO Core RAM: 256KiB
2021-07-29T11:32:52.883Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-07-29T11:32:53.120Z INFO Model: NRF9160_xxAA_REV2.
2021-07-29T11:32:53.555Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-07-29T11:32:54.131Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-07-29T11:33:07.475Z INFO Parsing HEX file:  C:\Users\marku\Downloads\thingy91_fw_2021-06-28_7a076c22\img_app_bl\debug\thingy91_asset_tracker_debug_nbiot_legacy_pco_2021-06-28_7a076c22.hex
2021-07-29T11:33:07.485Z INFO File was last modified at  28.6.2021, 14:47:40
2021-07-29T11:33:31.182Z INFO Recovery procedure finished
2021-07-29T11:33:31.186Z INFO Using nrfjprog to communicate with target
2021-07-29T11:33:31.628Z INFO Using J-Link Software version 6.88
2021-07-29T11:33:32.254Z INFO Segger serial:  960053486
2021-07-29T11:33:32.255Z INFO Segger speed:  2000  kHz
2021-07-29T11:33:32.255Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Feb  2 2021 16:48:58
2021-07-29T11:33:32.255Z INFO Core probed: 960053486
2021-07-29T11:33:32.255Z INFO Core RAM: 256KiB
2021-07-29T11:33:32.255Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-07-29T11:33:32.489Z INFO Model: NRF9160_xxAA_REV2.
2021-07-29T11:33:32.934Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-07-29T11:33:33.503Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-07-29T11:33:33.616Z INFO Writing procedure starts for core0
2021-07-29T11:33:51.248Z INFO Write procedure finished
2021-07-29T11:33:51.250Z INFO Using nrfjprog to communicate with target
2021-07-29T11:33:51.686Z INFO Using J-Link Software version 6.88
2021-07-29T11:33:52.314Z INFO Segger serial:  960053486
2021-07-29T11:33:52.314Z INFO Segger speed:  2000  kHz
2021-07-29T11:33:52.314Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Feb  2 2021 16:48:58
2021-07-29T11:33:52.314Z INFO Core probed: 960053486
2021-07-29T11:33:52.314Z INFO Core RAM: 256KiB
2021-07-29T11:33:52.314Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-07-29T11:33:52.544Z INFO Model: NRF9160_xxAA_REV2.
2021-07-29T11:33:52.983Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-07-29T11:33:53.564Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.

In LTE Link Monitor, i unchecked “Automatic requests”.
Then I rebooted my Thingy:91 via this terminal command:

And got the output shown below (connection attempt fails on my Thingy:91 since SIM card does not support NB-IoT.)

Regards,

Markus

Reply