Open andyinno opened 1 year ago
As an additional information, I tried to step debug with SVD file loading by using jlink instead.
By using jlink the FDCAN initialization proceed without the error mentioned before by using openocd.
With this information I am unsure if this issue is related to peripheral viewer or to openocd. Feel free to close it if not related to peripheral viewer. Otherwise if you think I need to investigate a bit more, please provide some additional test to perform.
thank you
Type: Bug Report
Describe the bug
Just for future reader... I posted my original question here: https://github.com/Marus/cortex-debug/issues/931#issue-1900492186
I am configuring FDCAN on a STM32 H5 microcontroller.
I have the situation in which adding the following line:
and enabling the interrupts I have continuously the following error set:
I therefore disabled the interrupt again and while having the XPERIPHERALS windows active I checked in which line the error flag is set.
the flag is set as soon as the __HAL_RCC_FDCAN_CLK_ENABLE macro is called in the initialization code. The interrupt is then always asserted and the program does not proceed.
Seen that I am using openocd for connecting to the nucleo board, (openocd config generated by stm32cube) I loaded the elf file in stm32cube and debugged it from there. I can confirm that also enabling the corresponding XPERIPHERALS window of the stm32cube, the program executes normally. The error is not set.
this means:
To Reproduce Steps to reproduce the behavior:
Expected behavior
to be able to debug my code while having a SVD file loaded
Code sample and logs