lowRISC / lowRISC/opentitan

[regtool] IP block defines device interfaces, named ['regif'] but its registers don't match (they are keyed by [None])

Open
#26,137 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

Hello,

I am facing an issue when trying to use the regtool **standalone**.
I have an IP with some simple registers, set the clocking, bus_interfaces, and everything in the hjson, but I am getting an error like this, and I'm stuck now.

`ERROR: IP block reset_controller defines device interfaces, named ['regif'] but its registers don't match (they are keyed by [None]).`

All registers are defined like this:

```
{
name: "IP_VERSION",
desc: "Info register: version, release date, etc.",
swaccess: "ro",
fields: [
//Field definitions
{
name: "PATCH",
desc: "",
bits: "7:0",
swaccess: "ro",
resval: "0"
},
{
name: "MINOR",
desc: "",
bits: "15:8",
swaccess: "ro",
resval: "0"
},
{
name: "MAJOR",
desc: "",
bits: "23:16",
swaccess: "ro",
resval: "1"
}
]
}
```

I've searched the docs and the web for solutions, but couldn't find any.
If someome could help me, It would be much appriciated.

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

Start with the standalone regtool invocation and the HJSON configuration described in the issue, focusing on the clocking, bus_interfaces, and register definitions. Determine why the device interface is keyed as regif while the registers are keyed as None; done means the configuration is accepted without the reported mismatch error.

Written by the indexing model from the issue text.

Assessment

Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.