cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
689 Views
Registered: ‎02-13-2018

Using Vivado 2017.4 with Petalinux 2017.1

Jump to solution

Has anyone used the Petalinux 2017.1 toolchain and imported a .hdf and .bit built with Vivado 2017.1?

 

Is this workable?

 

I see that someone did this with 2016 (https://forums.xilinx.com/t5/Embedded-Linux/Vivado-2017-1-Generated-HDF-file-import-into-Petalinux-2016-4/m-p/761510/highlight/true#M19451)

 

Thank you!

 

john

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
827 Views
Registered: ‎04-24-2017

@jwmurray,

 

Vivado and PetaLinux should be same version.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

0 Kudos
2 Replies
Highlighted
Moderator
Moderator
828 Views
Registered: ‎04-24-2017

@jwmurray,

 

Vivado and PetaLinux should be same version.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

0 Kudos
Highlighted
Observer
Observer
631 Views
Registered: ‎02-13-2018

I appreciate the recommendation to use the same version of Vivado and Petalinux because they have been tested together.  However, Xilinx supports using third party tool chains (e.g. gcc5.3.0) for building an operating system to run on top of a Vivado project.  This is well documented in the Petalinux tools.

 

I have a Vivado .hdf and .bit file from Vivado 2017.4 which defines the FPGA and other hardware.

 

My challenge is this:  I need to link with a specific third party library that is in binary form only.  That third party library is not provided by Xilinx.  Fine, I have two versions of that third party library

  a. One that is built using the Xilinx Petalinux 2017.1 toolchain

  b. Another that is built using gcc5.3.0

The answer provided says, "Don't use the 2017.1 toolchain."

 

Just as easily, I can treat the Petalinux 2017.1 toolchain as a third party toolchain to build my Linux distribution or the gcc5.3.0 toolchain.

 

Using 2017.4 is not an option, so I have to choose 2017.1 or gcc5.3.0.

 

Unless there is some inherent incapability that was built into the Petalinux 2017.1 toolchain to prevent it from working with the Vivado 2017.4 project, my risk is the same using either gcc5.3.0 as a third party toolchain or Petalinux 2017.1 as a third party toolchain.  To say, "Don't" simply implies that using Petalinux 2017.1 is worse than gcc5.3.0. 

 

I will have to test it both ways.

 

Thank you for the input.  I will let you know what happens.

 

0 Kudos