Skip to main content
Visitor II
Nov 18, 2026 8:30 AM UTC
Question

[SR5E1E7] How to officially program DCF (C1_APPLI_ADDR_REG) for standalone Flash boot from BAF?

Hello ST Team and Community,

I am working with the SR5E1E7 MCU (Core 1 / Cortex-M7, evbe7000s board profile, StellarESDK-1.7.0, SR5E1_MCTK-1.3.0).

I have successfully flashed and verified my application binary into internal Flash at 0x08000000 using StellarLINK / OpenOCD. However, upon power-cycle or standalone reset, the CPU remains stuck in the BAF (Boot Assist Flash) (PC = 0x1FFxxxxx, VTOR = 0x1FF00100) instead of jumping to the application in Flash.

Current Register & Memory Observations:

  • Flash Vector Table (0x08000000): 0x24004798 (valid initial MSP)

  • Reset Vector (0x08000004): 0x08000401 (valid Reset_Handler)

  • C1_APPLI_ADDR_REG (0x4400030C): 0x00000000 (application address not yet registered)

  • C1_VTOR_INIT_REG (0x44000304): 0x1FF00100 (currently pointing to BAF)

Current Workaround: When debugging via OpenOCD/GDB, manually overriding SP, PC, and VTOR allows the application (an LED blink test) to execute properly:

           set $sp = 0x24004798

           set $pc = 0x08000401

           set *(unsigned int *)0xE000ED08 = 0x08000000

           continue

 

Since RM0483 states that DCF records in the UTEST region (0x1FF80300) are non-reversible and limited to 4 updates, I have avoided writing to UTEST/DCF manually. Could you please provide the official ST tool, flash algorithm, or documented procedure/script to safely program the DCF record for C1_APPLI_ADDR_REG (0x08000000) so that Core 1 boots standalone from Flash?

Thank you!