Skip to main content
Suess
Associate III
August 10, 2026
Question

STM32CubeMX2 Feedback: Promising with some usability issues

The new tooling is nice and the UI is much cleaner to navigate with.

Positive Feedback ​@MorkBeck:

  • We love the VS Code direction
  • YES, it would be helpful to get H5 on here as well as it would keep our code bases aligned.
  • AI? No thank you, “focus to stay on reliability, documentation quality, and API maturity”. As anyone savvy knows, AI scrapes those docs anyways. Good docs and samples help a lot.

A few of issues we’re running into that are major speed bumps. I don’t know where your bug list is at to report or to see if it’s tracked:

  • Code Generation overwrites our `main.c` EVERY TIME. Yes it’s documented above, yet this is painful.
  • The `*.c.base@x.y.z” files are just absolute clutter!  “YAGNI” - You Ain’t Gonna Need It
    • And i can’t disable it either, that option is always grayed out.
  • Upgrading from CubeMX2 v1.01 to 1.1.1
    • Broke the EXTI configuration screen, and the page NEVER renders.
    • Causes other lack of functionality issues
    • Feel free to reach out to me.
  • Inability to pull Packs dynamically from command line (i.e. like PlatformIO does or NuGet packages)
    • These things are 45.9 MB for a 300 KB project. That’s insane when you have Bootloader + OpCode in a repo (90mb??)
    • We got do do a workaround by creating 5 new repos to maintain via Git Submodule versus treating it like a downloadable artifact on build servers.
    • Also, regenerating via CubeMX2 wipes out our “main.c”, can’t do that either.
  • CMake build configurations “Debug” and “Release missing on generation
    • It makes a “_debug_gcc_stm32c563ret6”. TL;DR: “Debug” suffices.
    • Never generated one for release builds.
    • From what I can tell, CubeMX2 only generates for one MCU only anyways.
  • An improved “.gitignore” would be helpful as we don’t really need:
    • .settings/exported-files.json
    • *.c.base@*
    • *.ld.base@*
    • compile_commands.json  ← Auto-generated by compiler
    • .clangd      ← Auto-generated by compiler
    • And any other extra generated slop
  • “.settings/exported-files.json” is picking up on “Build” folder artifacts
    • Build isn’t even in source control; adding an extra 1129 lines.

We all know Rome wasn’t built in a day. Looking forward to the future progress.

    2 replies

    Amel NASRI
    Amel NASRI
    ST Technical Moderator
    August 18, 2026

    Moved from Introducing STM32CubeMX2, a new flavor of STM32CubeMX tool for tracking and follow-up purpose.

    To give better visibility on the answered topics, please click on "Best Answer" on the reply which solved your issue or answered your question.
      MorkBeck
      MorkBeck
      ST Employee
      September 14, 2026

      Hi Suess,

      Thank you for the write-up. This is the most useful kind of feedback we get, and it is specific enough to act on, so let me go through it.

      First, on where to report: there is no public bug list. This forum is the right place, and I carry what lands here into our internal tracker.

      main.c overwritten on every generation. You are right, and documenting it is not an answer. We have it recorded as something regeneration has to stop doing. We are working in multiple ways to make regeneration a better experience! 

      The *.c.base@x.y.z files, and the greyed-out option. Taken, including the part where you cannot switch it off. The greyed-out option looks like a defect rather than a decision, and I'll come back on that one.

      Debug and Release build configurations. This is in scope for 1.2.0, and the build profile option — debug, release or both — landed in our internal builds at the end of August.

      EXTI screen never renders after 1.01 → 1.1.1. ​@Sara BEN HADJ YAHYA tried to reproduce this and could not. Could you give her your OS, the exact versions you moved between, whether the project was originally created in 1.01, and whatever the logs show? She'll take it from there. You also mention "other lack of functionality issues" — if you can name them, please do.

      Packs from the command line, and 45.9 MB for a 300 KB project. No commitment from me today. The size and your submodule workaround are what I'll carry into the discussion — five repos to keep one small project reproducible on a build server is a real cost.

      .gitignore, and exported-files.json picking up build artifacts. Both fair. The exported-files.json one reads like a straight bug.

      On H5: heard, and not only from you. There's no committed family list beyond what ships today, so I won't promise it.

       

      Mads, CubeMX2 marketing manager
       

        Terms & ConditionsAccessibility statement