Not possible to access nRF52840 vi J-LINK after downloading "peripheral Uart" example

RE: Not possible to access nRF52840 vi J-LINK after downloading "peripheral Uart" example

rhysfaulkner — Wed, 01 Nov 2023 21:51:03 GMT

Dear Svein,

I'm sorry to hear about the issues you're facing with your nRF52840 and the "peripheral Uart" example. It can be frustrating when things don't go as expected. Let's try to troubleshoot this together.

First, it's great to see your enthusiasm for learning and experimenting with Connect SDK and nRF Connect for Desktop. Here are some steps you can take to resolve the situation:

Check Connections: Double-check your hardware connections, ensuring that your nRF52840 is properly connected to your computer via the J-Link.
Verify Code Changes: Revert the code changes you made to the "peripheral Uart" example back to the original state to eliminate any code-related issues. Ensure that the unmodified example runs as expected.
VS Code Configuration: Make sure you have properly configured VS Code for use with your nRF52840. Check the build and debug configurations to ensure they are set up correctly.
J-Link Driver: Ensure that your J-Link driver is up to date. You can download the latest driver from the SEGGER website.
Try a Different USB Port or Cable: Sometimes, connectivity issues can be caused by faulty USB ports or cables. Try a different USB port or cable to rule out this possibility.
Reinstall SDK and Tools: If all else fails, consider reinstalling Connect SDK, nRF Connect for Desktop, and nRF-utilities to ensure that you have a clean and properly functioning development environment.
Seek Help from the Nordic Community: You're not alone in your journey. The Nordic Developer Zone and forums can be a valuable resource for troubleshooting issues and seeking help from experienced developers.

If you're still facing problems after trying these steps, don't hesitate to reach out to the Nordic support team. They have a wealth of experience and can provide specific guidance based on your setup and issue.

I hope this helps you get back on track with your project. Don't hesitate to ask for further assistance if needed. Keep up the great work in your learning journey!

Best regards,

RE: Not possible to access nRF52840 vi J-LINK after downloading "peripheral Uart" example

JONATHAN LL — Tue, 31 Oct 2023 11:45:39 GMT

Thanks for the update Svein,

Feel free to ask for anything related to the new SDK if there is anything that you are wondering about and we will do our best to help. Just create a new ticket for any questions and we will support

Regards,
Jonathan

RE: Not possible to access nRF52840 vi J-LINK after downloading "peripheral Uart" example

Svein — Mon, 30 Oct 2023 19:03:01 GMT

Hi Jonathan,

Thanks a lot for your quick response.

I tried to build the SW for our customer board, but there is a big risk that I have made some mistakes since I’m a newbie in using SDK Connect/NCS.

We started our development with SDK15 and today we are on SDK17.1.0 and SES. We will stick to SDK17.1.0 for the next couple of years or so, but for future update of our product we must move to NCS, that’s the reason why I have started to teach myself in NCS.

To my understanding DCDC inductors are not mounted in our PCB and I thick we can close this ticket for now.

Kind regard, Svein

RE: Not possible to access nRF52840 vi J-LINK after downloading "peripheral Uart" example

JONATHAN LL — Mon, 30 Oct 2023 09:54:44 GMT

Hi,

[quote userid="106381" url="~/f/nordic-q-a/105154/not-possible-to-access-nrf52840-vi-j-link-after-downloading-peripheral-uart-example"]I built the project and then downloaded it to nRF52840, (customer board).[/quote]

This is a custom board, have you built for the custom board or did you build for the DK ?

One potential issue could be that the customer board does not have the DCDC inductors mounted in the PCB. If DCDC is enabled in the software then it will be very difficult/impossible to reset the device.

Make sure to power cycle the device.

nrfjprog --recover should be sufficient to reset the device.

Regards,
Jonathan