cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jerald93
Visitor
Visitor
3,104 Views
Registered: ‎03-29-2019

ALVEO-U200 helloworld_ocl "system" run failure, Result mismatch

Jump to solution

Hi,

i have been trying out examples in SDAccel with alveo-u200 card on dell R740 server running ubuntu-16.04. I am able to compile and run "helloworl_ocl" example found at https://github.com/Xilinx/SDAccel_Examples/tree/master/getting_started/hello_world in sw emulation and hw emulation modes with correct output, but when i compile and run same in system or in HW mode i am getting failure with following log

Found Platform
Platform Name: Xilinx
Found Device=xilinx_u200_xdma_201830_1
INFO: Reading ../vector_addition.xclbin
Loading: '../vector_addition.xclbin'
Result =
Error: Result mismatch:
i = 0 CPU result = 42 Device result = 0
TEST FAILED

I am using "Xilinx SDx v2018.3 (64-bit) SW Build 2405991 on Thu Dec 6 23:37:15 MST 2018" for development, also tried building same with command line options and produsing similar issue.

following are the DSA details

	Card BDF:		0000:af:00.0
	Card type:		u200
	Flash type:		SPI
	DSA running on FPGA:
		xilinx_u200_xdma_201830_1,[TS=0x000000005bece8e1],[BMC=3.1]
	DSA package installed in system:	
		xilinx_u200_xdma_201830_1,[TS=0x000000005bece8e1],[BMC=3.1]

There is no modification in the example. looking forward to your replies

0 Kudos
1 Solution

Accepted Solutions
jerald93
Visitor
Visitor
2,929 Views
Registered: ‎03-29-2019

Thanks for the support. Issue was due to DMA failure.While running "XButil validate" command same error came.This may due to ubuntu grub configuration change for enabling IOMMU(This was done for some other project).When that change is reverted DMA failure resolved and application run in HW mode successfully without any problems.I dont understand why Intel IOMMU enble configuration affect DMA and shell installtion

View solution in original post

0 Kudos
7 Replies
graces
Moderator
Moderator
3,093 Views
Registered: ‎07-16-2008

Did you run the Make command for the emulations and hw deployment?

-----------------------------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
If starting with Versal take a look at our Versal Design Process Hub and our Versal Blogs.
-----------------------------------------------------------------------------------------------------------------------
0 Kudos
jerald93
Visitor
Visitor
3,086 Views
Registered: ‎03-29-2019

Did you run the Make command for the emulations and hw deployment?

Yes for command line building. I used IDE for last several builds with just pressing run option on the IDE with "Active build configuration" choosed as system"

0 Kudos
jerald93
Visitor
Visitor
3,060 Views
Registered: ‎03-29-2019

Hi

This is the status of build

Test                     Command line(MAKE)         SDx(IDE)

SW_emu                 success                               success

HW_emu                 success                              success

HW                           Result mismatch                result mismatch

 

And in case of make there is build error due to invalid folder name for vivado(attached log file - 01_make_build_error.txt ).i resolved that by modifying " . " in folder name by " _ ". for IDE there is no build error.

attaching build log(02_build_log.txt) and run log (03_run_error.txt) showing error.

I also tried to run "SDAccel_Examples/vision/edge_detection", both Hw emulation and sw emulation was success but Hw run failed.

0 Kudos
graces
Moderator
Moderator
3,032 Views
Registered: ‎07-16-2008

I was unable to reproduce the failure, neither did I received any build error in Make flow.

make all DEVICES=xilinx_u200_xdma_201830_1

helloworld_ocl_result.JPG

It looks you don't have the same naming .xclbin as defined in the Makefile.

BINARY_CONTAINERS += $(XCLBIN)/vector_addition.$(TARGET).$(DSA).xclbin

-----------------------------------------------------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
If starting with Versal take a look at our Versal Design Process Hub and our Versal Blogs.
-----------------------------------------------------------------------------------------------------------------------
jerald93
Visitor
Visitor
3,026 Views
Registered: ‎03-29-2019

Thank you for trying out the example.

I tried same example in nimbix cloud instance and got build error and i modified make file as i mentioned in previous reply. Test was successfull and got the correct result.

But in my local dell server setup it is still producing error and result mismatch. I am unable to understand what is missing in my setup

0 Kudos
jerald93
Visitor
Visitor
2,999 Views
Registered: ‎03-29-2019

The build error was due to DEVICE variable problem.i have been specifying it like below

/opt/xilinx/platforms/xilinx_u200_xdma_201830_1/xilinx_u200_xdma_201830_1.xpfm

when i changed that to only "xilinx_u200_xdma_201830_1" build was successful without any make file modification, but still Result mismath error is coming on Dell server setup

0 Kudos
jerald93
Visitor
Visitor
2,930 Views
Registered: ‎03-29-2019

Thanks for the support. Issue was due to DMA failure.While running "XButil validate" command same error came.This may due to ubuntu grub configuration change for enabling IOMMU(This was done for some other project).When that change is reverted DMA failure resolved and application run in HW mode successfully without any problems.I dont understand why Intel IOMMU enble configuration affect DMA and shell installtion

View solution in original post

0 Kudos