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.
I have the following questions reagrding ADS5402:
1. From the data sheet: "DBCLKP/N: DDR differential output data clock for Bus B. Register programmable to provide either rising or falling edge to center of stable data nominal timing". DDR means we get data at both rising and falling edge. If you center data at rising edge, it will also center at falling edge, right? Is clk duty cycle 50/50?
2. On page 26 of data sheet, dated January 2014
a. If SYNC is 1 pulse, what is the minimum and maximum pulse width?
b. If I use "1 pulse" SYNC, can I generate another pulse SYNC and expect the part to resync?
c. If SYNC is a periodic signal every 32 CLKIN cycles, do you resync every rising edge of SYNC? If yes, how do you do that if latency is 36 clks?
d. What is the benefit of SYNCOUT being a periodic signal of 32 CLKIN clock cycles? Why every 32 clks while the latency is 36 clks?
Thank you,
Vivian
Hi,
Yes, if the clock is set for DDR timing then if the rising edge is centered on a bit then the falling edge must also be centered on a bit. And the clock would be 50/50 duty cycle or very close to it. I will have to ask the datasheet author what was meant here. In other devices I sometimes see the option in a SPI register to change the timing, such as to make the clock centered on the data valid window or to make the clock aligned with the data transitions. I do not see such programmability in this register map, and I did not see such an option when I looked at the designers design spec. So I will have to ask what was meant by this statement.
The SYNC output (and input) is meant for cases where the user wants to use a number of devices to implement a number of channels and needs to synchronize the samples from all of the devices later. That is, if sample 'n' is latched into the FPGA from one device, then we want the FPGA to be able to match that sample up with sample 'n' from another channel instead of matching it up with sample n+1 or n-1.
The way we make provision for that is that there is a divide by 32 counter in the ADC that can output a SYNC signal that is the sample clock divided by 32. If this divide by 32 is reset to the same phase in all ADCs at the same time on the same clock edge, then the SYNC output can be used to synchronize the data streams later. There are several options described in the data sheet for using the SYNC input. The SYNC input will reset the counter when the input is latched and seen to be 'high' after seeing that it was 'low' onthe previous clock edge. This will reset the SYNC OUT counter.
If SYNC IN is a periodic signal, then if it resets the counter every 32 clock cycles then SYNC OUT is not disturbed - the signal is resetting the counter to the value that it already was going to be. So that is why SYNCIN needs to be sample clock divided by 32, or divided by 64, etc.
The period of SYNC out has nothing to do with the pipeline delay latency through the device. The latency through the device could be 2 cycles or 102 cycles, doesn't matter. The SYNC counter is still a divide by 32 and the SYNCOUT would be sample clock divided by 32. Latency doesn't affect that.
The SYNC IN signal can be 'low' for any number of cycles and 'high' for any number of cycles, as long as the low-to-high portion of the signal is every 32 cycles, or every 64 cycles, or every 96 cycles, etc.
Regards,
Richard P.
Hi,
There was a bit description left out of the register map in the datasheet. The datasheet is in the process of being edited so we will fix this.
Register address 0x01 bit D2 must be set to '1' to enable the SYNC output. With this bit set to '0' which is default the output pin is set to output a portion of the sample data that is needed during device manufacture.
Please set that bit and see if the expected SYNC pattern appears. Then check to see that your three device all output SYNC at the same phase. If not, we may need to look into the rules for setting the initial starting phase of the SYNC output.
Regards,
Richard P.