cancel
Showing results for 
Search instead for 
Did you mean: 

Enabling low level driver for one peripheral, includes the low level driver for RCC in GPDSC project.

TMath.1
Associate

But main.c contains code for the high level RCC access. Tested with CubeMX 5.6.1 and STM32L452VCT

Changing RCC also to the low level driver, includes the RCC HAL driver to the project, but main.c contains the low level access

3 REPLIES 3
TDK
Guru

HAL and LL are not independent. HAL often uses LL, and LL sometimes uses HAL. STMCubeMX does a pretty good job of only including those files that it needs, but it's possible one was included without being needed. Delete it and see if any errors pop up.

If you feel a post has answered your question, please click "Accept as Solution".
TMath.1
Associate

The problem is that, despite selecting the HAL driver in the project manager settings, the RCC HAL drivers are not included in the project file (GPDSC). Only the LL drivers are included.

Hi @TMath.1​ ,

You can refer to this discussion https://community.st.com/s/question/0D73W000000Pe3e to understand more about the dependence between HAL and LL.

Then, regarding the issue you are describing now, please share your .ioc file. It will help to reproduce issue.

-Amel

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.