Support for third party testbench wrappers about edalize HOT 3 OPEN

I'm currently working around this by supplying a TCL file in the fileset that performs the actual simulation. However, empty top level lists are not supported in a target, so I've had to create a dummy entity and architecture that do nothing, and specify this as the top level in the target. It isn't ideal, but it does work. I'm wondering if supporting an empty lop level list might be a neatest way to handle testbenches that need to be explicitly scripted like this?

from edalize.

Hi,

Sorry for the lack of replies. This does sound like a tricky problem. Very annoying that they need their own setup to achieve this. Good to hear that you managed to hack your way around this at least.

I'm not sure either which would be the best way to handle this. Allowing an empty toplevel list could be one way to achieve what you're looking for. Perhaps allowing to override the simulation run command could be another. Right now I think you're in a better position than me to judge what would be the easiest and least intrusive way to support this. Also trying to think of similar issues and if this would help in those cases as well

from edalize.

I'm starting to consider tools like FuseSoC or just using Edalize, and this issue with simulating Quartus IP has been the thing I'm worried about the most.

As @DHWinterWolf described, to simulate IP (even floating point entities, not just DDR3 controller IP, for example) you have to generate a simulation setup script from Quartus, open your simulator (Modelsim), then call said setup script.

@olofk Two years later, any new ideas on how to easily handle this, or new features that have already been added since the original post?

from edalize.