Can't connect to nRF52840-DK using nRF Connect Programmer

Hi,

I'm using Manjaro Linux, nRF Connect v3.10.0 and Programmer v2.3.3. I'm trying to connect to nRF52840-DK using this software, but I get an error:

14:45:31.110	Using @nordicsemiconductor/nrf-device-lib-js version: 0.4.3
14:45:31.111	Using nrf-device-lib version: 0.10.3
14:45:31.111	Using nrfjprog dll version: 10.15.1
14:45:31.111	Using JLink version: JLink_V7.62a
14:45:31.166	Application data folder: /home/koadas/.config/nrfconnect/pc-nrfconnect-programmer
14:45:31.469	[nrfdl][error](14:45:31.458) JLink ignore error -254 for serialnumber 000683847294 and continue
14:45:31.976	[nrfdl][error](14:45:31.935) JLink ignore error -254 for serialnumber 000683847294 and continue
14:45:32.078	[nrfdl][error](14:45:32.073) JLink ignore error -254 for serialnumber 000683847294 and continue
14:45:39.237	Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.
14:45:39.237	Please make sure J-Link Software and nrf-udev are installed. See https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/#macos-and-linux

I can connect to the board using JLink software or openocd without problems.

Can you help me?

Parents

0 Konrad Adasiewicz over 4 years ago

I had older version of this software installed on different PC (same OS) and it worked there. After upgrade I experience same issue.

Working logs:

2022-03-12T14:40:07.241Z INFO Application data folder: /home/kad/.config/nrfconnect/pc-nrfconnect-programmer
2022-03-12T14:40:07.559Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2022-03-12T14:40:07.613Z DEBUG App pc-nrfconnect-programmer v1.4.3 official
2022-03-12T14:40:07.614Z DEBUG App path: /home/kad/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2022-03-12T14:40:07.614Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.3.0)
2022-03-12T14:40:07.614Z DEBUG nRFConnect path: /opt/nrfconnect-appimage/resources/app.asar
2022-03-12T14:40:07.614Z DEBUG HomeDir: /home/kad
2022-03-12T14:40:07.614Z DEBUG TmpDir: /tmp
2022-03-12T14:40:08.263Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2022-03-12T14:42:25.314Z INFO Using nrfjprog to communicate with target
2022-03-12T14:42:27.100Z INFO Using J-Link Software version 6.98
2022-03-12T14:42:28.975Z INFO Segger serial:  683847294
2022-03-12T14:42:28.976Z INFO Segger speed:  2000  kHz
2022-03-12T14:42:28.977Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
2022-03-12T14:42:28.978Z INFO Core probed: 683847294.
2022-03-12T14:42:28.978Z INFO Core RAM: 256KiB.
2022-03-12T14:42:28.979Z INFO Core ROM: 1024KiB in pages of 4KiB.
2022-03-12T14:42:29.148Z INFO Model: NRF52840_xxAA_REV2.
2022-03-12T14:42:30.975Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2022-03-12T14:43:02.478Z INFO Core0: Non-volatile memory has been read. 2 non-empty memory blocks identified

After upgrade:

2022-03-12T14:48:36.691Z INFO Application data folder: /home/kad/.config/nrfconnect/pc-nrfconnect-programmer
2022-03-12T14:48:37.273Z DEBUG iface: wlp2s0
2022-03-12T14:48:37.274Z DEBUG IP4: -
2022-03-12T14:48:37.274Z DEBUG IP6: -
2022-03-12T14:48:37.274Z DEBUG MAC: -
2022-03-12T14:48:37.277Z DEBUG Client Id: -
2022-03-12T14:48:37.281Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-03-12T14:48:37.583Z DEBUG App pc-nrfconnect-programmer v2.3.3 official
2022-03-12T14:48:37.583Z DEBUG App path: /home/kad/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2022-03-12T14:48:37.583Z DEBUG nRFConnect 3.10.0, required by the app is (^3.10.0)
2022-03-12T14:48:37.583Z DEBUG nRFConnect path: /opt/nrfconnect-appimage/resources/app.asar
2022-03-12T14:48:37.583Z DEBUG HomeDir: /home/kad
2022-03-12T14:48:37.583Z DEBUG TmpDir: /tmp
2022-03-12T14:48:56.789Z ERROR Unsupported device.
            The detected device could not be recognized as
            neither JLink device nor Nordic USB device.
2022-03-12T14:48:56.790Z ERROR Please make sure J-Link Software and nrf-udev are installed. See https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/#macos-and-linux
2022-03-12T14:51:03.320Z DEBUG Sending usage data...
2022-03-12T14:51:03.322Z DEBUG Category: pc-nrfconnect-programmer
2022-03-12T14:51:03.322Z DEBUG Action: Close device
2022-03-12T14:51:03.322Z DEBUG Label: 
2022-03-12T14:51:03.323Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-03-12T14:51:03.332Z INFO Target device closed

