nRF91 DK not recognizing/flashing properly the host board through Debug Out pin

RE: nRF91 DK not recognizing/flashing properly the host board through Debug Out pin

Priyanka — Mon, 10 Jan 2022 14:09:06 GMT

Hi,

Could you try

nrfjprog --program C:/meo/application/meo_mini_firmware/build/zephyr/merged.hex --recover -f NRF91

You should be able to reprogram the device this way.

Regards,

Priyanka

RE: nRF91 DK not recognizing/flashing properly the host board through Debug Out pin

Saketaram — Thu, 06 Jan 2022 17:38:43 GMT

Hi Priyanka,

We are now working with

nRF Connect v3.9.3
SDK v1.8.0
nRF Command line v10.15.1
ToolChainManager v0.10.1
JLink v7.58b
McuBoot v1.7.1

It seems the issue stands on the mcuboot, that allowed proper functionning until last December, but didn't work anymore since January 2022 when using nRF command line: both nRF Programmer and west flash say host board was flashed but there is no RTT Viewer log on the recently flashed boards. But the previously flashed boards show the logs. And when the host board is updated through fota (with bin file from the cloud, not locally flashed) the host board also show the logs on RTT viewer for the connected board through DK.

Which version of mcuboot is compatible with the other parts which were recently upgraded? We also found this ticket on mcuboot that might be related: https://github.com/mcu-tools/mcuboot/issues/1164

What alternative do we have on mcuboot for fota. Could we use secure bootloader? Is it consistent in its performance?

Which nRF command line should we use?

Thanks for your prompt expertise.

RE: nRF91 DK not recognizing/flashing properly the host board through Debug Out pin

Priyanka — Wed, 05 Jan 2022 10:10:48 GMT

Hi,

Could you try updating the to the latest version of nRF Connect SDK v3.9.2?

I am not sure this would help, but we can troubleshoot. 🙂

Regards,

Priyanka