[cbridge] *cgen.yml Not Generated When All Peripherals Use LL Drivers

[DavidLesnjak]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When all enabled peripherals in STM32CubeMX are configured to use LL (Low-Layer) drivers only (i.e., no HAL drivers), cbridge fails to generate the MX_Device.h and *cgen.yml files.

Root Cause
STM32CubeMX does not generate the *_hal_msp.c file when no peripheral uses the HAL driver. Since cbridge relies on this file to extract pin configuration data, the generation of related output files fails.

Expected Behavior

Even when only LL drivers are used, cbridge should still be able to generate the required files.

Steps To Reproduce

1. From VSCode project lanch STM32CubeMx
2. In Project Manage -> Advanced Settings -> Driver Selector set RCC to LL
3. Click GENERATE CODE
4. Notice that expected MX_Device.h and *cgen.yml are not generated

Affected operating systems

• Windows amd64
• Windows arm64
• Linux amd64
• Linux arm64
• MacOS amd64
• MacOS arm64

Environment

No response

[jkrech]

@DavidLesnjak is this fixed with the latest patch release of CubeMX 6.14.1
If not, would you see a way forward for cbridge to workaround this "bug"?

If there is no *_hal_msp.c file to extract the pin information from, where would we get this information from instead?
Is this mentioned in the release notes?

[DavidLesnjak]

@DavidLesnjak is this fixed with the latest patch release of CubeMX 6.14.1 If not, would you see a way forward for cbridge to workaround this "bug"?

If there is no *_hal_msp.c file to extract the pin information from, where would we get this information from instead? Is this mentioned in the release notes?

@jkrech, sorry — I overlooked this earlier.
As far as I know, this issue has not yet been addressed.

The following is just off the top of my head, not double-checked:
The MX_Device.h file is primarily generated to configure CMSIS-Drivers, which rely on ST’s HAL drivers underneath.
If no HAL drivers are enabled in STM32CubeMX, we could simplify cbridge by skipping MX_Device.h generation entirely — or at least, if there is no *_msp.c file present, omit generating the data that would normally be extracted from it.