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.

DRV10983-Q1: I2C INTERFACE

Part Number: DRV10983-Q1

 DRV10983-Q1, Why when powered up does the device provide output pulses to the motor before uP has powered up or even when micro is stopped?

We can see that there is I2C activity yet the uP is in stop mode why do we get bus activity?

1. I cannot see why we should get pulses to motor before the I2C has been activated !

2. Why do we get I2C bus activity when uP has been stopped by ICE!

3. Is it because the power supply of the device is used to power the board?

  • Hey Victor,

    What is uP stand for? Is it microprocessor? If so, what microprocessor are you using? If it is a TI processor, the respective TI processor team can help you with the problem of there being I2C activity from the microprocessor when you dont mean to.

    What is the motor activity that happens? Does the driver try to spin the motor?

    Q1) I cannot see why we should get pulses to motor before the I2C has been activated !
    A1) The DRV10983-q1 will start driving the motor on power-up depending on what speed mode you set. If you want the motor to be stopped until commanded by a microprocessor, please set the I2C Speed Control Override bit (SpeedCtrl Address 0x30 "override" bit). Also make sure the speedcmd is set to 0. If there is some I2C commands being done one powerup from the uP that you dont control, this might mess with the settings
    Q2) Why do we get I2C bus activity when uP has been stopped by ICE!
    A2) What is ICE?
    Q3)Is it because the power supply of the device is used to power the board?
    A3) I dont think I2C activity is due to a power supply of the board.

    Overall, please try my answer 1 where you set the I2C Speed Control Override bit and see if the motor activity stops.
  • Thank you for your help.
    (ICE=in circuit emulator).

    We are still hopelessly stuck. We get the motor to spin on ELAV Board (non-Q1 part).

    But does nothing on our target board, the target board has same connections as Eval board, but we use Q1 part.
    We are confused as to what to do to get this board up and running, and losing patients with board.

    We cannot see how to get the Faulhaber ( $1000 motor) to spin on Q1 part. Do we take a hit and revert back to put the non Q1 to prove base PCB design is good?

    We can read back registry of EVAL board, and we have tried to use this in Q1, but Q1 registry is different and therefor we are no further forward.
  • I think the main problem is we do not fully understand what the registers are used for in the Q1 motor driver, and therefore we need to know what we need to put in in order to just get the pulse train going to motor.
  • I believe we are answering this question in this thread ( e2e.ti.com/.../798299 ). Thus I will close this thread and let us continue our conversation in the other e2e thread. Please correct me if I'm wrong.