<@U0172QZ342D> in the git repo that i cloned just ...
# caravel
a
@Matt Venn in the git repo that i cloned just now the power cells are written as "vdd" and "vss" in the user_proj_example.v and user_project_wrapper.v but the videos I am following from the "how-to" playlist from efabless; in that power cells are called "vssd1".
After getting some error I found out the config.json files also refer to them as vssd1, vccd1, vccd2 etc. while .v files refer to them as vdd and vss. there is a clear mismatch
It didnt throw any error regarding this while hardening the user_proj_example but now while hardening the user_project_wrapper its throwing some error which i don't know if is related
image.png
@Vijayan Krishnan
@Tim Edwards
t
What the power supply names are called in the
user_proj_example
module is irrelevant; the power supply names in
user_project_wrapper
must be "vccd1", "vssd1", etc., because there are automated scripts that analyze the project wrapper and expect the pin names to match what's expected. Within
user_project_wrapper
, the pin (net) names can get connected to different names in the instanced modules; e.g., in the call to instantiate
user_proj_example
, the pin assignment
.vdd(vccd1)
would connect the power supply named
vccd1
in
user_project_wrapper
to the power supply named
vdd
in
user_proj_example
.
a
@Tim Edwards Thank you i will change pin name in user_project_wrapper and run the floe again
m
@Ananya Mishra the power for
sky130
is
vccd1
and
vssd1
. The power for
gf180mcu
is
vdd
and
vss
.
t
@Mitch Bailey: Good point. Nothing in the discussion up to here specifies whether this project is on sky130 or gf180mcu, but it definitely makes a difference with respect to the power supply names.
a
Thank You @Tim Edwards and @Mitch Bailey. we were using sky130 only that issue got resolved, I changed all name in vccd1 format