Demystifying Deterministic Latency within JESD204B Converters

For high speed signal sampling and processing applications that need an array of synchronized analog-to-digital converters (ADCs), the ability to deskew and match latency variation across the converters is paramount. System design around this feature is critical, as any latency mismatches from the analog sample points to the processing blocks will degrade performance. Sample alignment is also needed for interleaved processing where one converter sample leads another by a fraction of a clock period.

One of the key features of the JESD204B third generation high speed serial converter interface is its ability to establish a deterministic latency for each converter in the system. When this feature is understood and used correctly, it can create a synchronized or interleaved sampling system across many ADCs in a single system.

Since deterministic latency is a relatively new converter interface feature, system designers typically have several questions about how to establish it, the signals of interest, and how it can be implemented for synchronous or interleaved processing. Below are some common questions and answers for designing a system with deterministic latency used across multiple JESD204B converters that are sampled together with an FPGA.

What is Deterministic Latency, and How does JESD204B Define it?

Deterministic latency across the JESD204B link is defined by the time it takes serial data to propagate from the parallel framed data input at the transmitter (ADC or source FPGA) to the parallel deframed data output at the receiver (digital-to-analog converter, or DAC, or receiver FPGA). This time is typically measured in either frame clock periods of resolution or device clocks.

The JESD204B specification for deterministic latency does not consider the analog front-end core of an ADC or the back-end analog core of a DAC. It is only based on the data into and out of the JESD204B digital framing. Not only are two active devices a function in this latency computation, but so is the spatial signal routing interfacing the two. This means the deterministic latency for each link could be larger or smaller within a multiconverter system, depending upon the spatial length of the JESD204B lane routing and their respective delays. Buffer delays on the receiver can help account for latency differences due to routing (Figure 1).

Figure 1. The deterministic latency for JESD204B between two devices will be based on three components: the delay from the transmitter framer to the output, the spatial routing delay, and the receiver delay from the input to the deframer. Data from two different ADCs in the same system could each have their own unique deterministic latencies.

Unlike a simple serial link configuration, such as low voltage differential signaling (LVDS), a JESD204B interface packs samples of data into defined frames. Each frame boundary of a couple or a few samples is marked by a special control character during the link handshaking, or initial lane alignment sequence (ILAS), from the transmitter. A larger defined group of frames, called a multiframe, is also marked with a respective control character during the ILAS. However, after this sequence is complete, the control characters are not needed and the full bandwidth of the link can be garnered. Both the frame and multiframe boundaries are coincident with a frame clock and multiframe clock respectively.

What do JESD204 Subclasses Mean in Relation to Deterministic Latency?

There are three subclasses of the JESD204B protocol to define the deterministic latency of the link. Subclass 0 which is backwards compatible with JESD204 and JESD204A, does not support deterministic latency. Subclass 1 supports deterministic latency by use of a system reference signal called SYSREF. Subclass 2 supports deterministic latency by a dual purpose use of the ~SYNC signal, which also allows the receiver to initiate the handshaking ILAS routine. The ability to accurately place SYSREF vs.~SYNC in time relative to the clock will dictate which subclass is needed for the system of interest.

How can Deterministic Latency be Used to Align Sampling Across Multiple Converters?

For a Subclass 1 converter implementation, frame clocks and multiframe clocks are aligned internally on each device by the occurrence of the system reference edge, SYSREF. When a SYSREF edge is detected, both of these clocks are aligned to that point in time. Since these clocks remain internal to each device, their boundaries within the transmitters are communicated over the serial link by the use of control characters.

Each receiver can implicitly decode the placement of the transmitter frame and multiframe clocks in time relative to its own clocks of the same name and relative to all transmit devices. This enables the receiver to deskew the samples on the relatively early arrival of data to match the link with the latest arrival of data, using buffer delays (Figure 2).

