Update the modem firmware over USB?

AchimKraus

Using USB to flash the Arm Cortex33 works well. Also using Jlink.
But I’m struggling to update the modem-firmware itself over USB. I was used to nRF Connect for Desktop / Programmer for that. But this doesn’t recognize the CP2102 chip. It works with the jlink, but using USB would make it easier.
Does anyone have an idea, if this is possible?
(I also asked in the Nordic DevZone, https://devzone.nordicsemi.com/f/nordic-q-a/96411/nrf-connect-for-desktop---programmer-v3-0-4-support-for-nrf9160-using-other-usb-chips )

jaredwolff

AchimKraus ut this doesn’t recognize the CP2102 chip

There should be an option in nRF Connect for Desktop to show all hidden devices. I committed it so I know it’s there. 😉

https://docs.jaredwolff.com/nrf9160-nrf-connect-desktop.html?highlight=nrf%20connect#using-with-lte-link-monitor

Also, I’m not sure if you tried, but to update the MFW via USB-to-serial you’ll need to follow the steps here: https://docs.jaredwolff.com/nrf9160-managing-mfw.html?highlight=upgrade%20mo#modem-firmware-update-over-uart

AchimKraus

Thanks!
The LTE Link Monitor works.
But the Programmer v3.0.4 reports:

10:34:03.877 Using nrf-device-lib-js version: 0.4.13
10:34:03.877 Using nrf-device-lib version: 0.12.8
10:34:03.877 Using nrfjprog DLL version: 10.16.0
10:34:03.877 Using JLink version: JLink_V7.66a
10:34:06.245 Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.
10:34:06.245 Please make sure J-Link Software and nrf-udev are installed. See https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/#macos-and-linux

I didn’t try you instructions in your link. FMPOV, it will be much easier, if that “Programmer” would work. I will try to spend next week some time in testing the hints I got from Nordic.

jaredwolff

What “Programmer” are you referring to? The one in nRF Connect for Desktop? That would only work if you connect a Tag Connect + nRF53/nRF91 Development kit. You’ll have to refer to the second link I provided if you want to update the modem firmware without a programmer/Tag Connect cable.

AchimKraus

What “Programmer” are you referring to? The one in nRF Connect for Desktop?

Yes

That would only work if you connect a Tag Connect + nRF53/nRF91 Development kit.

If it doesn’t work with the USB serial, JLink will be the way to go. The question for me is more, why will it not work. AFAIK it works via USB serial for the Thingy:91.

jaredwolff

If it doesn’t work with the USB serial, JLink will be the way to go. The question for me is more, why will it not work. AFAIK it works via USB serial for the Thingy:91.

It works with these instructions. Have you tried them?

AchimKraus

Hi Jared,

no, I didn’t tried it.
For me one important precondition is to use not too many different tools/tool-chains. The issue with that is, if you want to “delegate” tasks to others, including users, it must be simple and easy. I plan to build some PoC devices for agriculture, and I consider it important, that such users have a chance to apply update “over the wire”. The installation of the “nRF Connect for Desktop” is easy and the usage of the “Programmer” app as well. I don’t think, that installing python scripts from the CLI is a way to got for that. Maybe it fails, then I know, that I should use tester rather “nearby”.

jaredwolff

Got it.

I guess it’s not clear who is actually doing the update? If it’s for you in a single one-off situation, I’d still recommend the procedure I sent since you don’t need a programmer. If you do have a compatible programmer (nRF91DK or an updated nRF53) they can updated the MFW if you have a Tag Connect (TC2030-CTX-NL)

If it’s something whereas you are having many people or end users facilitate an update, I would suggest looking at the code in the mfw_update project to see how Nordic facilitates MFW updates through different means. That means you may need to build your own solution or get in touch with Nordic on how they recommend MFW updates over the air or over the wire.

In any case, I typically keep the MFW and SDK static for as long as feasible and only change when it relates to a bug fix. It could introduce many headaches if you update the MFW and it’s not supported by the SDK version you’re using.

This compatibility matrix is handy and a great reference in regards to that:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcomp_matrix_nrf9160%2FCOMP%2Fnrf9160%2Fnrf9160_modem_fw.html

AchimKraus

Just to complete:
The approach using the RF Connect for Desktop / Programmer doesn’t work for now. It seems to require more work by Nordic. Not sure, if that will get done at all.
The approach developed by Jared https://docs.jaredwolff.com/nrf9160-managing-mfw.html?highlight=upgrade%20mo#modem-firmware-update-over-uart works. But I’m afraid, that this is only possible in a development environment. We will see …