Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
12 years ago

Arria V delay values (D1, D3, etc.)

On page 59 of the arria v gx, gt, sx, and st data sheet, in the i/o timing section is table 63 about programmable ioe delay. For device -C4, the D1_DELAY has available settings 0-31 with a value of 0.870ns. Is that per step (so 2 = 1.74ns) or is that for the whole 32 steps (so 1 ~ 27ps)?

3 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    When I had similar questions to this I used the Quartus "Resource Property Editor" and just looked at the settings for the I/O delay elements. I'd recommend creating a simple design in Quartus, apply some timing constraints, and then look at those delay settings. You can adjust the TimeQuest delay constraints such that the delay element gets reprogrammed to a new value, so you can quickly confirm that your TimeQuest timing margins have changed by the appropriate delay change.

    Cheers,

    Dave
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Thank you, I didn't know I could see it there. However, No matter what I change the D1 Delay value to in the Assignment Editor, the properties still show "D1 Delay Chain" "0:0 ps" (same for D3 Delay Chain 0,1). I recompiled, restarted Quartus and Chip Planner, but still no effect on the values. Is there another step I am missing?

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    Is there another step I am missing?

    --- Quote End ---

    Here's what my notes say:

    "A delay setting can be changed in the resource editor, and the design can be updated via the menu selection; ‘Processing→Start→Start Check & Save All Netlist Changes’ to rebuild the design, followed by, ‘Processing→Start→Start Classic Timing Analyzer’ to update the timing."

    The notes were from 2008, hence the reference to the classic timing analyzer :)

    Cheers,

    Dave