hinxx
hinxx
> What development board are you using? I'm working with this board https://innovation.desy.de/technologies/microtca/boards/damc_fmc2zup/index_eng.html. My FPGA colleague took a quick peek at your config and commented that these transfers of 8kB...
> changes the behavior of the xdma_mm.sh script. I now have an output file of different size. Seems I need to buy that guy a beer ;). > Please test...
``` insmod: ERROR: could not insert module ../xdma/xdma.ko: Invalid module format ``` This might be the root of the problem. Might mean that the xdma.ko module was compiled for another...
I think you need to read 4 bytes at a time. Try with ``` dd bs=4 count=1 if=/dev/.. | hexdump -Cv ```
Sorry I don't speak/read/write Chinese. In python you could do this to wait for an event: ``` def wait_daq_done_irq(self): # Open the event0 device and try to read one event...
AFAICT, if the read() does not return and keeps waiting, then there are no events/IRQs to report. Are you sure your FPGA firmware is generating interrupts? There are several way...
Nothing jumps out to me, sorry. Maybe a long shot (or you are already aware of this) but, my buddy who does firmware design pointed out a peculiarity of the...
These instructions look very nice; even a SW like like me could probably build a FPGA image with them. > Doesn't look like Xilinx/AMD is doing anything with the pull...
> That driver has been accepted upstream.. Cool, did not notice that, thanks!
