-
Notifications
You must be signed in to change notification settings - Fork 1.6k
SPI Engine abstraction #1948
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
base: main
Are you sure you want to change the base?
SPI Engine abstraction #1948
Conversation
eeb0677 to
abf9ede
Compare
|
RetriggerCI |
1 similar comment
|
RetriggerCI |
Signed-off-by: Laez Barbosa <[email protected]>
abf9ede to
67b670e
Compare
Ad intel-compatible ad_* commands to the carrier common _qsys.tcl Now the same spi engine script is used for xilinx and intel projects. Other vendors can be added to the script in the future. Signed-off-by: Laez Barbosa <[email protected]>
Signed-off-by: Laez Barbosa <[email protected]>
67b670e to
3cd151e
Compare
caosjr
left a comment
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 have compiled ad4052 project with the main branch and this branch under the quartus 24.1, they have very similar output. The spi_engine script seems much clearer in this mode avoiding unnecessary code in the tcl of the projects.
|
I have compiled all the modified projects. Timing closure seems to be better for the AD57XX in this environment, I did not have to recompile as I did in the main branch. |
caosjr
left a comment
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.
Before approving I think it is worth a second check on the projects. Every project were consuming less registers than in the main branch, maybe there is some misconnection.
PR Description
Unifies SPI Engine projects for different vendors (Xilinx & Altera for now) into a single script. It uses intel implementations of the ad_* procs to keep vendor-specific lines to a minimum
This is implemented with a separate adi_board_intel.tcl, now sourced in the carrier-specific tcl, since that's where the intel commands were defined. Note that these methods are not spi engine specific, so that's a direction we could explore in the future. We could in the future move these intel procs to adi_board.tcl and have everything in a single place.
PR Type
PR Checklist