Actions
Forum Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 361 subscribers
  • Views 1941 views
  • Users 0 members are here
Related

Petalinux 2020.1 failed to compile with tagged version

pmdp3

Hello,

 

I am trying to build petalinux using ./make_uz7ev_evcc.sh

I set both the petalinux and the hdl version to tag 2020p1_uz_petalinux_UZ7EV_EVCC_20201104_065342

I am using Vitis 2020.1.

When the code runs create_petalinux_project(), it fails at

petalinux-config --silentconfig --get-hw-description=./hw_platform/ -p ${PETALINUX_PROJECTS_FOLDER}/${PETALINUX_PROJECT_NAME}

with:

[INFO] generating user layers

ERROR: Failed to add user layer: /home/pdaye/workspace/ultrazed/git/avnet/petalinux/projects/uz7ev_evcc_2020_1/project-spec/meta-user

ERROR: Failed to config project.

ERROR: Get hw description Failed!

 

Does anyone have an idea to the reason why it is happening?

Yours,

 

Pierre

Parents
  • 0

    Hi there,

     

    I think you changed the wrong variable.

    You do not change the version from 2020.1.  That needs to stay the same.  The only thing that would change is the meta-avnet definition in common.sh.

    However, you should not have to modify that either.

     

    All you need to do is pull down that tag itself.  All the variables, tagstamp.txt and anything else would be setup properly.

     

    Here is a script that I use when I am working with the 2020.1 tags/tips/etc.

    copy of getClones.sh

    # Zynq 7000 (non-Vitis)
#branchTag=2020p1_minized_petalinux_MINIZED_20201104_065342
#branchTag=2020p1_mz_petalinux_MZ7010_FMCCC_20201104_065342
#branchTag=2020p1_mz_petalinux_MZ7020_FMCCC_20201104_065342
#branchTag=2020p1_pz_petalinux_PZ7010_FMC2_20201104_065342
#branchTag=2020p1_pz_petalinux_PZ7015_FMC2_20201104_065342
#branchTag=2020p1_pz_petalinux_PZ7020_FMC2_20201104_065342
#branchTag=2020p1_pz_petalinux_PZ7030_FMC2_20201104_065342


# UltraScale+ (Vitis Capable)
#branchTag=2020p1_ultra96v2_oob_ULTRA96V2_20201104_065342
#branchTag=2020p1_uz_petalinux_UZ3EG_IOCC_20201104_065342
#branchTag=2020p1_uz_petalinux_UZ3EG_PCIEC_20201104_065342
branchTag=2020p1_uz_petalinux_UZ7EV_EVCC_20201104_065342


#branchTag=2020.1


if [ -z ${PETALINUX_VER+x} ]; 
then 
     echo "PETALINUX_VER is unset"; 
else 
     echo "PETALINUX_VER is set to '$PETALINUX_VER'"; 
fi


echo "Cloning '$branchTag'"; 
git clone https://github.com/Avnet/vitis.git
cd vitis
git checkout ${branchTag}
cd ..
git clone https://github.com/Avnet/bdf.git
git clone https://github.com/Avnet/hdl.git
git clone https://github.com/Avnet/petalinux.git
cd hdl
git checkout ${branchTag}
cd ..
cd petalinux
git checkout ${branchTag}
cd ..

     

    Copy this into ~/getClones.sh

    save it, and set it to executable

    sudo chmod 755 getClones.sh

     

    cd to your projects folder

    ex:

    cd ~/projects
mkdir getTag
cd getTag

     

    Run the script

    ./getClones.sh

     

    --Dan

  • 0 in reply to drozwood90

    Hello,

     

    Thank you for your quick response to my request! This is very kind of you.

    I am currently running the code you provided.

    In the meantime, and for my personnal knowledge, I don't understand why meta-avnet should have an impact at this point.

    From my reading of the make_uz7ev_evcc.sh script,

    1. First you check the repos and the env variables
    2. Then you check if you have to build the XSA
    3. Then you create the petalinux projet
    4. Then you configure the petalinux project

    The meta-avnet layer is, from what I understand, added during step 4 (configure_petalinux_project ln 89 call config.board.uz7ev_evcc.sh which does the patching).

    So I don't get where the problem could be as I haven't call the meta-avnet layer at that time...

     

    (In the meantime, the code is finished and it works! Thank you very much)

     

    Yours,

     

    Pierre

  • 0 in reply to pmdp3

    Hi there,

     

    Without knowing exactly which variables you changed, my feeling, related to what you posted, is you removed the ability of the tool to be able to tell what version of tool it is supposed to work with - which then upsets a chain of events and other variables related to that.

     

    We are working on some cleaner ways to handle this and trying to make things more clear.  This last release was the first time we tried this.

     

    Regardless, I am very happy that you got everything working now!

     

    --Dan

Reply
  • 0 in reply to pmdp3

    Hi there,

     

    Without knowing exactly which variables you changed, my feeling, related to what you posted, is you removed the ability of the tool to be able to tell what version of tool it is supposed to work with - which then upsets a chain of events and other variables related to that.

     

    We are working on some cleaner ways to handle this and trying to make things more clear.  This last release was the first time we tried this.

     

    Regardless, I am very happy that you got everything working now!

     

    --Dan

Children
No Data