• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 46 subscribers
  • Views 158 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DAC6571: I2C DAC6571 Driver probe issue

Ahmed Kausar Kaamila K T
Prodigy 20 points
Part Number: DAC6571

We are facing issues with enabling the driver for DAC6571 in our platform.

In device tree file, we have added the following lines:
&i2c12 {
    status = "okay";

    dac@4c {
        compatible = "ti,dac6571";
        reg = <0x4c>;
    };
};

We have also enabled the driver from the kernel makemenuconfig
Device Drivers ---> Industrial I/O support ---> Digital to analog converters ---> Texas Instruments 8/10/12/16-bit 1/2/4-channel DAC driver

Even after all these, the clock signal remains low and idle.

The journal log is as follows:

Jan 01 00:00:13 rcu kernel: ti-dac5571 12-004c: supply vref not found, using dummy regulator
Jan 01 00:00:13 rcu kernel: ti-dac5571 12-004c: failed to initialize channel 0 to 0
Jan 01 00:00:13 rcu kernel: ti-dac5571: probe of 12-004c failed with error -5

Please suggest some ideas to troubleshoot further.

Thanks and Regards

Ahmed Kausar Kaamila

  • 0
    TI__Mastermind 30838 points

    Hi Ahmed,

    Just to be sure, are there pullup resistors on the I2C lines in your schematic? We are not experienced with driver related issues on the controller side. I would recommend looking into the documentation of this driver to figure out what it is supposed to be doing. Is the driver actually configuring I2C on your controller? 

    The DAC does not have an internal reference, so "supply vref not found" must be looking for some other voltage in the system. This might not be a relevant message for this application.

    You mentioned that the clock signal remains low, so the second error is likely coming from the fact that there is no I2C communication happening. You should look into the driver and start by debugging the I2C module, and then try communication with the DAC after you've been able to successfully initialize the I2C.

    Best,

    Katlynne Jones