-
Notifications
You must be signed in to change notification settings - Fork 153
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
LiteX/LiteDRAM behaviour inconsistencies between Symbiflow/Vivado. #1740
Comments
I just ran the whole flow following the guide in symbiflow-examples and got working design (including RAM) on Arty. Here is a bootlog:
@enjoy-digital which LiteX/Symbiflow version you're using (LiteX in symbiflow-examples is not the latest one) |
I did the test with the latest LiteX and it still works:
I built the design with:
|
@kgugala: Thanks for the test. I haven't run the test myself sorry but was just moving the issue :) It seems we were seeing that the read validity windows was larger with Vivado than with Symbiflow which could cause calibration issues. That's something I already saw with Vivado with wrong IO/Internal VRef constraints, so that's why I was suggesting to check that IO constraints and Internal VRef constraints were correctly applied with Symbiflow. If that's the case and if things are working for you, we can probably close this issue. |
with 100MHz sys_clk I got wider windows:
|
OK, this looks good. I didn't realized the frequency has been reduced to 80MHz. So the remaining issue seems to be related to LiteX and already logged in litex-hub/litex-boards#166, litex-hub/litex-boards#263, so we can probably close this issue. |
ok, I'm closing this one then |
As discussed in enjoy-digital/litex#751, it seems the LiteDRAM calibration behavior is different between Symbiflow and Vivado. I'm closing the issue in LiteX and think this should be tracked here.
My guess (from previous bring up issues I had with LiteDRAM/Vivado on Xilinx boards) would be that the IOStandard or Internal VREF constraints are not correctly applied with Symbiflow.
The text was updated successfully, but these errors were encountered: