1,004
edits
Changes
Jump to navigation
Jump to search
mLine 58:
Line 58: − This block provides a level of abstraction between the precise CP2200/1 interface and a generalized interface seen by the internal blocks of the FPGA. It takes information on the next transfer to carry out and returns information on the last transfer completed. It has a pulse signal to begin a transfer and a pulse signal to notify of a completed transfer. This eliminates a need for the internal workings of the FPGA to be aware of the timing of the interface; it simply begins a transfer and waits for notification of the transfer's completion. The transceiver is intended to function on the Multiplexed Intel bus format to communicate with the CP2200/1.+ Line 84:
Line 84: + Line 95:
Line 96: + Line 106:
Line 108: + Line 118:
Line 121: + Line 130:
Line 134: + − + + + + + + + + + + + + + + + +
Programming the Ethernet controller (view source)
Revision as of 06:18, 29 October 2007
, 06:18, 29 October 2007→Non-State Components
==== transceiver ====
==== transceiver ====
This block provides a level of abstraction between the precise CP2200/1 interface and a generalized interface seen by the internal blocks of the FPGA. It takes information on the next transfer to carry out and returns information on the last transfer completed. It has a pulse signal to begin a transfer and a pulse signal to notify of a completed transfer. This eliminates a need for the internal workings of the FPGA to be aware of the timing of the interface; it simply begins a transfer and waits for notification of the transfer's completion. The transceiver is intended to function on the Multiplexed Intel bus format to communicate with the CP2200/1.
inputs
inputs
inouts
inouts
* ''AD'': 8-bit address and data bus
* ''AD'': 8-bit address and data bus
==== State Register ====
==== State Register ====
outputs
outputs
* ''Q'': three-bit data-out bus
* ''Q'': three-bit data-out bus
==== temperature register ====
==== temperature register ====
outputs
outputs
* ''Q'': ten-bit data-out bus
* ''Q'': ten-bit data-out bus
==== ADC registers ====
==== ADC registers ====
outputs
outputs
* ''Q'': 12-bit data-out bus; outputs data of register chosen by S bus
* ''Q'': 12-bit data-out bus; outputs data of register chosen by S bus
==== DAC registers ====
==== DAC registers ====
outputs
outputs
* ''Q'': 14-bit data-out bus; outputs data of register chosen by S bus
* ''Q'': 14-bit data-out bus; outputs data of register chosen by S bus
==== Reusable Components ====
==== Reusable Components ====
===== Components Interface with Transceiver =====
Several components were found useful as reusable units rather than unique modules.
===== Byte Fetcher (<tt>getByte</tt>) =====
Fetches a byte of data from the Ethernet Controller control and data registers. This unit helps abstract and package the communication steps with the transceiver. The two step process of sending a request with all accompanying parameters and waiting for reply is now a matter of a single "call". Aside from packaging, the component ensures proper timing among the sent signals. The actual request is performed via the <tt>reqFromAddr</tt> unit described below.
===== Auto-reader (<tt>AutoRd</tt>) =====
Performs the same function as the Byte Fetcher (described above) but is hard-wired to address the RXAUTORD (0x01). This is convenient because the Ethernet Controller's AutoRead interface will be used extensively to parse through packets. <tt>AutoRd</tt> is in fact a wrapper around <tt>GetByte</tt> passing through all signals accept the fixed address input.
===== Read Request (<tt>reqFromAddr</tt>) =====
Sends request for reading (R/W pin high) to transceiver at the specified address. "Go" pulse is appropriately delayed to ensure that parameter signals sent to transceiver have gone through their transitions. This unit is not intended for direct use, but rather to be the core of the fetcher components described above.
===== Write Request (<tt>reqFromAddr</tt>) =====
Sends a write request (R/W pin low) to transceiver at the specified address with the specified byte of data. The primary reason of this instruction "packaging" is to obscure the complexity of appropriate delays to ensure proper signal latching.
===== Miscellaneous Components =====
===== Miscellaneous Components =====