No Toolchain found for Target Local error

[aestetix]

I have installed Eclipse and followed the instructions to set up for ESP32 development but with the blinky example I get a "No Toolchain found for Target Local" error.

I don't actually have an ESP32, I am just trying to build the example code before buying a dev board.

Windows 8.1
Eclipse 20200313-1211
Python 3.7.7 (also tried 3.8.2)
IDF 3.3.2
Git installed and working
ESP-IDF plugin 1.0.1 from marketplace
ESP32 C/C++ development tools from marketplace

After installation I selected Help->Expressif IDF Tools Manager->Install Tools. Python was detected, set correct paths for the other things. Tried it again just now, output as follows:

Code: Select all

Installing tools...
This can take a while. Please be patient.
Executing C:\Users\****\AppData\Local\Programs\Python\Python37\python.exe D:\esp32\esp-idf-v3.3.2\tools\idf_tools.py install all
Installing tools: xtensa-esp32-elf, esp32ulp-elf, cmake, openocd-esp32, mconf, ninja, idf-exe, ccache
Skipping xtensa-esp32-elf@1.22.0-80-g6c4433a5-5.2.0 (already installed)
Skipping esp32ulp-elf@2.28.51.20170517 (already installed)
Skipping cmake@3.13.4 (already installed)
Skipping openocd-esp32@v0.10.0-esp32-20190313 (already installed)
Skipping mconf@v4.6.0.0-idf-20190628 (already installed)
Skipping ninja@1.9.0 (already installed)
Skipping idf-exe@1.0.1 (already installed)
Skipping ccache@3.7 (already installed)

Executing C:\Users\****\AppData\Local\Programs\Python\Python37\python.exe D:\esp32\esp-idf-v3.3.2\tools\idf_tools.py install-python-env
Requirement already satisfied: setuptools in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from -r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 4)) (46.1.3)
Requirement already satisfied: pyserial>=3.0 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from -r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 8)) (3.4)
Requirement already satisfied: future>=0.15.2 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from -r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 9)) (0.18.2)
Requirement already satisfied: cryptography>=2.1.4 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from -r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 10)) (2.9)
Requirement already satisfied: pyparsing<2.4.0,>=2.0.3 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from -r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 11)) (2.3.1)
Requirement already satisfied: six>=1.4.1 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from cryptography>=2.1.4->-r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 10)) (1.14.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from cryptography>=2.1.4->-r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 10)) (1.14.0)
Requirement already satisfied: pycparser in c:\users\****\.espressif\python_env\idf3.3_py3.7_env\lib\site-packages (from cffi!=1.11.3,>=1.8->cryptography>=2.1.4->-r D:\esp32\esp-idf-v3.3.2\requirements.txt (line 10)) (2.20)
Installing Python packages from D:\esp32\esp-idf-v3.3.2\requirements.txt

Executing C:\Users\****\AppData\Local\Programs\Python\Python37\python.exe D:\esp32\esp-idf-v3.3.2\tools\idf_tools.py export --format=key-value
OPENOCD_SCRIPTS=C:\Users\****\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190313\openocd-esp32\share\openocd\scripts
IDF_PYTHON_ENV_PATH=C:\Users\****\.espressif\python_env\idf3.3_py3.7_env
PATH=C:\Users\****\.espressif\tools\xtensa-esp32-elf\1.22.0-80-g6c4433a5-5.2.0\xtensa-esp32-elf\bin;C:\Users\****\.espressif\tools\esp32ulp-elf\2.28.51.20170517\esp32ulp-elf-binutils\bin;C:\Users\****\.espressif\tools\cmake\3.13.4\bin;C:\Users\****\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190313\openocd-esp32\bin;C:\Users\****\.espressif\tools\mconf\v4.6.0.0-idf-20190628\;C:\Users\****\.espressif\tools\ninja\1.9.0\;C:\Users\****\.espressif\tools\idf-exe\1.0.1\;C:\Users\****\.espressif\tools\ccache\3.7\;C:\Users\****\.espressif\python_env\idf3.3_py3.7_env\Scripts;D:\esp32\esp-idf-v3.3.2\tools;%PATH%

Hit ctrl-B and get the "No Toolchain found for Target Local" message. No other targets are defined.

Any assistance would be appreciated.

[ESP_kondalkolipaka]

Hello aestetix,

We appreciate your interest. You should be able to compile a project without having a dev board in hand. Just that, you need a create an ESP launch target as mentioned here https://github.com/espressif/idf-eclips ... unchTarget

While creating a launch target, you can mention any serial port - it doesn't matter at this level. But the same serial port will be used while flashing an application to the board.

All the best!

[aestetix]

Thanks, I can build it now. I followed your instructions and they didn't work, I still couldn't build by pressing ctrl-B. But then I clicked on the build icon in the toolbar and it built OK, and after that I could use ctrl-B as well. Some kind of first-run bug.

I still get a lot of errors in the editor though, it doesn't seem to have picked up any of the include files from the IDF.

[ESP_kondalkolipaka]

Hello,

Unresolved errors will disappear only after the build. Looking at your project structure, I don't see the "build" folder so I'm assuming build didn't happen.

[aestetix]

Oh, I must have taken the screenshot before the build completed, my mistake.

Anyway it is built and the errors have not resolved.



In any case I also tried VS Code and it seems to work a lot better. None of those errors and worked first time, although I did have to have a USB serial converter plugged in to give it a serial port to use.

So my question is is VS Code as good as Eclipse for ESP32 development? Is there some advantage to Eclipse? Because VS Code seems a lot better, Eclipse appears to just be broken on Windows.

[ESP_kondalkolipaka]

Try the following and see if it helps.

Code: Select all

Project > C/C++ Index > Rebuild

Can you also provide the below files to troubleshoot the issue?

Parser log:

Code: Select all

Project > C/C++ Index >  Create Parser Log

Compiler_commands.json file for the project:

Code: Select all

/blink/build/compile_commands.json

VSCode and Eclipse provide the more or less same set of features. We will leave it to the users based on the their preference.

[aestetix]

The JSON file had to be renamed to be attached and I redacted my username from it. My username does not contain spaces or any characters apart from basic English alphabet ones.

Thanks for the support.