Non-handhsake inter-module and host communication interfaces
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
I could not find a specific issue dealing with this topic so I am just creating a new one. If there is, feel free to reference it here and I will close this one.
My questions is on the current status of adding a standardized interface wrapper to modules generated using the CIRCT flow.
Currently, I am taking the RTL generated by CIRCT and adding all the additional components necessary to talk to the kernel via AXI manually. This allows me to connect AXI-based IP to it and more importantly, drive the kernel either via MMIO (requires sudo access) or even OpenCL using XRT.
I know ESI from @teqdruid is looking to achieve something similar to AXI (interconnect modules) but I am not sure on the status of the project or if it will be AXI compatible in a way.
Thanks in advance!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions RTL generated through the CIRCT flow, ESI, AXI, MMIO, OpenCL, and XRT, but names no files, tests, or entry points. Start by reviewing current ESI documentation and related issues to establish the status and desired AXI compatibility; a concrete scope and implementation target would be needed before work can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100