Jump to content

Jakob Kunzler

Members
  • Posts

    2
  • Joined

  • Last visited

Jakob Kunzler's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. I am using the 2017.4 petalinux tools to build projects for my original "old zybo" board (with the XC7Z010 part). Digilent provides a .bsp from this GitHub repository: https://github.com/Digilent/Petalinux-Zybo/releases/tag/v2017.4-1 that was last maintained in 2019. The pre-built images work fine from the petalinux project created from this .bsp. My issue is that when I run petalinux-build from a freshly generated project, several "do_fetch" process fail to connect to repositories located at git://github.com/mitchellorsucci/[various libraries here like libvrc, libuio, ] in order to fetch various open source components. I have verified that these repositories exist on GitHub. Here is a print out from the first failure: "ERROR: libuio-1.0-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-YEpTzLrPTj"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export GIT_SSL_CAINFO="/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/etc/ssl/certs/ca-certificates.crt"; export PATH="/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/layers/core/scripts:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/plnx_arm/usr/bin/crossscripts:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/x86_64-linux/usr/bin:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/x86_64-linux/sbin:/home/jwkunz/proj/zybopl/Zybo/build/tmp/sysroots/x86_64-linux/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/layers/core/scripts:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/layers/core/bitbake/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/sysroots/x86_64-petalinux-linux/usr/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/usr/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/sbin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/sbin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/../x86_64-petalinux-linux/bin:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-uclibc:/home/jwkunz/Xilinx/Petalinux/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-musl:/home/jwkunz/Xilinx/Petalinux/tools/common/petalinux/utils:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/petalinux/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/petalinux/bin/unexport:/home/jwkunz/Xilinx/Petalinux/tools/hsm/bin:/home/jwkunz/Xilinx/Petalinux/tools/webtalk/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/petalinux/bin:/home/jwkunz/Xilinx/Petalinux/tools/common/petalinux/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/gcc-arm-none-eabi-r5/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/microblaze-xilinx-elf/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/microblazeel-xilinx-linux-gnu/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/gcc-arm-none-eabi/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/gcc-arm-linux-gnueabi/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/aarch64-none-elf/bin:/home/jwkunz/Xilinx/Petalinux/tools/linux-i386/aarch64-linux-gnu/bin:/home/jwkunz/Xilinx/DocNav:/home/jwkunz/Xilinx/Vivado/2017.4/bin:/home/jwkunz/Xilinx/SDK/2017.4/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/microblaze/lin/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/arm/lin/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/microblaze/linux_toolchain/lin64_le/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/aarch32/lin/gcc-arm-linux-gnueabi/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/aarch32/lin/gcc-arm-none-eabi/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/aarch64/lin/aarch64-linux/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/aarch64/lin/aarch64-none/bin:/home/jwkunz/Xilinx/SDK/2017.4/gnu/armr5/lin/gcc-arm-none-eabi/bin:/home/jwkunz/Xilinx/SDK/2017.4/tps/lnx64/cmake-3.3.2/bin:/home/jwkunz/bin:/home/jwkunz/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"; export HOME="/home/jwkunz"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/mitchellorsucci/libuio.git failed with exit code 128, output: fatal: unable to connect to github.com: github.com[0: 140.82.114.4]: errno=Connection timed out" I suspect the issue is that petalinux is trying to pull these repositories via ssh given the "git://" prefix at the end, and I noticed these target repositories on GitHub require "Use a password-protected SSH key". As I recall GitHub had a big authentication overhaul a few years ago. I wonder if this .bsp project needs updated to account for these security changes. I can envision three solutions: 1) Can someone on this forum get me in contact with "mitchellorsucci" (or whoever now manages these repos) to help enable the authentication to successfully fetch? Or if it isn't an authentication problem, help me figure out the configuration issue with the repository. 2) Point me to some resources where I can learn how to change the bitbake configurations to pull from GitHub using another method. 3) Point me to some resources where I can learn how to change the bitbake configurations to pull from predownloaded sources. I know how to do this for the Xilinx sponsored sstate cache content, but how can I do this for the Digilent provided examples? Thanks! PS: I would have put this as an issue on GitHub, but it appears the issues are not regularly maintained.
  2. I was successful in booting the prebuilt petalinux image from the "old Zybo" this morning. Here are my steps. I'm not sure if they are "minimal" in the sense they may have unnecessary portions, but they did work for me. 1) Create a petalinux project from the provided .bsp given here using the 2017.4 version of the tools. This is downloaded from: https://github.com/Digilent/Petalinux-Zybo/releases/tag/v2017.4-1 2) Partition my 32 GB sd card with two partitions. You can do this from either Windows or Linux, but I personally did this from Windows using the disk partition tool. The first partition is about 1 GB for the "boot" stuff, and the second partition is for "data" that I want to give the operating system outside of the petalinux project. Both are formatted with Fat32 with the default block size. You can add support for other file systems using petalinux -c kernel, but Fat32 is the default in the given .bsp. 3) Copy the "BOOT.bin", "image.ub" from the prebuilt image folder inside the petalinux project onto the "boot" partition of the SD card. 4) Eject the SD card. Insert into the Zybo board. 5) Swap the boot jumper pins to "SD". Plug in the UART USB cable. 6) Turn on the Zybo's power. 7) Launch a serial monitor such as Putty with 115200 baud, 8 data bits, 1 stop bits, no parity, no flow control. 8) The Zybo board boots and logs the user in as root. Hope this helps.
×
×
  • Create New...