Honored Contributor
Honored ContributorHi,
Please take this with a grain of salt. I use NativeLink sparsely and I don't have the tools at hand to confirm. In ModelSim the /x/ will be top level entity *of the simulation*, which should be your test bench. So, when modelsim complains about /selector/ which is your module's name, it suggests you've mixed up your module's name, the instance name and your testbench's name. So, let's assume your test bench look something like this: entity selector_tb is end entity; architecture behavioral of selector_tb is begin ... uut : selector port map ( blablabla); ... end behavioral; Your testbench's entity name is "selector_tb". The module's entity name is "selector" but it's instance name within you testbench is "uut", "uut" stands for unit under test, in case you wonder. IIRC, when setting up native link, you need to tell it both the testbench's entity name (selector_tb) and the instance name in your testbench (uut). So, in ModelSim you'll have an hierachy like selector_tb/ +- dut/ +- selector's contents +- other stuff in your test bench
