Closed AndreanIvan closed 3 years ago
Hi @AndreanIvan,
Thank you for this report. The point you reported is actually related to the CubeMX generation problem and not to the firmware published in this repository. Unfortunately, we don't treat aspect related to CubeMX tool in our GitHub repositories. They are rather treated at the STM32CubeMX dedicated page of the ST Community .
Since this issue is not directly related to the STM32Cube firmware but rather to our ecosystem, please allow me then to close this thread. Thank you for your comprehension.
With regards,
To anyone running into this issue in the future: You need to assign which core uses the respective GPIO by right-clicking on each GPIO pin in cubeMX:
Then GPIO_init function will be populated according to configuration
Whenever I created a new project based on LoRaWAN Skeleton, it doesn't generate
MX_GPIO_Init()
in any file. This requires user to write their pin configuration manually, compared to the other project that are not based on LoRaWAN Skeleton whereMX_GPIO_Init()
is generated automatically.Board: STM32 Nucleo-WL55JC Custom board based on STM32WL55CC
IDE: STM32CubeIDE v1.7.0
Code Generator: STM32CubeMX v6.3.0
STM32CubeWL package version: v1.1.0
The code below is the
main.c
file, where I've done configuring my self-defined pin via STM32CubeMX. Because there is noMX_GPIO_Init()
, I have to write it manually.