Using Eclipse Plugin and idf.py in patallel does not work

RalphD
Posts: 97
Joined: Thu Nov 25, 2021 9:02 pm

Using Eclipse Plugin and idf.py in patallel does not work

Postby RalphD » Sun May 22, 2022 1:54 pm

Once again the Espressif tool chain causes a full stop on a project workflow.

Using Eclipse IDF plugin and IDF 4.4

We have build a small application based on the https-server sample project and have added very small functionality to it including tinyUSB stack used for logging through USB.

It all worked fine, compiling debugging etc.

Then we wanted to use flashing through USB and for this it is required to run idf.py dfu and dfu-flash for flashing through USB.

Consequently we opened the corresponding IDF CMD 4.4 from the windows start menu for performing this task.
Running idf.py dfu caused kicking in git and downloading things. Very surprisingly and unexpected. We have been working until now with Eclipse IDE seamlessly and would never expect this behavior.

the dfu file was build after recompiling.

Since this moment nothing worked at all. Not the unchanged sample projects could be compiled in Eclipse nor our own projects.
The message we got was "tool chain version mismatches"

To fix this we updated the IDF to 4.4.1 following the steps given in the documentation. idf.py builds the projects seamlessly.

However, Eclipse Plugin does not compile the project BUT flashes and debugs the project seamlessly.

The compile is ended with a short message "Build not configured correctly" and then flashed and debugged.

It seems that Eclipse plug in and idf.py do not function together on the same project.

What can we do to recover our custom projects? and what has happened?

However, that is not the end of the story. While all sample projects compile in idf.py fine and run after, our https-server based project does not run at all. It hits a break point at

Code: Select all

cpu_ll_get_cycle_count()
Looking into that, we assume that this may indicate that the ESP goes directly to sleep?

Again, our code was running before without any error or messages. As well this issue appears before any debug or even main() is hit. How to nail this dead end down?

Are we still having version mismatch issues? if so, how can we locate the issue?

Thanks

Who is online

Users browsing this forum: leschge and 134 guests