Chips-2.0 Demo for SP605 Development Card
|
Chips-2.0 Demo for Atlys Development Card
|
=========================================
|
=========================================
|
|
|
:Author: Jonathan P Dawson
|
:Author: Jonathan P Dawson
|
:Date: 2013-10-17
|
:Date: 2013-10-17
|
:email: chips@jondawson.org.uk
|
:email: chips@jondawson.org.uk
|
|
|
This project implements a TCP/IP stack. The TCP/IP stack acts as a server, and
|
This project implements a TCP/IP stack. The TCP/IP stack acts as a server, and
|
can accept a single connection to a TCP port. The connection is provided as a
|
can accept a single connection to a TCP port. The connection is provided as a
|
bidirectional stream of data to the application. The following protocols are supported:
|
bidirectional stream of data to the application. The following protocols are supported:
|
|
|
+ ARP request/response (with 16 level cache)
|
+ ARP request/response (with 16 level cache)
|
+ ICMP echo request/response (ping)
|
+ ICMP echo request/response (ping)
|
+ TCP/IP socket
|
+ TCP/IP socket
|
|
|
Synthesis Estimate
|
Synthesis Estimate
|
==================
|
==================
|
|
|
The TCP/IP server consumes around 800 LUTs and 300 Flip-Flops in a Xilinx Spartan 6 device.
|
The TCP/IP server consumes around 800 LUTs and 300 Flip-Flops in a Xilinx Spartan 6 device.
|
|
|
|
|
Dependencies
|
Dependencies
|
============
|
============
|
|
|
The stack is implemented in C, and needs Chips-2.0 to compile it into a Verilog
|
The stack is implemented in C, and needs Chips-2.0 to compile it into a Verilog
|
module.
|
module.
|
|
|
Source Files
|
Source Files
|
============
|
============
|
|
|
The TCP/IP stack is provided by two source files:
|
The TCP/IP stack is provided by two source files:
|
|
|
+ source/server.h
|
+ source/server.h
|
+ source/server.c
|
+ source/server.c
|
|
|
Configuration
|
Configuration
|
=============
|
=============
|
|
|
The following parameters can be configured at compile time within source/server.h:
|
The following parameters can be configured at compile time within source/server.h:
|
|
|
+ Local Ethernet MAC address (default: 0x000102030405)
|
+ Local Ethernet MAC address (default: 0x000102030405)
|
+ Local IP Address (default: 192.168.1.1)
|
+ Local IP Address (default: 192.168.1.1)
|
+ Local TCP Port number (default: 80 HTTP)
|
+ Local TCP Port number (default: 80 HTTP)
|
|
|
Compile
|
Compile
|
=======
|
=======
|
|
|
Compile into a Verilog module (server.v) using the following command::
|
Compile into a Verilog module (server.v) using the following command::
|
|
|
$ chip2/c2verilog source/server.v
|
$ chip2/c2verilog source/server.v
|
|
|
Interface
|
Interface
|
=========
|
=========
|
|
|
::
|
::
|
|
|
+-----------+
|
+-----------+
|
| SERVER |
|
| SERVER |
|
+-----------+
|
+-----------+
|
ethernet_rx [15:0] >===> >===> output_socket [15:0]
|
ethernet_rx [15:0] >===> >===> output_socket [15:0]
|
| |
|
| |
|
| |
|
| |
|
ethernet_tx [15:0] <===< <===< input_socket [15:0]
|
ethernet_tx [15:0] <===< <===< input_socket [15:0]
|
+-----------+
|
+-----------+
|
|
|
|
|
Ethernet Interface
|
Ethernet Interface
|
------------------
|
------------------
|
|
|
The Ethernet interface consists of two streams of data:
|
The Ethernet interface consists of two streams of data:
|
|
|
+ An input, input_eth_rx.
|
+ An input, input_eth_rx.
|
+ An output, output_eth_tx.
|
+ An output, output_eth_tx.
|
|
|
Both streams are 16 bits wide, and use the following protocol:
|
Both streams are 16 bits wide, and use the following protocol:
|
|
|
|
|
+------+-----------------+
|
+------+-----------------+
|
| word | designation |
|
| word | designation |
|
+------+-----------------+
|
+------+-----------------+
|
| 0 | length in bytes |
|
| 0 | length in bytes |
|
+------+-----------------+
|
+------+-----------------+
|
| n | data |
|
| n | data |
|
+------+-----------------+
|
+------+-----------------+
|
|
|
|
|
Socket Interface
|
Socket Interface
|
----------------
|
----------------
|
|
|
The socket interface consists of two streams of data:
|
The socket interface consists of two streams of data:
|
|
|
+ An input, input_socket.
|
+ An input, input_socket.
|
+ An output, output_socket.
|
+ An output, output_socket.
|
|
|
Both streams are 16 bits wide, and use the following protocol:
|
Both streams are 16 bits wide, and use the following protocol:
|
|
|
|
|
+------+-----------------+
|
+------+-----------------+
|
| word | designation |
|
| word | designation |
|
+------+-----------------+
|
+------+-----------------+
|
| 0 | length in bytes |
|
| 0 | length in bytes |
|
+------+-----------------+
|
+------+-----------------+
|
| n | data |
|
| n | data |
|
+------+-----------------+
|
+------+-----------------+
|
|
|
|
|
Stream Interconnect Conventions
|
Stream Interconnect Conventions
|
===============================
|
===============================
|
|
|
The main aims of the interface are:
|
The interfaces are based on the Chips Physical Interface Convetions which are
|
|
described in the Chips-2.0 `reference manual
|
|
`_.
|
|
|
- To be simple to implement.
|
|
- Add little performance/logic overhead.
|
|
- Allow designs to grow without adding extra levels of asynchronous logic.
|
|
- Easy to interface with standard interconnects.
|
|
|
|
::
|
|
|
|
RST >-o-----------------------------+
|
|
CLK >-+-o-------------------------+ |
|
|
| | | |
|
|
| | +-----------+ | | +--------------+
|
|
| | | TX | | | | RX |
|
|
| +---> | | +-----> |
|
|
+-----> | +-------> |
|
|
| | | |
|
|
| | | |
|
|
| out >=================> in |
|
|
| | _STB | |
|
|
| out >-----------------> in |
|
|
| | _ACK | |
|
|
| in <-----------------< out |
|
|
| | | |
|
|
+-----------+ +--------------+
|
|
|
|
Global Signals
|
|
--------------
|
|
|
|
|
|
|
|
+------+-----------+------+-------------+
|
|
| Name | Direction | Type | Description |
|
|
+------+-----------+------+-------------+
|
|
| CLK | input | bit | Clock |
|
|
+------+-----------+------+-------------+
|
|
| RST | input | bit | Reset |
|
|
+------+-----------+------+-------------+
|
|
|
|
|
|
|
|
Interconnect Signals
|
|
--------------------
|
|
|
|
|
|
|
|
+----------------+-----------+------+-----------------------------------------------------------+
|
|
| Name | Direction | Type | Description |
|
|
+----------------+-----------+------+-----------------------------------------------------------+
|
|
| | TX to RX | bus | Payload Data |
|
|
+----------------+-----------+------+-----------------------------------------------------------+
|
|
| _STB | TX to RX | bit | '1' indicates that payload data is valid and TX is ready. |
|
|
+----------------+-----------+------+-----------------------------------------------------------+
|
|
| _ACK | TX to RX | bit | '1' indicates that RX is ready. |
|
|
+----------------+-----------+------+-----------------------------------------------------------+
|
|
|
|
|
|
|
|
Interconnect Bus Transaction
|
|
----------------------------
|
|
|
|
- Both transmitter and receiver shall be synchronised to the '0' -> '1' transition of CLK.
|
|
- If RST is set to '1' upon the '0' -> '1' transition of clock the transmitter shall terminate any active bus transaction and set _STB to '0'.
|
|
- If RST is set to '1' upon the '0' -> '1' transition of clock the receiver shall terminate any active bus transaction and set _ACK to '0'.
|
|
- If RST is set to '0', normal operation shall commence as follows:
|
|
- The transmitter may insert wait states on the bus by setting _STB '0'.
|
|
- The transmitter shall set _STB to '1' to signify that data is valid.
|
|
- Once _STB has been set to '1', it shall remain at '1' until the transaction completes.
|
|
- The transmitter shall ensure that contains valid data for the entire period that _STB is '1'.
|
|
- The transmitter may set to any value when _STB is '0'.
|
|
- The receiver may insert wait states on the bus by setting _ACK to '0'.
|
|
- The receiver shall set _ACK to '1' to signify that it is ready to receive data.
|
|
- Once _ACK has been set to '1', it shall remain at '1' until the transaction completes.
|
|
- Whenever _STB is '1' and _ACK are '1', a bus transaction shall complete on the following '0' -> '1' transition of CLK.
|
|
|
|
::
|
|
|
|
RST
|
|
--------------------------------------------------------------
|
|
- - - - - - - - - - - - - - -
|
|
CLK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
|
- - - - - - - - - - - - - - - -
|
|
|
|
----- ------- ------------------------------------------------
|
|
X VALID X
|
|
----- ------- ------------------------------------------------
|
|
-------
|
|
_STB | |
|
|
----- ------------------------------------------------
|
|
---
|
|
_ACK | |
|
|
--------- ------------------------------------------------
|
|
|
|
|
|
^^^^ RX adds wait states
|
|
|
|
^^^^ Data transfers
|
|
|
|
RST
|
|
--------------------------------------------------------------
|
|
- - - - - - - - - - - - - - -
|
|
CLK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
|
- - - - - - - - - - - - - - - -
|
|
|
|
----- ------- ------------------------------------------------
|
|
X VALID X
|
|
----- ------- ------------------------------------------------
|
|
---
|
|
_STB | |
|
|
--------- ------------------------------------------------
|
|
-------
|
|
_ACK | |
|
|
----- ------------------------------------------------
|
|
|
|
|
|
^^^^ TX adds wait states
|
|
|
|
^^^^ Data transfers
|
|
|
|
..
|
|
|
|
- Both the transmitter and receiver may commence a new transaction without inserting any wait states.
|
|
|
|
::
|
|
|
|
RST
|
|
--------------------------------------------------------------
|
|
- - - - - - - - - - - - - - -
|
|
CLK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
|
- - - - - - - - - - - - - - - -
|
|
|
|
----- ------- ---- ---- --------------------------------------
|
|
X D0 X D1 X D2 X
|
|
----- ------- ---- ---- --------------------------------------
|
|
-------------
|
|
_STB | |
|
|
--------- --------------------------------------
|
|
-----------------
|
|
_ACK | |
|
|
----- --------------------------------------
|
|
|
|
^^^^ TX adds wait states
|
|
|
|
^^^^ Data transfers
|
|
|
|
^^^^ STB and ACK needn't return to 0 between data words
|
|
|
|
..
|
|
|
|
|
|
- The receiver may delay a transaction by inserting wait states until the transmitter indicates that data is available.
|
|
|
|
- The transmitter shall not delay a transaction by inserting wait states until the receiver is ready to accept data.
|
|
|
|
- Deadlock would occur if both the transmitter and receiver delayed a transaction until the other was ready.
|
|
|
|
