Changeset 10565
- Timestamp:
- 05/04/11 14:11:13 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
firmware/FAD/FACT_FAD_20MHz_VAR_PS/FACT_FAD_lib/hdl/w5300_modul.vhd
r10500 r10565 125 125 RD_3, 126 126 RD_4, 127 RD_5, 127 RD_5, 128 WAIT_FOR_TRIGGER_ID_RESET_1, WAIT_FOR_TRIGGER_ID_RESET_2, 128 129 RD_6, 129 130 READ_COMMAND_DATA_SECTION, … … 201 202 X"61A8", X"0000", X"0000", X"0000", X"7080", X"7080", X"7080", X"7080", --<<-- DACs 202 203 X"0000", 203 X" 0000", X"0000"204 X"1234", X"ABCD" -- MSword // LSword 204 205 ); 205 206 … … 893 894 when CMD_RESET_TRIGGER_ID => 894 895 reset_trigger_id <= '1'; 895 state_read_data <= RD_5;896 state_read_data <= WAIT_FOR_TRIGGER_ID_RESET_1; 896 897 897 898 when CMD_WRITE => … … 902 903 end case; 903 904 -- read data 904 905 906 when WAIT_FOR_TRIGGER_ID_RESET_1 => 907 state_read_data <= WAIT_FOR_TRIGGER_ID_RESET_2; 908 when WAIT_FOR_TRIGGER_ID_RESET_2 => 909 state_read_data <= RD_5; 905 910 -- these states are beeing processed, if the 'command' was a 'write command' 906 911 -- so it is assumed, that some data in config RAM changed, and we need full (re)config
Note:
See TracChangeset
for help on using the changeset viewer.