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.

DAC7311: Output state concern when low and high level holding time is not enough

Part Number: DAC7311

Hi,

My customer has a below question:

In datasheet, SCLK need at least 25ns hold-up time, otherwise it is abnormal.

Customer wants to know if the hold-up time is less than 25ns, what output state it will be?

Thanks!

  • Shenhua,

    Essentially the SCLK high and low times are derivative from the maximum serial clock frequency specification. For low-voltage 2.0-3.6V supplies this is 20MHz, which corresponds to 25ns high and low times assuming 50% duty cycle.

    As long as the other timing specifications are met, I doubt that maintaining exactly 50% duty cycle is a real requirement for the device. Is the customer also violating SCLK low time? This would effectively be exceeding the maximum SCLK frequency. It may not manifest itself as a problem 100% of the time as the exact conditions for the specifications may be marginal at extreme operating corners - but the risk would be that the DAC fails to successfully latch bits or frames on the SPI interface.
  • Hi

    customer have another question as below:

    we have another further question need your help on the DAC7311DCKR clock signal.

    I find in the datasheet that, the CPOL bit  is 0, while CPHA bit is 1, and as I know in SPI definition, this may mean the Clock signal should be low level when idle ?please help confirm this.

    Basing on our issue in customer side, in which the OVP is triggered when adjusting the output voltage from 18V to 19V, while the OVP point is 38V.  I have one concern, does the wrong clock signal logical level when idle  will cause this OVP if the  minimum SCLK high&low time is not met.

     

    I conducted test with the SCLK logical level when idle following the CPOL is 0, CPHA is 1, and found if the SCLK high&low time not met, the SPI may fail to adjust voltage.

    in customer side,  the SCLK logical level when idle is high , which may not follow the spec, and OVP triggered when SCLK signal high&low time not met.

     

    so, would you please help confirm  if the wrong logical level when idle will cause the DAC output max voltage? which will cause voltage be adjusted to the maximum voltage and trigger OVP.

  • SPI Standards

  • Max,

    The resolution of the oscilloscope capture you have shared is not sufficient for me to actually inspect any of the signals.

    I do not feel like the datasheet is suggesting that it is required that SCLK idles high and that CPOL = 0 & CPHA = 1 are requirements. That section is simply proposing a configuration that WOULD work, but not that is required. The main requirement is that data is latched on the falling edge of SCLK. This implies that both CPOL = 0 & CPHA = 1 or CPOL = 1 & CPHA = 0 would work.

    This perspective is reinforced by Figure 1 in the datasheet, which effectively illustrates SCLK optionally idling either high or low along with the timing specification t4 which indicates 0ns minimum time between SYNC falling edge and SCLK rising edge.

    What is harder to deduce from the datasheet is whether the time from SYNC falling edge to the first SCLK falling edge needs to be greater than the standard setup time defined by t5 (5ns) since SCLK falling edge to SCLK falling edge is not defined as a timing requirement.

    If you could please post a higher quality format of the oscilloscope capture you shared, it would be helpful for me to attempt to make some more informed observations. Even better would be a capture with time measurements between the SYNC falling edge and first SCLK falling edge in terms of replicating this on a bench setup or via simulation.

    Certainly SCLK idling low would give more timing margin to the first SCLK falling edge, so this could conceivably be a factor though we cannot ascertain this from the datasheet as it is.
  • This topic has been taken offline.