Torben

This PR needs complete rework in the current state. If QDMA is required, use one of the Versal devices, which use QDMA as standard.

Hello @KC-Kevin, I'm sorry to hear you have issues during setting up TaPaSCo and SVM. Unfortunately, you ran into different issues with our main branch. It is a bit outdated,...

Let me first answer your follow-up questions: (1) TaPaSCo consists of two more or less independent parts, the toolflow for creating bitstreams and the runtime to write and execute corresponding...

Hi, thanks for the additional information. I suspect an issue in the Linux kernel itself. As you can see in the stack trace in the dmesg log, the error (or...

Hi, you could also try to run a bitstream with SVM disabled and see if at least this works. (4) We are using RedHat Enterprise Linux 9 with kernel version...

Hi, thank you very much for your additional debugging effort! The new kernel at least solved the issue which was unrelated to the actual TaPaSCo code. As background information: What...

Hi, I'm happy to hear that you finally got it running! I will consider to update the kernel requirement in the documentation. Regarding the auto-reboot I will have to ask...

Hi, please, see the answers to your different questions below. I hope I covered everything. Auto-reboot: We do not have a solution for the auto reboot issue. In our experience...

Hi, I think these are two distinct issues. The first error message is related to the Intel IOMMU which seems to block DMA to host memory for some reason, if...

Hi, (1) These example kernels are not optimized in any way. They should only demonstrate how to use TaPaSCo in general. (2) The ```tapasco->launch(...)``` and ```job()``` calls are synchronous. So...