• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 575 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DRV10975: eeWrite Problem of DRV10975

Norton Chen
Expert 1420 points
Part Number: DRV10975

Dear all,

What kind of issue may cause eeWrite fail of DRV10975?

I use DRV10975 EVM GUI to set value for register of DRV10975.

As the following figure is the schematic.

I change the voltage from +12V to +24V when I am doing eeWrite.

Best regard,

Yu-Chuan, Chen

  • 0
    TI__Expert 6065 points

    1) For C3 in your schematic, the typical application schematic in the datasheet shows it should be a 10uF. I need to check if this is important, but this could be the issue.

    2) If you are using a sleep mode device, and the device is in sleep, I2C communication will not work unless you exit sleep. Refer to "Table 1. Conditions to Enter or Exit Sleep or Standby Condition".

    3) Also make sure you have a pullup on the SCL SDA lines

  • 0 in reply to Sanmesh Udhayakumar
    Expert 1420 points

    Hi,

    1) For C3 in the schematic, I will try 10uF. Please let me know if the capacitance is an important issue.

    2) I am sure the driver is not in the sleep mode because the motor is running.

    3) Of course there are pull-up resistance on the SDA and SCL lines. We use lots of the I2C device on our project.

    Best regards,

    Yu-Chuan, Chen

  • 0 in reply to Norton Chen
    TI__Expert 6065 points

    1) What specifically is indicating that i2c write is failing for you?

    Are you able to send read commands?

    2) Please follow the steps in sections 8.3.5 Non-Volatile Memory and 8.5.1 I 2C Serial Interface . Programming eeprom may fail for example if you dont program to the correct slave address or the eeprom wont be burned if you dont write (0xB6) to enProgKey in the DevCtrl register.

  • 0 in reply to Sanmesh Udhayakumar
    Expert 1420 points

    Hi,

    I thought the I2C communication is fail because I could not write eeprom of DRV10975.

    I have written B6 in the EEPROM Key.

    I pressed eeWrite to burn eeprom.

    After all, I pressed eeFresh the data of Configure are original data but not the latest.

    I shut down the power and reboot the DRV107975, the status of the motor were still the wrong data.(The motor could not run because of the wrong configure setting)

    Actually, I want to know what may cause eeprom write error.

    Regards,

    Yu-Chuan, Chen

  • 0 in reply to Norton Chen
    TI__Expert 6065 points

    1) I think you said you were using the DRV10975 gui. You are using the DRV10975 gui with the evm or with a custom board?

    2) I want to confirm which part of i2c communication are working and not working.

    a) Are you able to i2c read?

    b) are you able to write the enProgKey in the DevCtrl register, and then read it to check if the write is successful?

    c) Is the only i2c fail behavior that the you are not able to burn the eeprom with permanent settings, even after power on and off?

    3) As mentioned previously, please follow the steps in sections 8.3.5 Non-Volatile Memory and 8.5.1 I 2C Serial Interface . There are many steps that if you dont follow, wont allow programming to be successful.

    4) When the device is on and you write to different registers, you are actually only accessing the shadow eeprom registers, and these arent permanent. They only become permanent (permanent meaning the settings wont go away when power off and on) when you follow the procedure in 8.3.5 Non-Volatile Memory