Closed dalyles closed 1 year ago
Please package a specific test case showing the issue (eg make issue). Setting up and re-running the autotuner to recreate the issue is impractical.
Thanks but a log is not a test case. I need a package set of files and scripts representing a single run of OR that reproduces your result. If you are using ORFS you can use 'make global_place_issue' to create such.
This will include you cell library so make sure it is ok to make public.
Yes it's fine to for me to have it public. I think what I can do is tar.gz my workspace and the hand it over. Here it is: https://drive.google.com/file/d/1DtPxpZ8b4lO0sEOaZ5QO8GNJwG18_63L/view?usp=sharing
The makefile is already configured to the run described above.
@dalyles
Can you confirm with Best parameters found
run tag not contain complete log files?
Yes it does not contain complete log files. It ends at files starting with prefix 3, which assumes that placement failed.
@dalyles In sky130hd
platform why used nangate45
fastroute.tcl
in autotuner.json
?
"_FR_FILE_PATH": "../../../platforms/nangate45/fastroute.tcl",
"_FR_GR_OVERFLOW": {
"type": "int",
"minmax": [
1,
1
],
"step": 0
But sample make
run failed during global routing
[ERROR GRT-0119] Routing congestion too high. Check the congestion heatmap in the GUI and load ./reports/sky130hd/picorv32/base/congestion.rpt in the DRC viewer.
Error: global_route.tcl, 21 GRT-0119
Command exited with non-zero status 1
Elapsed time: 0:07.67[h:]min:sec. CPU time: user 7.60 sys 0.07 (99%). Peak memory: 192836KB.
make: *** [Makefile:625: results/sky130hd/picorv32/base/5_1_grt.odb] Error 1
Seems something wrong with your configuration itself?
Hi @vijayank88,
Yes, you're right. It seems to be an oversight on my part. I'll follow up once I can confirm that the runs are complete and working properly. Please stayed tuned.
Maybe you can try with clock period value of 20ns
and core utilization of 35
@vijayank88 Thank you. Instead I made sure the run went through properly and then let the autotuner optimize it before I saw your comment. Everything seems to be working well.
ok to close?
Subject
[Documentation] for documentation errors.
Describe the bug
I'm currently trying to run a cell named picor32.v with the autotuner, however upon completion of the runs, the output results are incomplete as shown here:
From my understanding, it doesn't seem to sucessfully make it through the placement stage.
Expected Behavior
What is expected is to have all output files in logs completed for further analysis.
Environment
To Reproduce
To Reproduce this bug youll need the following files (this is with sky130hd)
The RTL which is found here: https://github.com/YosysHQ/picorv32/blob/master/picorv32.v
The Autotuner file
autotuner.json
:The file
config.mk
:The file
constraint.sdc
Relevant log output
No response
Screenshots
More Detailed Screenshot of output of autotuner at terminating stage:
Additional Context
No response