VHDL测试台代码未显示1bit fulladder的输出结果

VHDL testbench code not showing output result of 1bit fulladder

提问人:bhaggya umayangana salwathura 提问时间:4/15/2021 最后编辑:bhaggya umayangana salwathura 更新时间:4/16/2021 访问量:536

问:

这里代码有一些警告,但没有发现错误,但测试台的这个fulladder输出波形和和进位没有显示。在进位和总和输出中显示了 u,但不是输入很好,只有总和和进位输出是问题所在,为什么这里有一些警告,有时我对那个警告有疑问,在这里我附上了你参考它的图像,并给我一些建议来解决这个问题。在此处输入图像描述

 -- 1-bit full adder testbench
 -- A testbench is used to rigorously tests a design that you have made.
 -- The output of the testbench should allow the designer to see if
 -- the design worked. The testbench should also report where the testbench
 -- failed.
  LIBRARY IEEE;
  use IEEE.STD_LOGIC_1164.ALL;
  -- Declare a testbench. Notice that the testbench does not have any input
 -- or output ports.
entity tb_1bitfulladder is
end tb_1bitfulladder;
 -- Describes the functionality of the tesbench.
 architecture MY_TEST of tb_1bitfulladder is
 -- The object that we wish to test is declared as a component of
 -- the test bench. Its functionality has already been described elsewhere.
 -- This simply describes what the object's inputs and outputs are, it
 -- does not actually create the object.
     component FULL_ADDER
      port( x, y, Cin : in STD_LOGIC;
       s, Cout : out STD_LOGIC );
     end component;
     -- Specifies which description of the adder you will use.
     --for U1: FULL_ADDER use entity WORK.FULL_ADDER(MY_DATAFLOW);
     -- Create a set of signals which will be associated with both the inputs
     -- and outputs of the component that we wish to test.
    signal X_s, Y_s : STD_LOGIC:='0';
    signal CIN_s : STD_LOGIC:='0';
    signal SUM_s : STD_LOGIC;
    signal COUT_s : STD_LOGIC;
    -- This is where the testbench for the FULL_ADDER actually begins.
  BEGIN
   -- Create a 1-bit full adder in the testbench.
    -- The signals specified above are mapped to their appropriate
     -- roles in the 1-bit full adder which we have created.
  UUT: FULL_ADDER port map (x=>X_s,       --(//this line has some warning i put it below END Othecode)
                         y=>Y_s,
                         Cin=>CIN_s,
                         s => SUM_s, 
                         Cout=> COUT_s
);
  -- The process is where the actual testing is done.       
  -- stimulus process
   stim_proc:process
      begin
  -- We are now going to set the inputs of the adder and test
  -- the outputs to verify the functionality of our 1-bit full adder.
  -- Case 0 : 0+0 with carry in of 0.
  -- Set the signals for the inputs.
   X_s <= '0';
   Y_s <= '0';
   CIN_s <= '0';
 -- Wait a short amount of time and then check to see if the
 -- outputs are what they should be. If not, then report an error
  -- so that we will know there is a problem.
  wait for 10 ns;

  assert ( SUM_s = '0' ) report "Failed Case 0 - SUM" severity error;
  assert ( COUT_s = '0' ) report "Failed Case 0 - COUT" severity error;
  wait for 40 ns;
   -- Carry out the same process outlined above for the other 7 cases.
   -- Case 1 : 0+0 with carry in of 1.
   X_s <= '0';
   Y_s <= '0';
   CIN_s <= '1';
   wait for 10 ns;
   assert ( SUM_s = '1' ) report "Failed Case 1 - SUM" severity error;
   assert ( COUT_s = '0' ) report "Failed Case 1 - COUT" severity error;
   wait for 40 ns;
-- Case 2 : 0+1 with carry in of 0.
   X_s <= '0';
   Y_s <= '1';
   CIN_s <= '0';
   wait for 10 ns;
   assert ( SUM_s = '1' ) report "Failed Case 2 - SUM" severity error;
   assert ( COUT_s = '0' ) report "Failed Case 2 - COUT" severity error;
   wait for 40 ns;
  -- Case 3 : 0+1 with carry in of 1.
   X_s <= '0';
   Y_s <= '1';
  CIN_s <= '1';
  wait for 10 ns;
  assert ( SUM_s = '0' ) report "Failed Case 3 - SUM" severity error;
  assert ( COUT_s = '1' ) report "Failed Case 3 - COUT" severity error;
  wait for 40 ns;
 -- Case 4 : 1+0 with carry in of 0.
  X_s <= '1';
  Y_s <= '0';
 CIN_s <= '0';
 wait for 10 ns;
 assert ( SUM_s = '1' ) report "Failed Case 4 - SUM" severity error;
 assert ( COUT_s = '0' ) report "Failed Case 4 - COUT" severity error;
 wait for 40 ns;
 -- Case 5 : 1+0 with carry in of 1.
  X_s <= '1';
  Y_s <= '0';
  CIN_s <= '1';
  wait for 10 ns;
  assert ( SUM_s = '0' ) report "Failed Case 5 - SUM" severity error;
  assert ( COUT_s = '1' ) report "Failed Case 5 - COUT" severity error;
  wait for 40 ns;
  -- Case 6 : 1+1 with carry in of 0.
   X_s <= '1';
   Y_s <= '1';
   CIN_s <= '0';
   wait for 10 ns;
    assert ( SUM_s = '0' ) report "Failed Case 6 - SUM" severity error;
    assert ( COUT_s = '1' ) report "Failed Case 6 - COUT" severity error;
   wait for 40 ns;
  -- Case 7 : 1+1 with carry in of 1.
   X_s <= '1';
   Y_s <= '1';
   CIN_s <= '1';

   wait for 10 ns;
  assert ( SUM_s = '1' ) report "Failed Case 7 - SUM" severity error;
  assert ( COUT_s = '1' ) report "Failed Case 7 - COUT" severity error;
  wait for 40 ns;
  end process;
END MY_TEST;
Warning: ELAB1_0026: tb_1bitfulladder.vhd : (35, 0): There is no default binding for component     "FULL_ADDER". (No entity named "FULL_ADDER" was found).
VHDL 测试台 Active-HDL

评论

0赞 Tricky 4/15/2021
该错误是因为它找不到 的代码。您需要在模拟之前添加它。FULL_ADDER
0赞 bhaggya umayangana salwathura 4/15/2021
这不是一个错误,而是一个警告,如果这是一个错误,那么我无法像上面的附图一样运行模拟。
0赞 4/16/2021
在未绑定一个或多个组件实例化的情况下详细说明设计层次结构并不违法,将其视为未安装组件的面包板。这是 VHDL 标准明确允许的。您没有显式绑定,默认绑定不会将实体FULL_ADDER标识为直接可见,它尚未成功分析(编译)并添加到工作库中,并且没有库子句和 use 子句使其在另一个引用库中可见。模拟器供应商为那些不打算让组件未绑定的人添加了警告。
0赞 4/16/2021
这个未注释的 UUT 替换了 U1 将是一个配置规范,提供显式绑定指示。您的课程讲师希望您成功地将实体FULL_ADDER和架构 DATAFLOW 分析到当前工作库中。如果具有明确的绑定指示,则会出现错误。--for U1: FULL_ADDER use entity WORK.FULL_ADDER(MY_DATAFLOW);
0赞 4/16/2021
IEEE Std 1076-2008 13.5 分析顺序 “如果在尝试分析设计单元时检测到任何错误,则尝试的分析将被拒绝,并且对当前工作库没有任何影响。”您是否尝试将FULL_ADDER及其架构分析到当前工作库中,但失败了吗?

答: 暂无答案