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 rmccabe3701
Visitor
1,366 Views
Registered: ‎04-25-2017

Error in add_dma_coherent_prop -- cannot generate device tree

I'm running Vivado 2017.2 and targeting the zcu102 development board (Ultrascale+)

I am attempting to generate a device tree for a block diagram with the following AXI-DMA subblock:

2017-11-27_17-55-21.png

The AXI-DMA block is configured like this:

 

2017-11-27_17-57-35.png

And I'm getting this error:

 

ERROR: [Common 17-55] 'get_property' expects at least one object.
Resolution: If [get_<value>] was used to populate the object, check to make sure this command returns at least one valid object.
ERROR: [Hsi 55-1545] Problem running tcl command ::sw_axi_dma::generate : ERROR: [Common 17-55] 'get_property' expects at least one object.
Resolution: If [get_<value>] was used to populate the object, check to make sure this command returns at least one valid object.

    while executing
"get_property IP_NAME [get_cells -hier $connectedip]"
    (procedure "add_dma_coherent_prop" line 4)
    invoked from within
"add_dma_coherent_prop $drv_handle "M_AXI_MM2S""
    (procedure "::sw_axi_dma::generate" line 55)
    invoked from within
"::sw_axi_dma::generate chil_path_dma_0_axi_dma_0"
ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
ERROR: [Hsi 55-1450] Error: running generate_bsp.
hsi::generate_bsp: Time (s): cpu = 00:00:10 ; elapsed = 00:00:12 . Memory (MB): peak = 516.320 ; gain = 0.000 ; free physical = 57574 ; free virtual = 122537
Error generating bsp sources. Please check the SDK.log file under the workspace folder for further details.
Failed to create BSP project device_tree
    while executing
"error [dict get $msg err]"
    (procedure "xsdk_eval" line 15)
    invoked from within
"xsdk_eval $chan "Xsdk" createProject "o{$fmt}" e [list $data]"
    (procedure "createbsp" line 65)
    invoked from within
"createbsp -name device_tree -hwproject hw1 -proc psu_cortexa53_0 -os device_tree"
    invoked from within
"if { $devTreeRepo ne "" } {
   createbsp -name device_tree -hwproject hw1 -proc psu_cortexa53_0 -os device_tree
}"

 

It works correctly if I do this hack to axi_dma.tcl:

 proc add_dma_coherent_prop {drv_handle intf} {
+    hsi::utils::add_new_property $drv_handle "dma-coherent" boolean ""
+    return
+
     set ip_name [::hsi::get_cells -hier -filter "NAME==$drv_handle"]
     set connectedip [hsi::utils::get_connected_stream_ip $drv_handle $intf]
     set intrconnect [get_property IP_NAME [get_cells -hier $connectedip]]

 

 

 

Tags (3)
4 Replies
Highlighted
Visitor rmccabe3701
Visitor
1,300 Views
Registered: ‎04-25-2017

Re: Error in add_dma_coherent_prop -- cannot generate device tree

bump

0 Kudos
Contributor
Contributor
1,195 Views
Registered: ‎11-23-2017

Re: Error in add_dma_coherent_prop -- cannot generate device tree

Hi ,

 

I am getting the same error while building device-tree generator using HSI. and i am using Vivado 2017.3.

 

probably, the problem with tool.

 

 

0 Kudos
Observer fpgaioc
Observer
733 Views
Registered: ‎09-02-2015

Re: Error in add_dma_coherent_prop -- cannot generate device tree

Hi Guys,

 

Did you ever get this resolved?  I am having the same problem with zcu102 and 2017.4,

while the SDK and bare metal works fine.

 

Thanks and best regards,

 

0 Kudos
Visitor ylhuillier
Visitor
462 Views
Registered: ‎09-05-2018

Re: Error in add_dma_coherent_prop -- cannot generate device tree

Hi guys,

 

Issue is still running in 2018.1 and 2018.2.

 

The problem comes from the axi_dma/data/axi_dma.tcl scripts which incorrectly handles the "enable single AXI4 data interface" option.

Instead of probing M_AXI_MM2S and M_AXI_S2MM, the script should look at the "packed" version M_AXI.

 

No time to fix that, going with @rmccabe3701's hack.

 

Regards,

0 Kudos