Hi,
This ticket is related to ticket #294825, but I wanted to separate out one definite issue into a separate ticket so it can be more carefully addressed.
The issue is related to these variable definitions in settings.json shown below. In this particular case I am using code from SDK v2.0.2 and a v2.0.0 toolchain, but you can prove to yourself that the same problem will occur if the SDK and the toolchain match. Now, the strange toolchain.path below is the correct path but with some TYPOES inserted. With the typos (or typoes), there is no problem generating support information. HOWEVER, if I remove the TYPOES and spell the toolchain path correctly, then the support information is not printed in the nRF Connect OUTPUT terminal window. If I create a phony toolchain directory (mkdir /home/burt/phony/toolchain) and set the toolchain path to that, the support information is printed. Only with a real toolchain path is the problem seen.
Also please note that up until a short while back, when I tried "the trick" and closed out VS Code, when I restarted it the path would get rewritten to the actual correct path--the one that stops the console output of support information. It's a bit of a mystery what I changed but now that weirdness is not happening. I thought adding the topdir made a difference, but that does not seem to matter.
Please investigate this thoroughly--it won't disappear by my wasting time creating virtual machines, and so forth. Even if there was something weird in my workspace, the system needs to be robust enough to help the user find any fault. But I doubt there are any faults in my downloaded SDK.
Ubuntu 22.04.1 LTS is the operating system.
