GDBstub for ESP32S3

Sysprogs forums Forums VisualGDB GDBstub for ESP32S3

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #36964
    mattia
    Participant

    Hello,

    I’m using an ESP32-S3 with VisualGDB 6.0R8 build5338 Custom Edition. I’m developing an application with USB MSC pendrive that must be connected to ESP32S3. In this way, I can’t debug anymore. Is there a way, using GDBStub, to debug as usual? How can I do?

    Thanks,

    Mattia Berton

    #36967
    support
    Keymaster

    Hi,

    We are not aware of any gdb stub for ESP32S3 that would do full debugging (more than analyzing a crashed device without stepping/running it).

    You can try asking Espressif for more details.

    #36968
    mattia
    Participant

    What I mean is this example: https://github.com/espressif/esp-idf/tree/master/examples/system/gdbstub, but as far as I can see, it uses only idf.py, and I don’t know if I can integrate in VisualGDB. What do you think?

    #36969
    support
    Keymaster

    Please make sure you can get it fully working outside VisualGDB first. Once it works, please feel free to share your findings (what exactly you did and what results you observed) and we will help you configure VisualGDB to replicate the results.

    Update: we have done some brief experiments with a regular ESP32 chip with mixed results. Cloning the example you mentioned does get the stub running, but trying to connect gdb to it fails with the “no registers” message, that would typically happen if the stub and the gdb executable used incompatible register formats. Given that the official documentation still only mentions the panic mode, and that the GDB stub setting is hidden from the regular configuration menu, looks like the stub might not be production-ready yet.

    Either way, you can configure VisualGDB to use the stub as shown in the attached file (also add “set serial baud 115200″ to Additional GDB Commands -> Before Selecting a Target), but there are some caveats (e.g. you would need to program the FLASH memory manually first, and connect to it in terminal and press Ctrl-C to trigger a break-in). If anyone can confirm that they get reasonable performance when using the stub, we will happily add streamlined GUI to launch it out-of-the-box.

    Attachments:
    You must be logged in to view attached files.
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.