Running nrfutil 91 modem-firmware-upgrade on Raspberry Pi,

[Elyasaf]

I want to run nrfutil 91 modem-firmware-upgrade --firmware "$FIRMWARE_PATH_1" --serial-number "$SERIAL_NUMBER" on Raspberry Pi,

unfortunately. The version that can be installed is only 5.2.0
So the commands are different. From the version 7.12 command set
I searched the ןמאקרמקא and came across the following set of commands:

nrfutil dfu serial -pkg $FIRMWARE_PATH_1 --serial-number $SERIAL_NUMBER

I found the serial number with the help of the command
nrfjprog -i
801013667
But the response for my commands

nrfutil dfu serial -pkg mfw_nrf91x1_2.0.1.zip -snr 801013667

I get:

Traceback (most recent call last):
File "/home/user/Projects/Data/nrfVevv/bin/nrfutil", line 8, in <module>
sys.exit(cli())
^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/nordicsemi/__main__.py", line 1041, in serial
do_serial(package, port, connect_delay, flow_control, packet_receipt_notification, baud_rate, serial_number, True,
File "/home/user/Projects/Data/nrfVevv/lib/python3.11/site-packages/nordicsemi/__main__.py", line 938, in do_serial
raise NordicSemiException("A device with serial number %s is not connected." % serial_number)
pc_ble_driver_py.exceptions.NordicSemiException: A device with serial number 801013667 is not connected.

I would appreciate help on how to complete the task.

Thank you very much

[JONATHAN LL]

Hi,

Are you able to use nrfjprog and reset the device? 

he version that can be installed is only 5.2.0

What is only version 5.2.0? nRFUtil or something else?


Have you followed the instructions in the docs?
https://www.nordicsemi.com/Products/Development-tools/nRF-Util/Download?lang=en#infotabs 


https://docs.nordicsemi.com/bundle/nrfutil/page/guides/installing.html#prerequisites 


Can also get latest from here: https://github.com/NordicSemiconductor/pc-nrfutil/releases 

What operating system are you running on your RPi?


You can find info on how to update the 91 series here https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_modem_9160.html 


With the device command you should be able to list all devices connected:

nrfutil device list --traits modem,jlink


Should look like this



Regards,
Jonathan

[Elyasaf]

Thank you for your response.
Because I can't send it by text, I am attaching the follow-up question in the file.

Thanks for your response.docx

[Elyasaf]

The link (which does not support ARM) ends with a link to the current version, which does not support arm architecture either.

Is there a 7.12.0 version that can run on a Raspberry Pi? 

Thanks a lot!

[JONATHAN LL]

Elyasaf said:

Is there a 7.12.0 version that can run on a Raspberry Pi? 

https://docs.nordicsemi.com/bundle/nrfutil/page/README.html#supported-operating-systems 



Currently no support

Regards,
Jonathan

[Elyasaf]

Thanks -

Now that it is clear that we cannot use the nrfutil tool,
Can you help me convert these commands from the nrfutil tool to the nrfjprog tool?

1.:

nrfutil device recover
nrfutil 91 modem-firmware-upgrade --firmware $FileName.zip --serial-number $JTagSerialNumber

2.:

nrfutil device program --firmware $FileName.hex --serial-number $JTagSerialNumber
nrfutil device reset

3.

nrfutil device recover
nrfutil 91 modem-firmware-upgrade --firmware $FileName.zip --serial-number $JTagSerialNumber
nrfutil device program --firmware $FileName.hex --serial-number $JTagSerialNumber
nrfutil device reset

Thanks!

[JONATHAN LL]

Elyasaf said:

Can you help me convert these commands from the nrfutil tool to the nrfjprog tool?

nrfutil device recover  = nrfjprog --recover

nrfutil device program --firmware $FileName.hex --serial-number $JTagSerialNumber = nrfjprog --program $FileName.hex --chiperase --verify

You can replace --recover with --chiperase, or if you allready have a empty device whitout approtect then you dont need any erase or recover, but --verify is still recommended. 

There is no direct equivalent to serial number in this way, you will use the JLINK seriell number and it is selected at when you run the command. 



nrfutil 91 modem-firmware-upgrade --firmware $FileName.zip --serial-number $JTagSerialNumber = rfjprog --program $FileName.zip --verify


nrfutil device reset = nrfjprog --reset


https://docs.nordicsemi.com/bundle/ug_nrf_cltools/page/UG/cltools/nrf_nrfjprogexe_reference.html#ariaid-title1 


Regards,
Jonathan

[Michael Kushnir]

Hey Jonathan,
I'll pick off from where Elyasaf left.
I succeeded converting all of the commands to ARM-compatible commands, except one.

nrfutil 91 imei-write --force --imei %1 --slot 1 --modem-firmware mfw_nrf91x1_2.0.1.zip --serial-number 260106008

I know there are AT commands for this that can be sent through a serial terminal but it's not relevant since my JLink doesn't support VCOM. Is there any other way to achieve it, perhaps using pynrfjprog?

I'd appreciate your assitance in this matter, thanks.

[JONATHAN LL]

Hi,

pynrfjprog will not work as it does the same as nrfjprog. So since the imei-write is not supported in nrfjprog it will not help.

I will ask internally if we have any other options.

Regards,
Jonathan

[Michael Kushnir]

Hey Jonathan,
I already solved the problem by using AT commands through an RTT client.
For any one who stumbles upon this:
 

• Burn firmware of modem shell sample that nrf connect sdk provides, you can do this in vscode with the nrf connect extension which works best and allows to build and burn right from the IDE.
• For my case I used a Jtag Edu Mini, which supports RTT Viewer by SEGGER.
• Using the commands at at+cgsn=1 and at at%imeiwrite=0,"xxxxxxxxxxxxxxx".