Hi,
This is caused by what appears to be a bug in the device definitions on the ST side. Different variations of the STM32G431 device are now defined with different memory layouts, so our BSP generation logic treats them as separate devices.
It will likely get fixed in the next BSP version once ST fixes the device definitions. Until then, you can use one of the 2 workarounds:
- Manually edit the BSP.XML file, replacing STM32G431RBIx with STM32G431RB.
- Opening VisualGDB Project Properties and changing the device type from STM32G431RB to STM32G431RBIx
On our side, we have updated the BSP generation logic to keep a track of such changes, and preserve the device entry with the short name, even if the latest SDK appears to split it into multiple devices.