Skip to main content
lafa
lafa
Associate II
December 2, 2021
Question

Can not select STM32H7B0 VREFBUF LL driver in CubxMX V6.4

  • December 2, 2021
  • 4 replies
  • 1982 views

0693W00000GZk2qQAD.png

This topic has been closed for replies.

4 replies

TDK
TDK
December 2, 2021

Not everything has both LL and HAL code generation options.

"If you feel a post has answered your question, please click ""Accept as Solution""."
Khouloud OTHMAN
Khouloud OTHMAN
Associate
December 2, 2021

Hello @lafa​ ,

First let me thank you for your feedback.

Actually, for VREFBUF peripheral, the LL driver is not supported by STM32CubeMX. Thus it is not available and it can't be selected through Driver Selector Panel.

Nevertheless, the project can build correctly even when using both drivers HAL and LL.

Hope this answers your question

Khouloud.

lafa
lafaAuthor
Associate II
December 3, 2021

Thanks for reply.

Just after I enable the VREFBUF peripheral, cube display it using LL, but if I click it, it will change to empty, after that I only can select HAL in list box.

For cleaness reason, I am trying to create a pure LL project:)

BTW:

  1. LL driver lack of COMP peripheral IT enable/disable APIs.
  2. cubemx forgets to generate TImer break input source configure code in MX_TIM1_Init() even if I have configured in CubeMX GUI.

Khouloud OTHMAN
Khouloud OTHMAN
Associate
December 7, 2021

Hello @lafa​ ,

> Just after I enable the VREFBUF peripheral, cube display it using LL, but if I click it, it will change to empty, after that I only can select HAL in list box.

This is odd, I assume this behavior is not systematic because I couldn't reproduce it from my side. For VREFBUF peripheral, CubeMX is only showing HAL driver: LL driver isn't displayed in any case.

0693W00000Hnov3QAB.jpgFor your other two points:

  1. LL driver lack of COMP peripheral IT enable/disable APIs.
  2. cubemx forgets to generate TImer break input source configure code in MX_TIM1_Init() even if I have configured in CubeMX GUI.

Could you please explain more the problems. You can share your .ioc for further check.

Otherwise, it will be more reliable to create two other separate posts in STM32CubeMX topic describing those problems.

Please do not hesitate to raise any feedback/ issue, it always matters.

Khouloud.

Terms & ConditionsAccessibility statement