Figure 2. Within a JESD204B transmitter, samples are aligned to frame and multiframe clocks after the clock latches a system reference (SYSREF) edge. For visual purposes, a multi frame is defined here as only comprising eight samples.

For synchronous sampling, these data links can be aligned in time within an FPGA. For interleaved sampling, each link can be offset by its corresponding relative phase delay. The deterministic latency can be identified for each link by measuring the delay in time from the receiver’s multiframe clock edge until each respective link’s multiframe control character. The caveat here is that the deterministic latency for each link must be shorter than the duration of a multiframe clock period (Figure 3).

Figure 3. Samples comprised in multiframes from four JESD204B transmitters are aligned to the multiframe clock within the receiver by use of buffer delays.

Is Deterministic Latency the Same as Total Converter Latency?

The total latency of an ADC is the time it takes an analog sample to be clocked in, processed, and output digitally from the device. Similarly, the total latency of a DAC is the time from when the digital sample data is clocked into the part, until that corresponding sample is clocked out of the analog output. Typically, these are both measured in sample clock periods of resolution, as they are frequency dependent. It is partly a function of the analog processing architecture within the single converter component. This is fundamentally not the same definition as the deterministic latency described by a JESD204B link implementation, which is a function of three components.

What is the Maximum Deskew Budget for Aligning Multiple Converters?

The transmitter sends multiframe control characters to mark the multiframe clock boundaries during the ILAS process. The receiver identifies these characters to create its own internal local multiframe clock that is aligned with each of the transmitters in the upstream link. For large array systems where multiple receivers are used, the multiframe clocks are also aligned across all of these devices. Therefore, the deterministic latency of any converter link cannot exceed the time of a single multiframe clock period. This is the total deskew time budget across the links.

The duration of a multiframe clock is typically tens of sample clock cycles. It can even be adjusted to be longer or shorter through setup parameter variables that are communicated during the handshaking of the link.

Will this Feature Correctly Align to the Same Analog Sample Point on Either an ADC or a DAC, or is Something More Required?

Deterministic latency provides a way to align samples based on the same point in time as they are presented to the JESD204B framer. An ADC will have more clock periods of latency in addition to this time that are needed to process an analog sample from its front end ahead of the JESD204B framer. The converter vendor must specify this time period ahead of the framer in duration of clocks. Conversely, a DAC will need additional clock periods after the deframer to process a sample to the output in analog form.

How Long does the Alignment Process Take Before Valid Analog Sample Data is Available?

A SYSREF edge sent to the converter and FPGA causes an alignment process to start. After this event, several multiframe clock periods, in addition to the ILAS sequence, are required to complete before valid sample data is available. This is equivalent to a relative time of many sample clock periods. The specific duration may depend on unique deterministic delays of the JESD204B core in the converter and the value will need to be communicated by the vendor. During this time, the link will be brought down and valid data will not be transmitted. In absolute time, the duration will be a function of the sample clock frequency.

What is the Most Challenging System Design Aspect for Achieving Synchronous Sampling?

One of the most challenging aspects of achieving synchronous or interleaved processing down to the sample level in Subclass 1 is the ability to align the enabling edge of SYSREF in time across multiple converters. In addition, each SYSREF edge will need to meet the setup and hold time to its respective sample clock. This will consume some of the available timing margin. The ability to actively and independently skew the fine phase between SYSREF and the clock will help achieve timing closure across the converters.

Does SYSREF Need to be a Single Event or can it be Recurring? What do I Need to Know About Each Case?

SYSREF alignment edges can be a one shot pulse, periodic, gapped periodic, or recurring nonperiodic. This will be dictated by the needs of the system and the timing flexibility of the phase skew between the clock and SYSREF at the source. For a recurring case of SYSREF, the frame and multiframe clocks will be realigned on each event. However, since the goal is to maintain an aligned set of clocks, the enabling edge of a recurring periodic SYSREF should fall on multiframe clock boundaries. Since the clocks should already be aligned after the first SYSREF edge, this will prevent unnecessary realignments.

