Microzed Petalinux 2016.1 BSP

We are currently automating the process of generating our PetaLinux designs, and this has caused a delay in releasing the updates.  There are no plans to discontinue support.   The 2015.4 BSPs should be posted next week, and the 2016.1 designs will follow quickly thanks to the new process we are using.  

You should have no problems with the 2015.2.1 BSPs.  The BSP files are compressed in .zip format on this site, so you need to extract them on your Linux host so that you have the mz_7010_2015_2_1.bsp file.  In the directory containing the BSP file, enter:

petalinux-create -t project -s mz_7010_2015._2_1.bsp

Ron

Thanks Ron for the update. However, when I try compiling the BSP, I get:

ghalady@ghalady-ubuntu:~/Microzed_Petalinux_2015_2_BSP$ which petalinux-create
/opt/pkg/petalinux-v2015.2.1-final/tools/common/petalinux/bin/petalinux-create
ghalady@ghalady-ubuntu:~/Microzed_Petalinux_2015_2_BSP$ petalinux-create -t project -s mz_7020_2015_2_1.bsp
petalinux-create: line 1040: /opt/pkg/petalinux-v2015.2.1-final/tools/linux-i386/petalinux/bin/unexport/realpath: No such file or directory
ERROR: source mz_7020_2015_2_1.bsp doesn't exist!
This command creates a new PetaLinux Project or component

Usage:
  petalinux-create [options] <-t|--type <TYPE> <-n|--name <COMPONENT_NAME>

Required:
  -t, --type <TYPE>                     Available type:
                                          * project : PetaLinux project
                                          * apps    : Linux user application
                                          * libs    : Linux user library
                                          * modules : Linux user module
                                          * generic : generic component
  -n, --name <COMPONENT_NAME>           specify a name for the component or
                                        project. It is OPTIONAL to create a
                                        PROJECT. If you specify source BSP when
                                        you create a project, you are not
                                        required to specify the name.

Options:
  -p, --project <PROJECT>               specify full path to a PetaLinux project
                                        this option is NOT USED for PROJECT CREATION.
                                        default is the working project.
  --force                               force overwriting an existing component
                                        directory.
  -h, --help                            show function usage
  --enable                              this option applies to all types except
                                        project.
                                        enable the created component

Options for project:
  --template <TEMPLATE>                 zynqMP|zynq|microblaze
                                        user needs specify which template to use.
  -s|--source <SOURCE>                  specify a PetaLinux BSP as a project
                                        source.
  --out <OUTPUT_DIR>                    diretory to place your project default
                                        is your working directory

EXAMPLES:

Create project from PetaLinux Project BSP:
  $ petalinux-create -t project -s <PATH_TO_PETALINUX_PROJECT_BSP>

Create project from template:
  $ petalinux-create -t project -n <PROJECT> --template zynq

Would truly appreciate a fix for this.

Best
Girish

ghalady@ghalady-ubuntu:~/test$ ls
Avnet_Microzed_7z010_2015_2_1_BSP.zip
ghalady@ghalady-ubuntu:~/test$ unzip Avnet_Microzed_7z010_2015_2_1_BSP.zip
Archive:  Avnet_Microzed_7z010_2015_2_1_BSP.zip
  inflating: WhatsNew2015_2.pdf     
  inflating: mz_7010_2015_2_1.bsp   
ghalady@ghalady-ubuntu:~/test$ petalinux-create -t project -s mz_7010_2015_2_1.bsp
petalinux-create: line 1040: /opt/pkg/petalinux-v2015.2.1-final/tools/linux-i386/petalinux/bin/unexport/realpath: No such file or directory
ERROR: source mz_7010_2015_2_1.bsp doesn't exist!
This command creates a new PetaLinux Project or component

Usage:
  petalinux-create [options] <-t|--type <TYPE> <-n|--name <COMPONENT_NAME>

Required:
  -t, --type <TYPE>                     Available type:
                                          * project : PetaLinux project
                                          * apps    : Linux user application
                                          * libs    : Linux user library
                                          * modules : Linux user module
                                          * generic : generic component
  -n, --name <COMPONENT_NAME>           specify a name for the component or
                                        project. It is OPTIONAL to create a
                                        PROJECT. If you specify source BSP when
                                        you create a project, you are not
                                        required to specify the name.

