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.  

[Vidar Berg]

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.

[Suryalakshmi]

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...

[Vidar Berg]

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?

[Suryalakshmi]

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.

[Vidar Berg]

Thanks for posting the picture. Everything appears to be in order. Switches are in their default posititions, etc.

Suryalakshmi said:

I tried giving both chips name. I just posted the picture of the one where I entered 5340's name

I understand, but the relevant errors are those that shown when the correct device is entered.

Please try to program the hex file below from the command line with nrfutil and see if that works.

ble_led_button.hex

$ nrfutil device program --firmware ble_led_button.hex --options chip_erase_mode=ERASE_ALL,reset=RESET_SOFT,verify=VERIFY_READ

[Suryalakshmi]

 It is showing error. Do I have to download anything?

[Vidar Berg]

Error says it is not finding the hex file. Did you download the ble_led_button.hex file and is it located in the same directory?

[Suryalakshmi]

There is no ble_led_button file in my system. From where should I download it?

[Vidar Berg]

I included it here:

Vidar Berg said:

Please try to program the hex file below from the command line with nrfutil and see if that works.

ble_led_button.hex

[Suryalakshmi]

I don't understand... This happend when I ran the command.

[Vidar Berg]

The error indicates that the interface mcu is unable to communicate with the nRF52833 target. Maybe it is not powered. Do you have the power source switch in the "VDD" position?