thanks for your response. To be honest, I'm afraid I don't really understand what you mean by your hint. How could the USB config keep the ESP32 in download mode? Could you provide me a clue where I have to look at?
Update: I was able to find a solution for this rather generic problem.
The root cause was a circular dependency between the prebuilt library and the application code: The library depends on the application to implement "prebuilt_ext_func()" while the application depends on the library to implement ...
As my demo only was a modification of the official IDF "import_prebuilt" example I expected this construct being correct. Nevertheless, I tried to extract the 'prebuilt' subproject from the example as you proposed. But the result is exactly the same .
thanks for your thoughts. I intentionally avoided to mix up the example with C++ files as I'm aware of the name mangling pitfall in that case. To be honest, my real application uses C++. But as the simplified, plain C example revealed it's not caused by that topic.
I have a curious linker problem with an "extern" declared function in a prebuilt library which I don't really understand.
Short background: I got a prebuilt static library (.a) that requires some functions to be defined by the application to result in an executable. Let's call such a function ...
I had this problem too, but I was developing with the latest ARDUINO framework,
When you say you "had" this problem does it mean you found a solution? As the Arduino framework is "just" a further abstraction layer it may be worth if you could share your ...