-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[VTA][Chisel] Add the missing TestDefaultPynqConfig #3380
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
Conversation
|
Hey @liangfu One reason why I did not added this test is because the Pynq uses 32-bit addresses (pointers), requiring the virtual-translation used in sim-driver see I have not tested the "TSIM" infrastructure with virtual-translation yet for these kinda devices, reason why I left it out atm. On the other end, F1 FPGAs uses 64-bit address as most of the computers nowadays. Since memory instructions in VTA only allow 32-bit, I used this field for the most significant 32 bits of the address whereas the other 32-bits (the lsb of the address) is passed via VTA registers. See this. I don't know if this make sense, but let me know if you have questions. |
|
@liangfu also let me know if you want to try the chisel backend, and I'll let you know the steps needed. |
|
@vegaluisjose I would like to use the Chisel backend as well. Still trying to setup a regular Chisel environment, having some trouble getting IntelliJ with the Scala and SBT plugins to connect to the proper libraries. So, any help would be appreciated. |
|
@Ravenwater I think we can move this to discuss forum, so others can benefit from it. You could start a thread there. Thanks! |
|
Thanks @vegaluisjose for your explanation, that makes total sense. On the other hand, I had some experience in programming with Chisel3 and make the generated verilog code compiled on Intel FPGAs. I would send another PR in making chiselVTA integrated into Qsys. |
|
As |
|
I have made a Can we give this a merge? UpdateSorry, the previous log comes from the |
No description provided.