search

rubund / graywolf

Other
107 stars 36 forks source link

sh: /usr/local/lib/graywolf/bin/edit_twfiles: No such file or directory #50

Open mhb0001 opened 3 years ago

mhb0001 commented 3 years ago

Hi

Running graywolf i get the following message:

sh: /usr/local/lib/graywolf/bin/edit_twfiles: No such file or directory

twflow terminated abnormally with 1 error[s] and 0 warning[s]

I am using graywolf as part of the qFlow. All works fine as long es i use for the place and route flow standard cells (osu018). However i would like to use it with our one digital library, I created the necessary .lef file and .par file ... and it does not complain about those.

It is true there is no edit_twfiles included in the graywolf package. The edit_twfiles are called in the

grep -r 'edit_twfiles' * flow/flow.noroute/mixed.flow:pobject edit_twfiles 1: 0 flow/flow.noroute/mixed.fnog:pobject edit_twfiles 1: 0 flow/flow.noroute/standard.fdbg:pobject edit_twfiles 1: 0 flow/flow.noroute/standard.flow:pobject edit_twfiles 1: 0 flow/flow.noroute/standard.fnog:pobject edit_twfiles 1: 0

If I replace with edit_twfiles with something existing such as Mincut, i receive some other error. What does that mean. When are those pobjects called. How can I avoid that? Or is the source code of edit_twfiles somewhere available?

Thanks and best regards,

mhb

svenn71 commented 3 years ago

I came here to report the same issue. Also called from qflow

edit_twfiles is slightly described in http://opencircuitdesign.com/qflow/archive/TimberWolf.pdf

According to that document it seems that edit_twfiles is called in something called mixed macro and standard cell circuit, but when I look at the flattened verilog netlist from yosys, there is no modules placed. Running with the -d flag for debug output I do not see some of the debug logging defined in the source.

Looking into the source, I find that there are a lot of debug functionality which is not turned on, and I cannot really find out how to enable the debug code. Defining DEBUG in include/yalecad/debug.h just gives a lot of compile errors as some of the procedure calls have the wrong number of parameters.

Maybe I should try the dev branch, but otherwise I am out of ideas for now

cheyao commented 2 years ago

I have this issue aswell, if anyone got the solution, please tell me

leochand101 commented 1 year ago

Did you check if the .par file even exists ? I debugged this to be the issue, compare your directory to the example nangate one, you will see GcdUnit.par doesnt exist, once you copy and paste that in there, the step will complete, but of course the inputs are not for your tech mostly, but the above error might be fixed. Then you will need to figure out how to convert the techlef data and your floorplan data to .cel format. Hope this works!