nRF Connect for VS Code, connected devices no device found

RE: nRF Connect for VS Code, connected devices no device found

Elfving — Thu, 14 Sep 2023 09:29:12 GMT

[quote user="BvdP4Celsius"]After an update from SDKV2.0.0 to V2.4.0 we experienced huge differences in the overlay file handling.[/quote]

Yeah, there is a large gap between these versions, so there might be some differences in device tree file handling (for instance pincontrol comes to mind). It is understandable that you would want to focus on one version of NCS for one project if it fits all your requirements, and not necessarily continuously update to the newest version.

[quote user="BvdP4Celsius"]In a previous question we already asked if there is some LTS version.[/quote]

Yeah that is a hard question to answer. We do not really follow that system, where there is one version that is LTS and others are not. Our dev-tags (eg 2.2.99-dev3) are not considered stable ofcourse, and you shouldn't use those for your project. If there are issues on a devtag we might tell you to simply use a tagged one. All tagged versions however are supported for "a longer period". Another thing is that there might be bigger differences between major tags, like from 2.1.0 to 2.2.0. Differences in only the last digit should be mostly bugfixes etc., and it should be easier for you to switch between those without making huge changes to your project.

So when you switch from NCS 2.0.0 to 2.4.0, I am not surprised that you need to change things in your project. Changing to 2.0.2 however should go more smoothly.

Regards,

Elfving

RE: nRF Connect for VS Code, connected devices no device found

BvdP4Celsius — Wed, 13 Sep 2023 07:46:07 GMT

Hi Elfving

Thanks for your reply.

After an update from SDKV2.0.0 to V2.4.0 we experienced huge differences in the overlay file handling. Needed to spend a considerable amount of time to get the project working again. That was the reason to postpone further updates of the SDK until the project we are working on is ready.
In a previous question we already asked if there is some LTS version.

RE: nRF Connect for VS Code, connected devices no device found

Elfving — Wed, 13 Sep 2023 07:32:35 GMT

[quote user="BvdP4Celsius"]In general, I am having trouble with VScode and nrf-connect. It seems to me not to be not stable and hard to use. [/quote]

I am sorry to hear that Bob. Of course I want to solve your issue, but please let me know if there are any other things that would make the NCS/VSC a smoother experience for you, and I will bring your suggestion to our VSC team.

[quote user="BvdP4Celsius"]found out that changing the nrf-connect.deviceProvider from nrfjprog to nrfutil solved the issue for now. However I am unable to find the setting nrf-connect.deviceProvider while writing this reply...[/quote]

You should be able to change nrf-connect.deviceProvider by right-clicking the NCS extension, and choosing "extension settings". With the newer versions of the extension it should opt for nrfutil by default.

The issue you're describing is something I've seen in for instance this case here, but I believe it should be solved in the newer versions of the extension. I see now that the customer in that other case actually had to change back to nrfjprog to get it to work on his side.., but either way, have you tried updating?

Regards,

Elfving

RE: nRF Connect for VS Code, connected devices no device found

BvdP4Celsius — Wed, 13 Sep 2023 06:52:35 GMT

Hi Elving,

We don't use the DK, we have a custom board.
In the meantime, I did some testing and found out that changing the nrf-connect.deviceProvider from nrfjprog to nrfutil solved the issue for now. However I am unable to find the setting nrf-connect.deviceProvider while writing this reply...

In general, I am having trouble with VScode and nrf-connect. It seems to me not to be not stable and hard to use.

RE: nRF Connect for VS Code, connected devices no device found

Elfving — Tue, 12 Sep 2023 09:26:20 GMT

Hello Bob,

That is odd. Did you install something recently before rebooting your computer? Could you try running "nrfjprog -i" with the DK turned on and connected? Are any LEDs on the DK on?

Could you show me a picture of the DK? A typical issue is that it has some switches that are flipped to the wrong position. You would for instance have issues communicating with the nRF52840DK if SW9 is flipped to USB.

Regards,

Elfving