SES NCS seem to build ok but throws "Error starting process echo"

[Smart.Enrg]

Hi

When I try to build NCS sample using SES (v5.40, also v5.30a nordic edition) it seems to build the project correctly (.elf, hex are generated) 
But it throws error at the very end (screenshot attached) "Error starting process echo".

What's the significance of this and how to resolve this issue? Please advise.

[Øyvind]

Hello, 

Can you please elaborate on your setup? Are you using a manually installed NCS, or are you using the Toolchain Managar? What version of NCS are you using? What project are you trying to build?

Segger Embedded Studio 5.30a Nordic Edition is the latest supported version for NCS. Can you provide settings from Tools -> Options -> nRF Connect?

Thank you!

Kind regards,
Øyvind

[Smart.Enrg]

Thanks Øyvind,

I am using Windows 10 and NCS installed by Toolchain Manager (v.0.9.1), from nRF Connect v3.6.1. Trying to build
for nrf52833dk_nrf52833 as target board. 

NCS version 1.4.99-dev1 - though v1.4.2 behaves the same. Couldn't try v1.5.0-rc1 yet Toolchain manager is having
trouble validating some repo it downloaded/ trying to download, will try that ASAP.

Tried with SES Nordic edition 5.30a, and the latest SES Nordic edition 5.34a. Non Nordic SES 5.40 behaves exactly
the same - i.e. builds to .elf .hex fine yet throws Build failed "Error starting process echo" 
Button "Open IDE" in front of NCS v1.4.2 in Toolchain Manager seem to launch SES v5.10d, same result though for 
Openthread coap_client or CLI project builds.

Tried different examples, instance shown below captured with ncs\v1.4.99-dev1\nrf\samples\openthread\coap_client

Øyvind said:

Segger Embedded Studio 5.30a Nordic Edition is the latest supported version for NCS. Can you provide settings from Tools -> Options -> nRF Connect?

When I try to build simple blinky project toolchain v1.4.2 or 1.4.0 - that seem to build well, no error

While trying different combinations for documenting this issue came across this new error - not sure what's that about?

P.S. One of my colleagues reported this error does happen for him too under Windows 10, but not under Ubuntu.

Please advise. Thanks