READ_BIT(RCC->CR, RCC_CR_HSERDY) fails with a HAL_TIMEOUT when running blinky in debug.

Forum|Forum|1 year ago
September 23, 2024
14 replies
4403 views

While in debug I get and error in this line of code. I do not get an error when running code not in debug.

/* Wait till HSE is ready */
while (READ_BIT(RCC->CR, RCC_CR_HSERDY) == 0U)
{
if ((HAL_GetTick() - tickstart) > HSE_TIMEOUT_VALUE)
{
return HAL_TIMEOUT;
}
}

SBC NUCLEO-U5A5ZJ-Q

CUBEMX IDE

This topic has been closed for replies.

Tesla DeLorean

Guru

It takes too long, or the HSE is not present / connected.

Check board level jumper or solder-bridges (SB)

Clock typically derived from MCU providing ST-LINK, the frequency and presence of this can be changed/disabled

Check the HSE is populated, or wired to another source.

Check Systick isn't clocking faster than anticipated.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..

L

lwatcdrAuthor

Associate

I left out on detail it works fine when I run it but fails when I am trying to debug it

Tesla DeLorean

Guru

Humans run more slowly..

Are you single-stepping this?

Check DBGMCU settings/options, if it is allowing interrupts to continue whilst stopped? How is HAL_Delay() / HAL_GetTicks() implemented in your build?

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..

L

lwatcdrAuthor

Associate

No that would take forever. I have used break points to find where the error is set. I increased the HSE time out to 10000 so it should be plenty of time.
Start in debug. Hit continue. It runs and then hits a breakpoint on the return a time_out.
No single stepping was used in the creation of this issue.

Roger SHIVELY

ST Employee

Hello @lwatcdr

This post has been escalated to the ST Online Support Team for additional assistance. We'll contact you directly.

Regards,

Roger

ST Support

CToun.1

Associate

I am encountering the same mentioned problem. Could you please share the solution or any guidance on how to resolve it?

H

Hneel

Graduate

Facing the same problem here.

I've tried setting the input frequency to 16 as suggested, but that didn't help.

Any other solutions?

PS: I've downloaded and installed the latest versions of STM32CubeIDE and STM32CubeMX today.

Here are some detail pictures of my board. I think these are the correct default settings. (I got the board from a customer. I don't think they changed anything to the jumpers.)

2025-01-08 10.52.47.jpg 2025-01-08 10.52.19.jpg