07-26-2021 06:13 AM
we are having an issue with petalinux and new HDF imports not having flash selections
we are using 2018.3 and a kcu105 eval board. We started with the prebuilt files and then the files created by the petalinux-build process. We can build and package a .mcs file from the petalinux BSP, load it in the board and it runs. So far so good.
We then created a hw design from the template in vivado and export the design. when this is done the flash section of the config menu shows only a manual selection. We expected the template to create a hw profile that would continue to work in petalinux the same as the BSP does. We have read a bunch of appnotes and UG docs to no avail.
Our HW designers are out of ideas. This is our first petalinux project and we are now stuck. We assume we are missing something simple and would appreciate any help or suggestions you all may have.
I have posted a similar question in the eval boards section of the forums. We are trying to figure out if we need to modify the HW design (we believe this is the case right now) or is it a petalinux config issue we are fighting.
attached are screencaps of the page in question
FlashConfig_OrgPage.png shows the config for the BSP prior to HW import
FlashConfig_AfterImportPage.png shows the config after the import operation
08-11-2021 06:09 AM
07-26-2021 11:41 PM - edited 07-26-2021 11:41 PM
Hi @Roger1 ,
Seems, you have not included AXI Quad SPI IP in your hardware design. Could you please cross-check once?
If you are not still seeing flash partitions, please share your .xsa and screenshot of your hardware design with us to check at my end.
07-27-2021 06:22 AM
I have previously brought the .hdf into a SDK project instead of petalinux and there is a AXI QSPI present.
I will forward the info you requested as soon as I can get it from my HW folks when they get in this morning
07-27-2021 07:51 AM
Hi abommera, thanks for the quick response. Here is a shot of our evaluation design block. We are using Vivado 2018.3 and SDK, not Vivits. I believe that the .xsa file is for a Vivtis design.
07-29-2021 01:49 AM
I have just created a petalinux project with your .xdf file. I could see the all partitions instead of only manual section. Please let me know what you need to see in this.
07-29-2021 06:29 AM
Can you provide the command details you used?
on our end
Ubutnu 18.04 LTS
vivado / SDK / petalinux 2018.3
petalinux-create -n kcu105_ref -t project -s /usidev/Downloads/Xilinx/Installation_Packages/xilinx-kcu105-axi-full-v2018.3-final.bsp
petalinux-config & petalinux-build all ok at this point.
Import HW description
petalinux-config --get-hw-description ./export
No Flash after this.
07-29-2021 10:38 AM
making some progress although i have no idea why.
I started a brand new PL project, imported the HDF and I now have flash. Lynn made some changes on the HW design so I assume that's why it is now there.
lynn made some further changes to hw, when I import HDF no changes to config info. command I used was from the UG1157 doc which is same as the original import operation.
Created another new PL project. Import same HDF file into the new project and latest HW changes show up in the PL config
Is there a different or additional commands I must run to update a design with a new HDF file rather than an initial import? the 1144 document indicates the that get-hw-description is mutually exclusive with the petalilnux-config <component> variant which we understand to mean if you run the get-hw-description the PL components are auto-configured.
07-30-2021 05:25 AM
Hello @abommera ,
we still cannot update an existing PL project using petalinux-config --get-hw-description ....
we have to import the HDF file into a new PL project to see the changes in the HW design.
It appears the flash issue we had was due to 2 issues.
current status is we see flash in the same manner as you see in your post. We were able to do a build but the deployment to the board did not run the same as the files generated from the virgin BSP (prebuilt and new build). we are looking into this now.
08-05-2021 05:30 PM
Hi @Roger1 ,
Can you check if your design satisfies minimal linux boot requirements mentioned in 2018.3 UG1144, From your design I don't see dual channel timer.
08-06-2021 05:32 AM
We have checked previously and believe it does meet minimum criteria. However, we will check again to be sure. Would be great if that were the issue and we got past this hurdle.
08-06-2021 08:27 AM - edited 08-06-2021 08:28 AM
I am the firmware engineer working with Roger on this design. Thanks for your willingness to help us. I have looked at the design and we are meeting all of the requirements as listed above for our design. We are trying to get the PetaLinux to run on the Xilinx KCU105 evaluation card. I have double checked everything above just to make sure that we are meeting the requirements and we are. Again thanks for your help.
08-06-2021 05:30 PM
Kyle shared your hdf when I build I don't see AXI Timer in your pl.dtsi file. If you can include in the design that would be great to investigate further.
08-06-2021 06:46 PM
08-11-2021 06:09 AM
08-12-2021 10:00 AM
Sorry I was busy with other task and issues. Yes please mark your post if issue is resolved.
08-13-2021 03:48 AM