Forum Discussion
Altera_Forum
Honored Contributor
Honored ContributorStrange comparator behavior
I have a simple comparator project which compares two 2-bit words. I wrote a code, but time diagrams show some strange behavior:
library IEEE;
use IEEE.std_logic_1164.all;
entity cmp is
port ( x0, x1, y0, y1, L, E, G : in std_logic;
Lo,Eo,Go : out std_logic);
end cmp;
architecture behav of cmp is
signal LEG: std_logic_vector(0 to 2);
begin
process (x0,x1,y0,y1,L,E,G)
begin
if x1>y1 then LEG<="001";
elsif x1<y1 then LEG<="100";
else
if x0>y0 then LEG<="001";
elsif x0<y0 then LEG<="100";
else
if G='1' then LEG<="001";
elsif L='1' then LEG<="100";
else LEG<="010";
end if;
end if;
end if;
end process;
Lo<=LEG(0); Eo<=LEG(1); Go<=LEG(2);
end behav;
2 Replies
Altera_Forum--- Quote Start --- I have a simple comparator project which compares two 2-bit words. I wrote a code, but time diagrams show some strange behavior:
https://alteraforum.com/forum/attachment.php?attachmentid=13620&stc=1 I looked through my code but didn't find a mistake which makes for example "Go" output to fall and rise near the 50th ns. Is it my mistake or maybe Max+Plus II (v.10.0) bug? --- Quote End --- I guess you are doing a gate-level simulation where real delays in silicon come in to play. Not all paths from input to output have the same levels of logic and as a result you get these glitches. Now you did build a truly asynchronous circuit, and these are inherently prone to race and glitch conditions. Google asynchronous race glitch (https://www.google.be/search?client=opera&q=asynchronous+race+glitch&sourceid=opera&ie=utf-8&oe=utf-8) and you will find lots of info to learn all about it.library IEEE; use IEEE.std_logic_1164.all; entity cmp is port ( x0, x1, y0, y1, L, E, G : in std_logic; Lo,Eo,Go : out std_logic); end cmp; architecture behav of cmp is signal LEG: std_logic_vector(0 to 2); begin process (x0,x1,y0,y1,L,E,G) begin if x1>y1 then LEG<="001"; elsif x1<y1 then LEG<="100"; else if x0>y0 then LEG<="001"; elsif x0<y0 then LEG<="100"; else if G='1' then LEG<="001"; elsif L='1' then LEG<="100"; else LEG<="010"; end if; end if; end if; end process; Lo<=LEG(0); Eo<=LEG(1); Go<=LEG(2); end behav;- Altera_Forum
There are also issues with your code.
You are using std_logic inputs, and using > to compare them. in VHDL, std_logic is a 9 state type, with ('U', 'X'. '0', '1', 'Z', 'W', 'L', 'H', '-') as all the states. In simulation, using > may lead to some odd situations as 'Z' and '-' are bother greater than '1'. In real hardware, only '0' and '1' can exist (and 'Z' on a tri state, but it cannot be checked for on hardware). So, I recomend using only = when comparing std_logic
