Skip to content

Help wanted - adding new backend to fusesoc/edalize #738

@svenka3

Description

@svenka3

Hello,
I am toying with fusesoc/edalize to add a new testbench linter named svck - it is built on top of Verible, but in Python. I have a hacked flow that seems to run for now, but am sure it is a hack and not clean. Here is what I have done so far:

  1. Read FuseSoC manual, it sort of pointed me to Edalize
  2. Read Edalize manual, added a new file named svck.py (copied from veriblelint, modified as per svck argument/req)
  3. Now, honestly I didn't read/search long enough to see how to use my modified/updated edalize with fusesoc - so that would be my basic Q (see below). For now I copied the svck.py to .lcoal/lib/.. and got it working

My questions/help requests:

  1. Is there a unified doc for addressing new tool addition - or what I did above in 1,2 is the right approach?
  2. How to use my modified/updated edalize with fusesoc?

Thanks
Srini

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions