"Open IP example design" not using the requested HDL?

[eml]

I'm generating some Ethernet IP on 2015.4 (10G Ethernet PCS/PMA (10GBASE-R/KR)), on two different computers. The xci requests Verilog output. On one computer, I actually get Verilog output. On the second computer, Vivado generates VHDL output, and modifies my xci to change the requested HDL from Verilog to VHDL.

Does anyone have a fix for this? It only happens on the Vivado GUI for "Open IP example design" - running a tcl open_example_project does the right thing.

[balkris]

check the product guide . The reason is only VHDL example design available so even if you are targeting for verilog you will vhdl only . Information provided in product guide

[balkris]

what is the core version and IP name. In case product guide mention both language than core should generate both language example design

[anusheel]

@eml

As per my understanding from your post, you are using two separate projects in two separate machines to generate two separate .xci files. One project uses VHDL to deliver IP files and other project uses Verilog?

What was the targeted language used under project settings before generating the core?

Thanks,
Anusheel
-----------------------------------------------------------------------------------------------
Search for documents/answer records related to your device and tool before posting query on forums.
Search related forums and make sure your query is not repeated.

Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------

[eml]

Not quite - exactly the same project, being implemented on two different computers. The xci requests Verilog. This works on one computer, producing Verilog, as expected. On the second computer, it actually produces VHDL, and changes the xci to show VHDL instead of Verilog. The only way to get the requested Verilog files on the second computer is to run the tcl directly.

[anusheel]

@eml

Can you please upload the scripts here for us to understand the flow?

Thanks,
Anusheel
-----------------------------------------------------------------------------------------------
Search for documents/answer records related to your device and tool before posting query on forums.
Search related forums and make sure your query is not repeated.

Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------

[eml · Accepted solution]

Ok, fixed, I think. The problem happens when you have a project which needs both VHDL and Verilog output.

If you use the GUI to 'Open IP example design', then the target language in the xci file (PROJECT_PARAM.PREFHDL) is ignored, and the project's target language is used instead (Tools > Project Settings > Target language). So, you have to set the target language independently in the GUI for each set of example design outputs.

However, if you use the tcl flow, open_example_project does correctly read PROJECT_PARAM.PREFHDL from the xci.

[eml]

However, if you use the tcl flow, open_example_project does correctly read PROJECT_PARAM.PREFHDL from the xci.

But read_ip does not. This all needs to be documented somewhere.