lowRISC / lowRISC/opentitan

[sw] Find out why verilator fails to build after building english breakfast

Open
#19,376 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component:Tooling Earlgrey-PROD Triaged TOP:englishbreakfast
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Description

The following scenario does not work:

  • build verilator for english breakfast (by using the english breakfast scripts)
  • restore all modified files in the git tree
  • then build verilator for earlgrey

I get the following error:

ERROR: %Warning-ASSIGNDLY: ../src/lowrisc_systems_ast_0.1/rtl/vcc_pgd.sv:39:33: Unsupported: Ignoring delay on this assignment/primitive.
   39 |     vcc_pok_o <= #(ast_bhv_pkg::VCC_POK_RDLY) gen_supp_a;
      |                                 ^~~~~~~~~~~~
                    ... For warning description see https://verilator.org/warn/ASSIGNDLY?v=4.210
                    ... Use "/* verilator lint_off ASSIGNDLY */" and lint_on around source to disable this message.

This can be fixed by removing the autogenerated files in hw/top_englishbreakfast/ip/ast/rtl/ and hw/top_englishbreakfast/ip_autogen/.

Find out why removing those files is necessary. Pirmin thinks that fusesoc is selecting the wrong files

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the sequence using the English Breakfast scripts: build Verilator, restore the Git tree, then build Earlgrey. Compare the generated files in hw/top_englishbreakfast/ip/ast/rtl/ and hw/top_englishbreakfast/ip_autogen/ and inspect how FuseSoC selects them. Done means the Earlgrey build succeeds without manually removing those generated files.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.