Post Go back to editing

AD5696R Software reset (power-on reset)


Please let me know if my understanding is correct.

Operating the software reset, command definition is following.

Is it correct ?



DAC ADDRESS:0001~1111 or  don't care?, for example "0000".

DAC DATA+DAC DATA:don't care?

Only setting the command "0110", power-on reset is executed in all DAC output?

or DAC ADDRESS needs any of the settings?

DAC DATA is "don't care" ?

Best Regards,


  • Hi sss-san,

    When executing the software reset comand, the DAC adress and the DAC data bytes are all don't-cares. The part (this includes all the DAC channels) will reset to their initial states. Depending on the state of your RSTSEL pin, the DAC channels will power up all four DACs either zero scale or midscale.

    If you have any further questions please do not hesitate to ask.



  • Hi,msamera-san

    Thank you for reply.

    Datasheet 21 page "Figure 50. I2C Write Operation",

    In this case,

    in order to execute a sequence of I2C typical write operation,

    We need to write the all bits and clocks till "stop by master" including "don't care bits_x" ?

    In other words, need to write the all 24 bits and clocks, FRAME 1~4 ?

    Where is the stop point ?

    COMMAND:0110 ;Software reset (power-on reset)


    00011xx0_0110xxxx_xxxxxxxx_xxxxxxxx_stop ?

    Best Regards,


  • Hi sss-san,

    You are correct. You need to send all 4 bytes (24 bits) to send a software reset command to the part.




  • Hi,Mark-san

    Thank you for the quick responce.

    It is clear now.

    Best Regards,


  • Hi,

    I know this is an old question, but when performing a software reset does the DAC respond with a NACK?  This seems to be the case as the channels are being reset to their power on value.

  • Hi,

    I haven't actually tried this but I'm expecting to have an ACK on the Device Address byte and the Command Byte, just not sure on the other don't care bytes. are you receiving NACK on them?

  • I expect I must be getting an ACK on the device and command bytes as the don't care bytes are transmitted - I'm using the Arduino Wire framework so just write the 4 bytes and don't worry about how Wire does that: it returns 'NACK' when I endTransmission() I don't see the responses between the beginTransmission() and endTransmission().  I'll have to dig out the scope later to see if I can monitor the traffic.  The reset does work so I was assuming that a NACK was a result of the device resetting itself.