Programming the Ethernet controller
The modules involved in communication with the Ethernet Controller chip serve as the core of the FPGA. The different tasks that need to be performed by these modules include
- executing the complex board reset and address lookup sequence
- polling for new packets and switching execution accordingly
- collecting sensor information upon a status report request
- programming the DAC upon a program packet receipt
- building return packets
In our design, the modules involved with packet handling and interfacing with sensor chip controllers are organized by state. A state register specifies the current stage of the process and only the corresponding module is allowed to act during that stage. Aside from defining a process sequence, the state serves as a complex "enable" signal for the modules, ensuring that only one module is driving the communication bus used to query the Ethernet Controller chip.
Interface
- See also: Ethernet packets
The compact approach to wire and poll the Ethernet Controller chop is via the Multiplexed Intel bus format. Aside from some use of the interrupt and reset pins, all communication is done via this bus. (The control architecture of the chip uses 8-bit registers selected with 8-bit addresses.) A communication over this bus begins with an pulse on the "ALE" pin, by the fall of which a valid address is expected on the 8-bit inout "AD" bus. After this /RD (/WR) signal falls, executing the read (write) process, and then rises accompanied with valid input from (to) the chip. The adjacent figure illustrates this process along with the approach to timing the conversation taken in this design. Please refer to Section 16.2 in the manual for details on the timing tolerances on this bus.
As shown in the figure, the 20 MHz clock is very convenient for metering this conversation. The communication delay for the FPGA (most of which runs essentially on 5 MHz) turns out to be only two clock cycles.
The eight states
There are eight major states to the module.
State list
| State | Module Name | Description | Succeeding State |
|---|---|---|---|
| 000 | Reset_hard | Coordinates the reset and start-up of the Ethernet Controller chip. | 101 |
| 001 | Reset_soft | Extends the reset to the PC-requested chips and records PC's MAC for later communication. | 101 |
| 010 | Idler | This is the active module during the FPGA's default idle state. It awaits the "Receive FIFO buffer not empty" interrupt and passes control to the Reader | 011\ |
| 011 | Reader | Skips the packet header and reads the first two bytes ("location" and "type") of the packet payload. It rejects misdirected or invalid-type bytes. Control is passed according to packet type to Query, Program or Reset Modules | 100, 110, 000, 001 |
| 100 | Querier | Queries the values of the Temperature sensor and ADC, stores them in their respective registers and passes control to the Transmitter for delivery | 101 |
| 110 | Programmer | Programs the DAC based on instructions in packet and stores the values in the DAC register. |
- (000) Reset Cycle
- The reset cycle resets the selected chips. There are flags for resetting all 4 chips: DAC, ADC, temperature sensor, Ethernet controller. This is the entry state from a power-on. From this state, proceed unconditionally to 001.
(001) Transmit "I"This state transmits an "I" packet to acknowledge that a reset occurred but the board is now prepared to accept new packets and function normally. From this state, proceed unconditionally to 010."S"-Packet (from state 101) would do just as well, returning zeroed registers, location address etc for computer's address LUT.- (010) Idle
- This is the idle state where the state machine awaits a new packet's arrival. If the Receive FIFO is empty, it loops back on itself and continues checking the FIFO. If the FIFO is not empty, proceed to 011.
- (011) Read Packet
- This state accesses the first packet. If packets need to be filtered by the FPGA, this state will filter and return to 010 on a bad packet. The MAC data is discarded, as it is unimportant to the FPGA, and the first data byte is read. This byte is used as a switch: an ASCII "R" loops to 000. A "Q" proceeds to 100. A "P" proceeds to 110. Any other value is a bad packet and the state machine returns to 010.
- (100) Poll Status
- This state polls the status chips (the ADC and the temperature sensor) so that recent data is ready for transmission.
- (101) Transmit "S"
- This state packages and transmits an "S" packet over the Ethernet to report back the status of the board in response to a "Q" packet.
- (110) Program DAC
- This state programs the DAC with new values according to the mask and data in the "P" packet.
- (111) Transmit "D"
- This state packages and transmits a "D" packet over the Ethernet to report back the DAC voltages in response to a "P" packet.
State interconnect
These states will form the outline of the functional block diagram. Within each state will be a smaller process or set of processes, possibly broken into substates. 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.
State variable
Based on the assignments of state values to the various states, certain interpretations of the state's bits arise. They may or may not prove useful in coding the system. They are given here in the case that they do become useful.
- S2:1:
- S2 = 0: "Core cycle" that executes regularly and forms the spine of the state diagram.
- S2:1 = 00: "Initialization cycle" that prepares the state diagram for normal functioning.
- S2:1 = 01: "Standard cycle" that the state machine returns to most frequently to process appropriate switching to branches.
- S2 = 1: "Branch cycles" that execute selectively based on received packets.
- S2:1 = 10: "Query cycle" as described in the page on Ethernet packets.
- S2:1 = 11: "Programming cycle" as described in the page on Ethernet packets.
- S2 = 0: "Core cycle" that executes regularly and forms the spine of the state diagram.
- S0:
- S0 = 0: "Setup state" to prepare internal workings for a communication.
- S0 = 1: "Transfer state" to communicate with the external PC.
Controller
Foreword on Timing
With a controller this complex, the timing of signals must be inspected even more scrupulously than usual. In particular, simultaneous transitions of data and "Done" lines must be avoided. When possible, a one-cycle-delayed "Done" signal is used to ensure that the data lines have been stabilized. (All delays are implemented via the c_delay module which postpones the signal by one cycle via two sequential flip-flops, each shifting by half-cycle). When this is inconvenient (e.g. when writing to registers) the target component must not be enabled on rising edges on "Go" or the clock. The registers, for instance, have been designed to read values on the falling edge of the clock - middle of the "Go" pulse, safely after the data line transitions.
Packet Reader (Packet type inspection)
Miscellaneous Reusable Components
Emulator
Since the modules described here represent the core of the FPGA, their combined simulation calls for inclusion of all other fringe modules. Essentially the whole FPGA will have to be tested to ensure this scheme for the core is acting properly. The challenge is in the complexity of the stimulus for such simulation: whole packets will need to be sent in and possibly inter-packet Ethernet Controller Chip states tested.
A stripped down emulator for the Ethernet Controller has been written. It is a essentially a set of registers with a Multiplexed Intel bus communication layer and packet file read/write layers. These registers, however, are not passive memory banks but include "events" that are triggered by particular register states. For instance writing to registers designated to make up a receive buffer pointer actually delivers the requested byte from the buffer to the appropriate control register to be available for a subsequent request. A simple interrupt system (stimulated externally by the simulation layer) has also been included.