Open your terminal and run the following command based on your distribution. Run this command to install the essential build tools, libraries, and network utilities:
sudo apt-get install -y gcc git make net-tools libncurses5-dev tftpd \ zlib1g-dev libssl-dev flex bison libselinux1 gnupg wget diffstat chrpath \ socat xterm autoconf libtool tar unzip texinfo zlib1g-dev gcc-multilib \ build-essential libsdl1.2-dev libglib2.0-dev screen pax gzip If you are using an RPM-based system, use yum : petalinux 2019.2 installation guide
While the embedded Linux landscape evolves rapidly, specific tool versions often remain industry standards for long-term projects. Xilinx’s (now AMD) PetaLinux 2019.2 is one such release. It is widely used in production environments due to its stability with the UltraScale+ and Zynq-7000 architectures and its alignment with the Vivado 2019.2 design suite. Open your terminal and run the following command
You must reconfigure the system shell to use bash . Run the following command: It is widely used in production environments due
sudo yum install -y gcc git make net-tools libncurses5-dev tftpd \ zlib-devel libssl-dev flex bison libselinux1 gnupg wget diffstat chrpath \ socat xterm autoconf libtool tar unzip texinfo zlib-devel gcc-multilib \ build-essential libsdl1.2-dev libglib2.0-dev screen pax gzip There are two critical pre-configuration steps that users often miss: disabling the firewall (or configuring it) and setting up the /bin/sh shell. The Dash vs. Bash Issue On Ubuntu, the default system shell ( /bin/sh ) is linked to dash (Debian Almquist Shell). PetaLinux build scripts rely heavily on bash . Using dash will cause cryptic syntax errors during the build process.
However, installing PetaLinux is notoriously more complex than installing standard desktop software. It requires a specific host environment, proprietary libraries, and precise user permissions.
