I am running an iMac with Apple Silicon and the fully updated OS.
I have installed Visual Studio Code - see below for the full details.
I have installed the Espressif IDF V1.4.0 from the Extensions list in VSCode.
As per the video at https://www.youtube.com/watch?v=Lc6ausiKvQM I typed in the 'Configure ESP_IDF Extension'. I then get the windows that says "...First, install the ESP_IDF Prerequisites for MacOS..." that links to https://docs.espressif.com/projects/esp ... setup.html and I make sure that everything is installed. I have also edited the ".zprofile" file to run the export.sh command.
On restarting VSCode I type the same command but still get the same message about installing the prerequisites.
How can I find what it thinks is missing?
Susan
Visual Studio Code configuration:
Version: 1.68.1
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-14T12:48:37.209Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin arm64 21.5.0
ESP-IDF extension in VSCode on MacOS M1 iMac
-
- Posts: 45
- Joined: Thu Aug 22, 2019 3:48 am
-
- Posts: 45
- Joined: Thu Aug 22, 2019 3:48 am
Re: ESP-IDF extension in VSCode on MacOS M1 iMac
OK - I'll answer this myself!
I went back to deleted everything in the ~/.espressif, ~/.vscode and ~/esp folders and restarted Visual Studio Code again but the issue remained.
I then deleted the above folders PLUS ~/Library/Application\ Support/Code and restarted VSCode. This time I could install the Espressif extension and have it let me configure it as per the video (linked to above).
Looks like this extension doesn't like something that is 'left over' from a previous version of something in VSCode.
Susan
I went back to deleted everything in the ~/.espressif, ~/.vscode and ~/esp folders and restarted Visual Studio Code again but the issue remained.
I then deleted the above folders PLUS ~/Library/Application\ Support/Code and restarted VSCode. This time I could install the Espressif extension and have it let me configure it as per the video (linked to above).
Looks like this extension doesn't like something that is 'left over' from a previous version of something in VSCode.
Susan
Who is online
Users browsing this forum: Baidu [Spider], Google [Bot] and 102 guests