Reply

0 Konrad Adasiewicz over 4 years ago

I had older version of this software installed on different PC (same OS) and it worked there. After upgrade I experience same issue.

Working logs:

2022-03-12T14:40:07.241Z INFO Application data folder: /home/kad/.config/nrfconnect/pc-nrfconnect-programmer
2022-03-12T14:40:07.559Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2022-03-12T14:40:07.613Z DEBUG App pc-nrfconnect-programmer v1.4.3 official
2022-03-12T14:40:07.614Z DEBUG App path: /home/kad/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2022-03-12T14:40:07.614Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.3.0)
2022-03-12T14:40:07.614Z DEBUG nRFConnect path: /opt/nrfconnect-appimage/resources/app.asar
2022-03-12T14:40:07.614Z DEBUG HomeDir: /home/kad
2022-03-12T14:40:07.614Z DEBUG TmpDir: /tmp
2022-03-12T14:40:08.263Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2022-03-12T14:40:08.264Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2022-03-12T14:40:08.265Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2022-03-12T14:40:08.266Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2022-03-12T14:40:08.267Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2022-03-12T14:40:08.268Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2022-03-12T14:40:08.269Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2022-03-12T14:40:08.270Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2022-03-12T14:42:25.314Z INFO Using nrfjprog to communicate with target
2022-03-12T14:42:27.100Z INFO Using J-Link Software version 6.98
2022-03-12T14:42:28.975Z INFO Segger serial:  683847294
2022-03-12T14:42:28.976Z INFO Segger speed:  2000  kHz
2022-03-12T14:42:28.977Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
2022-03-12T14:42:28.978Z INFO Core probed: 683847294.
2022-03-12T14:42:28.978Z INFO Core RAM: 256KiB.
2022-03-12T14:42:28.979Z INFO Core ROM: 1024KiB in pages of 4KiB.
2022-03-12T14:42:29.148Z INFO Model: NRF52840_xxAA_REV2.
2022-03-12T14:42:30.975Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2022-03-12T14:43:02.478Z INFO Core0: Non-volatile memory has been read. 2 non-empty memory blocks identified

After upgrade:

2022-03-12T14:48:36.691Z INFO Application data folder: /home/kad/.config/nrfconnect/pc-nrfconnect-programmer
2022-03-12T14:48:37.273Z DEBUG iface: wlp2s0
2022-03-12T14:48:37.274Z DEBUG IP4: -
2022-03-12T14:48:37.274Z DEBUG IP6: -
2022-03-12T14:48:37.274Z DEBUG MAC: -
2022-03-12T14:48:37.277Z DEBUG Client Id: -
2022-03-12T14:48:37.281Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-03-12T14:48:37.583Z DEBUG App pc-nrfconnect-programmer v2.3.3 official
2022-03-12T14:48:37.583Z DEBUG App path: /home/kad/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2022-03-12T14:48:37.583Z DEBUG nRFConnect 3.10.0, required by the app is (^3.10.0)
2022-03-12T14:48:37.583Z DEBUG nRFConnect path: /opt/nrfconnect-appimage/resources/app.asar
2022-03-12T14:48:37.583Z DEBUG HomeDir: /home/kad
2022-03-12T14:48:37.583Z DEBUG TmpDir: /tmp
2022-03-12T14:48:56.789Z ERROR Unsupported device.
            The detected device could not be recognized as
            neither JLink device nor Nordic USB device.
2022-03-12T14:48:56.790Z ERROR Please make sure J-Link Software and nrf-udev are installed. See https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/#macos-and-linux
2022-03-12T14:51:03.320Z DEBUG Sending usage data...
2022-03-12T14:51:03.322Z DEBUG Category: pc-nrfconnect-programmer
2022-03-12T14:51:03.322Z DEBUG Action: Close device
2022-03-12T14:51:03.322Z DEBUG Label: 
2022-03-12T14:51:03.323Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-03-12T14:51:03.332Z INFO Target device closed

Children

0 Marte Myrvold over 4 years ago in reply to Konrad Adasiewicz

Hi,

I will report this to the developers. Can you upload logs where you try to open the device with verbose logging enabled? Go to the About tab in the Programmer app to enable verbose logging, and select "Restart with verbose logging". Make sure to disable verbose logging again afterwards, as this option will generate a lot of additional log and create rather large log files.

Best regards,

Marte
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Konrad Adasiewicz over 4 years ago in reply to Marte Myrvold

2022-03-14T23_00_11.165Z-log.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Marte Myrvold over 4 years ago in reply to Konrad Adasiewicz

Hi,

I have forwarded the log to the developers, and I will update you when I get a response.

Best regards,

Marte
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Marte Myrvold over 4 years ago in reply to Marte Myrvold

Hi,

Can you provide information about the hardware version and production year/week of your DK? You should find this information on a sticker on your DK, as shown here:

Best regards,

Marte
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel