2025-11-24 5:36 PM
[VERSION]: MCWB v6.3.2
[TOOL]: STM32CubeMX v6.13.0, STM32CubeIDE v1.11.5
[BOARD]: STEVAL-PTOOL1V1
[PROJECT]: STEVAL-PTOOL1V1_6S_SL and STEVAL-PTOOL1V1_6S_HL
When I run the STEVAL-PTOOL1V1_6S_SL project generated by STM32CubeMX, the program loads and runs as expected. When I run the STEVAL-PTOOL1V1_6S_HL (which is just the Hall-effect version instead of the sensorless SL version), the program loads and runs when the debugger is connected, but would not run properly after a power cycle, unless I reset the chip using NRST. Both were tested on the same PCB.
I thought the program wasn't booting, but determined that it actually was, but it just wasn't getting past some of the init functions (I think the MX_MotorControl_Init call). If I add a delay (~1s) after the HAL_Init() and SystemClock_Config() calls, before the other peripheral init calls are made, the program runs normally after a reboot for the most part. I still see some times where it doesn't though.
I compared the two projects, and other than the obvious differences in motor control code, I don't see any differences in how the clocks are initialized, or anything in the motor library that I would think should cause this difference.
What is different about the HL version that would prevent it from getting past the init functions compared to the SL version?
Thanks,
Angelo
Solved! Go to Solution.
2025-11-25 2:50 PM
I found the issue, which was not related to the MX_MotorControl_Init() call, but actually in MX_NVIC_Init(). I turns out the UART IRQ was causing the behavior, so disabling that fixed it. Why did the other version not do it? It turns out it did, but I already discovered the same problem in the SL version long ago and forgot about it. :(
2025-11-25 2:50 PM
I found the issue, which was not related to the MX_MotorControl_Init() call, but actually in MX_NVIC_Init(). I turns out the UART IRQ was causing the behavior, so disabling that fixed it. Why did the other version not do it? It turns out it did, but I already discovered the same problem in the SL version long ago and forgot about it. :(