exit status 1 esp_int_wdt.h: No such file or directory

[lohtse]

why am I getting????

exit status 1
esp_int_wdt.h: No such file or directory

Any help would be awesome please

[tsys83]

please refer to
https://forum.arduino.cc/t/esp32-cam-cant-compile-a-project-from-github/1220008

The Interrupt Watchdog API (functions/types/macros prefixed with esp_int_wdt_) has been made into a private API. Thus, the previous include path #include "esp_int_wdt.h" has been removed. If users still require usage of the Interrupt Watchdog API (though this is not recommended),
it can be included via #include "esp_private/esp_int_wdt.h".

[killamilla0815]

Doesn't work for me: tried to compile with latest Arduino IDE 2.3.2 plus old legacy version 1.8.19 always ends up in a ton of warnings and errors. Finally this project seems be dead, which is really sad.

Finally, the only reason for me to try this version was the internal flash LED, cannot find a way to make it working with the default WebCameraServer for the AIThinker ESP32 CAM board. Anyone has a clue how to access the LED directly from the web-UI there ?

Thanks.

[snafu1282]

I, too, am getting the 'wdt' errors. Adding _esp_private/ in front does nothing. I wouldn't expect it to since there is no folder called esp_private.

While I have a ton of programming experience, very little of it is with Arduino, so I'm in the weeds a bit. Also, yeah, I made the mistake of ignoring Captain America's advice: i.e. I clicked the update button. That's when the issue started. I got 2 esp32cam's configured and working, but clicking update screwed any attempt to program a third one.

It's a shame too because I really like the interface much better than the default one.

I guess my real question is where were the the watchdog files previously; built right into the core? If so, my attempts to revert to ver 2.0.0 didn't seem to help. Anyone got ideas of how to fix it?

[lohtse]

I, too, am getting the 'wdt' errors. Adding _esp_private/ in front does nothing. I wouldn't expect it to since there is no folder called esp_private.

While I have a ton of programming experience, very little of it is with Arduino, so I'm in the weeds a bit. Also, yeah, I made the mistake of ignoring Captain America's advice: i.e. I clicked the update button. That's when the issue started. I got 2 esp32cam's configured and working, but clicking update screwed any attempt to program a third one.

It's a shame too because I really like the interface much better than the default one.

I guess my real question is where were the the watchdog files previously; built right into the core? If so, my attempts to revert to ver 2.0.0 didn't seem to help. Anyone got ideas of how to fix it?

best solution I found was here https://matchboxscope.github.io/firmware/FLASH.html flash either the top left or top middle via the connect button and all is working well with extra options too

https://matchboxscope.github.io/firmware/FLASH.html

[snafu1282]

I, too, am getting the 'wdt' errors. Adding _esp_private/ in front does nothing. I wouldn't expect it to since there is no folder called esp_private.
While I have a ton of programming experience, very little of it is with Arduino, so I'm in the weeds a bit. Also, yeah, I made the mistake of ignoring Captain America's advice: i.e. I clicked the update button. That's when the issue started. I got 2 esp32cam's configured and working, but clicking update screwed any attempt to program a third one.
It's a shame too because I really like the interface much better than the default one.
I guess my real question is where were the the watchdog files previously; built right into the core? If so, my attempts to revert to ver 2.0.0 didn't seem to help. Anyone got ideas of how to fix it?

best solution I found was here https://matchboxscope.github.io/firmware/FLASH.html flash either the top left or top middle via the connect button and all is working well with extra options too

https://matchboxscope.github.io/firmware/FLASH.html

Thanks @lohtse. I will have a look. My real question is "where the heck are the watchdog files now?". Why can't I just download a library of the files and add them to the Arduino installation? It seems a little strange to me. Or is it me. Is there such a library that I can download?

[lohtse]

No worries and happy too help..

As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you...

[snafu1282]

No worries and happy too help..

As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you...

Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors.

[lohtse]

No worries and happy too help..
As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you...

Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors.

I had done that sometime ago and always failed... But thank you for the suggestion..

[burassic]

No worries and happy too help..
As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you...

Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors.

Same problem, v 2.0.17 fixed it, thanks.

[lohtse]

No worries and happy too help..
As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you...

Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors.

Same problem, v 2.0.17 fixed it, thanks.

this one??

If so it made no difference for me... same issues

[burassic]

Yes, selected the drop down - picked 2.0.17, error disappeared compiled straight away. 

…

On 3 Sep 2024, at 13:09, lohtse ***@***.***> wrote: No worries and happy too help.. As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you... Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors. Same problem, v 2.0.17 fixed it, thanks. image.png (view on web) <https://github.com/user-attachments/assets/c167d595-c75a-4e86-b73d-f7de677c7534> this one?? If so it made no difference for me... same issues — Reply to this email directly, view it on GitHub <#313 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5IBCE7WMMUCQAFQVL5IBQLZUWRGHAVCNFSM6AAAAABEHGKR5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRWGM3DANRXGM>. You are receiving this because you commented.

[lohtse]

Yes, selected the drop down - picked 2.0.17, error disappeared compiled straight away. 
…
On 3 Sep 2024, at 13:09, lohtse @.***> wrote: No worries and happy too help.. As too the real questio... yep I completely understand... I did as the dev instructed yet no joy hence now using the link I provided you... Thx again, but I did find another solution. Someone in another thread pointed out that the issue is really with the boards definition file. I went to Boards Manager and installed v 2.0.17 of the Espressif esp32 board. That instantly got rid of the missing wdt errors. Same problem, v 2.0.17 fixed it, thanks. image.png (view on web) https://github.com/user-attachments/assets/c167d595-c75a-4e86-b73d-f7de677c7534 this one?? If so it made no difference for me... same issues — Reply to this email directly, view it on GitHub <#313 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5IBCE7WMMUCQAFQVL5IBQLZUWRGHAVCNFSM6AAAAABEHGKR5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRWGM3DANRXGM. You are receiving this because you commented.

As you can see from previous screenshot thats installed.. and the same issue continues

and infact a second issue appears too
xtensa-esp32-elf-g++: error: unrecognized command line option '-std=gnu++2b'; did you mean '-std=gnu++2a'?
exit status 1
Error compiling for board ESP32 Wrover Module.

[easytarget]

OK; I am closing a lot if issues today, but not this one.. There is useful info here and I want to capture it in my wrap-up

Note that; I am not doing any further development on this. it is old code and somewhat obsolete. I am currently working on retiring it; I will try to link to a more actively updated fork when I do.