EVSPIN32G 6.4.0: CubeMX generates code with wrong MCU package

[Cedd]

Hello,

We are currently in the testing phase with the EVSPIN32G4 board using the various available software suites.

After upgrading to the following latest versions:

• MC Workbench 6.3.2 → 6.4.0

• STM32CubeMX 6.??.? → 6.15.0

• STM32CubeG4 Firmware Package V1.6.0 → V1.6.1

I created a project in MC Workbench for the EVSPIN32G4 board and generated the project for CubeMX.
To my surprise, the microcontroller is no longer the correct one in CubeMX, even though it worked fine with the previous version.
The evaluation board uses a 64-pin package, but the automatic configurator now selects a 100-pin package instead.

I tried rolling back the software versions, but nothing seems to work: the package remains stuck on 100 pins.

Do you have any idea what could be causing this issue?
Thank you in advance.

[GMA]

Hello @Cedd,

The EVSPIN32G4 is a board based on the STSPIN32G4 system-in-package. The used STSPIN32G4 system-in-package is a 64-pin package as described here (refer to Figure 1. STSPIN32G4 system-in-package block diagram). The system-in-package STSPIN32G4 embeds an STM32G431 microcontroller (MCU), which is presented in the STM32CubeMX tool.