AD9081 Reference Design with the ad9081-fmca and Vivado 2018.3.1

For the AD9081 Reference Design with the ad9081-fmca and the ZCU102 board I get critical warnings when building the IP. I am using Vivado version 2018.3 and the warnings are with respect to 2019. What commit hash or version should I use of the repository if I am building with 2018.3. Are the critical warnings OK.

  • I can not see other critical warning than the version checking message. 

    please can you share your warnings ? 

    The project should be good to go with 2018.3 too.

    Laszlo

  • Thank you for the response. The following is a short snippet of the log around the warnings...

    I was mainly concerned about the mismatch in version.

    commit hash version  70d139af7f32c5d6f4e8d19a5d1c355f2a081f6b

    file = /library/axi_sysid/vivado.log

    INFO: [IP_Flow 19-234] Refreshing IP repositories
    INFO: [IP_Flow 19-1700] Loaded user IP repository 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library'.
    INFO: [IP_Flow 19-3656] If you move the project, the path for repository 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library' may become invalid. A better location for the repository would be in a path adjacent to the project. (Current project location is 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library/axi_sysid'.)
    WARNING: [IP_Flow 19-2248] Failed to load user IP repository 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ghdl/library'; Can't find the specified path.
    If this directory should no longer be in your list of user repositories, go to the IP Settings dialog and remove it.
    INFO: [IP_Flow 19-2313] Loaded Vivado IP repository 'C:/Xilinx/Vivado/2018.3/data/ip'.
    # adi_ip_files axi_sysid [list \
    #   "$ad_hdl_dir/library/common/up_axi.v" \
    #   "axi_sysid.v"]
    # adi_ip_properties axi_sysid
    CRITICAL WARNING: [filemgmt 20-742] The top module "axi_sysid" specified for this project can not be validated. The current project is using automatic hierarchy update mode, and hence a new suitable replacement top will be automatically selected. If this is not desired, please change the hierarchy update mode to one of the manual compile order modes first, and then set top to any desired value.
    Resolution: To switch to manual update order go to the Sources view, right-click on any node in the hierarchy and in the context menu select: 'Hierarchy Update' option 'No Update' or run the following Tcl Command: set_property source_mgmt_mode None [current_project] (which is the Manual Compile Order mode).
    INFO: [IP_Flow 19-459] IP file 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library/common/up_axi.v' appears to be outside of the project area 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library/axi_sysid'. You can use the ipx::package_project -import_files option to copy remote files into the IP directory.
    INFO: [IP_Flow 19-459] IP file 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library/common/up_axi.v' appears to be outside of the project area 'c:/Users/tony/projects/pro1/JUP-268/design/ip/ad9081/library/axi_sysid'. You can use the ipx::package_project -import_files option to copy remote files into the IP directory.



    file = library/xilinx/axi_adxcvr/vivado.log

    # set_property enablement_dependency {spirit:decode(id('MODELPARAM_VALUE.NUM_OF_LANES')) > 15} \
    #   [ipx::get_bus_interfaces up_ch_15 -of_objects [ipx::current_core]]
    # adi_add_auto_fpga_spec_params
    CRITICAL WARNING: [IP_Flow 19-4669] Invalid value for parameter validation type 'range'. The valid values are: list, range_long, range_float and none.
    # ipx::create_xgui_files [ipx::current_core]

  • Thanks for reporting these warnings,  apparently they are present with 2019.1 too. 

    I think both warnings are safe to ignore for now but we will try to fix them in the future. 

    Thank you,

    Laszlo