CubeMX for STM32WL55 does not offer GPIO initialization selection

[KDE]

CubeMX does not provide the option to choose whether GPIO pins should be initialized from the CM0+ or CM4 core. As a result, the generated code lacks GPIO clock definitions, GPIO ports, and pins. This prevents further progress and requires manual description of GPIO port initialization for each of the cores.

If for each STM32 core, CubeMX generated at least a list of ports and assigned pins as definitions, GPIO initialization according to requirements would be faster.

[Mahmoud Ben Romdhane]

Hello @KDE ,

Thank you for reporting.

Actually, this issue has been already reported internally to Dev team for correction (ticket number 150219) and it will be fixed ASAP.

Thank.

Mahmoud.

[Hvan .2]

After 3 hours of debugging (=3* 100 euro per hour) non-functioning GPIOs I found this forum post from more than 4 months ago! It turns out ST is not even capable of getting GPIOs working. The most basic of things without which even a blinky is not possible!

It is deeply shameful that ST doesn't seem to give a single *** about the quality of their development software and unloads its incompetence onto the developers who are working like crazy to solve all the issues that ST creates. Again: deeply shameful! 

 

And nice to post a ticket number from a ticketing system: where can I find the status of 150219? Or are mere mortals not allowed to check this?