Changes

Jump to navigation Jump to search
m
no edit summary
Line 48: Line 48:     
As described above, these states form the outline of the functional block diagram. This implementation calls for a central ''state register''.  Each block reads the state value in the register and enables itself upon seeing its own value.  After completion of its function, a block will write a new value to the state register to enable the next block. With several modules writing to the register, usual precautions must be taken to avoid more than one drivers forcing a line simultaneously. All modules must be designed to go to high impedance on their output lines when they are not active.
 
As described above, these states form the outline of the functional block diagram. This implementation calls for a central ''state register''.  Each block reads the state value in the register and enables itself upon seeing its own value.  After completion of its function, a block will write a new value to the state register to enable the next block. With several modules writing to the register, usual precautions must be taken to avoid more than one drivers forcing a line simultaneously. All modules must be designed to go to high impedance on their output lines when they are not active.
 +
 +
 +
== Miscellaneous non-state-based components ==
 +
 +
Please refer to the individual design detail pages for:
 +
* [[FPGA_Registers|Registers]]
 +
* [[FPGA_Reusables|Miscellaneous Reusable Components]]
 +
    
== Interface ==
 
== Interface ==
Line 69: Line 77:  
[[Image:DigBoardScheme.png|center]]
 
[[Image:DigBoardScheme.png|center]]
   −
== Miscellaneous non-state-based components ==
     −
Please refer to the individual design detail pages for:
  −
* [[FPGA_Registers|Registers]]
  −
* [[FPGA_Reusables|Miscellaneous Reusable Components]]
       
1,004

edits

Navigation menu