Hello,
We designed and tested a firmware on the nRF52833-DK board, whith plenty of debug sessions and reprogramming.
Then it has been build for our custom board, based on the nRF52833 chip too, used as a peripheral for a modem host (SPI line).
Using our J-Link (SWD mode), I programmed succesfully 5 boards last week (nrfutil and nrf Programmer), but not tested the boards, I had to leave them few days. Especially one board as been labelled "nrf dev" proof that the programming were successfull.
Today, I tried all the boards the whole morning, impossible to reprogram the boards.
Our EMS also sent us back few samples or faulty boards with a similar behavior (after analysis).
nRFutil error is always :
I looked at these tickets : devzone.nordicsemi.com/.../unable-to-recover-nrf52832-after-debugging-session (mentionned here too devzone.nordicsemi.com/.../nrf9160dk-failed-to-write-debugport-register-2-unknown-error-in-j-link-dll), or (devzone.nordicsemi.com/.../1775) or devzone.nordicsemi.com/.../cannot-program-bmd-340-with-nrf52dk (no solution)
They did not help.
Here what I tried :
- wirings checks several times
- J-Link libraries update to 8.10f (the version expected by nrfutil)
- J-Link firmware version check (up to date)
- VDD disconnection => LOW_VOLTAGE detected, the VDD is correct (1.8V)
- reset pin control (high and low) before and during programming
- batch script requesting "recover" in loop, doing power on/off or reset pin toggling
It seems to me that I'll not be able to reprogram the devices once programmed a first time.
Question :
- any other tips ? or tricks ?
- why on the nRF52-DK I'm able to reprogram the devices dozen of times ? (in VSCode only the overlay files are different)
Thanks !
LOGS
./nrfutil device recover --serial-number 000260111492 --log-level trace
=> C:\Users\xxx\.nrfutil\logs
VScode programming
log.log : the first error is