This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BOOSTXL-DRV8320S: I am getting an over current error without connecting the motor?

Part Number: BOOSTXL-DRV8320S
Other Parts Discussed in Thread: MSP430F5529, DRV832X, , DRV8350S-EVM


I have 1x MSP430F5529L Launchpad and BOOSTXL-DRW8320S development board. I am trying to control the maxon EC motor with these equipment. (My HALL sensors are not connected)

I install DRV832X_MSP430F5529_Trapezoidal_Sensorless_BLDC program into my Launchpad, then I try to control the engine with the BOOSTXL-DRV832X EVM program and I succeeded, but while running, suddenly the motor stopped and I started getting a over current error.

I managed to drive the engine using the settings above.

maxon EC motor


Waiting for your answer. Thanks


  • In addition,
    When I make the bit in the picture below passive, the card draws too much current. (Motor not connected)

    This problem started after it gave an over current error.

  • Hi Ali,

    Thanks for posting to the MD forum!

    Can you lower your source/sink gate drive current settings IDRIVE_HS and IDRIVE_LS to a smaller amount, i.e. 120mA/240mA? (Address 0x03 = 0x344 and Address 0x04 = 0x744)

    Try using lower gate drive settings. They are currently set to the maximum settings, which can cause inductive voltage spikes in the phase node that would trigger VDS overcurrent trips. 


  • Hi Aaron,

    Like you said I fixed the IDRIVE_HS and IDRIVE_LS values but the result is still the same, there was something I forgot to add yesterday, in the picture below the DRV8320S is overheating when I don't enable the DRIVER_ENABLE button. When activated, there is no warming.

    Motor tries to rotate but stops due to over current error. 

    The problem could be on what hardware, because the card was working properly at first. Now I entered the DRV and MOSFET order, I will change them and try again, but I did not think it would break so quickly, it is very strange that it gave an overcurrent error, there was no strain or jam in the motor.

    Is there a setting and measurement point in this process that you would like me to do or try?

  • Hi Ali,

    Have you checked your VDS overcurrent settings? What currents are you expecting from your motor in the application? Does the VDS voltage exceed your VDS overcurrent settings you have configured in SPI (0.75V?)

    There may also be a current limitation setting in software (Motor Phase Current Limit). It looks like it is set up to 6A. Have you tried increasing this value?

    If all else fails, are you using 48V for your supply? I noticed you are using a 48V rated motor. If so, bear in mind that the DRV832x family of devices are rated for 60-V absolute max, so any voltage/current transients in the phase outputs can result in the overcurrent conditions or exceeding abs max specs.

    The MSP430F5529 + BOOSTXL-DRV8320S solution has limited bulk capacitance for higher rated motors. Additionally, the sensorless firmware does not have great startup commutation and has resulted in larger current spikes due to open loop startup. We recommend one of two suggestions:

    - Migrating to a sensored firmware approach, if possible

    - Migrating to the DRV8350S-EVM, which has larger bulk capacitance and can handle up to 100-V abs max


  • Hi Ali,

    Did you replace the MOSFETs and DRV device? On the device that was overheating, is there any physical damage or any known shorts through impedance checks, like GHx-SHx or GLx-SLx?


  • Hi Aaron,

    Sorry for my late response, I tried the current value at maximum, the result is the same, no load is connected on my motor, the motor runs idle at the end.

    I haven't installed and tried the HALL sensors, but I don't think the result will change much. When I use it without a sensor, there may have been an increase in voltage / current as you said at the first start.

    I haven't changed the Mosfets and DRV device yet. When I change it, I will try and get back to you, but I have to learn which part is the problem. There is no physical damage on the GHx-SHx and GLx-SLx side, only DRV overheats on the circuit, but when DRIVER_ENABLE is received through the application, it does not heat.


  • Hi,

    You can close the topic. The problem was that one of the DRV and Mosfets burned.

    Thanks for your help.