ZCU670 Evaluation Kit Tutorial

Using Vivado to Build the Hardware Design and petalinux images

Build Flow¶

This tutorial explains the steps to build the hardware design and software images from the TRD source package.

Prerequisites¶

Vivado Design Suite 2024.1
PetaLinux 2024.1 tools

Note: After sourcing the Vivado tool open ../.Xilinx/Vivado/Vivado_init.tcl and add enable_beta_device command into it to enable all beta devices

To Build the TRD Package with the top Makefile:¶

Follow the below steps to generate petalinux images using the top Makefile in ../zcu670-ethernet-trd-2024.1/Makefile path.

Go to the working directory
```
cd ../zcu670-ethernet-trd-2024.1
```
Run the following command to build and generate sdcard image. Pass design argument as zcu670_25G_PTP_subsys for 25G design and zcu670_10G_PTP_subsys for 10G design.
- This Makefile calls lower level Makefiles to build hardware XSA and petalinux images. The image generation may take a hour time depends on the system specification.
```
make sdcard design=zcu670_25G_PTP_subsys
```

The generated images will be located at :

../zcu670-ethernet-trd-2024.1/petalinux/<design>/images/linux   

Note: Generated images for 25G and 10G are available in different folders as per design name.

To Build the Hardware Platform XSA:¶

Follow the below steps to build XSA using the Makefile in ../zcu670-ethernet-trd-2024.1/vivado/<design>/Makefile path. Navigate to zcu670_25G_PTP_subsys folder for 25G design and zcu670_10G_PTP_subsys folder for 10G design.

Go to the platform directory.

cd ../zcu670-ethernet-trd-2024.1/vivado/<design>

To build the XSA, Source Vivado tool and run the following command.
- The Makefile uses scripts/main.tcl file to create a Vivado project, populate the block design and finally build a XSA. The XSA generation may take a hour time depends on the system specification.
```
make xsa
```
The generated XSA will be located at:

../zcu670-ethernet-trd-2024.1/vivado/<design>/project/<design>.xsa   

To Build the Petalinux Images:¶

Follow the steps below to build petalinux images individually for 25G and 10G using the Makefile in ../zcu670-ethernet-trd-2024.1/petalinux/xilinx-zcu670-trd path.

Go to the petalinux BSP folder.

cd ../zcu670-ethernet-trd-2024.1/petalinux/xilinx-zcu670-trd

To build boot images, source petalinux tool and run the following command. Pass design argument as zcu670_25G_PTP_subsys for 25G design and zcu670_10G_PTP_subsys for 10G design.

Note: Default BSP in ../zcu670-ethernet-trd-2024.1/petalinux/xilinx-zcu670-trd folder contains IDT driver clock configuration file for 25G design. To build images for 10G design copy ../zcu670-ethernet-trd-2024.1/IDT/ZCU670_8A34001_10G.bin to ../zcu670-ethernet-trd-2024.1/petalinux/xilinx-zcu670-trd/project-spec/meta-user/recipes-apps/idtcm/files folder and rename ZCU670_8A34001_10G.bin file as idtcm.bin file.

The Makefile configures the hardware platform required to build the petalinux images and create BOOT.BIN, which comprise of FSBL, UBoot, PMU firmware and hardware bit file.

make boot design=zcu670_25G_PTP_subsys

The generated images will be located at:
```
../zcu670-ethernet-trd-2024.1/petalinux/xilinx-zcu670-trd/images/linux   
```
Note: The XSA used to configure petalinux is available in ../zcu670-ethernet-trd-2024.1/prebuilt/<design>/ path.
Copy the image (image.ub , BOOT.BIN and boot.scr ) to the FAT32 formatted SD card and insert the card in SD card slot to run the design. This image is functionally equivalent to the prebuilt sdcard image provided with package.

Next Steps¶

Hardware and Software Architecture
Go back to the zcu670 Targeted Reference Designs start page

References¶

Vivado user guide UG901
Petalinux user guide UG1144

License¶

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License.

You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.