Skip to main content
Wassim Ben Chikha
Associate III
September 27, 2017
Question

Problems in sleep mode using STM32CubeHALv1.7.0

  • September 27, 2017
  • 3 replies
  • 2788 views
Posted on September 27, 2017 at 14:29

Hi,

I

use the

STM32L152RE

device

and

I

found some problems when I

execute

the sleep mode

in STM32CubeHALv1.7.0

.

In fact, w

hen I use the __HAL_PWR_VOLTAGESCALING_CONFIG function with PWR_REGULATOR_VOLTAGE_SCALE3 for

a

low frequenc

y (lower than 4MHz)

, this instruction

stops the

execut

ion

, while this function is executed for the two other

ranges

(PWR_REGULATOR_VOLTAGE_SCALE1 and PWR_REGULATOR_VOLTAGE_SCALE2). I tried to change the value of this variable

(PWR_REGULATOR_VOLTAGE_SCALE3)

from

PWR_CR_VOS (

0x00001800

)

to 0x0000C000. With this setting, the function runs.

P

lease, is it possible to check if there is an error

in the

definition

of this value?

In the other hand

, the HAL_RCC_DeInit

function

does not execut

e

. Indeed,

the

execution

is stopped

in

the function of switching the SYSCLK to MSI

(CLEAR_BIT(RCC->CFGR, RCC_CFGR_SW);)

. When, I

change this function CLEAR_BIT

by

SET_BIT

function

and change the order of the 4

th

instruction (Reset CFGR register) before

the instruction switch SYSCLK to MSI, the code is executed and the sleep mode

outperforms

the normal mode

in terms of energy consumption

.

P

lease, can you verify if there

are

some problem

s

in the function

HAL_RCC_DeInit

?

T

hank you in advance.

Best regards,

Wassim Ben Chikha

Note: this post was migrated and contained many threaded conversations, some content may be missing.
    This topic has been closed for replies.

    3 replies

    Vangelis Fortounas
    Associate II
    October 4, 2017
    Posted on October 04, 2017 at 09:28

    Hello!

    I tried to change the value of this variable

    (PWR_REGULATOR_VOLTAGE_SCALE3)

    from

    PWR_CR_VOS (

    0x00001800

    )

    to 0x0000C000. With this setting,

    This setting leaves VOS unchanged , sets the reserved bit 15 and also sets LPRUN  bit14

    0690X00000608PnQAI.png

    For the second part of your question:

    Please, can you verify if there are some problems in the function HAL_RCC_DeInit

    It seems that HAL_RCC_DeInit function sets as systemclock the MSI , whithout check for MSIRDY flag in the RCC_CR register. Yes i thing this is a problem .

    0690X00000608PsQAI.png

    Regards

    vf

    Wassim Ben Chikha
    Associate III
    October 4, 2017
    Posted on October 04, 2017 at 15:01

    Hello Vangelis,

    According to the RM0038 Reference manual, I agree with you that

    changing the value of the variable

    (PWR_REGULATOR_VOLTAGE_SCALE3)

    from

    PWR_CR_VOS (

    0x00001800

    )

    to 0x0000C000, leaves VOS unchanged, sets the reserved bit 15 and also sets LPRUN  bit14. But, the __HAL_PWR_VOLTAGESCALING_CONFIG function using PWR_REGULATOR_VOLTAGE_SCALE3 (0x00001800) stops the execution. Thus, I think that there is an error in the definition of this value.

    Vangelis Fortounas
    Associate II
    October 4, 2017
    Posted on October 04, 2017 at 15:59

    Hello again!

    But, the __HAL_PWR_VOLTAGESCALING_CONFIG function using PWR_REGULATOR_VOLTAGE_SCALE3 (0x00001800) stops the execution.

    I checked the

    __HAL_PWR_VOLTAGESCALING_CONFIG and according to RM sets or clears the VOS bits.

    I will try later to find why stops the execution .I have a board with L152.

    It would help a lot if you post  some code here. Like an .IOC file and main func .

    Regards

    vf

    Technical Moderator
    October 4, 2017
    Posted on October 04, 2017 at 11:56

    Hello Wassim,

    Your reported issue about

    HAL_RCC_DeInit

    function 

    is raised internally for further review.

    All your comments and suggestions are welcome to improve our solutions.

    Best Regards

    Imen

    In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
    Wassim Ben Chikha
    Associate III
    October 4, 2017
    Posted on October 04, 2017 at 12:00

    Hello Imen,

    Many thanks for your time and consideration.

    Kind regards,

    Wassim Ben Chikha

    Technical Moderator
    November 22, 2017
    Posted on November 22, 2017 at 12:40

    Hello,

    Thank you Luca, this issue is already raised internally to the developer team for fix.

    Best Regards

    Imen

    In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks