cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Participant
Participant
1,400 Views
Registered: ‎05-24-2018

Petalinux 2018.3 - failed to config project

Hi

I recently started working on ZCU102 evaluation board and I found a document (UG1209) for ultrascale+ MPSoc embedded design tutorial. Following that, and UG1144 for petalinux installation and other reference, I want to load linux on the PS using petalinux as the example in UG1209 suggests on page number 47.

I followed all the steps for installation mentioned in UG1144 and the steps to design the hdf file as mentioned in UG1209 but when I am running the command to configure it ends up giving following error and I am not getting how I can resolve this or what is causing this error.

 

petalinux-config --get-hw-description=/home/crypto/zxu102_linux/zxu102_linux.sdk
INFO: Getting hardware description...
INFO: Rename zynq_wrapper.hdf to system.hdf
[INFO] generating Kconfig for project
[INFO] menuconfig project
ERROR: Failed to menu config project component
ERROR: Failed to config project.
ERROR: Get hw description Failed!.

 

I am using petalinux 2018.3 & vivado 2018.3 on a host linux machine with ubuntu 16.04

Could anyone help me out regarding this issue?

0 Kudos
7 Replies
Highlighted
Moderator
Moderator
1,387 Views
Registered: ‎09-12-2007

Re: Petalinux 2018.3 - failed to config project

Can you confirm that the HDF exists at this path:

petalinux-config --get-hw-description=/home/crypto/zxu102_linux/zxu102_linux.sdk

0 Kudos
Highlighted
Participant
Participant
1,374 Views
Registered: ‎05-24-2018

Re: Petalinux 2018.3 - failed to config project

Hi

Yes, the hdf file is at that location. It is named zynq_wrapper.hdf as it is also shown in the log attached in the 4th line after getting hardware description where it is converting zynq_wrapper.hdf to system.hdf

The file is in the mentioned path only. 

Also I rechecked the libraries required for petalinux as well, they are also to their latest required version as mentioned in UG1144.

0 Kudos
Highlighted
Participant
Participant
1,344 Views
Registered: ‎05-24-2018

Re: Petalinux 2018.3 - failed to config project

Hi

I looked into the config.log file in the build folder and it shows the following log. Could you help in explaining and resolving through this-

 

[INFO] generating Kconfig for project
INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
hsi::open_hw_design: Time (s): cpu = 00:00:05 ; elapsed = 00:00:05 . Memory (MB): peak = 734.879 ; gain = 195.785 ; free physical = 7751 ; free virtual = 100908
[INFO] menuconfig project
/home/crypto/xilinx-zcu102-zu9-es2-rev1.0-2018.3/build/misc/config/Kconfig.syshw:29:warning: defaults for choice values not supported
/home/crypto/xilinx-zcu102-zu9-es2-rev1.0-2018.3/build/misc/config/Kconfig:630:warning: config symbol defined without type
Your display is too small to run Menuconfig!
It must be at least 19 lines by 80 columns.

 

Which display is it talking about? My terminal in linux machine or something else?

If its about terminal window so my terminal window is already set to 24 rows*80 column at the moment.

Highlighted
Participant
Participant
1,334 Views
Registered: ‎05-24-2018

Re: Petalinux 2018.3 - failed to config project

Hi

It is working now, seems the terminal size was the issue. I just maximized the terminal screen and executed the same command and it worked which earlier was not working when my terminal was not maximized it was just a small window over other window as well.

Thanks for the replies and support anyways.

Highlighted
Observer
Observer
1,126 Views
Registered: ‎08-27-2019

Re: Petalinux 2018.3 - failed to config project

it resolved the issue but just feel this is too amazing
0 Kudos
Highlighted
613 Views
Registered: ‎10-28-2019

Re: Petalinux 2018.3 - failed to config project

This happened to me as well.  The PetaLinux installation is prone to errors and is flaky at best

Highlighted
Explorer
Explorer
424 Views
Registered: ‎04-19-2018

Re: Petalinux 2018.3 - failed to config project

Petamazing! It just happened to me with 2019.2.... restart the VM and done.

0 Kudos