cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
691 Views
Registered: ‎02-14-2019

Vivado Behavioral Simulation getting stuck with Riviera Pro Simulator

Jump to solution

Hi All,

I created a Vivado project and ran a simulation using the default Vivado simulator, everything works as expected (i.e the testbench and the waveforms)

When I switch the "Target Simulator" to "Riviera Pro Simulator" and run a behavioral simulation, Vivado is getting stuck and the linux terminal shows-
"[1]+ Stopped /scratch/Xilinx/Vivado/2018.2/bin/vivado"

My only option is to kill the process. There isn't any error message, and I can only see that the last stage was-
"Executing analysis and compilation step..." (please see image attached).

Techincal details-
- Vivado version- 2018.2
- Riviera Pro 2018.10.137.7135 built for Linux64
- I pre compiled all Xilinx libraries using "Tools>Compile Simulation Libraries" and I'm pointing the the appropriate "compile_simlib/riviera" in "simulation setting"
- I used the following tutorial to set up evryting-
https://www.aldec.com/en/support/resources/documentation/articles/1525

Can anyone please help me?

Thanks!

vivado_stuck.png
Screenshot from 2019-02-20 11-02-36.png
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Visitor
Visitor
610 Views
Registered: ‎02-14-2019

Solved!

I realized I had 2 versions of Riviera installed (2015 and 2018) and while the Xilinx pre compiled libraries was generated for 2018, the PATH launched Riviera 2015 which caused a mismatch.

After I fixed the paths and it works :)

View solution in original post

0 Kudos
2 Replies
Highlighted
Xilinx Employee
Xilinx Employee
645 Views
Registered: ‎07-16-2008

Does it work fine if you take the generated script and run it in standalone Riviera Pro?

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
Visitor
Visitor
611 Views
Registered: ‎02-14-2019

Solved!

I realized I had 2 versions of Riviera installed (2015 and 2018) and while the Xilinx pre compiled libraries was generated for 2018, the PATH launched Riviera 2015 which caused a mismatch.

After I fixed the paths and it works :)

View solution in original post

0 Kudos