Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IS_LPTIM_PERIOD() lower value should be 0 #33

Open
DaniAtGH opened this issue Nov 20, 2023 · 0 comments
Open

IS_LPTIM_PERIOD() lower value should be 0 #33

DaniAtGH opened this issue Nov 20, 2023 · 0 comments
Assignees
Labels
hal HAL-LL driver-related issue or pull-request.

Comments

@DaniAtGH
Copy link

The Period start value has changed from 0 to 1 in the macro IS_LPTIM_PERIOD(). In my opinion the lowest autoreload value should be 0.
I have tested a 1s period with the external LSE clock 32,768kHz and STM32L071CB: Timeout = 0x7FFF, due to processor errata = 0x7FFE, HAL_LPTIM_TimeOut_Start_IT(&lptimHandle, 1U, 0x7FFEU)). The LPTIM interrupt is raised every 999,95ms and before (with the HAL version 1.10.5) every 999,99ms (HAL_LPTIM_TimeOut_Start_IT(&lptimHandle, 0U, 0x7FFEU)).
Same issue is also in STM32CubeL4.

@ALABSTM ALABSTM self-assigned this Nov 27, 2023
@ALABSTM ALABSTM added the hal HAL-LL driver-related issue or pull-request. label Nov 27, 2023
@ALABSTM ALABSTM added this to To do in stm32cube-mcu-fw-dashboard via automation Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hal HAL-LL driver-related issue or pull-request.
Projects
Development

No branches or pull requests

2 participants