nrf52840 cant connect to nrf connect v3.6.1

[yu1998]

11:14:55.624

Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'

11:14:55.954

Server setup loaded from C:\Users\jason_yu\Desktop\nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_ias_c\findMeMasterServer.ncs.

11:14:56.839

Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

can use putty to connect nrf52840 btw

[Henry_Chou]

Jason:

What's the Segger J-link version in your side?....If the j-link version is not match 3.6.1, it will be happened the same bug situation as your statement.

[yu1998]

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded D:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 5.20/bin/JLinkARM.dll
Firmware Version: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00
DLL Version: 6.88a
Hardware Version: V1.00
Target Voltage: 3.300

[Henry_Chou]

The 3.6.1 release note:

https://github.com/NordicSemiconductor/pc-nrfconnect-launcher/releases

It's mention that driver nrfjprog v10.12.1 and JLink 6.88a. But yours is the same 6.88a

So your bug is not the same with mine. Because my bug is happened in 6.86f. And the nRF51 series can't be recognized. So I reinstall the old one (3.6.0)

[yu1998]

i wonder if there is other way to test without the nrf connect this program do have lots of bug 

[Henry_Chou]

Because you have to server setup with .ncs file. So that I have no idea about your solution now.

But I think re-install 3.6.0 or earlier is another choice. I had done the older version before. It's okay. 

[yu1998]

i tried 3.6.0 but still does not work

[yu1998]

Actually it work sometimes but it works out randomly some times it just show error btw