Hi
Seems like all new nRF DKs shipped with nRF5340 as interface mcu have limited speed on Debug Out.
nrfjprog -r --clockspeed 646
Applying system reset.
Run.
nrfjprog -r --clockspeed 647
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 198 milliseconds with result -102
ERROR: Unable to connect to a debugger.
[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.
I tested this with PCA10040 (1050306391, 3.0.0 2023.22) and PCA10056 (1050242811 3.0.2 2023.21) with exactly the same result. All frequencies below 646 are successful, all above that fail.
With old PCA10040 (based on some ATSAM chip) i can run --clockspeed 50000 with no problems. When the external cable is not connected, all 3 boards can flash onboard nRF chip with max speed (50000 kHz).
This seems to be firmware limitation. Is it somehow related to Segger licensing?
NCS images are much larger than old SDK, thus development of custom boards gets slowed down.. How to work around it?
Running on MacOS 13.6.7 M2 Pro.
nrfjprog version: 10.24.0 external
JLinkARM.dll version: 7.94a
