brianvg

~~On reviewing some of the other issues, is it possible this is related to not having the number of buffers set to 1 in the IP core?~~ I rebuilt the...

I am guessing, like you @bperez77, I just have the wrong settings in my IP core. > @Westwood68 Do you happen to remember/have the settings for the AXI VDMA IP...

Hi @bperez77, the program does indeed crash when the single test transfer is performed (single_transfer_test). Since making some changes to the IP core, I am now getting a null pointer...

I guess this is the same problem as described in issue #52. I am not sure if I will get further than they did, but if I do, I will...

I have added some kprint statements to the module to see exactly where in the DMA transfer things go sideways... See below, where I added also the lines of code...

Hi @EKjeldsen, I am glad I am not the only one having this problem. I tried your suggestion of commenting out the send_sig_info function call in the dma callback. I...

Follow up: I was running very small transfers to test the engine. Out of curiosity I ran some normal, frame sized transfers using the following command: >sudo ./axidma_benchmark -v -f...

By the way, @EKjeldsen, does the "vdmatest" kernel module from Xilinx work in your system? That kernel module also does not work in my system. Typical Xilinx. I made some...

@bperez77 : I have noticed in the character device driver, you have case statements for dma read, vdma read, dma write, vdma write, but then only a dma read and...

Hi @EKjeldsen, I just ran a test with the corrected entry for the frame buffer. I do not observe any changes in behavior, still seeing the segmentation fault. Nice catch...