Post Go back to editing

AD5554 Daisy Chain Hold Time Management

Category: Datasheet/Specs
Product Number: AD5554
Software Version: Rev H.

In our application we would like to chain several AD5554's together and run the chain at 20 MHz.

While reading through the datasheet we noticed that propagation on the SDO pin occurs on the positive edge of SCLK, the same edge use for sampling SDI. The propagation time ranges from 2 to 20 ns while the SDI data hold time is 20 ns.

This would suggest that if we directly connect two AD5554's in the chain then we will see hold time violations in all but the most extreme corners of SDO propogation delay. If we attempt to use board traces to produce the delay required to meet the hold time in the worst case (18 ns extra delay) we would need approximately 18 feet of board trace which is unrealistic. An active delay device could be used instead but this increases the number of BOM items.

I was assuming the chaining functionality would be more straightforward, otherwise the device could have been designed to update SDO on the falling edge like a traditional SPI device to avoid a costly external solution to this issue. Am I misinterpreting the datasheet?

Thanks!

Parents
  • Hi  , 

    I'm looking at the datasheet as well and the SDO timing doesn't make sense to me. Data is updated (with delay) on the same edge as the sampling of the SDI which will violate not the hold time but the data setup time. My gut tells me that the reference for the data transition on SDO should be on the falling clock edge instead. I'll ask one of our guys to do a quick setup on the lab to confirm this. 

    Best regards,

    Ian

  • Just checking in, were you all able to verify device behavior in the lab? I would be happy to do so myself but your eval board is out of stock.

    We just want to know if 1) the SDO pin truly updates with the rising edge of SCLK, the same edge used for sampling and 2) if daisy chaining two parts very close together is viable as per the earlier discussion on hold time violations (update propagates from SDO before sampling is finished).

  •   , so sorry, I thought I closed this one already. Turns out SDO is referred to the rising edge. Same edge as SDI gets sampled. So I'm pretty sure you won't be able to daisy chain two of these devices with the timing violations . The documentation hasn't been updated in a while and this might be the first time someone wanted to use the daisy-chain functionality, (in this forum at least). 

Reply Children