cancel
Showing results for 
Search instead for 
Did you mean: 

ST Motor Pilot/Profiler will not connect when using UART.

dfshea
Associate III

Hello, I have a custom motor controller that I've developed that uses the STSPIN32G4. After a bunch of goof ups I finally managed to get it configured, presumably correctly, in the MC Workbench Board Designer. However once I upload the compiled program to the board, I cannot connect to it using the motor profiler or motor pilot software. I have checked that I have the right baud rate (115200), I've enabled motor profiler in the project, and I've tested my UART connection with CubeProgrammer (which functioned as expected). 

I'm wondering what the issue is? My assumption is that if I have UART communication at the correct baud rate with CubeProgrammer, then the only issue could be in software somewhere because ASPEP just isn't getting a response beacon. My assumption could be totally wrong though and I could have also configured something wrong in hardware. Just let me know if you have any ideas as to what could be going wrong, or if you need any more information to diagnose. Thank you!

13 REPLIES 13
dfshea
Associate III

Hello, I tried turning on bus voltage (I did not turn on over current). I also tried switching off the profiler feature in application configuration. The same issue arises when I do this.

GMA
ST Employee

Hello @dfshea,

Bus voltage feature has to be defined on your board description and aligned with your hardware (EVSPIN32G4 example):

 

GMA_1-1741798769698.png

If TIMx_BRK_M1_IRQHandler() is called, you have to check why OCP occurred. Check if the Current Sensing Hardware Variant parameters (gains, shunt) are aligned with your HW, verify the RShunt voltage level, ...
Your last attached zip file is empty.

 

If you agree with the answer, please accept it by clicking on 'Accept as solution'.
Best regards.
GMA
dfshea
Associate III

I’m not sure that interrupt is getting called, I put a breakpoint there and it didn’t stop. I also don’t have OCP turned on so why would it be triggering OCP?

dfshea
Associate III

I have some info that might be helpful that I just found out: the code (in debug mode) runs totally fine until I try to connect over UART. For example if i pause the program, the pointer goes to the while loop, however as soon as I try to connect over UART it breaks, I press pause and get the error message below:

dfshea_0-1741807788197.png