Using the current caravel model with an MPW-ONE design I now get 1000's of these messages! Ok it's moving cells, do I really need to know that much detail?

. Moving to closest stripe at (21.840um, 5.400um).

[WARNING PSM-0030] Vsrc location at (-1141881.776um, -2144136.416um) and size =10.000um, is not located on a power stripe. Moving to closest stripe at (21.840um, 5.400um).

[WARNING PSM-0030] Vsrc location at (-1141741.776um, -2144136.416um) and size =10.000um, is not located on a power stripe. Moving to closest stripe at (21.840um, 5.400um).

[WARNING PSM-0030] Vsrc location at (-1141601.776um, -2144136.416um) and size =10.000um, is not located on a power stripe. Moving to closest stripe at (21.840um, 5.400um).

[WARNING PSM-0030] Vsrc location at (-1141461.776um, -2144136.416um) and size =10.000um, is not located on a power stripe. Moving to closest stripe at (21.840um, 5.400um).

Can I turn them off?

This was the topic of the previous thread. So far I've not managed to harden an mpw1 macro in mpw2. I reharden first in mpw2 tools.

This is building user_proj_example. Nothing hardened in it.

I don't understand your first post then. What is the mpw one design you mentioned?

Or, is it magically being hardened for inclusion in the wrapper.

Have you updated the configuration TCL file to include the power rails? Check the example designs in openlane. They all have a new config line

I've increased the die size in the user_proj_example/config.tcl. That's all.

Weird

This project https://github.com/miscellaneousbits/caravel_user_project.git will cause 100's of 1000's of these warnings!!!

@Jean You can disable this check by setting

FP_PDN_CHECK_NODES

to 0. Make sure you are on v0.14/v0.15/mpw-two-b tag of openlane.

Ok, but why is it happening at all? Cell locations at negative coordinates doesn't sound good.