nRF Connect SDK - Create a new application is missing the latest versions

[Saxman58]

I am using the latest (I believe) nRF Connect for VS Code extension, version 2024.12.55.  But when I "Create a new application" and pick the ncs-example-application, it only offers me up to v2.6.0 as seen below:

But the GitHub repository has newer versions, matching the later SDK versions.  Does the VS Code extension need to be updated?

If I want to base my application on v2.6.1 or v2.6.2, how would I do that?  The GitHub ncs-example-application repo only has the application files, not the full west application environment and matching version of the SDK that is installed by the VS Code extension "Create new application" script.

[dejans]

Hi,

I am using the latest (I believe) nRF Connect for VS Code extension, version 2024.12.55.

But the GitHub repository has newer versions, matching the later SDK versions.  Does the VS Code extension need to be updated?

You already have December 2024 release of the nRF Connect for VS Code, and you do not need to update your extension. Please note that release version 2024.12.55 contains major changes in dealing with SDK and Toolchain. You can find more information in version 2024.12.55 release notes.

ncs-example-application has its own west.yml file with the structure similar to what is shown in the T2 topology. After initialization and update (using west update) you should have everything that is needed to run the application also in NCS versions above v2.6.0.

I tried to replicate your issue but without success. I have followed Getting Started Guide and used the same method for initialization as described in the application's README file. Have you followed the same guide?

Best regards,
Dejan

[Saxman58]

Hi Dejan,

It looks like I get what I need by editing the sdk version in the application west.yml file and then running west update.

I just expected that the pulldown list of SDK example application options in VS Code would match what you have in the GitHub repository (adding 2.6.1, 2.6.2, 2.7 and 2.8).  The pulldown menu in the screenshot only goes to 2.6.0.  And I tried the same thing on a Windows machine (the other is a Mac) and see the same thing.  The nRF Connect for VS Code release notes point to this page, which mirrors the example application versions stopping at 2.6.0:

https://nrfconnect.github.io/ncs-app-index/

So it appears that the only way to get the later versions is to first install 2.6.0 and then upgrade the SDK and possibly the example code.

I thought that I had everything installed right since I can compile and run my own and example apps as standalone (and the T2 topology based BME280 driver course example).  Are you saying that you see later versions than 2.6.0 when you do the following in VS Code?:

Create a new application --> Browse nRF Connect SDK Add-on Index --> nRF Connect SDK example application

Glen

[dejans]

Hi Glen,

Saxman58 said:

It looks like I get what I need by editing the sdk version in the application west.yml file and then running west update.

This is great to hear.

Saxman58 said:

I thought that I had everything installed right since I can compile and run my own and example apps as standalone (and the T2 topology based BME280 driver course example).  Are you saying that you see later versions than 2.6.0 when you do the following in VS Code?:

No, I did not see any versions of the application beyond v2.6.0 in VS Code. I focused on testing if the application can be run successfully using versions later than v2.6.0 even though there is no such version in the "Create New Application from index" drop-down list.

Saxman58 said:

So it appears that the only way to get the later versions is to first install 2.6.0 and then upgrade the SDK and possibly the example code.

Could you clarify "the only way to get the later versions"? Do you mean getting later versions of the application to show up in the "Create New Application from index" drop-down list or something else?

Best regards,
Dejan

[dejans]

Hi Glen,

I have also checked the reason for this issue internally. The reason why you do not see any versions beyond v2.6.0 is because NCS Addons changed the policy of listing new releases and now each new release needs to be manually merged into the index. However, this has not been done yet by the owners of the ncs-example-application. Therefore, you will not see any newer releases until they are merged.

Best regards,
Dejan

[Saxman58]

Yes, that's what I meant.  I'm happy with manually updating, but I just wanted to let you know that the newer versions were missing from the drop down list.