Ionel

Technical Forum Moderator
  • Content Count

    117
  • Joined

  • Last visited

1 Follower

About Ionel

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Male
  • Location
    Cluj-Napoca

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The user guide(UG1144) for petaliunx is a good starting point. And start with creating a new project. Also this may help https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842250/PetaLinux Or using this project for ZedBoard. However since you have a custom IP you may need to change various aspects of the project like the device tree and creating a custom kernel driver for your IP or a using uio for a driver in user-space.
  2. Please use petalinux/yocto to build the kernel. Additionally if you intend to manually build kernel you can use this instructions for reference.
  3. @Gumesh You may want to take a look at this project Vivado 2020.1 project for Zybo-z7-20 https://github.com/Digilent/Zybo-Z7-HW/tree/20/Petalinux%2Fnext Petalinux 2020.1 project https://github.com/Digilent/Zybo-Z7-OS/tree/20/Petalinux%2Fnext Currently there is work done to port to Vivado and petaliunx 2021.1 In newer version the xilinx linux kernel (5.4 for petalinux 2020.1 and 5.10 for petaliunx 2021.1) is used instead of digilent linux kernel.
  4. @Mikek Have you tried a different terminal ? for instance teraterm ? Or in linux something like picocom?
  5. @iyer25 When you install petalinux make sure you install in a directory owned by your user (not root) also run the installer as normal user (not as su) If you want to have only one version of petalinux and install in the same directory it be best to remove the previous version and start with a clean directory If you have installed multiple versions source only one version per terminal. Also you can remove|rename /home/meghuiyer/.PetaLinux/ and let petalinux to recreate the folder
  6. Genesys ZU: Zynq Ultrascale+ Has an Ethernet port. Is there a reason you need two?
  7. @dpk Depending of you petalinux version you need to add the config to: project-spec/meta-user/recipes-core/images/petalinux-image-full.bbappend (<19.2) project-spec/meta-user/conf/user-rootfsconfig (>19.1) Then you will have this option in "petalinux-config -c rootfs" menu.
  8. @adanowitz you need to add kernel-devsrc package to your petalinux rootfs then copy the {petalinux-rootfs}/lib/modules/{KVER}/build/ directory in your ubunu rootfs /lib/modules/{KVER}/build/
  9. 5.A. is reduntant since it is ovrewriten by 5.B. command. Also 5.B command is changing the hardware configuration that may not have a support for mipi/pcam 5.C. It is possible that you change the hardware to add support for mipi/pcam It is not clear. Hardware changes here should be reflected by the device tree.(under amba_pl node where all PL nodes are nested. Check pl.dtsi file under components directory to see what was generated by petalinux for your hardware description (.hdf/.xsa). 5.F What is xlnk node used for? Are you trying to overwrite an existing device tree node? Why have it
  10. Just to sync our understanding. Please fill in the `???` and if some statement are not true please make sure you clarify that in next post. 1. You have a development machine which has: a. Arch x86_64 OS: ubuntu 18.04 b. Vivado version ???, XSDK version ???, petalinux version ??? 2. Your target hardware: a. Is a zedboard rev ??? b. A pcam rev ??? is attached over FMC adapter 3. Your hardware configuration is https://github.com/Digilent/ZedBoard-FMC-Pcam-Adapter-DEMO/releases/tag/v2019.1-1 without any modifications. 4. You have run the bare-metal(standalone/without O
  11. Hi @[email protected] Does it boot if you comment all pcam related nodes in your device tree?
  12. @DigbyT, The bitstream is for the PL component in zynq. Option --fpga is used to provide a custom bitstream in case you have a different hardware description(hdf|xsa) than the one used to configure the petalinux project. The bootloader is responsible to load the PL(FPGA) with the provided bitstream. If you omit the --fpga option then `images/linux/system.bit` will be used by default. Replacing the bitstream is like changing parts of the hardware, it may be safe but only if the software is ready/prepared the handle those changes. In some cases the device tree also need to change.
  13. It is referring to linux kernel sources not petalinux. Linux kernel is build by petalinux. You can point petalinux to your custom kernel using petalinux-config command.
  14. Hi @Cris , Have you tried a clean build after upgrading to 2020.2 ? If not, try removing everything in build directory except downloads directory. Also remove components directory. Finish work in progress with petalinux-build -c {component} -x finish before removing components directory.
  15. @svaughn442 Edit /etc/resolv.conf to contain only the following lines nameserver 1.1.1.1 nameserver 8.8.8.8 Alternatively If your router provides DNS Servers you may want to replace /etc/resolv.conf with a symbolic link to /run/systemd/resolve/resolv.conf: cd /etc/ sudo rm resolv.conf sudo ln -s /run/systemd/resolve/resolv.conf resolv.conf Then reboot the board with sudo reboot. This should fix the problem.