Honored ContributorHi all,
making the code coverage with Modelsim on my VHDL testbench, the result is 100%, but only a single instruction is covered, which is the one that calls the sub-module within the testbench. Is there the possibility to make a deeper Code Coverage, going covering also the sub-module within the testbench? Thanks to all.
Honored ContributorI would have thought, that depends on how you right the testbench. You should generate test cases that should exercise all parts of the design, maybe even move into constrained random testing.
I dont understand what you mean by "single instruction", and "calls a module". There are no instructions in VHDL, and you cannot "call" a module. Components are instantiated, functions are called.Honored ContributorHi Tricky,
in fact a function is called: "wait;" . Here's a part of code:library ieee;
use ieee.std_logic_1164.all;
...
entity testbench is
generic(
...
);
end testbench;
architecture arch of testbench is
signal reset : std_logic;
begin
the_reset_sim : RESET_SIM -- RESET_SIM instance
generic map
(
WIDTH=>100
)
port map
(
reset_o=>reset
);
PeriodMeter : period_meter --my module instance
generic map
(
PULSE_CNT_BITS=>PULSE_CNT_BITS,
TIME_CNT_BITS=>TIME_CNT_BITS,
PRESCALE_VAL=>PRESCALE_VAL
)
port map
(
clk_i=>o_clk,
reset_i=>reset,
in_i=>o_clk,
d_o=>o_register
);
SimProcess : process
begin
wait; -- this is the only one function called
end process SimProcess;
end arch;this code does nothing. The wait you see just tells the process to halt (because a process is just a never-ending loop).
You will need to generate a reset and clock in the testbench to stimulate the period meter, along with any other inputs.Honored ContributorWhat compilation options are you using in Modelsim? I think that code coverage will probably be disabled if optimizations are enabled during the compilation.
I've never used code coverage in Modelsim (the version distributed with Quartus doesn't include that) but maybe you'll find more information about that in the manual.Honored ContributorYou have to enable code coverage for your unit/device under test (in your case "period_meter") if you want to see if these are covered. A 100% code coverage of your testbench just tells you that all instructions in your testbench are executed but not what coverage your unit under test has.
As Tricky said already you need to generate a stimulus for your unit under test or you will get 0% coverage for your component.
