After trying the tutorial, the process works, but when am about to install the SDK the file corrupts, And I want to ask if you think this fault could be from my system
Hi, I am on a MacBook Pro with Apple Silicon running Sonoma. the #include in the tutorial are all unable to find the , , . Thoughts other then sending me to tech support? Something I missed in your video setup?
Hi. nRF Connect for VS Code might show some error squiggles for header files not found for an unbuilt application. These errors will automatically be resolved once you add and build a build configuration. /Robin
Hello, I did exactly (the one exception being that I already had the Segger jlink software installed directly from Segger so the nrf command line tools installer didn't need to also install jlink) as your video instructed, and I am running into an issue. The nRF Connect for VS Code extension cannot validate the toolchain and gives this error message: "jlink is required but not found. Please ensure that SEGGER J-Link Software and Documentation Pack is installed." VS Code, jlink, the nRF Connect extension, the nRF Command Line Tools, installed toolchain and SDK are all on the latest version. Any ideas why I might be running into this and how I can solve it? I'm on Windows 11, and my jlink install is located at C:\Users\USER\SEGGER
Hello, which J-Link version do you got? We suspect it has to do with wrong version or that nRF Connect SDK or toolchain do not find the J-Link. Have you tried uninstall and installing the J-Link as instructed in the video and documentation? If you still are facing error, please reach out directly to our tech support team on DevZone with further details on the error: devzone.nordicsemi.com/
Is it possible to install the nRF Connect extension for VScodium? I prefer more private IDE without telemetry.
Of course
You can add extension sources from VSCode and just use it like that
That makes it literally the same, but just without telemetry)
After trying the tutorial, the process works, but when am about to install the SDK the file corrupts,
And I want to ask if you think this fault could be from my system
We would require more details to know for sure. Please contact our tech support team directly on DevZone: devzone.nordicsemi.com
Hi, I am on a MacBook Pro with Apple Silicon running Sonoma. the #include in the tutorial are all unable to find the , , . Thoughts other then sending me to tech support? Something I missed in your video setup?
Hi. nRF Connect for VS Code might show some error squiggles for header files not found for an unbuilt application. These errors will automatically be resolved once you add and build a build configuration.
/Robin
Hello, I did exactly (the one exception being that I already had the Segger jlink software installed directly from Segger so the nrf command line tools installer didn't need to also install jlink) as your video instructed, and I am running into an issue.
The nRF Connect for VS Code extension cannot validate the toolchain and gives this error message: "jlink is required but not found. Please ensure that SEGGER J-Link Software and Documentation Pack is installed."
VS Code, jlink, the nRF Connect extension, the nRF Command Line Tools, installed toolchain and SDK are all on the latest version. Any ideas why I might be running into this and how I can solve it?
I'm on Windows 11, and my jlink install is located at C:\Users\USER\SEGGER
Hello, which J-Link version do you got? We suspect it has to do with wrong version or that nRF Connect SDK or toolchain do not find the J-Link. Have you tried uninstall and installing the J-Link as instructed in the video and documentation? If you still are facing error, please reach out directly to our tech support team on DevZone with further details on the error: devzone.nordicsemi.com/
@@NordicSemi I was able to get help on devzone, turns out that the JLink install was in my user directory instead of Program Files, thanks!
@@EthanFischer-e2n glad to hear you got help. Thanks for letting us know.