The differences between behaviors of 'std_logic_vector' and

[Weng Tianxiang]

Hi,
Based on suggestions from this group, when switching libraries from
USE ieee.std_logic_1164.all;
use ieee.std_logic_unsigned.all;
use ieee.std_logic_arith.all;

to
USE ieee.std_logic_1164.all;
use ieee.numeric_std.all;

this morning I really found a big new issue dealing with
'std_logic_vector' and 'unsigned'.

Here is the definition of 'unsigned' from ieee.numeric_std.vhd:
type UNSIGNED is array (NATURAL range <&gt of STD_LOGIC;

Here is the definition of 'std_logic_vector' from ieee.stdlogic.vhd:
TYPE std_logic_vector IS ARRAY ( NATURAL RANGE <&gt OF std_logic;

Actually one cannot see any big differences between 'unsigned' and
'std_logic_vector'.

But the following code shows big differences between the two's
behaviors within a generate loop:

signal A : unsigned(1 downto 0);
....

Generate_A : for I in 0 to 3 generate
ModuleX : port map (
...
A => A(I), <-- error due to A's range between 1-0 while I = 2
...
);
end generate;

signal A : std_logic_vector(1 downto 0);
....

Generate_A : for I in 0 to 3 generate
ModuleX : port map (
...
A => A(I), <-- no error, because integer I is between 3-0
-- and A's range is 3-0 due to its definition
of 2 bits
...
);
end generate;

Why?

Thank you.

Weng

 

[Mike Treseler]

Weng Tianxiang wrote:

Actually one cannot see any big differences between 'unsigned' and
'std_logic_vector'.

The package contains much more than that type declaration.
Have a look at the functions that cover unsigned.

http://www.csee.umbc.edu/help/VHDL/packages/numeric_std.vhd

-- Mike Treseler

 

[Weng Tianxiang]

Sorry! I found the error. The error is not related to what I have
thought,
it relates to situation:
std_logic => A(I),
In a generate loop as following:
Lable_A : for I in 0 to 3 generate
.... port map (
...
A => A(I),
...
);

A() must be declared as
signal A : unsigned(3 downto 0);

And it cannot be decleared as
signal A : unsigned(1 downto 0); <-- my error

Thank you.

Weng