Com port conflict ?

Henrik 5 months ago

Using the nRF54L15 Development Board.

Did try to run the "nRF connect for desktop" - "Quick start"

I do not get a reply from the Board when doing one of the samples.

Fullscreen 2024-12-10T09_42_19.195Z-log.txt Download

2024-12-10T09:42:19.544Z INFO Initialising the bundled nrfutil device
2024-12-10T09:42:19.630Z DEBUG Started watching devices
2024-12-10T09:42:22.854Z INFO Using the bundled core version for nrfutil device: 7.13.0
2024-12-10T09:42:23.670Z INFO Using nrfutil-device version: 2.7.5
2024-12-10T09:42:23.671Z INFO Using nrf-device-lib version: 0.17.41
2024-12-10T09:42:23.671Z INFO Using nrfjprog DLL version: 10.24.2
2024-12-10T09:42:23.671Z INFO Using JLink version: JLink_V7.94i
2024-12-10T09:42:27.625Z DEBUG Selected device: nRF54L15 DK
2024-12-10T09:42:27.654Z DEBUG Changed step: Info
2024-12-10T09:42:28.580Z DEBUG Changed step: Rename
2024-12-10T09:42:29.548Z DEBUG Changed step: Program
2024-12-10T09:42:42.828Z DEBUG Changed step: Verify
2024-12-10T09:42:45.854Z INFO Opened port with options: {"path":"COM7","baudRate":115200}
2024-12-10T09:42:51.139Z INFO Closed port: COM7

I earlier did a DTM test Image, and had the "Direct Test Mode" function work.

But later I did not success in getting any DTM build to work !

The Build is successful, but after flash (by visual studio code), the DTM application fail by

"cannot communicate with the device. Make Sure it is not in use by other application, that the correct serial port has been selected, and that it uses firmware with Direct Test Mode"

I did also try to "recover" the board - same problem

Parents

0 Håkon Alseth 5 months ago

Hi,

For some reason, you are failing to flash properly:

...
2024-12-13T10:20:53.174Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
 - [Probe] The fw-read operation is not supported, code: Generic.
Message: Batch task fw-read failed, [Probe] The fw-read operation is not supported.

This is how a successful log looks:

13:56:16.220	Initialising the bundled nrfutil device
13:56:16.564	Using the bundled core version for nrfutil device: 7.13.0
13:56:16.681	Using nrfutil-device version: 2.6.4
13:56:16.681	Using nrf-device-lib version: 0.17.35
13:56:16.681	Using nrfjprog DLL version: 10.24.2
13:56:16.681	Using JLink version: JLink_V8.10f
13:56:16.681	Installed JLink version does not match the expected version (JLink_V7.94i)
13:56:16.739	Getting serial port options from the persistent store for 001057721462.pc-nrfconnect-programmer
13:56:33.053	Parsing HEX file: /home/hkn/Downloads/DTM_2.8.0_nrf54l15dk_nrf54l15_cpuapp.hex
13:56:33.075	File was last modified at 12/13/2024, 1:56:28 PM
13:56:33.091	Update files regions according to Application core
13:56:33.091	Parse memory regions for file
13:56:37.064	Selecting device with the serial number 001057721462
13:56:37.529	Selected device with the serial number 001057721462
13:56:37.529	Using nrfutil device to communicate with target via JLink
13:56:37.529	JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct 9 2024 11:01:34
13:56:37.529	Device family NRF54L_FAMILY
13:56:37.529	Device version NRF54L15_xxAA_ENGB
13:56:37.529	Board version PCA10156
13:56:37.539	Update files regions according to Application core
13:56:37.539	Parse memory regions for file
13:56:37.869	Reading readback protection status for Application core
13:56:37.870	Reading readback protection status for Application core 0%
13:56:37.883	Reading readback protection status for Application core 100%
13:56:37.883	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
13:56:37.884	Reading readback protection status for Application core completed
13:56:38.389	Loading core information for Application core
13:56:38.391	Loading core information for Application core 0%
13:56:38.393	Update files regions according to Application core
13:56:38.393	Parse memory regions for file
13:56:38.397	Loading core information for Application core 100%
13:56:38.398	Loading core information for Application core completed
13:56:38.399	Update files regions according to Application core
13:56:38.399	Parse memory regions for file
13:56:38.881	Reading readback protection status for Application core
13:56:38.881	Reading readback protection status for Application core 0%
13:56:38.892	Reading readback protection status for Application core 100%
13:56:38.892	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
13:56:38.893	Reading readback protection status for Application core completed
13:56:39.032	Device is loaded and ready for further operation
13:56:41.191	Recovering Application core
13:56:41.192	Recovering Application core 0%
13:56:41.418	Recovering Application core 100%
13:56:41.419	Recovering Application core completed
13:56:41.419	Writing HEX to Application core
13:56:41.449	Writing HEX to Application core 0%
13:56:41.473	Writing HEX to Application core 50%
13:56:41.473	Writing HEX to Application core 50%
13:56:41.909	Writing HEX to Application core 100%
13:56:41.909	Writing HEX to Application core 50%
13:56:41.909	Writing HEX to Application core 100%
13:56:41.914	Writing HEX to Application core completed
13:56:41.914	Loading core information for Application core
13:56:41.917	Update files regions according to Application core
13:56:41.917	Parse memory regions for file
13:56:41.922	Loading core information for Application core 0%
13:56:41.923	Loading core information for Application core 100%
13:56:41.923	Loading core information for Application core completed
13:56:41.925	Update files regions according to Application core
13:56:41.926	Parse memory regions for file
13:56:42.861	Reading readback protection status for Application core
13:56:42.861	Reading readback protection status for Application core 0%
13:56:42.873	Reading readback protection status for Application core 100%
13:56:42.874	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
13:56:42.875	Reading readback protection status for Application core completed

Can you try to program with nrfjprog via cmd prompt?

If that also fails, add a "--log" and upload the failure log here.

Kind regards,

Håkon

Reply