Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

jrhaws — Tue, 15 Aug 2023 21:38:37 GMT

I have not seen this issue since I switched to just running in Windows and not through WSL.

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

jrhaws — Tue, 08 Aug 2023 15:08:41 GMT

Correct - this is very intermittent. I have not seen this issue since I switched the filesystem my code was on from WSL to Windows proper. Maybe that was playing into it. I'll continue testing and let you know.

Thanks!

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

Elfving — Tue, 08 Aug 2023 11:28:46 GMT

[quote user="jrhaws"]

I'll share schematics as soon as I can verify our NDA with you guys.

[/quote]

Great! Would be nice to get that out of the way.

[quote user="jrhaws"]

However, sometimes the system seems to get into a state where it cannot flash at all - like it cannot communicate with the programmer.

[/quote]

So this just happens every now and then? Not necessarily every time from now on either?

Regards,

Elfving

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

jrhaws — Mon, 07 Aug 2023 19:46:33 GMT

Elfving,

Yes, I can flash other boards (and this particular board) just fine many times.

However, sometimes the system seems to get into a state where it cannot flash at all - like it cannot communicate with the programmer.

I have been running VS Code off a shared drive with a WSL installation, so maybe that was playing into this as well.

I'll share schematics as soon as I can verify our NDA with you guys.

Thanks for the support!

Jon

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

Elfving — Mon, 07 Aug 2023 08:04:53 GMT

[quote user="jrhaws"]Thanks for the help![/quote]

No problem at all, though I should mention that there might be some delays here on DevZone during these summer months due to vacations and low staffing. Though we are starting to get out of that phase now.

[quote user="jrhaws"]we use an external Segger JLink base instead of an onboard chip.[/quote]

Great, just wondered if it was an external programmer from another DK.

As the custom board has worked for a while I assume the board layout is fine, though out of curiosity: have you gotten the hardware reviewed?

Are you able to flash anything else, eg. other copies of this custom board, with this programmer?

Regards,

Elfving

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

jrhaws — Fri, 04 Aug 2023 14:36:55 GMT

This is a custom board. We are just programming with SWD, similar to how the dev kits are done, but we use an external Segger JLink base instead of an onboard chip.

I'm not an expert on how the programmers work, but VS code can see the device (the programmer) and when I click debug, it runs a the nrfjprog command to flash the image to the board then start the debugger. It works fine a lot of the time, but there seems to be a sequence of operations that makes the chip invisible for a period of time and even power cycling the target doesn't clear it out.

We have the SWDIO/RESET and SWDCLK lines of the nrf52832 run out to Tagconnect pads on our board and we connect our programmer to that via ribbon cable.

What other details would you like to know?

Thanks for the help!

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

Elfving — Fri, 04 Aug 2023 11:41:01 GMT

Hello Jon,

Is this a DK or a custom board? If it is a custom board, could you expand a bit on how you are programming it?

Regards,

Elfving

RE: Cannot flash NRF52832 with Segger JLink device after a full day of flashing normally

jrhaws — Thu, 03 Aug 2023 23:21:37 GMT

I also ran this and got this result:

PS C:\Users\jonathan.haws> nrfjprog.exe --recover -f NRF52 --log
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 10020 milliseconds with result -21
[error] [ Worker] - 10 second timeout elapsed, no time left to wait for debug port to power up.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.