Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duh validate doesn't find custom buses #59

Open
olofk opened this issue Nov 21, 2019 · 2 comments
Open

duh validate doesn't find custom buses #59

olofk opened this issue Nov 21, 2019 · 2 comments

Comments

@olofk
Copy link

olofk commented Nov 21, 2019

I'm getting has unknown busType when I run duh validate on my component. The bus defintion lives in a separate directory, and I was able to get duh-portinf to use it with the -b flag but I can't make duh validate find it

@drom
Copy link
Member

drom commented Nov 21, 2019

Yes, @olofk most of the tools right now only works with the bus definitions from https://github.com/sifive/duh-bus . I agree that we need a good mechanism to include bus definitions from other sources. And not only bus definitions but components and designs as well.
I was thinking of NPM based solution when every DUH library would be an NPM package, exporting index of DUH documents. NPM already knows how to find, install and manage such packages from many different sources: https://docs.npmjs.com/files/package.json#urls-as-dependencies
What do you think?

@adeelliaquat-lm
Copy link

Hi,
Recently we started working on Duh, and we did a similar thing. We added the support of AXI5-Lite (AMBA-5) in Duh. It is yet to be functionally verified, but we were able to run the complete Duh flow along with Duh validation and scala export. We did some modifications manually. The screenshot of the exported scala chunk is attached below:

AXI5_Lite_ss1

Yes, @olofk most of the tools right now only works with the bus definitions from https://github.com/sifive/duh-bus . I agree that we need a good mechanism to include bus definitions from other sources. And not only bus definitions but components and designs as well.
I was thinking of NPM based solution when every DUH library would be an NPM package, exporting index of DUH documents. NPM already knows how to find, install and manage such packages from many different sources: https://docs.npmjs.com/files/package.json#urls-as-dependencies
What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants