I get a warning every time I launch SES of cmsis header files that exist and dated later...

[Antonio]

After I select Yes to All, or No to All, it tells me to get I license, which I just click continue, and then after that everything works fine.

The install is kusher according to guidelines of how to install nRF Connect, even checking each step with the "Getting Started Assistant" that comes with nRF Connect v3.3.0. I have done it several times, each time with a new virtual machine.

I can compile, flash and execute samples in both nRF91 as well as nRF52840, both using SDK 16 and nRF Connect SDK, using SES as is.

Configuration:

- Mac pro running catalina and parallels

- Windows 10 with all updates

- SES 4.20a

- ncs in c:\ncs

- ses is in c:\ncs\SES

- nrf v1.1.0

I am attaching the message that I receive.

Please advise.

Thanks!

[Susheel Nuguru]

This is the conflict between the Nordic SES version and the segger installed version. It really does not matter what option you choose there and the project should open normally.  It is a bit annoying, but not a blocker for the work I hope. We are trying to address this in the future versions.

[Antonio]

Thank you Susheel for the prompt response.

Is there a known workaround, like a special version of segger that will work, or maybe the order of installation?

[Susheel Nuguru]

I haven't tested this but one of our colleague says that removing the Nordic version of SES folder fixes the error

If you deleted the "Nordic" V3 folder, the error does not occur. But then you need to re-license.

We here at devzone channel do not have a privilage to talk about fix versions, but I can say that this is being looked at.

I hope this helps.

[Antonio]

I think I did it wrong, because it did not work. When I execute SES it creates the Nordic folder again.

I think I'll just wait for the fix

[navigator]

Ok, those errors were starting to run me down.  Especially since other folks in the office look to me to setup things nicely for them.  And it hasn't been pretty with the nag screens...

Here is a workaround for SES 4.42a using Windows 10.
I cooked up a script to clean up the directory mess, then enter into SES 4.42a without any warnings and yes, it still keeps your license.

1. Create the following script and adapt paths as needed.
2. Call it emStudioWorkaround.bat, and put it wherever you like.
3. Add a shortcut to it on your desktop, and change properties so it starts in a minimized window.
4. Lastly, assign an icon to the shortcut.
Browse to emStudio.exe and assign the official Segger icon to your new script.

rd "c:\users\YOUR_USER_NAME\nordic\segger embedded studio\v3\packages" /s /q
c:
cd "c:\YOUR_SES_INSTALL_PATH\arm_segger_embedded_studio_v442a_win_x64_nordic\bin"
start emStudio.exe

Works like a charm for me.
Enjoy!

[Antonio]

Thank you navigator!!! Worked like a Charm.

In my case, since I am using this also for SDK16, I placed the batch file inside the directory where the emProject is:

This is project_name.bat:

rd "c:\users\YOUR_USER_NAME\nordic\segger embedded studio\v3\packages" /s /q
start project_name.emProject

Enjoy!