Skip to main content
Ryan Gronlie
Associate
April 29, 2025
Solved

CubeMX v6.14.1 has no option for SMBus-two-wire-interface on peripheral I2C2

  • April 29, 2025
  • 3 replies
  • 546 views

STM32CubeMX v6.14.1 (Firmware Package is STM32Cube FW_G0 V1.6.2) has removed the option for peripheral I2C2 to select SMBus-two-wire-interface.

This prevents me from migrating my project as only SMBus-Alert-mode is available but can't be used as the alert pin is already allocated for GPIO. So the CubeMX migration changes I2C2 to I2C mode.

The original project is from STM32CubeMX v6.10.0 and the Firmware Package is STM32Cube FW_G0 V1.6.2

I tried creating a project from scratch and the SMBus-two-wire-interface option just isn't available.

STM32CubeMX 6_10_0.png

STM32CubeMX 6_14_1.png

 

 

Best answer by STTwo-32

Hello @Ryan Gronlie 

It seems to be a wrong behavior on the STM32CubeMX. I've already escalated internally for correction on the Future (under internal ticket number 208843).

 

PS: this has been solved on the version 6.15.0 of the STM32CubeMX.

Best Regards.

STTwo-32

3 replies

STTwo-32
STTwo-32Best answer
Technical Moderator
April 30, 2025

Hello @Ryan Gronlie 

It seems to be a wrong behavior on the STM32CubeMX. I've already escalated internally for correction on the Future (under internal ticket number 208843).

 

PS: this has been solved on the version 6.15.0 of the STM32CubeMX.

Best Regards.

STTwo-32

Visitor II
September 22, 2025

I am having the same issue with version 6.15.0 of STM32CubeMX so I argue that it has NOT been fixed completely.

bradcb212_0-1758580522661.png

I need a workaround or something to fix this. It looks like I can possibly load an old project and modify.

Recommendations?

Associate
January 6, 2026

I can confirm that this is still an issue with version 6.16.1 of STM32CubeMX for the STM32G474.

I really need a fix for this for a critical migration we're doing for a client.

Technical Moderator
February 27, 2026

Hello @redmore ,

This issue is fixed in the latest release of STM32CubeMX v6.17.0.

Thank you for your contributions.

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Technical Moderator
January 6, 2026

Hello All,

I escalated this issue reproduced for the STM32G474 to STM32CubeMX team to take a closer look at the problem (through Internal ticket number: 224666).

I will make sure to post here once I have updates.

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"