Flashing issues

RE: Flashing issues

captionaesthetic — Sat, 15 Jul 2023 05:00:13 GMT

I think is:
- Same warnings if I hit Erase and Flash to the board.
- I program nrf5340-DK custom boards.

RE: Flashing issues

salvatoreglenn — Fri, 21 Apr 2023 03:23:22 GMT

I think is:
- Same warnings if I hit Erase and Flash to the board.
- I program nrf5340-DK custom boards.
- It may happen after recovery regardless of application.

drift hunters

RE: Flashing issues

Edvin — Mon, 04 Jul 2022 13:39:08 GMT

Not on the questions 2 and 3, other than that you can manually reset the device using "nrfjprog --reset" and that you can reconnect the debugger when you get the error in question 3.

Regarding 1, it is just a warning saying that --verify is not used, which it is not when you are using the west flash command (which is being used by nRF Connect for VS Code.

Best regards,

Edvin

RE: Flashing issues

MaximSh — Sun, 03 Jul 2022 07:23:09 GMT

Any updates?

RE: Flashing issues

Edvin — Tue, 14 Jun 2022 08:01:57 GMT

Thank you for clarifying. I will forward this to our VS Code development team.

Best regards,

Edvin

RE: Flashing issues

MaximSh — Tue, 14 Jun 2022 07:38:33 GMT

Hi,
I think all issues started after updating nRF Command Line Tools from 10.15.4 to 10.16.0.

Also if i press Erase and Flash to the board button i see same warnings.
I use custom board nrf5340 that programed via nrf5340-DK
No it is not depend on what application, also after recover it can happen.

RE: Flashing issues

Edvin — Tue, 14 Jun 2022 06:48:31 GMT

Hello,

These warnings are caused due to an update in nrfjprog (nRF Command Line Tools), which is used by West when flashing the devices.

1: Just be aware that the programming is not using the --verify flag. In general, that is not a problem. This would typically only be an issue when you are using nrfjprog --program, but you forget to erase the chip first (using --eraseall or --sectorerase).

2: I have seen that from time to time. When you see this, what DK/sample are you using?

3: Does that depend on what application you are trying to debug? Or is it regardless of the application? Does it happen if you use "nrfjprog --recover" on the device before programming and start a debug session?

Best regards,

Edvin