Skip to main content
EBdhaifi
EBdhaifi
Associate
April 26, 2022
Question

SERIOUS Problem with clock configuration STM32L051K6U6TR

  • April 26, 2022
  • 9 replies
  • 4925 views

Hi community,

I have a serious problem with this microcontroller STM32L051K6U6TR.

I have created a code using STM32CubeIDE and based on STM32CubMX wizard creator, however, the clock is set up to match the microcontroller & its peripherals (USART, I2C, ..) clock requirements as shown this photo :

0693W00000Lz4roQAB.png 

The generated code is compiled and flashed to the microcontroller without any error. I just tried this code :

0693W00000Lz4tBQAR.png 

thr problem is that the microcontroller gets crached. After debugging the code, I released that this issue is coming from HAL_Delay, because if I try the code without it, the proble is gone. Finally, I released that any call of a function or setting that uses the Clock of the CPU, the craching of the code occurs. I played a lot with the clock configuration in CubeMX to solve it but the same problem is still there, because I'm still thinking that maybe the clock setting generated by the CuBeMX is not supported physically by the microcontroller.

Did anyone face a simular issue ? Any suggestion might be a great help.

This topic has been closed for replies.

9 replies

waclawek.jan
waclawek.jan
Super User
April 26, 2022

How do you know the code is crashing? What are exactly the symptoms?

Is this a known-good hardware like Nucleo or Disco?

JW

EBdhaifi
EBdhaifiAuthor
Associate
April 27, 2022

Hello,

the code is not literary "crached" but lets say enters into infinite loop inside this function : 

while((HAL_GetTick() - tickstart) < wait)
 {
 }

So my understanding is that the microcontroller cannot get a tick in millisecond from the main clock, that's why a tried a lot of clock configuration.

Unfortunately this microcontroller is not used in any dev-board.

TDK
TDK
April 26, 2022

> Finally, I released that any call of a function or setting that uses the Clock of the CPU, the craching of the code occurs.

Literally every instruction uses the CPU clock. Not just function calls. If it was a serious clock issue, your code would not make it to the main loop.

Debug the code, hit pause, examine why it's "crashed" specifically and address/debug as needed.

"If you feel a post has answered your question, please click ""Accept as Solution""."
EBdhaifi
EBdhaifiAuthor
Associate
April 27, 2022

Hello,

the code is not literary "crached" but lets say enters into infinite loop inside this function :

while((HAL_GetTick() - tickstart) < wait)
 {
 }

So my understanding is that the microcontroller cannot get a tick in millisecond from the main clock, that's why a tried a lot of clock configuration.

TDK
TDK
April 27, 2022

Your code is stuck within HAL_Delay, but that's where you code should be 99.99% of the time because your main loop doesn't do anything useful. What exactly is the issue here?

Why are you claiming it is crashed as opposed to operating normally?

"If you feel a post has answered your question, please click ""Accept as Solution""."
EBdhaifi
EBdhaifiAuthor
Associate
May 10, 2022

SOLVED !!

The issue was that the BOOT0 wasn't pulled down properly ;)

Terms & ConditionsAccessibility statement