The default value is 10ms. You can set it in your board’s defconfig.

 

From: Anthony Kreft <anthony.kreft@...>
Date: Wednesday, August 1, 2018 at 16:25
To: "devel@..." <devel@...>, Jun Li <jun.r.li@...>
Subject: Re: [Zephyr-devel] STM32L0 k_sleep

 

Thank you, that worked. It should probably go in the board’s defconfig like most of the others already have.

On Aug 1, 2018, 6:02 PM -0500, Li, Jun R <jun.r.li@...>, wrote:

Have you tried to add the following option in your “prj.conf”?

CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000

 

Which set the clock tick resolution to 1ms.

 

From: <devel@...> on behalf of Anthony Kreft <anthony.kreft@...>
Date: Wednesday, August 1, 2018 at 08:39
To: "devel@..." <devel@...>
Subject: [Zephyr-devel] STM32L0 k_sleep

 

Hi All,

I noticed with my nucleo_l053r8 board that if I call k_sleep(1) in the basic/blinky sample, the time between LED toggles is about 10 milliseconds instead of 1 millisecond. Could there be a problem with the STM32L0 sleep function that is adding extra time?

Thank you,
Anthony