Hi,

I’ve been using VisualGDB for quite a while, and in my opinion it is by far the best IDE for the ESP32 family. For other hardware I usually stick to the vendors’ own tools (STM32CubeIDE, Keil, MPLAB X), so I can’t really judge VisualGDB there.

I think the idea behind CodeVROOM is excellent. It has the potential to become the perfect solution for professional coding and especially debugging on ESP32 devices. I gave it a try and was able to create, flash and debug an ESP32 project out of the box, without any hassle. I’m not aware of any other IDE that offers this level of quality without a lengthy installation and configuration process.

One thing I noticed, though: CodeVROOM apparently reused my existing VisualGDB/ESP-IDF installation, since nothing had to be installed. This makes me wonder what the experience looks like on a clean machine without VisualGDB and ESP-IDF. How are the toolchains and tools installed and configured in that case?

This is of particular interest to me because I’m planning to make a YouTube video about CodeVROOM, and I would like to at least mention how the tools get installed. Any information on how the tool installation works on a fresh system would be very helpful.

One drawback I ran into during my first tests: the debugging layout is not preserved. When I arrange the tool windows the way I want them during a debug session (which windows are open and where they are placed), this setup is lost once the session ends. After restarting the debugger, I have to set everything up again from scratch. For daily debugging work this is a significant limitation. Is there a way to save the debug layout, or is this planned for a future version?

I’m going to test CodeVROOM with other ESP32 variants over the next few days and will report back.

Keep up the great work!

Best regards,
Thomas