nRF Connect / VS Code broken for M1 Mac users

[Scott]

There are at least several show-stopper level issues with your nRF Connect SDK and VS Code for M1 Mac users

First not supporting the native VS Code app is annoying and forces us to use a much slower non-native Intel based build

Second - even after installing that, I'm stuck forever in nRF Connect for Desktop on « Checking if VS Code and dependencies are installed »

Third after going around that and installing directly in VS Code [ which incidentally seems to kind of work in the M1 based VS Code ] I get a lot of «

[west]: warning: templates not found in /usr/local/Cellar/git/2.32.0_1/share/git-core/ » warnings

Fourth - just with the basic hello_world sample app, compilation fails because zephyr.h and sys/printk.h are not found

Fifth - spaces and other perfectly valid characters in filenames/directory names are not allowed 

I definitely / strongly prefer this to the SEGGER studio requirement ( which is annoying because of the licensing hoop and just because I don't want to use or mandate our developers use a specific IDE ) but there are a lot of issues that desperately need to be addressed before this is viable in production for anyone who doesn't have a lot of time and resources to burn getting things to work

[manav]

Have been facing the same issue. This is certainly not encouraging to use these boards. No support at all, i have checked all the other threads related to this issue.

[Sigurd Hellesvik]

Hi Manav

If you are experiencing your own version of this issue and the information in this case is no enough for you, please open a new ticket, and we will help you.

Regards,
Sigurd Hellesvik

[Scott]

It's so frustrating.

I like and have a longstanding relationship with Nordic. I generally like and want to use their products. Unfortunately things like this make it almost impossible.

We finally gave up on using the nRF Connect SDK because of this and reverted to the deprecated nRF5 SDK which means we are stuck on the 52832/52840 and can't move to some of their newer and more exciting chips without a significant rewrite 

Sigurd Hellesvik the issue isn't obscure and there is no need for additional tickets.

M1 Mac support is spotty and incomplete which makes your nRF Connect SDK and MS Code integration useless for many of us. Fix that and you'd be helping many of your users immensely. Don't and we'll be reluctantly forced to migrate away from your silicon

[Sigurd Hellesvik]

Hi

Our developers are working on M1 support for our tools.

Unfortunately, we are not yet able to give a time estimate on when it will be finished.

Regards,
Sigurd Hellesvik

[Scott]

Good to hear that.

It's fine because we've given up on this and have already invested a great deal of time doing development using the antiquated nRF5 SDK instead and we won't have time to spend porting to the nRF Connect SDK anytime soon