-
Notifications
You must be signed in to change notification settings - Fork 20
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
AXI DMAC: Test Framelock #104
Conversation
2318ee1
to
6271fe7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Partial review
Some other notes: update the license header's year where it's needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A note on the configurations. Configuration lists that are used for certain IPs can be passed to the system_bd just the same as other regular simple values with ad_project_params. On top of this, the scripts automatically create variables based on the configuration lists. You can check axi_tdd project for an example. I don't want you to change it unnecessarily, just to let you know about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't comment on the test program, as I don't know how Framelock works yet.
0bfc053
to
b5bd38c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unresolved a couple of changes and requested some others.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When looking into the testbench, I saw something weird with the tlast signal. When running cfg2_fsync configuration with test_program_frame_delay, after a single test was finished running, on the monitoring AXI Stream interface the tlast signal was not asserted, meaning that the packet was not transferred. Is this a framelock specific feature that causes the tlast not being asserted or something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Structurally and functionally everything seems to be good. I didn't check the the Framelock functionality in detail, so can't comment on the stimulus itself.
Tested, working.
746acf0
to
8da4367
Compare
8da4367
to
cc87d7e
Compare
cc87d7e
to
17ae7b1
Compare
62215b7
to
d394c0a
Compare
A VIP to drive or receive an I/O, the direction is configured by a parameter. Signed-off-by: Jorge Marques <[email protected]>
AUTORUN mode is meant to be executed without a processing system, so the whole execution should occur without writing any register, only by parametrizing, at dmac_api, skip any writes during the probe. Add framelock methods to support the framelock feature. Signed-off-by: Jorge Marques <[email protected]>
Verify the framelock when the writer is faster than the reader and vice-versa. Test with delay and in AutoRun mode. Signed-off-by: Jorge Marques <[email protected]>
d394c0a
to
32121c8
Compare
Tests #analogdevicesinc/hdl/1332.
Add a VIP for IO.
Add AXI DMAC Framelock testbench.
Will merge conflict with #103 since adds the same changes to support libraries in this repo.
Uses "old" axi_dmac_pkg. Happy to update it to the new class based pkgs, either in this pr or in a future one.