I am trying to update some tools in openlane using the steps given in the GitHub page. But I am getting the following errors. How to resolve this?

which tool is giving you those errors?

Replace

If you'd like to use a recent enough version of replace, which will be used by default in the next release, modify

scripts/tcl_commands/placement.tcl

, change

global_placement

into

global_placement_or

in the

run_placement

proc.

Ok will try that

Are you using a macro with a custom LEF view?

Yes

@Praharsha: You need to use an interactive script in this case for now. Check https://github.com/efabless/openlane/blob/f5dc481ea0a857d0cb4ab9d69161fbc45534a06a/designs/striVe_soc_oram/script.tcl for reference. (You can run an interactive script with

./flow.tcl -interactive -file /path/to/script.tcl

)

@Ahmed Ghazy Thank you. Will try this out

could you share the script you're using?

@Ahmed Ghazy Currently I ran till placement only. This is the script

I had a look at your verilog files, you want to mark the AMUX macro as a black box by either adding the

(* blackbox *)

attribute on top in AMUX2_3V.v file or specify it in the

config.tcl

file as

VERILOG_FILES_BLACKBOX

and remove the ``include` line from the top level verilog. Are you doing that already?

@Ahmed Ghazy :Yeah. I was trying to figure how to make that as black box. Thank you for informing. Is that what is causing the error in placement as well?

No, it's not what is causing that; we're not explicitly using the

global_placement

command of openroad, so that error doesn't make much sense.

Yes I have set the core utilisation to 10%

@Parth Parikh: This block of code is commented out on the repo (https://github.com/efabless/openlane/blob/master/scripts/openroad/or_replace.tcl#L25)

@Ahmed Ghazy ohh. Well in my file it was not commented. After commenting, that error is gone. Now I am getting floating point exception error after implementing global_placement_or. It is coming on running 'replace_initial_place_cmd' in or_replace.tcl

@Praharsha can you, as a start, reduce the 0.9 in PL_TARGET_DENSITY because this value is too high. Set it to a value that is <0.4. This is probably not the issue here, but it will eventually cause other issues. Check this for more details: https://github.com/efabless/openlane/wiki#what-is-the-difference-between-fp_core_util-and-pl_target_density

@Amr Gouhar Okay. I'll do that. Although ,in my design there is only 1 cell. So it shouldn't make much difference right?

@Praharsha technically yes, I'm just saying it's a good practice to get used to, since it will cause other issues later in other designs.

@Amr Gouhar yes. Thank you for educating. Also, if you have any idea why floating point exception is arising, it would be really helpful

@Praharsha you can switch to the openroad version by replacing global_placement with global_placement_or, or if you already switched to that. You can do one of two things: 1. change the commit hash of replace in the replace dockerfile 2. change the commit hash of openroad app (if your using global_placement_or) in the dockerfile then inside the ./docker_build/ if 1 then run:

make build-replace
make export-replace
make merge

if 2 then run:

make build-openroad_flow
make export-openroad_flow
make merge

Beware that changing the commit hash to a newer version may not always succeed because the dependencies might have changed in those newer versions, so if it failed, make sure to check the dependencies on the respective repos. We will try to replicate your issue as soon as we can, and see if we can solve it. You can open an issue on the replace repo as well.

@Amr Gouhar Thank you so much

Adding additional liberty files is not there yet, but if you open an issue on the GH repo, it will help us keep track of it.

Ok sure. I'll open an issue.