Skip to main content
Associate
January 8, 2025
Solved

STM32CubeMX not saving pinout for onboard LED1 and LED3 when using NUCLEO-H753ZI BSP

  • January 8, 2025
  • 2 replies
  • 936 views

When I assign pinouts for LED1 and LED3 on the NUCLEO-H753ZI in STM32CubeMX with the BSP selected, they are no longer assigned when the project is reloaded.

Best answer by STTwo-32

Hello @Howard_E 

Those two behaviors have been reproduced on my side, and I've escalated them internally for correction on the future (under internal ticket number 200752). Thank you so much for your help.

 

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

Best Regards.

STTwo-32

2 replies

STTwo-32
Technical Moderator
January 9, 2025

Hello @Howard_E and welcome to the ST Community.

Could you please provide more details about How to reproduce this behavior.

Best Regards.

STTwo-32

Howard_EAuthor
Associate
January 9, 2025

Not sure if I selected Human Machine Interface when I first created the project but I can reproduce with a new project.

Create a new project and select NUCLEO-H753ZI from the board selector.

Click Start Project.

When Board Project Options dialog opens, click OK to select all options under Human Machine Interface.

Under Categories, click BSP and uncheck Human Machine Interface.

Pin PE1 (LD2) will be set to GPIO_Output, but PB0 (LD1) and PB14 (LD3) will now be reset.

Unlock PB0 and/or PB14 and change state GPIO_Output.

Save, close, and reopen project.

Pins PB0 and PB14 will be reset.

If you go back and enable the Human Machine Interface, PB0 and PB14 will still reset when you save, close, and reload the project file.

STTwo-32
STTwo-32Best answer
Technical Moderator
January 9, 2025

Hello @Howard_E 

Those two behaviors have been reproduced on my side, and I've escalated them internally for correction on the future (under internal ticket number 200752). Thank you so much for your help.

 

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

Best Regards.

STTwo-32

Explorer
January 13, 2025

I have a similar issue with the Nucleo-WL55J. In my case the GPIO pins are also reset when reopening CubeMX. But, I also observed that the entries in the .ioc files are still there. So in my case I manually set PB9 as an OUTPUT and the file still reads:

PB9.GPIOParameters=GPIO_Speed,GPIO_Label
PB9.GPIO_Label=LED_GREEN
PB9.GPIO_Speed=GPIO_SPEED_FREQ_HIGH
PB9.Locked=true
PB9.Signal=GPIO_Output

However, when opening the file in Cube MX, PB9 is undefined.

STTwo-32
Technical Moderator
January 20, 2025

Hello @INT_Jan 

I can't see any issue on that. Everything works fine on my side. 

 

Best Regards.

STTwo-32