-
Notifications
You must be signed in to change notification settings - Fork 585
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
No compatibility with Efinity 2024.2.294 #2126
Comments
Thanks @m-byte, we can probably close this since your PR has been merged. |
@enjoy-digital not quite, as I only took care of the second point above. |
@m-byte: OK thanks, that's re-opened then. |
Good idea on copying over the xml file from the previous version :) I looked briefly to see if the name had changed, and it appears that not just the name has changed but also the structural content. |
There are multiple changes in 2024.2 that seem to break compatibility:
pt/db/device_*.xml
files are gone. This might be intentional, however, I just copied them over from the previous version for myself, which seems to help (will investigate further at some later point in time)2. the vdb file is placed in theoutflow
directory, while litex expects it to be inwork_syn
. As a workaround, I added a check into my local codebase, whether the file exists inwork_syn
and use theoutflow
directory if it doesn't.The text was updated successfully, but these errors were encountered: