nRF5_SDK

[MikeDale]

None of the examples in the SDK are useable in Visual Studio Code.  All are missing the required application source files

Get this error 

The directory "c:\Users\mtd18\!GD-LT\Concerto\Fanstel\Docs\nRF5_SDK_17.1.0_ddde560\examples\802_15_4\wireless_uart" does not contain an application source.

[Amanda Hsieh]

Hi, 

nRF5 SDK doesn't support Visual Studio Code. See the release note:

The following toolchains/devices have been used for testing and verification:
 
 - ARM: MDK-ARM version 5.25   
 - GCC: GCC ARM Embedded 9.2020-q2.major
 - IAR: IAR Workbench 7.80.4
 - SES: SES 5.42a

Regards,
Amanda H

[MikeDale]

Really!!!!!!!!!!

Nordic's software development tool, Visual Studio Code.  Does not support Nordic's SDK, Software Development Kit.  Correct?

I'm in the solution analysis phase.  Evaluating BT modules.  No budget to start buying software to "try".  Any suggestions?

[Amanda Hsieh]

Hi, 

The Visual Studio Code supports the nRF Connect SDK (NCS). nRF5 SDK is legacy and works with “traditional” IDEs such at Keil, IAR and SES. See nRF Connect SDK and nRF5 SDK statement. 

To work with Visual Studio Code, I would suggest you use NCS. 

-Amanda H.

[Randy Lee]

SES for Nordic parts is free.. It's a great platform to work with that SDK.  The problem is that SDK is also Not Recommended for New Designs (basically) -- all the new stuff is being done on nRF Connect SDK which uses VS Code.  With the nRF Connect SDK you pretty much have to work with Zephyr (as serious design mistake IMHO) whereas you really want to work with FreeRTOS in nRF5 SDK.

Anyway, pick your path and the tools are free either one; they are just mutually exclusive directions.

[EmmaAlva]

With the nRF Connect SDK, you essentially need to use Zephyr (which I believe is a significant design flaw), while many would prefer to use FreeRTOS with the nRF5 SDK.

tiny fishing