The decoder does not support ESP32 1.x platforms, such as 1.0.6

[Baxtouxe]

Hi, I can't figure out how to use the decoder. I keep getting this error :

ESP Exception Decoder
Sketch: sketch_mar21a FQBN: esp32:esp32:esp32

Could not detect the GDB tool path

----------------------- Board dump attached

board_dump.txt

---

[kittaakos]

Hi, thank you for giving the extension a try.

I assume you've seen that someone had a similar issue and mentioned that reinstalling the platform fixed it: #15 (comment). I didn't find any suspicious entries in the board dump, but please confirm you have the additional URL set in the IDE's boards manager for the ESP32 platform.

It would be really helpful if you could gather and share more logging data. To do so, follow the steps outlined here: #10 (comment).

Could you also let me know which version of the Arduino IDE and which version of the ESP32 platform you’re using? Knowing more about your setup will make it easier to find a solution.

[Baxtouxe]

Hi,

I have this additional URL : https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json

I'm using Arduino IDE 2.3.4
I was using ESP32 platform1.0.6
I tried to do do a simple update to 2.0.17 of ESP32 platform and it does works. (I have to make make work with 2.0.17 now)
Reverting back to ESP32 platform 1.0.6 made the problem come back again.
Is the extension not compatible with ESP32 platform 1.0.6?

[kittaakos]

I was using ESP32 platform1.0.6
I tried to do do a simple update to 2.0.17 of ESP32 platform and it does works. (I have to make make work with 2.0.17 now)

Thank you for your efforts in seeking a solution and sharing your findings with us. You're the best

I was using ESP32 platform1.0.6

The latest ESP32 platform version is 3.1.3; I have not tried it with all possible ESP installations, but it used to work with 2.x and now with 3.1.1

Is the extension not compatible with ESP32 platform 1.0.6?

If you see Could not detect the GDB tool path, it's probably not compatible.

Is there a reason you have to stick to 1.x? I might add a fix, but it's not my highest priority to add a patch for a four-year-old release.

[Baxtouxe]

Thank you for your efforts in seeking a solution and sharing your findings with us. You're the best

Of course! It's a pleasure. It worked very well after switching to 2.0.17, I found the reason for the crash immediatly.

I was sticking to 1.x because it was a old and big project. It wasn't that easy to switch to 2.0.17
I was able to port it though, but took me a while to do so.