Issue with nRF Connect SDK - Nordic DevAcademy Intermediate Course

[masterLee]

Hi,

I follow the custom board exercise steps with mynRF52840 DK and when I reach step 8.1 , in the deviceTree visual editor, I notice that the GPIO0/1/TE options under "soc" are grayed-out initially and after ticking them, I notice that the .dts file is not updated automatically and also I get the following warning when I open the "Pin Views".

Also I checked the defconfig file and the required flags are set

Now if I press the Add Node button "+"  at the top right corner of the "Pin Views" , then select "Enable peripheral" and then I select the GPIO0/1/TE,  the three nodes are enabled in the Nodes window. and the "Pin Views" and .dts file are also updated as expected.

So, why the first case is not working like the course?

What am I doing wrong here?

[Kazi Afroza Sultana]

Hello,

Which version of NCS are using?

The intermidate course doesn't yet support v2.7.0 or above as outlined here: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/.  

[masterLee]

[Kazi Afroza Sultana]

I have tried this here on my system. It looks ok. I am not sure why there is no pin. Did you follow the steps mentioned in the course documentation? How the board files look like? 

[masterLee]

It seems that it is a version issue... that also exists in version 2.8.0. By enabling the checkmarks does not enable the PIns in the .dts file . I tested it in both versions. For some reason they are not linked in the Devicetree Visual editor. I have downloaded all latest versions.

[Kazi Afroza Sultana]

Hello,

You are correct. It is related to VS code extension version. There will be fixed in next release. Similar issue (+) Nordic DevZone.

[masterLee]

Yes , when is the next version going to be released ....

[Kazi Afroza Sultana]

There should be some fixed-on NC v2.9.0. I can see one fix here https://github.com/nrfconnect/sdk-nrf/pull/18420. 

[masterLee]

When should I expect a reliable stable version???

Tell me again why developers should move to nRF Connect SDK with zephyr in VSCode?
Is it because
a) it is stable?
b) it is easy to migrate from bare metal nRF5 SDK? 
c) it has Short development time?

Because I have not seen any of those things so far.

You are supposed to make it easier for developers that already have to struggle with prototypes custom boards etc...

Issues on your software tools should be identified first by your testers team... not wait for it from the end users...

Bottom line you have great hardware, good job! 

Your  VSCode development tools...not even close...

As I said before if it is not ready, please, don't recommend it for new designs.