This repository provides example designs for connecting NVMe SSDs and other M.2 M-key modules to various FPGA, MPSoC, and ACAP evaluation boards. These designs are compatible with both standalone and PetaLinux environments, and all scripts and code are provided for building these environments. The interface between the evaluation board and M.2 modules is facilitated by Opsero's FPGA Drive FMC Gen4 and M.2 M-key Stack FMC mezzanine cards, either of which can be used with these designs.
FPGA Drive FMC Gen4 | M.2 M-key Stack FMC |
---|---|
Important links:
- Datasheet for the FPGA Drive FMC Gen4
- Datasheet for the M.2 M-key Stack FMC
- The user guide for these reference designs is hosted here: Ref design for FPGA Drive FMC docs
- To report a bug: Report an issue.
- For technical support: Contact Opsero.
This project is designed for version 2024.1 of the Xilinx tools (Vivado/Vitis/PetaLinux). If you are using an older version of the Xilinx tools, then refer to the release tags to find the version of this repository that matches your version of the tools.
In order to test this design on hardware, you will need the following:
- Vivado 2024.1
- Vitis 2024.1
- PetaLinux Tools 2024.1
- FPGA Drive FMC Gen4 or M.2 M-key Stack FMC
- M.2 NVMe PCIe Solid State Drive
- One of the supported carriers listed below
This repo contains several designs that target various supported development boards and their FMC connectors. The table below lists the target design name, the M2 ports supported by the design and the FMC connector on which to connect the mezzanine card. Some of the target designs require a license to generate a bitstream with the AMD Xilinx tools.
Target board | Target design | M2 Slot 1 PCIe Lanes |
M2 Slot 2 PCIe Lanes |
FMC Slot | Standalone | PetaLinux | License required |
---|---|---|---|---|---|---|---|
KC705 | kc705_hpc |
4 | - | HPC | ✅ | ❌ | YES |
KC705 | kc705_lpc |
1 | - | LPC | ✅ | ❌ | YES |
KCU105 | kcu105_hpc |
4 | 4 | HPC | ✅ | ❌ | YES |
KCU105 | kcu105_lpc |
1 | - | LPC | ✅ | ❌ | YES |
VC707 | vc707_hpc1 |
4 | - | HPC1 | ✅ | ❌ | YES |
VC707 | vc707_hpc2 |
4 | - | HPC2 | ✅ | ❌ | YES |
VC709 | vc709_hpc |
4 | - | HPC | ✅ | ❌ | YES |
VCU118 | vcu118 |
4 | 4 | FMCP | ✅ | ❌ | YES |
Target board | Target design | M2 Slot 1 PCIe Lanes |
M2 Slot 2 PCIe Lanes |
FMC Slot | Standalone | PetaLinux | License required |
---|---|---|---|---|---|---|---|
PicoZed 7015 | pz_7015 |
1 | - | LPC | ✅ | ✅ | NO |
PicoZed 7030 | pz_7030 |
1 | - | LPC | ✅ | ✅ | NO |
ZC706 | zc706_hpc |
4 | - | HPC | ✅ | ✅ | YES |
ZC706 | zc706_lpc |
1 | - | LPC | ✅ | ✅ | YES |
Target board | Target design | M2 Slot 1 PCIe Lanes |
M2 Slot 2 PCIe Lanes |
FMC Slot | Standalone | PetaLinux | License required |
---|---|---|---|---|---|---|---|
UltraZed-EV Carrier | uzev |
4 | 4 | HPC | ✅ | ✅ | NO |
ZCU104 | zcu104 |
1 | - | LPC | ✅ | ✅ | NO |
ZCU106 | zcu106_hpc0 |
4 | 4 | HPC0 | ✅ | ✅ | NO |
ZCU106 | zcu106_hpc1 |
1 | - | HPC1 | ✅ | ✅ | NO |
ZCU111 | zcu111 |
4 | 4 | FMCP | ✅ | ✅ | YES |
ZCU208 | zcu208 |
4 | 4 | FMCP | ✅ | ✅ | YES |
ZCU216 | zcu216 |
4 | 4 | FMCP | ✅ | ✅ | YES |
Target board | Target design | M2 Slot 1 PCIe Lanes |
M2 Slot 2 PCIe Lanes |
FMC Slot | Standalone | PetaLinux | License required |
---|---|---|---|---|---|---|---|
VCK190 | vck190_fmcp1 |
4 | 4 | FMCP1 | ✅ | ✅ | YES |
VCK190 | vck190_fmcp2 |
4 | 4 | FMCP2 | ✅ | ✅ | YES |
VHK158 | vhk158 |
4 | - | FMCP | ✅ | ✅ | YES |
VMK180 | vmk180_fmcp1 |
4 | 4 | FMCP1 | ✅ | ✅ | YES |
VMK180 | vmk180_fmcp2 |
4 | 4 | FMCP2 | ✅ | ✅ | YES |
VEK280 | vek280 |
4 | 4 | FMCP | ✅ | ✅ | YES |
VPK120 | vpk120 |
4 | - | FMCP | ✅ | ✅ | YES |
VPK180 | vpk180 |
4 | - | FMCP | ✅ | ✅ | YES |
Notes:
- The VPK120, VPK180 and VHK158 have enough GTs to interface with both M.2 slots, however they have only 2 integrated PCIe blocks one of which is on the opposite side of the device with respect to the relevant GT quads, making routing a challenge. For this reason these designs supports only 1x M.2 slot.
These reference designs can be driven by either a standalone application or within a PetaLinux environment. The repository includes all necessary scripts and code to build both environments. The table below outlines the corresponding applications available in each environment:
Environment | Available Applications |
---|---|
Standalone | PCIe enumeration test |
PetaLinux | Built-in Linux commands Additional tools: mke2fs, badblocks, mount, mkfs, blkid, fdisk, pciutils |
The standalone software application reports on the status of the PCIe link and performs enumeration of the detected PCIe end-points (ie. the M.2 modules).
Clone the repo:
git clone https://github.com/fpgadeveloper/fpga-drive-aximm-pcie.git
Source Vivado and PetaLinux tools:
source <path-to-petalinux>/2024.1/settings.sh
source <path-to-vivado>/2024.1/settings64.sh
To build the standalone PCIe enumeration test application (Vivado project and Vitis workspace):
cd fpga-drive-aximm-pcie/Vitis
make workspace TARGET=uzev
Build all (Vivado project and PetaLinux):
cd fpga-drive-aximm-pcie/PetaLinux
make petalinux TARGET=uzev
More comprehensive build instructions can be found in the user guide:
We strongly encourage community contribution to these projects. Please make a pull request if you would like to share your work:
- if you've spotted and fixed any issues
- if you've added designs for other target platforms
- if you've added software support for other devices
Thank you to everyone who supports us!
Opsero Inc. is a team of FPGA developers delivering FPGA products and design services to start-ups and tech companies. Follow our blog, FPGA Developer, for news, tutorials and updates on the awesome projects we work on.