2022-02-25 02:38 AM
2022-03-01 01:24 AM
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
2022-02-28 05:58 AM
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.
2022-03-01 01:24 AM
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