Vivado/Petalinux version

[shansen]

Hello, my company is evaluating the TE0720 for a new product line. The latest available Petalinux template for this board uses Vivado/Petalinux 2019.2.

Our question is: how often does Trenz release version updates? (every 2 years, every 3 versions, etc)?

We've experienced bugs with Vivado in the past and have been forced to upgrade versions several times to fix these issues. Our concern is that a product designed around the TE0720 may have problems down the road if there is a feature or bugfix we need, and Trenz stops updating the examples/templates (especially Petalinux; we actually tried to update Petalinux from 2019.2 to 2020.2 for the TE0720, but encountered many issues and decided to stop).

Thanks for your time, and I'll also add that we are very pleased with the build quality and features of the TE0720.

[JH]

Hi,
we try to update one time per year. We normally do this for even Vivado/Vitis/Petalinux version, because they are more stable (odd versions are mainly use for new features and even for bugfixes by xilinx).

We start 2020.2 updates, but we have a lot of modules and assembly version, so this take time.

I've start updating documentation:
https://wiki.trenz-electronic.de/display/PD/Xilinx+Development+Tools
especially on petalinux was some more changes: https://wiki.trenz-electronic.de/display/PD/PetaLinux
Maybe this help you.

This week I will publish 2020.2 TE0808 today. I start with TE0720 at next.
br
John

[shansen]

Great news, thanks John. We'll look forward to the 2020.2 update for the TE0720.

[JH]

2020.2

https://wiki.trenz-electronic.de/display/PD/TE0720+Test+Board
br
John

[lalit]

Hello John,

I'm looking for similar for TE0803, especially for petalinux. Would you know when starter kits for this SOM for 2020.2 be available.
I followed your guide but getting u-boot errors.

Thanks

[JH]

Hi,
SD boot or QSPI boot?
Did you add boot.scr file?

PS: I will update design one time again:
1. Prebuilt Linux boot.bin is missing for most variants (I forgot to def. enable generation)
2. There is Xilinx bug in device tree generation when you generate use xsa for single core variant, this is related to: https://forums.xilinx.com/t5/Embedded-Linux/Petalinux-2020-1-reference-to-non-existent-cpu1/td-p/1121625
3. I think I will change default boot.scr file because mixed mode (QSPI boot (Boot.bin on QSPI) with image.ub on SD) is not good supported by default boot.scr and there boot options available which are not used from reference design
br
John