PetaLinux
PetaLinux can be built for these reference designs by using the Makefile in the PetaLinux
directory
of the repository.
Requirements
To build the PetaLinux projects, you will need a physical or virtual machine running one of the supported Linux distributions as well as the Vitis Core Development Kit installed.
Attention
You cannot build the PetaLinux projects in the Windows operating system. Windows users are advised to use a Linux virtual machine to build the PetaLinux projects.
How to build
From a command terminal, clone the Git repository and
cd
into it.git clone https://github.com/fpgadeveloper/sfp28-fmc-xxv.git cd sfp28-fmc-xxv
Launch PetaLinux by sourcing the
settings.sh
bash script, eg:source <path-to-installed-petalinux>/settings.sh
Launch Vivado by sourcing the
settings64.sh
bash script, eg:source <vivado-install-dir>/settings64.sh
Build the Vivado and PetaLinux project for your specific target platform by running the following commands and replacing
<target>
with one of the target design labels listed in build instructions.cd PetaLinux make petalinux TARGET=<target>
The last command will launch the build process for the corresponding Vivado project if that project has not already been built and it’s hardware exported.
Boot from SD card
Prepare the SD card
Once the build process is complete, you must prepare the SD card for booting PetaLinux.
The SD card must first be prepared with two partitions: one for the boot files and another for the root file system.
Plug the SD card into your computer and find it’s device name using the
dmesg
command. The SD card should be found at the end of the log, and it’s device name should be something like/dev/sdX
, whereX
is a letter such as a,b,c,d, etc. Note that you should replace theX
in the following instructions.
Warning
Do not continue these steps until you are certain that you have found the correct device name for the SD card. If you use the wrong device name in the following steps, you risk losing data on one of your hard drives.
Run
fdisk
by typing the commandsudo fdisk /dev/sdX
Make the
boot
partition: typingn
to create a new partition, then typep
to make it primary, then use the default partition number and first sector. For the last sector, type+1G
to allocate 1GB to this partition.Make the
boot
partition bootable by typinga
Make the
root
partition: typingn
to create a new partition, then typep
to make it primary, then use the default partition number, first sector and last sector.Save the partition table by typing
w
Format the
boot
partition (FAT32) by typingsudo mkfs.vfat -F 32 -n boot /dev/sdX1
Format the
root
partition (ext4) by typingsudo mkfs.ext4 -L root /dev/sdX2
Copy the following files to the
boot
partition of the SD card: Assuming theboot
partition was mounted to/media/user/boot
, follow these instructions:$ cd /media/user/boot/ $ sudo cp /<petalinux-project>/images/linux/BOOT.BIN . $ sudo cp /<petalinux-project>/images/linux/boot.scr . $ sudo cp /<petalinux-project>/images/linux/image.ub .
Create the root file system by extracting the
rootfs.tar.gz
file to theroot
partition. Assuming theroot
partition was mounted to/media/user/root
, follow these instructions:$ cd /media/user/root/ $ sudo cp /<petalinux-project>/images/linux/rootfs.tar.gz . $ sudo tar xvf rootfs.tar.gz -C . $ sync
Once the
sync
command returns, you will be able to eject the SD card from the machine.
Boot PetaLinux
Plug the SD card into your target board.
Ensure that the target board is configured to boot from SD card:
VCK190, VMK180, VEK280, VPK120: DIP switch SW1 is set to 1000 (1=ON,2=OFF,3=OFF,4=OFF)
UltraZed-EV: DIP switch SW2 (on the SoM) is set to 1000 (1=ON,2=OFF,3=OFF,4=OFF)
ZCU102, ZCU104, ZCU106, ZCU111: DIP switch SW6 must be set to 1000 (1=ON,2=OFF,3=OFF,4=OFF)
ZCU208, ZCU216: DIP switch SW2 must be set to 1000 (1=ON,2=OFF,3=OFF,4=OFF)
Connect the Quad SFP28 FMC to the FMC connector of the target board.
Connect the USB-UART to your PC and then open a UART terminal set to 115200 baud and the comport that corresponds to your target board.
Connect and power your hardware.
Boot via JTAG
Tip
You need to install the cable drivers before being able to boot via JTAG. Note that the Vitis installer does not automatically install the cable drivers, it must be done separately. For instructions, read section installing the cable drivers from the Vivado release notes.
Warning
If you boot the Zynq-7000, Zynq UltraScale+ or Zynq RFSoC designs via JTAG, you must still
first prepare the SD card. The reason is because these designs are configured to use the SD card to store
the root filesystem. If you boot these designs via JTAG without preparing and connecting the SD card, the
boot will hang during at a message similar to this: Waiting for root device /dev/mmcblk0p2...
Setup hardware
Prepare the SD card according to the instructions above and plug the SD card into your target board.
Ensure that the target board is configured to boot from JTAG:
VCK190, VMK180, VEK280, VPK120: DIP switch SW1 is set to 1111 (1=ON,2=ON,3=ON,4=ON)
UltraZed-EV: DIP switch SW2 (on the SoM) is set to 1111 (1=ON,2=ON,3=ON,4=ON)
ZCU102, ZCU104, ZCU106, ZCU111: DIP switch SW6 must be set to 1111 (1=ON,2=ON,3=ON,4=ON)
ZCU208, ZCU216: DIP switch SW2 must be set to 1111 (1=ON,2=ON,3=ON,4=ON)
Connect the Quad SFP28 FMC to the FMC connector of the target board.
Connect the USB-UART to your PC and then open a UART terminal set to 115200 baud and the comport that corresponds to your target board.
Connect and power your hardware.
Boot PetaLinux
To boot PetaLinux on hardware via JTAG, use the following commands in a Linux command terminal:
Change current directory to the PetaLinux project directory for your target design:
cd <project-dir>/PetaLinux/<target>
Download bitstream to the FPGA:
petalinux-boot --jtag --kernel --fpga
An explanation of the above command is provided by the petalinux-boot
command:
For microblaze, it will download the bitstream to target board, and
then boot the kernel image on target board.
For Zynq, it will download the bitstream and FSBL to target board,
and then boot the u-boot and then the kernel on target
board.
For Zynq UltraScale+, it will download the bitstream, PMUFW and FSBL,
and then boot the kernel with help of linux-boot.elf to set kernel
start and dtb addresses.
UART terminal
You will need to setup a terminal emulator to use the PetaLinux command line over the USB-UART connection. Connect with a baud rate of 115200.
In Windows
You will need to find the comport for the USB-UART in Windows Device Manager. As a terminal emulator, you can use the open source and free Putty.
In Linux
In Linux, you can find the USB-UART device by running dmesg | grep tty
. Typically, the device will be
/dev/ttyUSB0
or it could be followed by a different number. To open a terminal emulator, you can use
the following command:
sudo screen /dev/ttyUSB0 115200
Port configurations
All designs will try to automatically configure the eth0 device on boot, so it can be useful to connect the eth0 device to a DHCP router before the hardware is powered-up. Note that on Zynq and ZynqMP designs, the eth0 device is connected to the development board’s Ethernet port and not the Quad SFP28 FMC.
Zynq UltraScale+ designs
eth0: Quad SFP28 FMC Port 0
eth1: Quad SFP28 FMC Port 1
eth2: Quad SFP28 FMC Port 2
eth3: Quad SFP28 FMC Port 3
Versal designs
eth0: GEM0 to Ethernet port of the dev board
eth1: Quad SFP28 FMC Port 0
eth2: Quad SFP28 FMC Port 1
eth3: Quad SFP28 FMC Port 2
eth4: Quad SFP28 FMC Port 3
Example Usage
Enable port
This example will bring up a port.
root@axieth:~# sudo ifconfig eth1 up
[ 228.274146] xilinx_axienet a0000000.ethernet eth1: Link is Up - 10Gbps/Full - flow control off
[ 228.282753] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Enable port with fixed IP address
This example sets a fixed IP address to a port.
root@axieth:~# sudo ifconfig eth1 192.168.2.30 up
[ 390.080498] net eth1: Promiscuous mode disabled.
[ 390.085406] net eth1: Promiscuous mode disabled.
[ 390.091089] xilinx_axienet a0000000.ethernet eth1: Link is Down
[ 394.175238] xilinx_axienet a0000000.ethernet eth1: Link is Up - 10Gbps/Full - flow control off
[ 394.183769] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Enable port using DHCP
This example enables a port and obtains an IP address for the port via DHCP. Note that the port must be connected to a DHCP enabled router.
root@axieth:~# sudo udhcpc -i eth1
udhcpc: started, v1.31.0
[ 68.814013] xilinx_axienet a0000000.ethernet eth1: Link is Up - 10Gbps/Full - flow control off
[ 68.822670] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
udhcpc: sending discover
udhcpc: sending select for 192.168.2.23
udhcpc: lease of 192.168.2.23 obtained, lease time 259200
/etc/udhcpc.d/50default: Adding DNS 192.168.2.1
Check port status
In this example, we use the ifconfig
command with no arguments to check the port status.
The first interface (eth0) shown below is connected to the on-board Ethernet port and it has not been
enabled, whereas the second interface (eth1) is connected to the Quad SFP28 FMC port 0 and it has
been enabled and configured with IP address 192.168.2.30.
root@axieth:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:35:00:22:01
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:30
eth1 Link encap:Ethernet HWaddr 00:0A:35:00:01:22
inet addr:192.168.2.30 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::20a:35ff:fe00:122/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6033 (5.8 KiB) TX bytes:3302 (3.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
We can also use ethtool
to check the port status as follows.
root@axieth:~# ethtool eth1
Settings for eth1:
COMING SOON
Ping link partner using specific port
In this example we ping the link partner at IP address 192.168.2.10 from interface eth1.
root@axieth:~# ping -I eth1 192.168.2.10
PING 192.168.2.10 (192.168.2.10): 56 data bytes
64 bytes from 192.168.2.10: seq=0 ttl=128 time=0.545 ms
64 bytes from 192.168.2.10: seq=1 ttl=128 time=0.455 ms
64 bytes from 192.168.2.10: seq=2 ttl=128 time=0.380 ms
64 bytes from 192.168.2.10: seq=3 ttl=128 time=0.356 ms