Hi Sangeetha, The text you pasted is some tcl which sets up functions to print warnings in the event of timing errors. You'll always see this code fly by, since the tcl input is printed to screen.
If you actually have timing errors you will see, towards the end of your build: ERROR: Found timing violations => Worst Setup Slack: <some negative number> ns ERROR: Found timing violations => Total Setup Slack: <some other negative number> ns Do you see these? Cheers Jack On Fri, 9 Jan 2026 at 13:04, Sangeetha Andavan <[email protected]> wrote: > Hi everyone, > > I’m Sangeetha, new to CASPER. I’m currently learning how to use the CASPER > toolflow to design simple digital backends, starting with older platforms > such as RedPitaya, SKARAB, and SNAP. > > While following the tutorial for a basic LED blinking design, I > encountered a timing-related error during the build. The relevant debug > output is shown below: > > [2026-01-09 > 17:37:17,207][toolflow.py:1927][add_tcl_cmd][DEBUG][MainThread]: Adding tcl > command: > > proc check_timing {run} { > if { [get_property STATS.WNS [get_runs $run] ] < 0 } { > send_msg_id "CASPER-1" {CRITICAL WARNING} "ERROR: Found timing violations > => Worst Negative Slack: [get_property STATS.WNS [get_runs $run]] ns" > } else { > puts "No timing violations => Worst Negative Slack: [get_property > STATS.WNS [get_runs $run]] ns" > } > > if { [get_property STATS.TNS [get_runs $run] ] < 0 } { > send_msg_id "CASPER-1" {CRITICAL WARNING} "ERROR: Found timing violations > => Total Negative Slack: [get_property STATS.TNS [get_runs $run]] ns" > } > > if { [get_property STATS.WHS [get_runs $run] ] < 0 } { > send_msg_id "CASPER-1" {CRITICAL WARNING} "ERROR: Found timing violations > => Worst Hold Slack: [get_property STATS.WHS [get_runs $run]] ns" > } else { > puts "No timing violations => Worst Hold Slack: [get_property STATS.WHS > [get_runs $run]] ns" > } > > if { [get_property STATS.THS [get_runs $run] ] < 0 } { > send_msg_id "CASPER-1" {CRITICAL WARNING} "ERROR: Found timing violations > => Total Hold Slack: [get_property STATS.THS [get_runs $run]] ns" > } > } > > Based on my understanding, I checked the platform clock settings and set > the clock frequency to 125 MHz, corresponding to the ADC clock. However, > the timing violation persists. > > I would really appreciate any guidance on whether the clock configuration > is correct for this tutorial, or if I’m missing something fundamental in > the setup. > > Thanks in advance for your help. > > Best regards, > Sangeetha > > -- > You received this message because you are subscribed to the Google Groups " > [email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAH_Z%2BUCVOA0izUoYmRNv8BtTCuUayYWHBicbKdrOuSpmmziKqQ%40mail.gmail.com > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAH_Z%2BUCVOA0izUoYmRNv8BtTCuUayYWHBicbKdrOuSpmmziKqQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSks%2B1hbjXHw%2Bt%3DOvuHERjY0iwqvh4gnidjVdF6Ex%2BqFrA%40mail.gmail.com.
