Modem shell hex file is not valid

[VishalGujela]

Hi 

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

1. We used 'carrier_deploy_e7f4d5d4-f607-43a6-b383-cfdb6d725c82.zip' to flash SW in secure boot mode.
2. 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.

[VishalGujela]

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

[Albrecht Markus Schellenberger]

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

[VishalGujela]

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

[Albrecht Markus Schellenberger]

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

[VishalGujela]

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