Skip to main content
LLr.1
LLr.1
Associate III
February 25, 2022
Solved

CUBEWL - For Sigfox Push button example, I cannot find the classic MX_GPIO_Init() generated with CubeMX, why ? Thank you

  • February 25, 2022
  • 2 replies
  • 1150 views

..

This topic has been closed for replies.
Best answer by YBOUV.1

Hello @LLr.1​ , @Sara BEN HADJ YAHYA​ 

gpio.c generation was deactivated in the .ioc because the gpios are managed by their respective functions (BSP_PB_Init for the button). That is why you don't have this gpio.c source nor the call to MX_GPIO_Init().

But we received complains about this specific behavior in CubeWL. This is fixed in the release CubeWL1.2.0 to come within a week from now

hope this answer your question

2 replies

Sara BEN HADJ YAHYA
Sara BEN HADJ YAHYA
ST Technical Moderator
February 28, 2022

Hello @LLr.1​ ,

Thanks for your feedback,

I checked the example and you are right, the MX_GPIO_Init() is supposed to be generated in gpio.c file but this file seems to be missing.

Starting a project from scratch using CubeMX, the file is generated correctly so this is not an MX issue, the example seems to be corrupted.

@YBOUV.1​  could you please check this issue ?

Sara.

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
YBOUV.1
YBOUV.1Best answer
ST Employee
March 1, 2022

Hello @LLr.1​ , @Sara BEN HADJ YAHYA​ 

gpio.c generation was deactivated in the .ioc because the gpios are managed by their respective functions (BSP_PB_Init for the button). That is why you don't have this gpio.c source nor the call to MX_GPIO_Init().

But we received complains about this specific behavior in CubeWL. This is fixed in the release CubeWL1.2.0 to come within a week from now

hope this answer your question

Terms & ConditionsAccessibility statement