One of the adverse effects of a periodic SYSREF signal is that there is the potential for it to couple onto the analog signal of interest. That’s why a periodic signal isn’t always recommended and should only be used if absolutely necessary. If a periodic SYSREF is used, care must be taken to properly isolate it from the analog front end of an ADC.

What are Some Ways that SYSREF Skew can be Adjusted to be Within a Single Clock Period?

Ideally, the SYSREF and clock for each converter and FPGA could be precisely routed, with a timing margin to meet the strict setup and hold times across all components. But with the ever increasing sample speeds of high performance converters, timing closure cannot always be met with precise printed circuit board (PCB) routing alone. Pin to pin variance across parts, coupled with supply and temperature drift, can create a relatively large timing skew across an array of high speed converters. Advanced timing adjustment features may be needed to provide active SYSREF phase skew.

For example, an informative alert from an ADC could identify whether the SYSREF edge was latched within the setup and hold keep out timing window. If this were to occur, ambiguity would exist for which clock edge is used for the timing reference, clock[N] or clock[N+1]. Depending upon where a SYSREF edge was detected, the phase of the sample CLK edge relative to SYSREF could be delayed at the clocking source to maintain a valid timing condition that meets setup and hold time.

Another option could be to use the next falling edge of the sample clock instead of the rising edge to get a half period of phase margin. Each converter in the system could be tuned this way, provided the clocking source has independent phase adjustment of the respective SYSREFs and CLKs (Figure 4).

Figure 4. To achieve alignment down to the sample level athigh speeds, meeting the setup and hold time of SYSREF relative to the input clock can be challenging. The ability to skew each SYSREF input earlier in phase to prevent a setup time violation, relative to its CLK, helps meet timing closure across multiple converters in a system.

Is a Converter with Support of Subclass 1 or Subclass 2 Required to Use the Deterministic Latency Feature?

Subclass 1 and Subclass 2 are the only subclasses that support deterministic latency as described in the JESD204B specification. In Subclass 1, the SYSREF signal defines the deterministic latency. In Subclass 2, the ~SYNC is the signal that defines this latency. Some converter vendors have created a Subclass 0 implementation to be used for support of a synchronization scheme that aligns samples. In this case, the alignment procedure of the multiframe clocks between converters and FPGAs is not used

A time stamping mechanism at the sample level could be used to mark the occurrence of SYSREF using appended auxiliary information known as control bits. Each sample that is coincident with a SYSREF edge is marked with a unique control bit. Within the FPGA, each link that has this timestamp can be delayed to equal the longest path and then aligned to each other, independent of the latency differences between the converters (Figures 5 and 6).

Figure 5. By use of a SYSREF control bit timestamp, sample alignment in Subclass 0 could be achieved within an FGPA processing block, regardless of any actual latency variance across several ADCs from the analog inputs to the JESD204B outputs.

Figure 6. By using an appended control bit as a trigger (red) that is tagged coincident with the front-end analog input, an FPGA can align samples from signal chains with different latencies.


While deterministic latency is a somewhat complex option of JESD204B, when properly used, it can be a powerful feature for high performance signal processing system design. Samples from an array of ADCs can be aligned and deskewed within an FPGA by means of buffer delays to achieve synchronous or interleaved sampling. JESD204B subclass identification is important to understand the timing alignment capabilities of the system. Timing closure at the SYSREF and CLK input pins across the system ADCs is critical toachieving time aligned samples.


Ian Beavers

Ian Beavers [] は、アナログ・デバイセズ(ノースカロライナ州グリーンズボロ)のオートメーション/エネルギー/センサー・チームのプロダクト・エンジニアリング・マネージャです。1999 年、アナログ・デバイセズ入社。半導体業界での経験は 20年以上。ノースカロライナ州立大学で電気工学の学士号を、グリーンズボロのノースカロライナ大学で M.B.A. を取得。