hi, now I'm getting this error in my project in op...
# openlane
i
hi, now I'm getting this error in my project in open lane "[ERROR]: There are hold violations in the design at the typical corner", this error point me to a file with the timings. What I need to change to fix the hold violation error?, increment target density, bigger chip, etc ..
v
post CTS timing logs check it. How much hold violation exist? Try
Copy code
repair_timing -hold
Which Openlane version currently using? Try with latest version once
i
6.76 data required time -4.87 data arrival time -1.90 slack (VIOLATED)
for the openlane version I'm using 2021.11.23_01.42.34
how I use the ''' repair_timing -hold'''
👀 1
?
v
2021.12.21_01.44.20 latest openlane tag available
i
ok, I will try with the new openlane tag and see. Also I move some of the GPIO to be closer together, becuase the timing viloation was in the outer most GPIO pins
with the latest's version of open lane that you suggested I get an assertion error in yosys
ERROR: Assert `p != NULL' failed in kernel/yosys.cc:453.
v
is this caravel based project?
i
yes
v
You might try increasing PL_RESIZER_HOLD_SLACK_MARGIN
1
i
yes, I will try that, for now I'm stuck with the "ERROR: Assert `p != NULL' failed in kernel/yosys.cc:453."
in the ABC pass
v
2021.11.23_01.42.34 try with this openlane tag itself
i
yes, I re-download that tag but the error is same. I don't know why
doing the make test in openlane I get the same error. So I don't know what to do now.
v
try to install in new directory and try it.
i
I just found the issue, xD. No space left because of the multiple images of doker. I just manage to return to the correct openlane tag
v
yes
which openlane tag resolved your hold violation issue?
i
still working on that, now I'm having issues to finish the routing in less than 64 steps. For now I want to try again with the new output configuration ( Not using the outer most IO ports) and if still happens I will start testing different tags to solve the issue. I will keep you posted.
Hi @User, I'm testing the setting that you mention. For now I just have a finish openlane with slew violations and hold violation. The slew were low (0.1). But for the Hold violation, I have and error popping but in the report was only one that have 0.00 as a result and that was mark as a violation. Now I'm trying again with the margings a little bit up hopping to have it now without errors.
v
you can ignore the message if 0.00
i
ok, thanks. I'm think I'm close to dile in the parameters.