cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
yachli
Participant
Participant
716 Views
Registered: ‎12-07-2015

xdma_rw user write error in 32bits windows system

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

0 Kudos
Reply
4 Replies
yachli
Participant
Participant
678 Views
Registered: ‎12-07-2015

xdma_rw user write 0x04 0x11 0x22 0x33 0x50

above is 64bit well worked , 

 

64bit.png

 

below is 32bits work badly, data come late 1 clock with bram_en

32bit.png

0 Kudos
Reply
yachli
Participant
Participant
673 Views
Registered: ‎12-07-2015

and XDMA core axi lite master is 32 bitsxdma.jpg

0 Kudos
Reply
bethe
Xilinx Employee
Xilinx Employee
659 Views
Registered: ‎12-10-2013

Hi @yachli,


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.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Reply
yachli
Participant
Participant
650 Views
Registered: ‎12-07-2015

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.

0 Kudos
Reply