Modem shell hex file is not valid

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Fri, 30 Jul 2021 10:03:31 GMT

Hello Vishal,

I’m unfortunately not able to compile the Modem Shell application with all its features and MCU bootloader enabled, as this exceeds the memory limit of the Thingy:91.

Could you please let me know which features you need?

Thanks and regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Thu, 29 Jul 2021 13:15:58 GMT

Yes , please provide that application.

I guess that might help us out.

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Thu, 29 Jul 2021 13:08:17 GMT

Hello Vishal,

now I messed things up a little bit. My very apologies for that!

Of course, there is an MCUboot image available, located in ../img_fota_dfu_hex/debugthingy91_asset_tracker_debug_nbiot_legacy_pco_2021-06-28_7a076c22.hex.

I set my Thingy91 into boot mode, choose the Thingy:91 in the Programmer Tool and selected the above-mentioned file:

Initiated the download by pressing the “Write” button

Download started.

And finished successfully.

In LTE Link Monitor I can confirm that the firmware image is starting up.

By the way: there is a Modem Shell application available now, but we do not provide an official application image for that. If you would like, I can prepare one for you Thingy:91.

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Thu, 29 Jul 2021 11:56:55 GMT

Hi Markus ,

We actually aren't using nrf Devkit we're using thingy 91 and i guess we don't have one so is there any other option to enable the logs.

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Thu, 29 Jul 2021 11:45:12 GMT

Hello Vishal,

[quote user="VishalGujela"]Will you please tell me the procedure that you followed while flashing the image and what you did before and after flashing it it.[/quote]

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

RE: Modem shell hex file is not valid

VishalGujela — Thu, 29 Jul 2021 10:39:38 GMT

Hey Markus ,

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

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Thu, 29 Jul 2021 08:55:16 GMT

Hello Vishal,

I have tested the image on my Thingy:91, and I can not reproduce the issue you are facing. Could you provide me with a log?

Thanks and regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Wed, 28 Jul 2021 07:01:43 GMT

Hello Markus ,

As you guided in previous reply i did the same i flashed that image but after that the device is stopped responding it's stuck on "at+cfun?"

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Wed, 21 Jul 2021 13:02:44 GMT

Hello Vishal,

could you please flash the image:

img_fota_dfu_hex/debug/thingy91_asset_tracker_debug_nbiot_legacy_pco_2021-06-28_7a076c22.hex

and check if that makes any difference?

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Wed, 21 Jul 2021 05:00:15 GMT

Thank You for your support Markus now we are able to register our thingy 91 on NBIOT network but, during the attach process we're not able to capture the eNODEB to UE or vice versa logs .

Please help us out

Regads,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Tue, 20 Jul 2021 11:24:36 GMT

Hello Vishal,

thanks for the explanation!

Are you facing this issue in Tera Term only, or is this something you can reproduce with for instance the LTE Link Monitor as well?

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Sat, 17 Jul 2021 04:38:20 GMT

Yes, i flashed the image that you are mentioning .

And i am using this (mfw_nrf9160_1.3.0) firmware .

After configuring or completing these steps i started tera term for serial port configurations then i got the errors or messages i mentioned above..

Reagrds,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Fri, 16 Jul 2021 13:24:14 GMT

Hello Vishal,

I’m very sorry, but I have trouble following what you are doing.

So, you have successfully flashed the img_fota_dfu_hex/thingy91_asset_tracker_nbiot_legacy_pco_2021-06-28_7a076c22.hex, right?

What modem firmware is your device currently operating with, then?

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Fri, 16 Jul 2021 11:42:30 GMT

Actually i was able to boot the device finally but the issue that i am facing now is that i'm not been able to configure the Thingy 91 from tera term .

The error that i was receiving is :

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Fri, 16 Jul 2021 11:16:33 GMT

[quote user="VishalGujela"]The file with all the binaries are located on desktop[/quote]

Which folder are the binaries located in? As you can read in the CONTEXT.txt, the image from the right folder has to be choosen:

Folder contents:

img_app_bl/

- Full application images including bootloader.
- These files can be used with:
- nRF Connect Programmer (only with SEGGER J-Link or another debug probe)
- nrfjprog CLI

img_fota_dfu_hex/

- These images contain only application and bootloader is not included.
- Images are in HEX format.
- These files can be used with nRF Connect Programmer (only via USB bootloader).

img_fota_dfu_bin/

- These images contain only application and bootloader is not included.
- Images are in binary format.
- These files can be used with:
- Over-the-air update, for example, via nRF Cloud, Azure or AWS.
- mcumgr CLI (via USB bootloader only)

The following folders contain images configured for modem debugging:

- img_app_bl/debug
- img_fota_dfu_hex/debug
- img_fota_dfu_bin/debug

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Fri, 16 Jul 2021 03:53:50 GMT

Yes , I followed the steps mentioned in guide .

The file with all the binaries are located on desktop

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Thu, 15 Jul 2021 13:32:20 GMT

Are you performing the steps described in this guide when trying to update the firmware image?

In which folder is the image your are trying to flash located?

Regards,

Markus

RE: Modem shell hex file is not valid

VishalGujela — Thu, 15 Jul 2021 11:08:41 GMT

Hello,

I've used the provided hex file from your source file (thingy91_asset_tracker_nbiot_legacy_pco_2021-06-28_7a076c22) but still the UI is showing that ue is not in mcu boot mode and try again please help me out or put a light on that mcu boot mode method .

Regards,

Vishal

RE: Modem shell hex file is not valid

Albrecht Markus Schellenberger — Wed, 14 Jul 2021 12:47:10 GMT

Hello,

I assume that the files are build without native MCUboot support. So you have to flash them using an external debug probe, like the nRF9160 DK.

Regards,

Markus