Unable to connect to J-Link from SES - nRF5340D

RE: Unable to connect to J-Link from SES - nRF5340D

Marte Myrvold — Thu, 15 Jul 2021 08:40:09 GMT

Hi,

I am happy to hear that you got it to work, and thank you for sharing this to help others!

I recommend looking at Working with nRF53 Series in our documentation for more information about working with this SoC. This page also explains how to build and program samples for the DK.

Best regards,

Marte

RE: Unable to connect to J-Link from SES - nRF5340D

Yeshvanth M — Wed, 14 Jul 2021 13:57:30 GMT

Thanks a lot, it worked.

Apparently, I had to install nrfjprog manually using pip. Even west can be installed the same way.

infocenter.nordicsemi.com/index.jsp

Then to get started with a BLE example for the very first time,

File->"Open nRF Connect SDK Project...", select hci_rpmsg, and board with _cpunet suffix.

Build and run project.

Next create another project File->"Open nRF Connect SDK Project...", and this time select peripheral_lbs sample, and board with _cpuappns suffix.

Build and run project.

LED1 should be blinking slowly when the application has initialized Bluetooth correctly. Now it should be possible to use a mobile phone to enumerate the "Nordic_Blikny" device (using for example nRF Connect Android app).

You can take a look at this example project: www.hackster.io/.../getting-started-with-nrf5340-dk-74297e

That should get you going. I explained this so that anyone who is starting with the nRF5340DK would find this useful.

RE: Unable to connect to J-Link from SES - nRF5340D

Marte Myrvold — Wed, 14 Jul 2021 11:09:24 GMT

Hi,

The error NOT_AVAILABLE_BECAUSE_PROTECTION indicates that the readback protection is enabled. You must disable the readback protection by recovering the device in order to be able to connect to and program it. You can use west or nrfjprog to recover the device.

With west you can recover both cores with the following command:

west flash --recover

With nrfjprog you must recover the cores separately. Make sure you recover the network core before the application core.

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover

Best regards,

Marte