unable to flash the code in BT 40

RE: unable to flash the code in BT 40

lalith88 — Fri, 21 Mar 2025 11:18:12 GMT

yes, with same firmware. Not even single line of code change.
I have tried with other module it was show first same errors
C:\Users\lnaik\Desktop\New_develop>nrfjprog --recover --coprocessor CP_NETWORK
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 14 milliseconds with result -21
[error] [ Worker] - Eraseprotect is enabled and readback protection setting is ALL, can't recover device.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
and now its working fine.

RE: unable to flash the code in BT 40

Susheel Nuguru — Fri, 21 Mar 2025 11:06:18 GMT

I have a first hand experience with this error -102 when the supply voltage was not enough to the chip. If that is not the case, then your module might be broken. Have you tried it with another module? Are you sure your input power supply is giving enough power?

RE: unable to flash the code in BT 40

lalith88 — Fri, 21 Mar 2025 06:39:13 GMT

nrfjprog version 10.24.2 external
now i am getting this kind of error can you check this
[0/16] Performing build step for 'tfm'
ninja: no work to do.
-- west flash: using runner nrfjprog
-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: c:\Users\lnaik\Desktop\New_develop\build_1\zephyr\merged.hex
[error] [ Client] - Encountered error -102: Command select_coprocessor executed for 140 milliseconds with result -102
ERROR: Failed when selecting coprocessor APPLICATION
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program 'c:\Users\lnaik\Desktop\New_develop\build_1\zephyr\merged.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 600105674

RE: unable to flash the code in BT 40

Susheel Nuguru — Thu, 20 Mar 2025 13:39:33 GMT

Are you sure that there is enough power supplied to the chip? Did you try it on any other chip apart from this one? If not can you please try this.

It has to be either not enough power or some error/damage with the chip. Which version of nrfjprog are you using?

RE: unable to flash the code in BT 40

lalith88 — Thu, 20 Mar 2025 10:33:22 GMT

C:\Users\lnaik\Desktop\New_develop>nrfjprog --eraseall --coprocessor CP_NETWORK
[error] [ nRFXX] - Device does not have an ARM debug port.
[error] [ Client] - Encountered error -3: Command enable_coprocessor executed for 0 milliseconds with result -3
ERROR: NETWORK coprocessor is invalid on UNKNOWN family devices[error] [ nRFXX] - Device does not have an ARM debug port.

[error] [ Worker] - NETWORK is not a valid coprocessor for the device
ERROR: An invalid argument was provided. Use --help for a list of valid
ERROR: arguments.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

C:\Users\lnaik\Desktop\New_develop>nrfjprog --recover --coprocessor CP_NETWORK
[error] [ nRFXX] - Device does not have an ARM debug port.
[error] [ nRFXX] - Device does not have an ARM debug port.
[error] [ Client] - Encountered error -3: Command enable_coprocessor executed for 15 milliseconds with result -3
ERROR: NETWORK coprocessor is invalid on UNKNOWN family devices[error] [ Worker] - NETWORK is not a valid coprocessor for the device

ERROR: An invalid argument was provided. Use --help for a list of valid
ERROR: arguments.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed. can you check these out please

RE: unable to flash the code in BT 40

lalith88 — Thu, 20 Mar 2025 10:31:15 GMT

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\Users\lnaik\Desktop\New_develop\build_1\zephyr\merged.hex
[error] [ Worker] - Encountered unexpected debug port ID 4, expected 6
[error] [ Client] - Encountered error -5: Command select_coprocessor executed for 22 milliseconds with result -5
ERROR: Failed when selecting coprocessor APPLICATION
ERROR: The --family option given with the command (or the default from
ERROR: nrfjprog.ini) does not match the device connected.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 18: nrfjprog --program 'c:\Users\lnaik\Desktop\New_develop\build_1\zephyr\merged.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050060012 can you check this error

RE: unable to flash the code in BT 40

lalith88 — Thu, 20 Mar 2025 10:30:56 GMT

RE: unable to flash the code in BT 40

Susheel Nuguru — Thu, 20 Mar 2025 06:44:11 GMT

Hmm, recover should have worked even if erase protection is enabled.

Can you try erase all and then try recover?

> nrfjprog --eraseall --coprocessor CP_NETWORK

> nrfjprog --recover --coprocessor CP_NETWORK