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

[xilinx] Logic for parsing AXI memory ports from kernel #958

Merged
merged 8 commits into from
Apr 12, 2022

Conversation

yn224
Copy link
Contributor

@yn224 yn224 commented Mar 18, 2022

This PR suggests the method in which AXI ports can be parsed out of generated kernel.xml file of the Xilinx tool (relates to PR #888).

YoungSeok Na and others added 2 commits April 8, 2022 16:07
Starting with Alex's XML parsing stuff, we now actually pass this stuff
to our `gen_xo.tcl` script. This also uses the `mode` attribute on the
`port` XML elements to distinguish which ports are relevant.
@sampsyo
Copy link
Contributor

sampsyo commented Apr 8, 2022

This has gone green, and I think it's ready to ship! ⛵ ✨

I started with @yn224's XML parsing snippet, made it a little more specific, did some refactoring, and hooked it into the command-line interpolation to correctly invoke the TCL script. I added a second test to the new Xilinx-specific suite: this time the dot-product example compiled from Dahlia, to demonstrate that we now support compiling programs with more than one external memory. These tests just passed on havarti.

This would check the first currently-unchecked checkbox in #876.

@rachitnigam
Copy link
Contributor

@sampsyo does this fix #853?

@sampsyo
Copy link
Contributor

sampsyo commented Apr 12, 2022

Ah, yes.

@rachitnigam
Copy link
Contributor

Great, thanks for wrapping this up!

@rachitnigam rachitnigam merged commit f706af7 into master Apr 12, 2022
@rachitnigam rachitnigam deleted the xml-parse branch April 12, 2022 20:44
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

Successfully merging this pull request may close these issues.

[xilinx] Use a single AXI interface to communicate with all memories
3 participants