|Sebastien Bourdeauducq dc08c382a2||1 month ago|
|examples||6 months ago|
|src||1 month ago|
|.gitignore||3 years ago|
|LICENSE||3 years ago|
|README.md||5 months ago|
|demo.json||3 years ago|
|flake.lock||2 months ago|
|flake.nix||4 months ago|
|kasli-soc-master.json||2 years ago|
|kasli-soc-satellite.json||2 years ago|
|local_run.sh||2 years ago|
|remote_run.sh||2 years ago|
ARTIQ on Zynq
How to use
- Install the ARTIQ version that corresponds to the artiq-zynq version you are targeting.
- To obtain firmware binaries, select the latest successful build on Hydra for the targeted artiq-zynq version, or use AFWS. If using Hydra, search for the job named
- Place the
boot.binfile, obtained from Hydra's "binary distribution" download link or from AFWS, at the root of a FAT-formatted SD card.
- Optionally, create a
config.txtconfiguration file at the root of the SD card containing
key=valuepairs on each line. Use the
mackeys 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.
- 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.
- 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.
- Create and use an ARTIQ device database as usual, but set
"target": "cortexa9"in the arguments of the core device.
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
rtio_clock: source of RTIO clock; valid values are
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.
ARTIQ on Zynq is packaged using the Nix Flakes system. Install Nix 2.8+ and enable flakes by adding
experimental-features = nix-command flakes to
Pure build with Nix and execution on a remote JTAG server:
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:
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
- 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
runtimefor DRTIO-less or DRTIO master variants, or
satmanfor DRTIO satellite.
- If the board is connected to the local machine, use the
- To update
zynq-rs, update the cargo files as per usual for Rust projects, but also keep
Copyright (C) 2019-2023 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/.