Skip to main content
Associate II
Jul 24, 2025 10:36 AM UTC
Question

EVSPIN32F0601S3 Disconnects from Motor Pilot 6.3.0 When Pressing "Start" .

Hi ST Team,

I'm using the EVSPIN32F0601S3 development board and attempting to control a BLDC motor via Motor Control Workbench 6.3.0 and Motor Pilot 6.3.0.

Everything connects successfully when I open Motor Pilot — the board is detected, and parameters are correctly loaded. However, as soon as I press the "Start" button to run the motor, Motor Pilot immediately disconnects from the board. There's no error message aside from the disconnect itself.

What I've tried so far:

  • Verified UART connection (using STLink onboard)

  • Ensured the power supply to the board and motor is stable

  • Reflashed the firmware generated by Workbench

  • Tried different USB cables and ports

  • Rechecked motor parameters (voltage, current, sensor type, etc.)

Environment:

  • Motor Control Workbench & Motor Pilot 6.3.0

  • EVSPIN32F0601S3 with STSPIN32F0601

  • BLDC motor (sensorless)

  • Windows 10

It seems like the firmware crashes or resets when the motor is commanded to start, leading to a loss of communication with Motor Pilot.

Has anyone else experienced this or have suggestions on how to debug further?

Thanks in advance!

This topic has been closed for replies.

3 replies

GMA
ST Technical Moderator
Jul 24, 2025 1:01 PM UTC

Hello @Sunil_Kumar_G,

It could occur when the MCU is overloaded. Try using a lower PWM frequency value.
With a debugger, you can check the MCI[] table which contains the following:

  • "state" element indicates whether an error has occurred or not
  • "CurrentFaults" and "PastFaults" elements specify the error type (defined in mc_type.h)
If you agree with the answer, please accept it by clicking on 'Best answer'.Best regards.GMA
Associate II
Jul 30, 2025 9:17 AM UTC

Hello St Team,

No errors have occurred. Only my UART is getting disconnected, while the motor is running fine.

 

GMA
ST Technical Moderator
Jul 30, 2025 9:24 AM UTC

Hello @Sunil_Kumar_G,

It could occur if the MCU is heavily loaded. Could you try reducing the PWM frequency?

If you agree with the answer, please accept it by clicking on 'Best answer'.Best regards.GMA