Options:
  -p, --project <PROJECT>               specify full path to a PetaLinux project
                                        this option is NOT USED for PROJECT CREATION.
                                        default is the working project.
  --force                               force overwriting an existing component
                                        directory.
  -h, --help                            show function usage
  --enable                              this option applies to all types except
                                        project.
                                        enable the created component

Options for project:
  --template <TEMPLATE>                 zynqMP|zynq|microblaze
                                        user needs specify which template to use.
  -s|--source <SOURCE>                  specify a PetaLinux BSP as a project
                                        source.
  --out <OUTPUT_DIR>                    diretory to place your project default
                                        is your working directory

EXAMPLES:

Create project from PetaLinux Project BSP:
  $ petalinux-create -t project -s <PATH_TO_PETALINUX_PROJECT_BSP>

Create project from template:
  $ petalinux-create -t project -n <PROJECT> --template zynq

Ghalady,

  I cannot see anything wrong with what you are doing, and I can follow the exact sequence you provided on my Linux host and it works perfectly.  So the only thing I can think of is that somehow your PetaLinux 2015.2.1 installation is corrupt.

The only evidence I have (besides that your correct commands don't work) is that when I purposely enter an invalid bsp file name, I get back:

realpath:  No such file or directory

Error:  source mz_7020_2015_2_11.bsp doesn't exist!

This is correct, because of the extra 1 in the name.  I notice in your installation, it returns the a specific line in the petalinux-create command, which is different than I see.  

So my guess is that you should delete your 2015.2.1 PetaLinux installation, download a fresh version of the installer from the Xilinx site, make sure you validate the download by verifying the checksum, and reinstall.   Then give it another try.

Ron

I had the same issue and figured it out. The realpath utility included with that version of Petalinux does not work correctly. I installed a version of realpath from Ubuntu sudo apt-get install realpath and then replaced the version supplied with Petalinux with a link to /usr/bin/realpath. Everything worked after that.

Apologize the delay in updating the status. Thanks Ron and Cellis,

              I figured out the issue, it was to do with the 32-bit lib packages which was missing on my ubuntu distribution :

lib32z1, lib32ncurses5, lib32bz2-1.0, lib32stdc++6, libselinux1

After installing these, I could get the BSP installed.

Also, are the newer BSP's automated ? How would I generate BSP for 7z010 Microzed for any newer release of Petalinux newer than 2015.2.1 ?

Thanks / Best

Girish

Hi there,

The newer BSPs are intended to be automated in the build process.  The process and scripting needed for this does not look like it was released as of this posting.

You can check back at the below page when the update is released publicly.
http://microzed.org/support/design/1519/10

As for building a newer released, the process should be the same flow - substituting the newer Petalinux files.  Please note that We have not worked through this flow as of this post so you are free to attempt that build yourself.  Once that has been released expect the post to be at the above link.  As I understand it, the newer build will be with the automated process, which means this will be slightly delayed due to this being the initial release.

--Dan

We are validating PicoZed 2015.4 BSPs built from the automated process right now.  These should be posted in the coming week, and solutions for the other Zynq boards will follow fairly quickly.  MicroZed wll be the next release target.

The next PetaLinux BSP series will be for 2016.2.

Please note that it is certainly possible to create project from scratch without a BSP by following the information in the Xilinx PetaLinux Guide UG1144.  If you create a custom hardware project for a device, this is the procedure that would be followed as a precursor to creating a new, custom BSP for the augmented hardware platform.

The commands you need to pay attention to are:

1. Create an empty zynq project:

petalinux-create --type project --template zynq --name <Project_Name>

2. Use the .hdf file exported from Vivado to populate the new project template

petalinux-config –get-hw-description –p ~/<new PetaLinux project>

You can also use this command to configure the project, the kernel or the root file system, but for starters I recommend just leaving everything as default to get a first kernel boot.

3. Build the project

petalinux-build

4. Create the boot image

petalinux-package  --boot --fsbl <path > --fpga <path> --uboot

Ron

A bit of time has gone by since the above posts; are the 2016.4 BSPs ready now?

Hello Pkeating,

Unfortunatly they are not ready as of now.

Regards,

Josh