Backup registry save and system reset risky for STM32WBA?

[YBAYR.1]

Hello everyone,

as mentioned in the title, I'm using STM32WBA in a project. Immediately after sending data to the stm32wba  coordinator, I add an expression to the backup register and reset the processor using `Nvic_system_reset`. I check this at startup and then run a different routine. It runs continuously in a loop.

My question is, are there any disadvantages to resetting the processor? Would it cause problems like freezing?

Does this situation lead to a logical fallacy?

What exactly does the MCU do with the reset process?

HAL_NVIC_SystemReset();

[Ouadi]

Hello @YBAYR.1,

Please find the answer to your question :

• No, using NVIC_SystemReset() itself will not physically damage the MCU or directly cause a “freeze”.
• Yes, it can cause problematic behavior (reset loops, protocol issues, unexpected boot paths) if not carefully controlled.
• The MCU on reset:
  • Completely reinitializes CPU, RAM, and peripherals.
  • Executes the normal reset handler and main() as if it just powered up.
  • Preserves backup registers, unless backup domain reset is issued.
• For STM32WBA, be especially careful with the wireless stack: frequent resets break connections and add significant overhead.

Hop this helps.

Best regards,

Ouadi