cancel
Showing results for 
Search instead for 
Did you mean: 

STM32WB1MMCH6TR Power Consumption Issue After OTA Update

TadejF
Associate

Hi everyone,

 

I'm facing a problem with my STM32WB1MMCH6TR. After performing an OTA update, the power consumption jumps from 120µA to 2.5mA, which is significantly higher than expected. Interestingly, the power consumption returns to normal after I power cycle the board.

I'm uploading the exact same code that is currently running on the MCU, so there shouldn't be any code changes causing this. Has anyone encountered a similar issue or have any suggestions on what could be causing this behavior?



I appreciate any help you can provide.
Tadej

1 ACCEPTED SOLUTION

Accepted Solutions
Sarra.S
ST Employee

Hello @TadejF, welcome to ST community, 

Are you enabling debug in low power mode? if (DBG_CR) bits remain active after an OTA update, it can cause increased power consumption and can be resolved by power cycle (which resets the register) or by simply clearing the debug bits in DBG_CR. 

Another thing to be aware of, is this erratum related to WB series:

 

SarraS_0-1728899372924.png

Even if in your application HSE is not targeted to be used,  you have to turn it off in order to avoid this overconsumption that is in 350uA range.

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

2 REPLIES 2
Sarra.S
ST Employee

Hello @TadejF, welcome to ST community, 

Are you enabling debug in low power mode? if (DBG_CR) bits remain active after an OTA update, it can cause increased power consumption and can be resolved by power cycle (which resets the register) or by simply clearing the debug bits in DBG_CR. 

Another thing to be aware of, is this erratum related to WB series:

 

SarraS_0-1728899372924.png

Even if in your application HSE is not targeted to be used,  you have to turn it off in order to avoid this overconsumption that is in 350uA range.

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hello Sarra,

Thank you,

Calling the following functions:

  HAL_DBGMCU_DisableDBGSleepMode();
  HAL_DBGMCU_DisableDBGStopMode();
  HAL_DBGMCU_DisableDBGStandbyMode();

before the main loop sorted the problem.

Best regards,
Tadej