Vitis_Platform_Creation/Feature_Tutorials/02_petalinux_customization: ZCU104 yocto-machine name invalid
@sven2314 is already working on this.
Since May 11, 2023.
Assessment
This issue has not been assessed yet.
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 **
- Follow the instructions in section "02_petalinux_customization".
- Run this command "make all"
- 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.
- Dominant language
- C
- Stars
- 1.6k
- Forks
- 626
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Xilinx/Vitis-Tutorials
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Xilinx/Vitis-Tutorials#514 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Xilinx/Vitis-Tutorials#513 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Xilinx/Vitis-Tutorials#512 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Xilinx/Vitis-Tutorials#509 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Xilinx/Vitis-Tutorials#508 ·
All issues in Xilinx/Vitis-Tutorials
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libsdl-org/SDL#16444 ·
Maintainers usually reply within 1 day
-
bug Component component: net
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#11852 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MiSTer-devel/ao486_MiSTer#243 ·
-
Dropped last row with parallel scan of attached SQLite tables if the rowid range is a multiple of 122,880Possibly taken @staticlibs claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
duckdb/duckdb-sqlite#240 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
siderolabs/pkgs#1710 ·
Maintainers usually reply within 1 day