I have not dug into the details, although seems like has looked at it and confirmed there is a different issue. Isn't everybody running into this problem? Does that mean everybody uses the non-project flow? I get this error all the time and it is pretty much impossible to learn the tool flow when I can't get any simulations working. I get the same error when I create a project with the target language as Verilog and the simulation language as Mixed.I had a previous post on this subject.but closed it since I was getting all kind of different answers that were not working.As a person who is just trying to learn Vivado, I am really confused. The top level file has to go into the non-default work libraryThe only workaround that i can think of right now is the same as that was already called out and that is to use the non-project flow.The issue is with how Vivado is passing the information to the scripts and this is why in integrated flow when we cannot find the correct top, you run into this issue.ThanksDuth. Vivado project management flow cannot parse the hierarchy and thus the user has to specify the top3. If I set the automatic compile order on the main project it takes a moderately long time to evaluate, and the automatic rules get the order wrong. Note the change in the command for xelab:Running: C:/Xilinx/Vivado/2015.1/bin/unwrapped/win64.o/xelab.exe -wto 2ea3f3fd9d5c45a398e9ba956659405c -debug typical -relax -mt 2 -L TestXil -L MVhdl -L secureip -snapshot il1behav MVhdl.il1 -log elaborate.logUsing 2 slave threads.I believe this issue wont happen if you are using scripted mode and you manually force the. The below order doesnt work:Running: C:/Xilinx/Vivado/2015.1/bin/unwrapped/win64.o/xelab.exe -wto 2ea3f3fd9d5c45a398e9ba956659405c -debug typical -relax -mt 2 -L MVhdl -L TestXil -L secureip -snapshot il1behav TestXil.il1 -log elaborate.logUsing 2 slave threads.ERROR: XSIM 43-3225 Cannot find design unit TestXil.il1 in library work located at xsim.dir/work.But this one works. To add my observation in your testcase, the compile order has some effect here with il1 set as TOP. However, il1 is in MVhdl.The issue looks like it might be related to project option:But, whatever the reason, I would like to be able to specify exactly the entity to simulate, including the library the entity comes from.Ian Lewis. I also tried just naming the entity, il1, and that simulated TestXil.il1. I have the top simulation target set to MVhdl.il1.
0 kommentar(er)
