02-26-2017 12:54 PM
Can anybody tell me how to upgrade from Petalinux 2013.4 to 2016.4?
Are the directory structures the same or may I have to start from scratch?
I see references to Yocto in Petalinux 2016.4. Has Yocto been adopted to perform all build operations?
Trying to get an idea of the magnitude of changes required.
02-26-2017 08:27 PM
02-28-2017 06:15 AM
I just thought I would share my experiences of migration.
I took over a project from someone and it was in Petalinux 2014.
They had a written procedure to build everything. (basically throw that out the window) Your best bet is to start a new project in 2016.4 Then create all the apps, modules, etc. If you have experience with the yocto bitbake environment it will be helpful in the transition. Basically what you will need to do is convert your makefiles to bb files Or at least that is the approach I took.
There is some upfront pain of getting things to configure correctly, however I think the environment is much more robust than the former method. The main reason I upgraded to 2016 was to have access to Python in the build and not have to hack-job it in to my environment. I think it was a good transition. FWIW This was a simple project and it took a couple weeks to work out the system from both migrating the Vivado project to 2016 and the Petalinux.
1) You will need to install 2016.4 Petalinux as a normal account, cannot be sudo/root. To keep my flow as similar as before, and I am working on a VM, I put 2016.4 in the same area as previous versions, I just had to make the area writable for my user account.
2) Do not just copy over the project and try to run it as 2016.4, I ran into some oddness that disappeared as soon as I made a fresh project directory. Then just copy in the source files after creating the apps/mods/etc.
3) Vivado also made sense in my case to start a fresh project.
03-04-2017 09:16 AM
04-06-2017 07:03 AM
Given a very short time frame allowed, I'm considering dropping back to Petalinux 2016.2, appears to be fewer changes.