-
Notifications
You must be signed in to change notification settings - Fork 8
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
Vitis 2024.1 Release #1
Comments
None that I know, sorry. Ping @jasvinderkhurana in case you folks are working in this direction. |
@Fatalon, As of today we don't have a version compatible with Vitis 2024.1, but we have plans to update it. I don't have concrete dates.. but we will work on updating KRS on ubuntu 24.04 and Vitis 2024.1 or above.. |
okay, thanks for your reply. So for this moment, I switched back to Petalinux which is supported by the new flow out-of-the-box and try to get the cross-compiling of ROS2 applications working there - if you have any tips regarding that, let me know |
@Fatalon , can you provide some details on what example or application you are trying to compile? I can try to reproduce it at my end and then may be I can guide you well. |
Thanks a lot! |
Thanks for sharing the detail on the sample you are trying! I have recently tried Vitis Vision library function on Ubuntu 22.04 with Vitis 2022.1 release and they work perfectly fine. I have to try with Vitis 2024.1 tools. I want to understand if Vitis 2024.1 version is a must requirement for your development or can you fallback to Vitis 2022.1? If you can use the older version, I can give you a simple example which you can build Vitis vision functions with KRS and you don't need to flash the sd_card everytime.. you can just copy the bitstream and .xclibin for your new functions. |
I am driving an Ubuntu 22.04 as my daily PC and I remember when I started a few months ago, XRT and/or Petalinux installer weren't working for Vitis 2022.1 anymore - because they were already listed in the archive I considered better to move on to the most modern release and put some time also learning the new Python CLI and scripting the whole flow. If I can get the general flow to work with Ubuntu 22.04 in Vitis 2022.1 would be fine for me as well and I would be very keen on having a look on the example but only as a workaround as I think the new Python CLI is way easier to maintain/extend then the tcl scripts |
@jasvinderkhurana could you please share the solution with 2022.1 for testing with me? To have at least something working would be really great! :) |
@Fatalon , Sorry for the delay! Actually I have an internal version of the example and I am working on making it a public release with proper documentation. For you, I have prepared this example with a basic documentation on how to use this. Please have a look at the attached files and let me know if this is helpful for you. |
no problem :) Thanks a lot for your effort, I will have a look at it next Monday, when I am back at my desk :) |
I checked it out but I am still unsure, if I got it fully working. Currently, I have the problem that I only generate the HLS files (when using the "With HLS Kernel" command but not the corresponding host code program.
But I can load the kernel via xmutil into the system.
But I am not sure, if it now uses the kernel or not 😁 Also, your documentation states: Just as a sidenote - as I have currently 2024.1 and 2022.2 already installed on my system, I tried the whole examples with 2022.2 - I saw some critical warnings in the HLS synthesis phase but I am pretty sure the current issues are unrelated to that. |
I get a segfault now
|
resolved it - perhaps you should mention in your documentation that you need to build a few packages for the -DNOKERNELS=false case as well, like colcon-hardware-acceleration, ament_acceleration,.. otherwise your module fails. the current output I get is now
|
how can I verify if it uses the HLS kernel or just a testbench executable? |
Hi is this repo here still active?
Do you have perhaps a version compatible with Vitis 2024.1 (which uses GCC 12.2.0)
The text was updated successfully, but these errors were encountered: