• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 160 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM26LV32: Device-to-Device Skew

Kazuki Itoh
Genius 11110 points
Part Number: AM26LV32


Tool/software:

Hi team,

Could you let me know why the device-to-device skew of AM26LV32 is longer than single device pulse skew?

Best regards,
Kazuki Itoh

  • +1
    TI__Guru* 77901 points

    Kazuki,

    The device's datasheet has more built in room for margin on the first two skews. In actual measurement I see the device to device skew is 2x the channel to channel skew.

    -Bobby

  • 0 in reply to BOBBY
    TI__Genius 11110 points

    Hi Bobby,

    The actual measurement shows the device‑to‑device skew to be twice the channel‑to‑channel skew can be rephrased as 'half of the device‑to‑device skew equals the channel‑to‑channel skew.' If the margin is removed for the first two skews, tsk(p) and tsk(o), is it correct to understand the values as:

    - Actual value of tsk(p): 3 ns / 4.5 ns
    - Actual value of tsk(o): 3 ns / 4.5 ns
    - Guaranteed value of tsk(pp): 6 ns / 9 ns?

    Best regards,
    Kazuki Itoh

  • +1 in reply to Kazuki Itoh
    TI__Guru* 77901 points
    Kazuki Itoh said:

    is it correct to understand the values as:

    - Actual value of tsk(p): 3 ns / 4.5 ns
    - Actual value of tsk(o): 3 ns / 4.5 ns

    From what I see, the actual measured values appear to be even lower than this. These parameters also have a larger built in margin of safety. 

    -Bobby