Skip to content
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

Increasing payload size to 256K breaks memory training #195

Open
sqazi opened this issue Nov 27, 2024 · 1 comment
Open

Increasing payload size to 256K breaks memory training #195

sqazi opened this issue Nov 27, 2024 · 1 comment

Comments

@sqazi
Copy link
Contributor

sqazi commented Nov 27, 2024

Memory training failed very quickly. I also noticed that the build showed a red error message showing that timing constraints were not met.

@kgugala
Copy link
Member

kgugala commented Nov 28, 2024

bigger payload size will allocate more blockrams for storing the program. This will need more logic to handle this and makes it harder for the tools to route. If you have timing violations the system may simply not work correctly in the end. This can result in failed training.

Can you share the exact command you used for running the build?

Also - new HW revision should make it easier to have more memory in the system. US+ FPGAs have more memory resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants