I took a detailed look at the flagged timing paths with the violations. They are all Max violations of the form: SOC to external flash interface (flash_csb, flash_clk, flash_io0), soc/_30758_ (another ff clocked by clk) and also many timing paths to soc.core.RAM128 and soc.core.RAM256. No other timing violations to user_project_wrapper code is found. This happens for s-ck-max.rpt, s-max.rpt, and s-soc-max.rpt (only these files) in all nom, min and max corners. Can all of these timing path violations be safely IGNORED? If I need to fix all of these paths prior to re-submission, how can I proceed? Urgently need guidance in this area. [Thanks to Dinesh A for replying previously]

max violations can be solved by slowing the clock. I have noticed many max violations in caravel itself (over 25k)

@Sam Lim My suggestion is to change the caravel clock to 40ns in sdc In file: $CARAVEL_ROOT/signoff/caravel/caravel.sdc Change the clock period from 25ns to 40ns create_clock -name clk -period 40 [get_ports {clock}]