VHDL DE2 board understanding Processes and Signals

Question

So I wrote a program to turn on LEDS if SW, a switch, is '1'  and off if '0'.   entity StateLCD is 
	port(
		SW : in std_logic_vector(0 downto 0);
		LEDG : out std_logic_vector(7 downto 0);
		LEDR : out std_logic_vector(7 downto 0));
end StateLCD;
architecture StateLCD_Behaviour of StateLCD is
	
	SIGNAL LEDState: std_logic_vector(7 downto 0);
begin
	process(SW)
			
	begin
	
		if(SW = "1") THEN
			LEDState &lt;= "11111111";
		else
			LEDState &lt;= "00000000";
		end if;
		
		LEDG &lt;= LEDState;
	end process;
end StateLCD_Behaviour;
  It works, but shouldn't it only work if I used variables instead of signals? With signals, It seems like the LEDS should be turning off when SW is '1' and turning on at '0' since signals only update at the end of a process. So I would be getting the opposite of the output I want? Where as variables would update immediately. Thanks for any help.

altera_forum · Answer

Simple answer: Sensitivity lists are ignored in hardware synthesis.  The bad with the present code is that a RTL simulation behaves different than the hardware.

altera_forum · Answer

--- Quote Start ---  So I wrote a program to turn on LEDS if SW, a switch, is '1'  and off if '0'.   entity StateLCD is 
    port(
        SW : in std_logic_vector(0 downto 0);
        LEDG : out std_logic_vector(7 downto 0);
        LEDR : out std_logic_vector(7 downto 0));
end StateLCD;
architecture StateLCD_Behaviour of StateLCD is
    
    SIGNAL LEDState: std_logic_vector(7 downto 0);
begin
    process(SW)
            
    begin
    
        if(SW = "1") THEN
            LEDState &lt;= "11111111";
        else
            LEDState &lt;= "00000000";
        end if;
        
        LEDG &lt;= LEDState;
    end process;
end StateLCD_Behaviour;
It works, but shouldn't it only work if I used variables instead of signals? With signals, It seems like the LEDS should be turning off when SW is '1' and turning on at '0' since signals only update at the end of a process. So I would be getting the opposite of the output I want? Where as variables would update immediately. Thanks for any help.  --- Quote End ---     Variable or signal will do since in both cases the assignment is fixed to same thing that depends only on switch state.

altera_forum · Answer

your sensitivity list only takes care of "SW", which means your process is only executed when there is any change in SW. signals are updated at the end of process, with your code it means the LEDG is assigned with the existing(previous) value.

anyway, if you want to tie signals to outputs, you don't need to put them inside process

altera_forum · Answer

--- Quote Start ---  your sensitivity list only takes care of "SW", which means your process is only executed when there is any change in SW. signals are updated at the end of process, with your code it means the LEDG is assigned with the existing(previous) value.  --- Quote End ---  As FvM explained, this statement is only true with a simulator. A synthesizer will ignore the sensitivity list, and the best way to simulate what the synthesizer actually does is this code:process(SW,LEDState)
            
    begin
    
        if(SW = "1") THEN
            LEDState &lt;= "11111111";
        else
            LEDState &lt;= "00000000";
        end if;
        
        LEDG &lt;= LEDState;
    end process;I've changed the sensitivity list to contain all the signals that are read by the process. If you simulate this, when you change the switch state the process will be executed a first time, update LEDState, then run a second time and update LEDG. Then you get the same behaviour between the simulation and the synthesized code.

altera_forum · Answer

Ok. i think i might have misunderstood some things. thanks for clearing things up.

Forum Discussion

VHDL DE2 board understanding Processes and Signals

8 Replies

Recent Discussions

Agilex 7 F Series Transceiver Pins Allowed Voltages During Powerup/When Unpowered

LTC Connector DE10-Standard FPGA

QSPI DDR Interface with Cyclone10LP: Maximum frequency

System PLL of Agliex5 PCIE example design cannot be locked after configuration

MAX 10 FPGA POR trip Levsl and tRAMP