-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cannot build AIE application on vitis 2023.2 (No longer support) #2
Comments
@logosAllen - 2024.2 example are currently targeted to be released end of Jan. you can still develop your own applications on 2024.2 - but yeah you wont have a working reference until later. |
Hello @jue-s , |
@Max-Huang14 - Just checked with the team - they are making progress but still have a blocking issue to resolve. their updated release time is first 2 weeks of Feb |
Hi @jue-s, Following up on this issue, as we're now in the second week of the updated release timeframe (first two weeks of February). Could you please provide a brief status update? Specifically, I'd like to understand:
We appreciate the team's hard work on this, and we understand that unforeseen issues can arise. Regular updates would be very helpful for our planning. Thanks! |
@logosAllen - I am waiting to hear back from program manager on exact timeline, though i dont think the release will happen this week -the blocking issue has been identified, but we are figuring out the best way to pull in the fix to 2024.2. they alkso need to do more testing to make sure there's no other issues. Appreciate your patience as the team is actively pushing towards release. will update on the new targeted release date when i find out. |
Hi,
According to this post, the "2023 AI Engine Tools License" has been phased out, and only the "2024 AI Engine Tools License" is available now.
To ensure compatibility and ease of use, could you kindly provide a runnable example for Vitis 2024.2 that works with the updated license?
Your support would be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: