Using Clock Domains to Control the Execution Rate of Clock-Driven Loops

FPGA targets support more than one clock. By configuring each Clock-Driven Loop to use a different clock, you can implement multiple clock domains in your Clock-Driven Logic code to execute your code at different rates to achieve separate timing objectives within one application.

What to Use

• Clock-Driven Loop
• Clock terminal of the Clock-Driven Loop

What to Do

Create the following diagram to implement clock domains that control the execution rates of code within Clock-Driven Loops.

Customize the gray sections for your unique programming goals.

Divide your code into sections according to the separate timing objectives of your application. Place each section inside a Clock-Driven Loop.

When you wire a clock to the Clock-Driven Loop, all code placed within the loop attempts to execute within one clock cycle of the chosen clock. For each Clock-Driven Loop on your diagram, select a clock that allows you to execute code at a rate that meets your timing objective for that section of code. Note   To execute more than one Clock-Driven Loop at the same clock rate, wire a single clock constant to multiple loops. Tip   To create modular code for use with different clocks in different applications, wire a clock control to the Clock-Driven Loop instead of a clock constant.

Troubleshooting

If your code fails to meet the timing objectives of your application using the clocks you choose:

• Create derived clocks to run code at a lower frequency.
• Use pipelining to reduce the length of the critical path. In the Timing Violations tab, you can highlight the critical path on the diagram.

Examples

Search within the programming environment to access the following installed example: Multiple Clock Domains.