10-17-2018 12:46 AM
xdma + AR65444 runs well in 64bits windows system, but in 32bits windows it cannot work with "xdma_rw user write ..." command,
The problem is that the latest write command always get a result of the last command.
32 bits windows run badly:
xdma_rw user write 0x04 0x11 (nothing happen)
xdma_rw user write 0x04 0x12 (bram got 0x11)
xdma_rw user write 0x04 0x13 (bram got 0x12)
xdma_rw user write 0x04 0x14 (bram got 0x13)
64 bits windows run well :
xdma_rw user write 0x04 0x11 (bram got 0x11)
xdma_rw user write 0x04 0x12 (bram got 0x12)
xdma_rw user write 0x04 0x13 (bram got 0x13)
xdma_rw user write 0x04 0x14 (bram got 0x14)
what's the possibile cause? thanks
10-18-2018 08:54 AM
Per the documentation, the Windows driver source is compiled for a 64-bit Windows operating system only. You could follow the directions in the AR for Windows source, and make modifications to the driver to restrict it to 32-bit only, and recompile, but this is not expected to function on a 32-bit system.
10-18-2018 05:59 PM
thanks for your reply.
Yes, I did recompiled the driver source to compatible with 32bit windows . Investigation show that driver had send data to hardware correctly and vivado also got it(above pic), Unfortunately it is one clock late than expect.