• State Verified Answer
  • Replies 14 replies
  • Subscribers 74 subscribers
  • Views 147 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 343315
Options

I am using nRF52833 PCA10100. When I try to connect the device through J link commander it is always giving "cannot connect to the device." What should I do?

Suryalakshmi

I initially tried Segger Embedded Studio for ARM and I clicked on connect to J link device, an error occured. I wasn't sure at that time. Then I used the nRF CONNECT for desktop. The device was getting detecting, so I tried to flash a sample program for blinking the peripheral LED. Again it was showing error. Then I tried using JLINK commander, but it was also not able to connect to the device. I tried to see the problem by giving the output to chatgpt. It is saying that the SoC is locked and I should unsecure it. I tried it but I can't unsecure it. I don't know where I am wrong.   

Parents
  • 0

    Hello,

    Are you testing with both a nRF5340 DK and a nRF52833 DK (pca101000), or only the latter? I see you are attempting to select the nRF5340 in Jlink commander, but this is the wrong chip if you are connected to a nRF52833 DK.

  • 0 in reply to Vidar Berg

    It has both chips. nRF5340 is the part which have J link device. nRF52833 is for the peripherals. I am very new to nordic devices. So I only know little bit about the board. Even though unsecuring is not happening the option for it comes only when I select nRF5340. When I select nRF52833, it just directly says can't connect to the device. Also thank you for responding...

  • 0 in reply to Suryalakshmi

    Yes, the nRF5340 chip on this board is used as the interface mcu for the board. Could you please post a picture of your board and how it is connected to your pc? From your second screenshot it appears to be detected as a nRF5340DK, which I haven't seen happen before. Do you also see this if you open the 'Programmer' app?

  • 0 in reply to Vidar Berg

    Actually in the Jlink commander when the device name was asked. I tried giving both chips name. I just posted the picture of the one where I entered 5340's name.  And for the picture. I will post it below.  One time I tried to flash the LED blink program through nRF connect app. I kept pressing on the reset button and I saw something flashing in the chip, even though it showed error in the connect app. The LED1 on the peripheral actually started blinking that time. I again tried to flash another program, then the written program got erased and the new program wasn't flashed. A day later, I tried to connect the usb cable to the nRF52833 side. When I used to connect it like that, the LED1, 2, 3 and 4 used to turn on when the respective button was pressed. Now when I connect on that side, the LEDs are not turning on anymore. It happened after the program got flashed.

Reply
  • 0 in reply to Vidar Berg

    Actually in the Jlink commander when the device name was asked. I tried giving both chips name. I just posted the picture of the one where I entered 5340's name.  And for the picture. I will post it below.  One time I tried to flash the LED blink program through nRF connect app. I kept pressing on the reset button and I saw something flashing in the chip, even though it showed error in the connect app. The LED1 on the peripheral actually started blinking that time. I again tried to flash another program, then the written program got erased and the new program wasn't flashed. A day later, I tried to connect the usb cable to the nRF52833 side. When I used to connect it like that, the LED1, 2, 3 and 4 used to turn on when the respective button was pressed. Now when I connect on that side, the LEDs are not turning on anymore. It happened after the program got flashed.

Children
Related
Terms of service