Alternative IDE to SES and VSC?

RE: Alternative IDE to SES and VSC?

FZe — Mon, 13 Dec 2021 09:53:54 GMT

Thank you I will disable all optimizations and have a go.

Trond Einar Snekvik Thanks for the CLion tip I will try it out as well

RE: Alternative IDE to SES and VSC?

Trond Einar Snekvik — Mon, 13 Dec 2021 09:44:07 GMT

To add to Einar's answer: We've heard a lot of good things about Jetbrains CLion, which (although it isn't supported by Nordic) does work well with nRF Connect SDK. They aim to support embedded development, and their project model revolves around CMake, just like the nRF Connect SDK. It requires a license, but they offer a 30 day trial period if you'd like to test it. Just note that Nordic will not be able to support you if you encounter any issues.

Regarding VS Code, it's possible to rearrange the sidebar views to your liking by dragging the different sections into different sidebars altogether. For instance, it's possible to put the nRF Connect SDK actions view in the explorer sidebar by dragging its titlebar to the explorer icon, and dropping it somewhere in there.

Microsoft is also working on adding support for a second sidebar. It's still experimental (and a bit buggy, I find), but it does work:

In VS Code 1.63.0, you must first add

"workbench.experimental.sidePanel.enabled": true

to your settings.json. Then, you need to restart VS Code, and press into View -> Appearance -> Show side panel to enable it. Then, you can drag views from the sidebar over to this new panel on the right. Again; this is still a bit buggy, as it's an experimental features, but once it becomes stable, it should help quite a lot with your sidebar switching issues.

RE: Alternative IDE to SES and VSC?

Einar Thorsrud — Mon, 13 Dec 2021 07:34:51 GMT

Hi,

The only IDEs Nordic supports with the nRF Connect SDK is Segger Embedded Studio and Visual Studio Code. Hopefully you will get some feedback on other alternatives from other community members, though.

Regarding problems with stepping and watching variables in SES that sounds like typical problems you get when the code has been built with optimizations. You should normally build without optimization if you want to step and watch variables.