2025-07-09 7:41 AM - last edited on 2025-07-09 9:28 AM by Andrew Neil
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.
Solved! Go to Solution.
2025-07-10 12:37 AM - edited 2025-07-10 2:15 AM
Hello @Cedd,
Using MCSDK 6.4.0 EVSPIN32G4 example (EVSPIN32G4_Shinano.stwb6), generating the code with STM32CubeMX 6.14.1 or 6.15.0 and FW Package 1.6.1, I am able to compile with no error the project with STM32CubeIDE.
Using STM32CubeIDE 1.18.1, I had a message for updating ST-LINK. After firstly "Refresh device list", and "Open in update mode", I upgraded ST-LINK.
After ST-LINK update, I am able to flash the board and launch the FW with STM32CubeIDE.
Loading EVSPIN32G4_Shinano.ioc file on STM32CubeMx 6.14.1, STM32G431VBTx MCU with LQFP100 mention is display as expected, as it is the MCU embedded inside STSPIN32G4 system-in-package.
2025-07-09 8:56 AM
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.
2025-07-09 11:12 PM - edited 2025-07-09 11:59 PM
Hello GMA,
It’s certain that the STM32G431 is present in the STM32CubeMX tool.
But that’s not my problem.
I created a project with MC Workbench to try again with the EVSPIN32G4, but with this new version, the wrong microcontroller is selected for this evaluation board, and I can’t flash it.
A few months ago, everything was working perfectly, but this new version causes problems when trying to use the evaluation board.
I even tried the official example project:
Name: EVSPIN32G4_Shinano
Path: mcsdk://example/EVSPIN32G4_Shinano.stwb6
It also uses the wrong microcontroller.
2025-07-10 12:37 AM - edited 2025-07-10 2:15 AM
Hello @Cedd,
Using MCSDK 6.4.0 EVSPIN32G4 example (EVSPIN32G4_Shinano.stwb6), generating the code with STM32CubeMX 6.14.1 or 6.15.0 and FW Package 1.6.1, I am able to compile with no error the project with STM32CubeIDE.
Using STM32CubeIDE 1.18.1, I had a message for updating ST-LINK. After firstly "Refresh device list", and "Open in update mode", I upgraded ST-LINK.
After ST-LINK update, I am able to flash the board and launch the FW with STM32CubeIDE.
Loading EVSPIN32G4_Shinano.ioc file on STM32CubeMx 6.14.1, STM32G431VBTx MCU with LQFP100 mention is display as expected, as it is the MCU embedded inside STSPIN32G4 system-in-package.