Jaco Hofmann

tapasco-debug sounds good and we can put a fitting flag to notify the host of ECC capabilities into the status core. I'm building supporting infrastructure for things like this in...

Yes, that issue is part of the original PR. I decided to not port the old tapasco-debug as that one was quite flaky and failed easily, e.g. by changing the...

Maybe we could write a list of desired features: * Change the menu: Show all PEs + Platform components. Number or cursor selects desired one. * Pressing enter on the...

If the interrupt controller and DMA are properly registered in the status core, the debug application can simply show the correct information depending on the platform. libtapasco_test has some of...

As TaPaSCo does not know the number of parameter we could use a default of e.g. the first 3 and add +/- to change the number of shown parameters.

We use eventfd for that: https://github.com/esa-tu-darmstadt/tapasco/blob/8b21b7fa7d0c4142402554425b5b9b337d45d20f/runtime/libtapasco/src/interrupt.rs#L86 The read will not block but return an error if nothing is available. In this case the thread will yield, but of course in...

No, only the speed at which the interrupt is noticed by the host. So for long running PEs this is less of an issue. Check out slide 12 and 13...

> Out of curiosity: Did you compare the power consumption of busy wait and interrupt-based wait strategies? I am wondering how much power is used up by the PCIe-IP. PCIe...

From looking at it, I don't see a reason why it shouldn't for this particular function. For others I've been using < 0 to indicate an error and >= 0...

Can you upload your trainaspower.log?