Firmware update of nPM2100 EK with the nPM PowerUP v2.2.3 fails

[timov43]

I connected the new nPM2100 EK to Linux PC and opened the nPM Power UP application.
In the app I'm able to select the EK.

The nPM Power UP tells me that "Programming required. The nPM EK firmware version does not match the required firmware version."

When I start the programming it fails and de-select the EK.

Log:
11:54:33.395 Selecting device with the serial number B47DE1947B4768A7
11:54:33.505 Selected device with the serial number B47DE1947B4768A7
11:54:33.505 Selected device with s/n B47DE1947B4768A7
11:54:33.506 Opened port with options: {"path":"/dev/ttyACM0","baudRate":115200}
11:54:33.593 Closed port: /dev/ttyACM0
11:54:55.707 Error while setting up device with the serial number B47DE1947B4768A7
11:54:55.707 "Failed with exit code 1.\nOne or more program tasks failed:\n * B47DE1947B4768A7: Error when programming through MCUBoot: Error verifying MCUBoot image prior to update. Error code: 603 (Timeout). (McubootTimeout)\n\n\nMessage: Failed, Error when programming through MCUBoot: Error verifying MCUBoot image prior to update. Error code: 603 (Timeout)."
11:54:55.707 Deselected device
11:54:55.708 Deselected device


Any idea why this is happening?

[Vidar Berg]

Hello,

I'm checking internally if we have had reports of this issue. It does not seem like a permission issue, but do you have these udev rules installed :https://github.com/NordicSemiconductor/nrf-udev?

Best regards,

Vidar

[timov43]

Yes I have:

ls -la /lib/udev/rules.d/ | grep nrf
-rw-rw-r-- 1 timo timo 493 kesä 7 2018 71-nrf.rules
-rw-rw-r-- 1 timo timo 189 kesä 7 2018 99-mm-nrf-blacklist.rules


1.
When I select the nPM2100 EK in the nPM PowerUP, the following is printed to terminal from where I have launched the AppImage

./nrfconnect-5.2.1-x86_64.AppImage
Error occurred in handler for 'serialport:is-open': Error: PORT_NOT_FOUND
at zNe (/tmp/.mount_nrfcon41xLk5/resources/app.asar/dist/main.js:650:6208)
at /tmp/.mount_nrfcon41xLk5/resources/app.asar/dist/main.js:452:6843
at WebContents.<anonymous> (node:electron/js2c/browser_init:2:86176)
at WebContents.emit (node:events:519:28)

2.
Then I refuse for FW update and start serial monitor + reset to EK.
The following is printed to the serial monitor

**> hw_version
* Booting nRF Connect SDK f6f4537b890f ***
shell:~$ hw_version
hw_version=npm2100ek_nrf5340_cpuapp,pca=10170,version=0.9.0
shell:~$ > kernel uptime
kernel uptime
Uptime: 1746 ms
shell:~$ > app_version
app_version
app_version=0.4.1+0
shell:~$ > npm_pmic_ping check
npm_pmic_ping check
Pinging PMIC succeeded
shell:~$ > npm_adc sample 500 2000
npm_adc sample 500 2000
Success: sampling state=running,sample interval=500 ms, report interval=2000 ms
[00:00:00.029,388] <inf> module_cc_sink: DAC is not available
[00:00:00.154,541] <inf> module_batt_input_detect: Battery board id: 6
[00:00:00.154,632] <wrn> module_fg: No available battery model for connected battery
[00:00:02.021,636] <inf> module_pmic_adc: vbat=3.112500,tdie=22.740000,soc=nan,vout=3.077343
[00:00:04.016,906] <inf> module_pmic_adc: vbat=3.112500,tdie=22.740000,soc=nan,vout=3.065624


3.
Then I try to do the FW update by deselecting the EK and then selecting it agin.
The following is printed to the serial monitor:

hw_version
hw_version=npm2100ek_nrf5340_cpuapp,pca=10170,version=0.9.0
[00:02:30.016,906] <inf> module_pmic_adc: vbat=3.112500,tdie=22.740000,soc=nan,vout=3.065624
[00:02:32.016,906] <inf> module_pmic_adc: vbat=3.112500,tdie=22.740000,soc=nan,vout=3.065624
[00:02:33.663,421] <err> mcumgr_stat_grp: Invalid stat name: smp_com
[00:02:34.016,906] <inf> module_pmic_adc: vbat=3.112500,tdie=22.740000,soc=nan,vout=3.065624

[Vidar Berg]

Thanks for the confirmation and additional information. The logs shows that the app is clearly able to communicate with the EK and that it's just failing on the FW update part. I asked the team about this but it does not seem like we have seen reports of this exact issue before. They also tried downgrading their EK to the same FW version in an attempt to replicate the issue:

I tried pre-programming a 0.9.0 EK with a 0.4.1+0 image (everything as they have). Got pretty much the same terminal prints and PowerUP logs (with all the errors looking similar), but the upgrade still succeeded 

 The only difference on my side is I run nrfconnect with --no-sandbox simply because sandboxing doesn't work on my system and I didn't bother to fix it. Just something to try as a potential workaround, since I'm out of ideas atm

If possible I would also suggest you try doing the update from another PC.

[timov43]

Made FW update with another PC (Xubuntu 22.04 + JLink v8.4.8)
Firmware update done without any problem.

Thanks

[Vidar Berg]

Thanks for the update. Please let us know if you encounter this update issue again.