-
Notifications
You must be signed in to change notification settings - Fork 103
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
Add support for Generic TDD Engine (TDDN) #527
Conversation
Signed-off-by: Ionut Podgoreanu <ionut.podgoreanu@analog.com>
Add test example for the Generic TDD Engine using Pluto. Works with Pluto in Phaser mode. Signed-off-by: Ionut Podgoreanu <ionut.podgoreanu@analog.com>
Generated documentation for this PR is available at Link |
This comment has been minimized.
This comment has been minimized.
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.
Approving pro-forma after discussion with Jon
@podgori how is this different than the existing TDD class? |
This class is specific to the Generic TDD engine, the new scalable and standalone TDD IP, which aims to reduce the naming confusion around the existing TDD core built for AD9361, as well as expanding its number of output channels for systems which require more than six controlling signals (up to 32 channels). As such:
|
Can we replace the existing design (adi.tdd) with this one? |
These attributes are inherited from the ADF4159 and implemented through debug attributes. Signed-off-by: Ionut Podgoreanu <ionut.podgoreanu@analog.com>
As discussed, we can leave these 2 classes separate for now. |
Description
Adding support for TDDN:
Type of change
How has this been tested?
The example script was tested on Pluto in Phaser mode. The TDD configuration and functionality from pluto_tddn.py example was validated and tested with an oscilloscope.
Documentation
TDDN wiki page: https://wiki.analog.com/resources/fpga/docs/axi_tdd
Checklist: