89 lines
4.8 KiB
Markdown
89 lines
4.8 KiB
Markdown
ARTIQ on Zynq
|
|
=============
|
|
|
|
How to use
|
|
----------
|
|
|
|
1. Install the ARTIQ version that corresponds to the artiq-zynq version you are targeting.
|
|
2. To obtain firmware binaries, select the latest successful build on [Hydra](https://nixbld.m-labs.hk/) for the targeted artiq-zynq version, or use AFWS. If using Hydra, search for the job named ``<board>-<variant>-sd`` (for example: ``zc706-nist_clock-sd`` or ``zc706-nist_qc2-sd``).
|
|
3. Place the ``boot.bin`` file, obtained from Hydra's "binary distribution" download link or from AFWS, at the root of a FAT-formatted SD card.
|
|
4. Optionally, create a ``config.txt`` configuration file at the root of the SD card containing ``key=value`` pairs on each line. Use the ``ip``, ``ip6`` and ``mac`` keys to respectively set the IPv4, IPv6 and MAC address of the board. Configuring an IPv6 address is entirely optional. If these keys are not found, the firmware will use default values that may or may not be compatible with your network.
|
|
5. Insert the SD card into the board and set up the board to boot from the SD card. For the ZC706, this is achieved by placing the large DIP switch SW11 in the 00110 position.
|
|
6. Power up the board. After the firmware starts successfully, it should respond to ping at its IP addresses, and boot messages can be observed from its UART at 115200bps.
|
|
7. Create and use an ARTIQ device database as usual, but set ``"target": "cortexa9"`` in the arguments of the core device.
|
|
|
|
Configuration
|
|
-------------
|
|
|
|
Configuring the device is done using the ``config.txt`` text file at the root of the SD card, plus the contents of the ``config`` folder. When searching for a configuration key, the firmware first looks for a file named ``/config/[key].bin`` and, if it exists, returns the contents of that file. If not, it looks into ``/config.txt``, which contains a list of ``key=value`` pairs, one per line. The ``config`` folder allows configuration values that consist in binary data, such as the startup kernel.
|
|
|
|
The following configuration keys are available:
|
|
|
|
- ``mac``: Ethernet MAC address.
|
|
- ``ip``: IPv4 address.
|
|
- ``ip6``: IPv6 address.
|
|
- ``startup``: startup kernel in ELF format (as produced by ``artiq_compile``).
|
|
- ``rtio_clock``: source of RTIO clock; valid values are ``ext0_bypass`` and ``int_125``.
|
|
- ``boot``: SD card "boot.bin" file, for replacing the boot firmware/gateware. Write only.
|
|
|
|
Configurations can be read/written/removed via ``artiq_coremgmt``. Config erase is
|
|
not implemented as it seems not very useful.
|
|
|
|
Development instructions
|
|
------------------------
|
|
|
|
ARTIQ on Zynq is packaged using the [Nix](https://nixos.org) Flakes system. Install Nix 2.8+ and enable flakes by adding ``experimental-features = nix-command flakes`` to ``nix.conf`` (e.g. ``~/.config/nix/nix.conf``).
|
|
|
|
Pure build with Nix and execution on a remote JTAG server:
|
|
|
|
```shell
|
|
nix build .#zc706-nist_clock-jtag # or zc706-nist_qc2-jtag or zc706-nist_clock_satellite-jtag etc.
|
|
./remote_run.sh
|
|
```
|
|
|
|
Impure incremental build and execution on a remote JTAG server:
|
|
|
|
```shell
|
|
nix develop
|
|
cd src
|
|
gateware/zc706.py -g ../build/gateware -V <variant> # build gateware
|
|
make GWARGS="-V <variant>" <runtime/satman> # build firmware
|
|
cd ..
|
|
./remote_run.sh -i
|
|
```
|
|
|
|
Notes:
|
|
|
|
- The impure build process is also compatible with non-Nix systems.
|
|
- When calling make, you need to specify both the variant and firmware type.
|
|
- Firmware type must be either ``runtime`` for DRTIO-less or DRTIO master variants, or ``satman`` for DRTIO satellite.
|
|
- If the board is connected to the local machine, use the ``local_run.sh`` script.
|
|
|
|
Pre-Commit Hooks
|
|
----------------
|
|
|
|
You are strongly recommended to use the provided pre-commit hooks to automatically reformat files and check for non-optimal Rust practices using Clippy. Run `pre-commit install` to install the hook and `pre-commit` will automatically run `cargo fmt` and `cargo clippy` for you.
|
|
|
|
Several things to note:
|
|
|
|
- If `cargo fmt` or `cargo clippy` returns an error, the pre-commit hook will fail. You should fix all errors before trying to commit again.
|
|
- If `cargo fmt` reformats some files, the pre-commit hook will also fail. You should review the changes and, if satisfied, try to commit again.
|
|
|
|
License
|
|
-------
|
|
|
|
Copyright (C) 2019-2024 M-Labs Limited.
|
|
|
|
ARTIQ is free software: you can redistribute it and/or modify
|
|
it under the terms of the GNU Lesser General Public License as published by
|
|
the Free Software Foundation, either version 3 of the License, or
|
|
(at your option) any later version.
|
|
|
|
ARTIQ is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU Lesser General Public License for more details.
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
along with ARTIQ. If not, see <http://www.gnu.org/licenses/>.
|