ESP-IDF: configurations and FLASH programming

Sysprogs forums › Forums › CodeVROOM › ESP-IDF: configurations and FLASH programming

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #37487
    ImHoTep
    Participant

    Hi,

    Thanks for build 0.8.0.391! The Reset Window Layout crash is fixed, and adjusting the layout works better now, although it still doesn’t behave quite as I would expect. Due to time constraints, I’ll leave the layout topic aside for the moment and come back to it later.

    There are two features I really miss compared to VisualGDB, and I’d like to ask whether they are planned:

    1. **Programming without debugging.** In VisualGDB I often use “Program and Start Without Debugging” to quickly flash a change. In CodeVROOM I couldn’t find an equivalent, so I always have to start a debug session just to flash the device. Ideally, this would also work over the UART bootloader (e.g. the ESP-Prog’s serial port) without a JTAG adapter.

    2. **A configuration manager like in VisualGDB.** CodeVROOM offers a Debug/Release selector, but I couldn’t find a way to configure the configurations themselves. For ESP-IDF projects, switching between Debug and Release doesn’t seem to change anything, because both use the same sdkconfig (e.g. the compiler optimization level stays at Debug -Og). In VisualGDB I can create and manage configurations with the Configuration Manager, which is very practical. Are you planning something similar for CodeVROOM, e.g. with a separate sdkconfig per configuration?

    Best regards,
    Thomas

    #37489
    support
    Keymaster

    No problem. Feel free to get back to us with the layout feedback whenever you are ready. We forked this discussion into a separate topic for better tracking.

    Programming without debugging should already work by running “idf.py -B <build directory> flash” in the Smart Terminal, but due to a bug in the menu translation, it was not shown properly for single-target ESP-IDF projects. We have fixed it in this build: CodeVROOM-0.8.0.396.exe. It now appears as a menu command in the project menu. We can also add a command to the debug menu if you believe it makes things more intuitive.

    The debug/release selection currently indeed just affects CMAKE_BUILD_TYPE. The configuration manager from VisualGDB should be fairly straight-forward to port, we just didn’t get to it yet. We will look into it in the next couple of days, and will post another update here.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.