artiq/doc/manual/fpga_board_ports.rst

FPGA board ports
================

KC705
-----

The main target board for the ARTIQ core device is the KC705 development board from Xilinx.

Pipistrello
-----------

The low-cost Pipistrello FPGA board can be used as a lower-cost but slower alternative.

When plugged to an adapter, the NIST QC1 hardware can be used. The TTL lines are mapped to RTIO channels as follows:

+--------------+----------+-----------------+
| RTIO channel | TTL line | Capability      |
+==============+==========+=================+
| 0            | PMT0     | Input only      |
+--------------+----------+-----------------+
| 1            | PMT1     | Input only      |
+--------------+----------+-----------------+
| 2-18         | TTL0-16  | Output only     |
+--------------+----------+-----------------+
| 19-21        | LEDs     | Output only     |
+--------------+----------+-----------------+
| 22           | TTL2     | Output only     |
+--------------+----------+-----------------+

The input only limitation on channels 0 and 1 comes from the QC-DAQ adapter. When the adapter is not used (and physically unplugged from the Pipistrello board), the corresponding pins on the Pipistrello can be used as outputs. Do not configure these channels as outputs when the adapter is plugged, as this would cause electrical contention.

The board can accept an external RTIO clock connected to PMT2.
doc/manual: add FPGA board info and TTL line assignments 2014-11-22 08:39:22 +08:00			`FPGA board ports`
			`================`

			`KC705`
			`-----`

			`The main target board for the ARTIQ core device is the KC705 development board from Xilinx.`

Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`Pipistrello`
doc/manual: add FPGA board info and TTL line assignments 2014-11-22 08:39:22 +08:00			`-----------`

Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`The low-cost Pipistrello FPGA board can be used as a lower-cost but slower alternative.`
doc/manual: add FPGA board info and TTL line assignments 2014-11-22 08:39:22 +08:00
Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`When plugged to an adapter, the NIST QC1 hardware can be used. The TTL lines are mapped to RTIO channels as follows:`
doc/manual: add FPGA board info and TTL line assignments 2014-11-22 08:39:22 +08:00
more TTL channels and larger input FIFOs on Papilio Pro 2014-11-30 15:50:57 +08:00			`+--------------+----------+-----------------+`
			`\| RTIO channel \| TTL line \| Capability \|`
			`+==============+==========+=================+`
			`\| 0 \| PMT0 \| Input only \|`
			`+--------------+----------+-----------------+`
			`\| 1 \| PMT1 \| Input only \|`
			`+--------------+----------+-----------------+`
Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`\| 2-18 \| TTL0-16 \| Output only \|`
more TTL channels and larger input FIFOs on Papilio Pro 2014-11-30 15:50:57 +08:00			`+--------------+----------+-----------------+`
Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`\| 19-21 \| LEDs \| Output only \|`
more TTL channels and larger input FIFOs on Papilio Pro 2014-11-30 15:50:57 +08:00			`+--------------+----------+-----------------+`
Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`\| 22 \| TTL2 \| Output only \|`
more TTL channels and larger input FIFOs on Papilio Pro 2014-11-30 15:50:57 +08:00			`+--------------+----------+-----------------+`

Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`The input only limitation on channels 0 and 1 comes from the QC-DAQ adapter. When the adapter is not used (and physically unplugged from the Pipistrello board), the corresponding pins on the Pipistrello can be used as outputs. Do not configure these channels as outputs when the adapter is plugged, as this would cause electrical contention.`
targets/ARTIQMiniSoC: support dynamic switching of RTIO clock to XTRIG 2014-12-01 18:53:29 +08:00
Remove UP support. The only advantage of UP is to support the Papilio Pro, but that port is also very limited in other ways and the Pipistrello provides a more reasonable platform that also supports AMP. On the other hand, RPCs on UP are difficult to implement with the session.c protocol system (without an operating system or coroutines), along with many other minor difficulties and maintainance issues. Planned features such as watchdogs in the core device are also difficult on UP. 2015-04-27 20:43:45 +08:00			`The board can accept an external RTIO clock connected to PMT2.`