Add bootloader IO in/out info to cubeIDE/MX pinout configuration?

[dmaST]

IMHO, to prevent IO OUT conflicts when MCU is a fresh new one with blank FLASH, bootloader IO in/out info should be added to cubeIDE/MX pinout configuration.

Thanks

[Tesla DeLorean]

+1  And any pins with "Chatter Hazard" that might be misinterpreted for a connection attempt. ie GPS/GNSS Receivers that start squawking immediately at startup

Many of the newer STM32 allow for USART RX/TX pin-swap modes, can be helpful to deconflict those pins.

Also a number of STM32 (mostly CM0(+)) where the SWDIO/SWCLK can be UART RX/TX pairs, although ST's pin mapping strategy isn't entirely helpful nor consistent.

[TDK]

This would be useful. Maybe just a checkbox to flash pins that are used by the bootloader.

Note that for STM32s without an empty check mechanism, this is much less of an issue as the bootloader never gets entered. It feels like ST is moving away from the empty flash check in general, but I'm not sure what the U5 and H5 series does.

https://community.st.com/t5/stm32-mcus/empty-check-mechanism-on-stm32/ta-p/49369