UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor a7med
Visitor
137 Views
Registered: ‎10-17-2019

Problem-with-xilinx-u250-xdma-201820

Jump to solution
0 Kudos
1 Solution

Accepted Solutions
Visitor a7med
Visitor
122 Views
Registered: ‎10-17-2019

Re: Problem-with-xilinx-u250-xdma-201820

Jump to solution

Fo any one who encounter the same issue. I managed to solve the issue by installing newer XRT (201830) and then installed the ml-suite shell for u250 (201820) then the flashing command went through. My guess because the U250 had newer 201830 shell DSA, the XRT (201820) couldn't detect it so it reported as Unkown and failed.

After flashing, I uninstalled XRT(201830) and installed the (modified XRT built from source due to new linux kernel name clash bug https://github.com/Xilinx/XRT/issues/1717) for 201820 branch. then the ml-suite examples finally worked 

View solution in original post

0 Kudos
2 Replies
Visitor a7med
Visitor
123 Views
Registered: ‎10-17-2019

Re: Problem-with-xilinx-u250-xdma-201820

Jump to solution

Fo any one who encounter the same issue. I managed to solve the issue by installing newer XRT (201830) and then installed the ml-suite shell for u250 (201820) then the flashing command went through. My guess because the U250 had newer 201830 shell DSA, the XRT (201820) couldn't detect it so it reported as Unkown and failed.

After flashing, I uninstalled XRT(201830) and installed the (modified XRT built from source due to new linux kernel name clash bug https://github.com/Xilinx/XRT/issues/1717) for 201820 branch. then the ml-suite examples finally worked 

View solution in original post

0 Kudos
Visitor a7med
Visitor
108 Views
Registered: ‎10-17-2019

Re: Problem-with-xilinx-u250-xdma-201820

Jump to solution
correction, I had to use the 201830 as 201802 still not working
0 Kudos