HAL_RCC_OscConfig detects null pointer with a valid pointer?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-12-03 1:50 AM
Called from SystemClock_Config.
The pointer is clearly ok, as you can see in the Vars window, but the check detects it as null and exits with HAL_ERROR.
Doesn't make any sense, any thoughts?
Labels:
- Labels:
-
RCC
-
STM32CubeMX
-
STM32F1 Series
This discussion is locked. Please start a new topic to ask your question.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2021-12-04 3:38 AM
Which STM32?
> the check detects it as null and exits with HAL_ERROR
Are you sure it's this check which returns with HAL_ERROR? Single-step in disasm window and observe what's happening in the registers.
Alternatively, switch optimization (maybe only for this particular function) off.
JW
