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.

DRV2604L / involuntarily I2C access

Guru 29720 points
Other Parts Discussed in Thread: DRV2604L, DRV2604
Hi Team,
 
My customer said that I2C address of 0x58(I2C address of another slave device) could access DRV2604L although that of DRV2604L is 0x5A.
It seems reset function occured after sending following command, so he speculates DEV_RESET(Register address:0x01) works involuntarily.
----------------------------------------------
-I2C address: 0x58h
-Register address: 0x01h
-R/W: Write
-Data: 0xC3h
----------------------------------------------
Is it possible case of DRV2604L?
I'd like to confirm if I2C address of 0x58 can't access DRV2604L just in case.
 
Best regards,
Yaita / Japan disty
  • Hello Yaita-san,

    I have tried this and have verified that it is responding to 0x58. We have found the problem and are discussing internally. Please allow us some time to discuss.

  • Rodney-san,
     
    I'm looking forward to your reply.
    In addition, I'd also like to know the following.
     
    - If there is any workaround to use with another slave device(I2C address is 0x58)
    - If DRV2604(not "L" version) could be the same case
     
    Best Regards,
    Yaita
  • Yaita-san,

    Unfortunately, to my knowledge, the only work around would be to go into test mode and change some of the registers (not advised by customers). However, let me check with our systems team to see if they know another way.

    In regards to the not "L" version, it will have the same issue since it is based on the same die architecture.

  • Yaita-san,

    Is there any way the other device that responds to 0x58 can change their address?

    What is the schedule/phase of this current project?

  • Rodney-san,
     
    No, 0x58 device can't be changed own address.
    My customer can't no longer change the device and his board.(MP schedule of the project is this October first)
    So, my customer consider to take measures by software. For example, to reset DRV2604L when he accesses to 0x58 device. etc..
    .
    Could you explain detail about this issue?
    My customer would like to confirm if his measures are sufficient.
    Could DRV2604L also be read(not only write) by 0x58? Does issue occur only 0x58?
     
    Best Regards,
    Yaita
  • Thank you for your continuous suppoort.
    I will have a talk through TI local FAE from now and wait his reply.
     
    Best regards,
    Yaita