Hello ST Community,
I am working with the NUCLEO-WL55JC1 and the official Sigfox_PushButton example.
When running the application, the firmware consistently fails during EEPROM emulation initialization. The execution enters E2P_Init() and stops very early inside the function.
Observed behavior:
After that, the application ends up in Error_Handler()
The failure happens every time during startup
Project details:
Board: NUCLEO-WL55JC1
MCU: STM32WL55JC1 (dual-core CM4 + CM0+)
Toolchain: STM32CubeIDE
Firmware package: STM32CubeWL
Example: Sigfox_PushButton
EEPROM configuration:
In sgfx_eeprom_if.h, EEPROM emulation is configured as follows:
Flash page size: 0x800 (2 KB)
EEPROM bank size: 2 pages (4 KB)
EEPROM base address set to the last two Flash pages:
EE_BASE_ADRESS = 0x0803F000
(256 KB Flash device, address range 0x08000000 – 0x0803FFFF)
I already performed:
Full chip erase
Clean rebuild
Debugging on Cortex-M4
Verification that EEPROM does not overlap with application code
Despite this, E2P_Init() still fails very early.
Additional observation:
The project appears as a single project in CubeIDE (not clearly separated into CM4 / CM0+ projects), which makes me wonder if the issue could be related to:
Incorrect dual-core project structure
CM4/CM0+ initialization sequence
EEPROM middleware assumptions about Flash layout or device size
Question:
Is there any known issue with E2P_Init() in the Sigfox examples on STM32WL55?
Is the Sigfox_PushButton example expected to run only when imported exactly as the dual-core project provided in STM32CubeWL (without regeneration)?
Are there any specific requirements or patches related to EEPROM emulation on WL55 that could cause this early failure?
Any guidance or confirmation from ST engineers would be greatly appreciated.
Thank you in advance.
