When I ran python3 test_glayout.py ,I got the belo...
# ieee-sscs-dc-24
c
When I ran python3 test_glayout.py ,I got the below output
m
If you have installed the pdk in a non standard location, be sure that PDK_ROOT and PDK point to the right locations.
c
How can I do that
I have no clue in these set ups .could you help here?
s
The easiest thing to do is to set up a soft link in /usr/bin pointing towards right direction. You can read about setting up soft link https://www.liquidweb.com/kb/creating-and-removing-symbolic-links-symlinks/#:~:text=A%20symbolic%20link%2C%20sometimes%20called,or%20folders%20with%20long%20paths.
The proper way would be Put
PDK_ROOT
as environment variable in your
.bashrc
and source it Then use something like
Copy code
import os; pdk_root=Path(f"{os.getenv('PDK_ROOT')}/")
everywhere where the hard coded parts were written. In my Case, I had to modify a)
Copy code
-/openfasoc/generators/glayout/glayout/flow/pdk/sky130_mapped/sky130_mapped.py in which pdk_root = Path('/usr/bin/miniconda3/share/pdk/') which is replaced by import os; pdk_root=Path(f"{os.getenv('PDK_ROOT')}/")
b) in the
test_glayout.py
file change the array to
Copy code
if pdk_root is None:
                print("using default pdk_root: /usr/bin/miniconda3/share/pdk/")
            else: 
                print('using provided pdk_root')
                self.pdk_files['pdk_root'] = pdk_root
Not Recommended at all if you don't know your way around Linux.
It might show errors even after than. Function is showing the error and change paths manually. The softlink is the quickest and dirty way to resolve these issues.
c
Tq for your time.the error got resolved
c
Please don't change the internal files it can cause very unreliable behaviour when you're pushing pcells to the repo later
how did you install the tools?
s
Thanks. Thats a good advice that didn't occurred to me. I think the better solution is pushing the softlink to the place where these code expects the pdk to be namely in
/usr/bin/miniconda3/share/pdk
That would be good right?
c
No need for that either, the code accepts a
str
or
pathlib.Path
variable wherever pdk is required to be coded in
m
@Saptarshi Ghosh can you please stick to the recommended install steps. If you are interested in supporting others then let's discuss it and we can get you involved. Chetanya's worries are valid.
s
As I shown in my QA, sending the
str
or
Pathlib.Path
didn't worked. The reason is the hard-coded path in the
sky130_mapped.py
Which hasn't been setup with the path input. We can continue in my QA too which has steps which lead me to above
Thanks Mehdi. I tried with the docker but couldn't make it work. But with what you mentioned, maybe I should try again. And get help with that errors instead of this approach. Thanks
👍 1
m
Thank you ! I think that would be really helpful. Let us know us if it doesn't work.
s
One quick question, (not related to this conversation) what is with two repos? Do we need both? One is the idea-fasoc and another is chipathalon. I cloned both but not sure how to organise things in terms of file hierarchy!
m
Logistics on the chipathon repo. Dev on openfasoc.
❤️ 1