DVSim fails on fusesoc after prim_generic changes

[ysekhar]

I am seeing a blocker when trying to rebase to master for a PR and run dvsim.
Locally if I rebase to an older known version I dont see any error
Not sure if this is related to the prim changes that were pushed. Could you please sort master out ?

fusesoc: error: unrecognized arguments: --mapping=lowrisc:prim_generic:all:0.1 --work-root=/home/ycsekhar/work/code/git_repo/opentitan/scratch/ycsekhar-zR-ac-range-dv-with-bypass-and-locking/ac_range_check-sim-vcs/default/fusesoc-work
make: *** [/home/ycsekhar/work/code/git_repo/opentitan/hw/dv/tools/dvsim/sim.mk:30: gen_sv_flist] Error 2

[a-will]

You need to update your Python environment.

pip install -r python-requirements.txt

[andreaskurth]

Thanks for reporting this, @ysekhar, and for posting the solution (or at least what I expect should solve the problem), @a-will. This is likely caused by the merge of PR #23555, so I'm adding you and @HU90m as co-assignees.

We mentioned the need to update Python when we discussed PR #23555 in WGs and it was part of an email announcement in December 2024. The up-to-date guidance is available in this doc, which was circulated in #general on Slack on the day after the PR got merged. @a-will sent a message to #dv on Slack a few hours ago (after this issue was created) to point out the need to update the Python environment.

CI passes on master, so the problem is not present in the code base in an up-to-date environment.

As for the open action items: we need to ensure our documentation is consistent with PR #23555 (tracked in Issue #27372) to cover all permanent changes and we probably should send a follow-up email to increase the visibility of the transient changes.

Please let us know whether that resolves the problem you experience or need more guidance. Thanks!

[ysekhar]

Thanks @a-will & @andreaskurth for the responses. Updating python env does fix the issue.

Unfortunately I was not part of OT in Dec 2024 and was not aware of the PR or the decisions taken.
I agree with the proposed solution for sending follow-up for such changes that impact almost everyone!