How do I configure HDL Coder so that it recognizes my Vivado version?

16 views (last 30 days)
I'm having difficulty with HDL Coder. I am trying to create a project to deploy onto my fpga and have set the hdlsetuptoolpath to the correct directory for my version of Vivado (2023.2). It seems to successfully preprend the Vivado path to the system path, but when I pull up the HDL Workflow Advisor and get to step 1.1 Set Target Device and Synthesis Tool, it can't calculate the synthesis tool version and defaults to 2022.1. This causes a problem down the line, even if I select to ignore the tool version mismatch when setting it to 2023.2 in step 1.2. This is what I see in the Command Window:
Warning: Unable to calculate synthesis tool version number.
Please make sure command
"/home/ezenia/Vivado/2023.2/bin/vivado -version" is available
and executable.
Synthesis tool log:
vivado v2023.2 (64-bit)
Tool Version Limit: 2023.10
SW Build 4029153 on Fri Oct 13 20:13:54 MDT 2023
IP Build 4028589 on Sat Oct 14 00:45:43 MDT 2023
SharedData Build 4025554 on Tue Oct 10 17:18:54 MDT 2023
Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
Copyright 2022-2023 Advanced Micro Devices, Inc. All Rights
Reserved.
> In downstream.AvailableTool.queryToolVersion
In downstream/AvailableTool/checkToolVersion
In downstream/AvailableTool/loadToolPathInfo
In downstream/AvailableTool/loadToolOnSystemPath
In downstream/AvailableToolList/loadAllToolsOnSystemPath
In downstream/AvailableToolList/buildAvailableToolList
In downstream.AvailableToolList.refreshToolList
In downstream.integration
In utilHDLAdvisorStart
In hdladvisor
In hdlToolStrip>runWorkflow (line 829)
In hdlToolStrip>WorkflowAdvisorCB (line 289)
In hdlToolStrip (line 7)
Warning: Defaulting to synthesis tool version 2022.1.
I can proceeed with warnings until I get to step 4. Embedded System Integration. From there, it fails and I cannot create a project because of this issue. I am able to run a -version command in my terminal and it retrieves the version so I'm unsure of what the problem is or how to fix it. I also chose a separate installation directory and verified that it works, so the hdlsetuptoolpath also doesn't seem to be the root of the problem.
Also-- I am using MATLAB R2023b, Vivado 2023.2 for my target device (Analog Devices CN0585), Ubuntu 20.4
Any help would be greatly appreciated!

Accepted Answer

Kiran Kintali
Kiran Kintali on 19 Feb 2025
Edited: Kiran Kintali on 19 Feb 2025
Please review this post that is relevant here.
HDL Coder users have the option to invoke any unsupported version of Vivado by selecting the "Allow Unsupported Version" option in HDLWFA. However, it's important to note that we may not be able guarantee successful completion of all steps, as the Vivado version is not fully qualified internally.
Furthermore, the issue the you may be experiencing might be due to an incorrect Vivado path configuration. For instance, even though you mentioned using Ubuntu OS, if you set the path to a Windows version of Vivado, MATLAB will default to one of the supported Vivado version in that release and may display the same warnings reported above.
Please review these aspects and try again. Do not hesitate to reach to tech support for additional help.
  1 Comment
Ezenia
Ezenia on 24 Feb 2025
Thank you! I had already checked off the box allowing the unsupported version when I got that message. I made sure to check the correct paths and just get a warning because it's 2023.2 and not 2022.2, so it should be fine.

Sign in to comment.

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!