Xilinx / Xilinx/Vitis-Tutorials

Vitis_Platform_Creation/Feature_Tutorials/02_petalinux_customization: ZCU104 yocto-machine name invalid

Open
#382 1 comment 0 reactions 1 assignee View on GitHub

@sven2314 is already working on this.

Since May 11, 2023.

Dominant language
C
Stars
1.6k
Forks
627
PR merge metrics
No merged PRs in 30d

Description

** Which tutorial are you running? **
Vitis_Platform_Creation/Feature_Tutorials/02_petalinux_customization

** Describe the issue **
Configuration of yocto-machine name "zcu104-zynqmp" is invalid. There is an error occuring :

rsync: link_stat "/tools/petalinux-v2022.1-final/components/misc/yocto_machines/zcu104-zynqmp.conf" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]

I can validate that there isn't any file on Petalinux installation folder, except a configuration file named "xilinx-zcu104.conf". So if this is the correct file a change on the Makefile can fix the issue: https://github.com/Xilinx/Vitis-Tutorials/blob/f6bdfbd1d7d03c1c61653676e70b72ce453a635b/Vitis_Platform_Creation/Feature_Tutorials/02_petalinux_customization/ref_files/zcu104/Makefile#L51

** To Reproduce **

  1. Follow the instructions in section "02_petalinux_customization".
  2. Run this command "make all"
  3. See the error
    "rsync: link_stat "/tools/petalinux-v2022.1-final/components/misc/yocto_machines/zcu104-zynqmp.conf" failed: No such file or directory (2)
    rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]"

** Your environment: **

  • OS: Ubuntu 18.04
  • Software Version: 2022.1
  • Hardware : zcu104

** Additional context **
It's not a critical error, as the build of the petalinux project continues.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.