EVLSPIN32G0A1: MC Workbench 6.x generates project with wrong MCU

[Zaheer_Shaikh]

Hello ST Community, 

I am seeking assistance with a project generation issue using STM32 Motor Control SDK (v6.x) and the EVLSPIN32G0A1 evaluation board. 

The Problem: Even though I explicitly select the EVLSPIN32G0A1 board (which features the STSPIN32G0A1 / STM32G071 core) in the Motor Control Workbench, the generated .ioc file and STM32CubeIDE project target the STM32G031C8Tx instead. 

Consequences: 

• Debugger Error: When attempting to flash the code, the ST-LINK GDB server returns: "Target no device found" or a Device ID mismatch because it is looking for a G031 but finding a G071 core. 
• Configuration Mismatches: The clock tree and memory boundaries in the .ioc are being set for the G031 (64KB Flash) instead of the STSPIN32G0 (128KB Flash). 

What I have tried: 

1. Creating a new project in MC Workbench and selecting the board from the "Boards" tab. 
2. Configuring the project for the 6-Step (Trapezoidal) algorithm. 
3. Verifying the pin mapping for Hall Sensors (PA0, PA1, PA2) and Gate Drivers in the 6-Step Wizard. 
4. Checking that the Workbench "Project Hw & Info" shows the correct MCU (STSPIN32G0A1) before generation. 

Despite these steps, CubeMX still opens the project as an STM32G031C8Tx project. 

Environment: 

• MCSDK Version: 6.4.1 
• Hardware: EVLSPIN32G0A1 
• IDE: STM32CubeIDE 

Has anyone encountered this template mismatch where the Workbench ignores the board's native MCU and defaults to a G031? How can I force the generator to use the correct STSPIN32G0 target? 

[GMA]

Hello @Zaheer_Shaikh,

Refer to STSPIN32G0A1 page, it is mentioned: The integrated MCU (STM32G031x8) allows performing field oriented control, the 6-step sensorless, and other advanced driving algorithms including the speed control loop.