News:

Attention: For security reasons,please choose a user name *different* from your login name.
Also make sure to choose a secure password and change it regularly.

Main Menu

Porting TE0821 from 2019.2 to 2020.1

Started by jhane, August 03, 2020, 07:01:07 AM

Previous topic - Next topic

jhane


  We are in the process of starting moving our project to the TE0821 SOM.  I was able to port our RTL and petalinux from 2018.3 to 2019.2 with little problem but since it's early in the design process I thought I would try to just make the jump to 2020.1
  Petalinux 2020.1 has made some changes so the upgrade is not quite as simple.  I've been able to get the system to boot but a few thing, like SD and QSPI are not working in linux.  I've realized that my devicetree changes in the meta-user are not being applied so I'm sure I've got some kind of naming mismatch somewhere.

  Has anybody tried this yet? 

thanks,
jeff

JH

Hi,

I'm sorry at the moment we working with 19.2, so I can't help much with 20.1

Did you start 19.2 petalinux project with 20.1? or did you generate a 20.1 petalinux project from scratch? Did you use a xsa which was generated with vivado 20.1?
You should start petalinux project from scratch, for 19.3 we add only this changes manually: https://wiki.trenz-electronic.de/display/PD/TE0821+Test+Board#TE0821TestBoard-SoftwareDesign-PetaLinux


br
John

jhane

Hi,
   No problem, I know I jumping ahead.

   I built my FPGA and petalinx with 2019.2 first and then updated those.  I did not try from scratch but can try with my  xsa tomorrow.  I can see my device-tree recipe run and the system-user.dtsi is copied to the device-tree build directory but it's just not included in the build. 

jeff

JH

Hi,
you must use this one from the meta-user subdirectory:
https://wiki.trenz-electronic.de/display/PD/PetaLinux+KICKstart#PetaLinuxKICKstart-PetalinuxConfiguration
include you changes in the "/system-user.dtsi".


this should be used normally, but maybe your project is corrupted because petalinux projects are seldom compatible. I would suggest to create  from scatch.

PS: you can also check dtb file, when you convert it back to dts:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842279/Build+Device+Tree+Blob#BuildDeviceTreeBlob-Step3:CompilingaDevicetreeBlob(.dtb)filefromtheDTS




br
John

jhane

I see the issue after generation a project from scratch.  The device-tree recipe is different in 2020 than 2019.  I had looked at a BSP for the zcu102 and should have seen this but obviously missed it.  Now things are working as expected.

thanks,
jeff

JH

Hi,
yes it looks like Xilinx has done some more changes:
https://www.xilinx.com/support/answers/73686.html
--> scroll down to "2020.1 New Features:"

Maybe this has to do with this point: "Upgraded Yocto Project version to 3.0 Zeus release"
br
John

jhane

Hi John,

  No, that one was easy because the error message said my layer was not compatible so I was able to look at another BSP and find the answer.  However, I somehow missed to changes to the device-tree recipes .  Also now there must be a u-boot boot script on the boot partition to be able to boot. 
  I've got working images now but petalinux 2020.1 seems a bit flaky.  Now I just need to port my R5 app to Vitis:(

jeff