cancel
Showing results for 
Search instead for 
Did you mean: 

Missing enum values for STOP2_MODE in system_debug_signal_t cause compilation error

lgc
Associate

I am configuring to support Stop mode 2 in the stm32_wpan configuration section in the STM32CubeMX.

The following lines are generated in stm32_lpm_if.c

SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ENTER);
SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ACTIVE);
SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_EXIT);

However, the definitions of LOW_POWER_STOP2_MODE_ENTERLOW_POWER_STOP2_MODE_ACTIVE and LOW_POWER_STOP2_MODE_EXIT don't get generated, which are causing undefined compilation errors.

I checked the expected types for these definitions, and see that these should be defined as part of the system_debug_signal_t enum inside debug_signals.h. I have tried looking for additional configurations that might generate the missing definitions but I haven't had any success so far.

What should I look into or how can I generate these missing definitions? I could try to manually add these definitions to system_debug_signal_t. but then any time I re-generate with new configurations it will get ovewritten.

I am using STM32CubeMX version 6.14.0  

Toolchain: EWARM V9.20

MCU Reference:STM32WBA63CIUx.

Firmware package name and version: STM32Cube FW_WBA V1.6RC2

The project uses the STM32_WPAN and X-CUBE-FREERTOS software packs, currently trying to set the following configurations in STM32_WPAN:

CFG_LPM_LEVEL = 2

CFG_LPM_STDBY_SUPPORTED = 2 (for Stop mode 2)

1 ACCEPTED SOLUTION

Accepted Solutions
lgc
Associate

Hello Ghofrane,

Thank you for your response. I resolved this issue when I updated the STM32CubeWBA firmware package to the official 1.6.0 release. The issue appears to be on an OEM release of 1.6.0 which has an older date of 15 of November 2024.

Thanks and regards

View solution in original post

2 REPLIES 2
Ghofrane GSOURI
ST Employee

Hello @lgc 

First let me thank you for posting.

I would appreciate it if you could provide your IOC so that I can check the configuration and further investigate.

THX

GHofrane

lgc
Associate

Hello Ghofrane,

Thank you for your response. I resolved this issue when I updated the STM32CubeWBA firmware package to the official 1.6.0 release. The issue appears to be on an OEM release of 1.6.0 which has an older date of 15 of November 2024.

Thanks and regards