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

fusesoc file based on CAPI 1 standard. #59

Open
johnathan-convertino-afrl opened this issue Dec 14, 2023 · 2 comments
Open

fusesoc file based on CAPI 1 standard. #59

johnathan-convertino-afrl opened this issue Dec 14, 2023 · 2 comments
Assignees

Comments

@johnathan-convertino-afrl

fusesoc has moved to the CAPI 2 standard for its core description files. The current core file wb2axip.core is CAPI 1 and will cause fusesoc to give an error to the end user. Recommend removing it to avoid confusion.

Future Improvement: individual fusesoc core files in the repo, if this is something you would like let me know and I'll get it done.

@ZipCPU
Copy link
Owner

ZipCPU commented Dec 18, 2023

Sigh.

This is one of my frustrations with FuseSOC. While I love the project's goals, and think very highly of its developer, I don't use it. This makes it difficult for me to maintain the core files used by it, as I never know when something changes, or what it needs to change to in order to keep a functionality I'm not using working. Likewise, I have no means of automatic testing to verify that the FuseSOC core's continue to work as desired.

@johnathan-convertino-afrl
Copy link
Author

johnathan-convertino-afrl commented Dec 19, 2023

I haven't personally had that issue in version 2 (started at 2.1 and now up to 2.3).

The documentation is frustrating to say the least. I end up reading source code to figure out how to use it. This is not acceptable.

I have added fusesoc core files for some of this repos IP in a separate repo. Essentially it uses a generator to git pull your repo so that the files are available to the core files in mine. Only issue is fusesoc finds your old core file and complains. Which is why I put in the request to delete it, since it seemed to serve no purpose at this point.

repo link

This method keeps the files from tainting this repo.

@ZipCPU ZipCPU self-assigned this Dec 21, 2023
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

2 participants