"vscode-ncs-devtools" Repository Does Not Exist

[vindicator]

Archlinux

Visual Studio Code: Version: 1.58.0-insider

nRF Connect: v2021.9.98

I installed the "nRF Connect" extension in vscode, and went to look into a problem I was encountering only to find the "Repository" link points to a non-existent address (https://github.com/NordicPlayground/vscode-ncs-devtools).

So, that's the first issue. The second (original reason) was setting the SDK path...

I originally downloaded and unzipped "nRF5_SDK_17.1.0_ddde560". I figured that'd be what I needed, though it seemed rather sparse compared to what I had been working with for my ST devices.

Later I found "sdk-nrf", for which I downloaded the master branch (--depth 1). That looked more full compared to the other "SDK" I downloaded.

That is the path I used for the SDK in the extension, but it shows "undefined" before the path. I'm going to assume it's because of "tags", which is what I was going to look into in the non-existent repository.

Then when I went to create a new Application, I see "Application template" says "No samples found.", and clicking "Browse" shows no samples and the right-pane shows "No documentation available", even though I am "online", given I was able to download/install the extension.

The SDK path shows the samples directory has 22 other folders, so yeah, there ARE samples even though the extension claims otherwise.

EDIT0: I'm betting my "original reason" is caused by me NOT using "west" to do stuff. I was REALLY "manually" setting things up ("git clone"). I'm thinking I'll be fine without using the extension tool and just manually going deep with it all. It's pretty much how I do it with ST anyway, I just have to find the "DEFINES" needed for my device, which I'm sure is already in the SDK path somewhere.

EDIT1: It's also looking like to me that the NCS is meant to replace nrf5 SDK, so I should just stick with the sdk-nrf repository.

EDIT2: Weird, there's no "Edit" for replies? I'm not seeing any "More" for my reply below that I wanted to edit. In any case, it looks like I may be in a world of hurt if I don't use "west" and all of the dependencies. Python seems to be deeply ingrained in the SDK, as I'm finding while just wanting to build the doc. All starting with the Manifest in "west.yml". Bugger.

[Øyvind]

Hello,

I installed the "nRF Connect" extension in vscode, and went to look into a problem I was encountering only to find the "Repository" link points to a non-existent address (https://github.com/NordicPlayground/vscode-ncs-devtools).

Can you elaborate on how you installed the extension? When installing the nRF Connect for VS Code extension, you should see a Welcome Page similar to this:

I originally downloaded and unzipped "nRF5_SDK_17.1.0_ddde560". I figured that'd be what I needed, though it seemed rather sparse compared to what I had been working with for my ST devices.

Have a look at this blog post on DevZone regarding nRF5 SDK vs nRF Connect SDK (NCS). 

That is the path I used for the SDK in the extension, but it shows "undefined" before the path. I'm going to assume it's because of "tags", which is what I was going to look into in the non-existent repository.

Please make sure to follow instructions provided by our NCS Getting Started documentation. 

nRF Connect: v2021.9.98

I'm not familiar with this version. Is this nRF Connect for Desktop? 

Kind regards,
Øyvind

[vindicator]

I installed it the normal way, through the extension section.

It's just that when you're in that extension and click the "Repository" link at the top, the address doesn't exist.

Good blog post. Even better than the links I found searching about it, and confirms what I figured in my "EDIT".

Yeah, I know about the "Getting Started" and just don't like having those hoops and "extras" to install (I mean why is "west" required when you can just git clone the sdk?), which is why I'm just going to forego it all and just do it all manually. I've already got the SDK and that should be enough (along with ARM gcc and cortex-debug that I already had when working on my ST device).

Mind you this is my first nordic device (the dongle) and I may end up finding somehow that all of those python and west and other dependencies are going to end up being required, but I'll deal with that should I figure out that is the case.

Uhh, okay that's weird. I had already uninstalled the extension and when I went back to look at the version, I now see it as "v2021.9.314". I've NO idea where that other version came from. I'm sure I had just copied/pasted it in here as well. I don't even see how I could've mistyped it if I did type it since it is so far off. In that screenshot I pasted here, it was just taken now.

WOAH! GET THIS!!! I JUST reinstalled it, and that same version shows:

Yeah, I don't know what kind of crazy stuff is happening here...

/home/username/.vscode-insiders/extensions/nordic-semiconductor.nrf-connect-2021.9.98/.github/package.json:

{
	"name": "nrf-connect",
	"displayName": "nRF Connect",
	"description": "Develop applications based on nRF Connect SDK with ease!",
	"publisher": "nordic-semiconductor",
	"author": {
		"name": "Nordic Semiconductor",
		"url": "https://www.nordicsemi.com/"
	},
	"version": "2021.9.98",
	"repository": {
		"url": "https://github.com/NordicPlayground/vscode-ncs-devtools",
		"type": "git"
	},
	...

Heh, that marketplace page you linked to (https://marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-connect-extension-pack), take a look at where THAT "Repository" goes to ("404").

EDIT0: So the "More" button, so I could "Edit" this, didn't show for the reply until I clicked on the time for my reply. Don't know why that was the case.

[Øyvind]

vindicator said:

Yeah, I know about the "Getting Started" and just don't like having those hoops and "extras" to install (I mean why is "west" required when you can just git clone the sdk?), which is why I'm just going to forego it all and just do it all manually. I've already got the SDK and that should be enough (along with ARM gcc and cortex-debug that I already had when working on my ST device).

Yes, you are right. You don't need to use west, the Zephyr meta tool, you're free to use e.g. Ninja to build your project and Git directly if you prefer. 

vindicator said:

Mind you this is my first nordic device (the dongle) and I may end up finding somehow that all of those python and west and other dependencies are going to end up being required, but I'll deal with that should I figure out that is the case.

If this is your first device, then I do recommend getting a proper development kit as the dongle is not designed for easy development. Make sure to read the board documentation, and the Working with nRF52 series.

vindicator said:

Heh, that marketplace page you linked to (https://marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-connect-extension-pack), take a look at where THAT "Repository" goes to ("404").

Thanks for pointing that out. The issue is already reported and will be fixed I am told. 

vindicator said:

EDIT0: So the "More" button, so I could "Edit" this, didn't show for the reply until I clicked on the time for my reply. Don't know why that was the case.

Do you mean the More button in DevZone?

[vindicator]

Hey! Thanks for that non-west link. I had seen those other 2 links already, but hadn't gotten to that one yet until now.

Yeah, for some weird reason that "More" button didn't show... Actually, now I'm getting a better idea of "maybe why".

While I'm replying to your message now, I obviously got the "Reply" "Verify Answer" "More" options to yours, but no other replies, only my main post has "Reply" "Like" "More".

Now while in this reply, I right-mouse clicked the time for my previous reply to open it in a new tab.

For that message, I got the options, but again no other reply had those options.

My expectation would be that every reply would have those options automatically, and I wouldn't have to click on the time for a given message for those options to show up:

[Øyvind]

Hello, my apologies for the late reply. 

Yes, we are aware of the issue and are working to fix this. The workaround is to refresh the page and it will usually be fixed on the first refresh. 

Kind regards,
Øyvind