Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

1 Follower

About Ionel

  • Rank
    Prolific Poster

Profile Information

  • Gender
  • Location

Recent Profile Visitors

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

  1. 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
  2. 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 without any modifications. 4. You have run the bare-metal(standalone/without O
  3. Hi @[email protected] Does it boot if you comment all pcam related nodes in your device tree?
  4. @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.
  5. 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.
  6. 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.
  7. @svaughn442 Edit /etc/resolv.conf to contain only the following lines nameserver nameserver 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.
  8. @NewBee Most likely a null pointer or a wrong address. You can find out by debugging the example and see where the program fails. Make sure the CMA size is set in bootargs. Also The kernel is patched to include an axidma module. But it looks like the patches are included.
  9. You can configure petalinux rootfs to include apache2 server and PHP interpretor. For apach2 use petalinux-config -c rootfs command As for PHP you need to add the yocto recipe to petalinux image using project-spec/meta-user/conf/user-rootfsconfig or project-spec/meta-user/recipes-core/images/petalinux-image-full.bbappend (for petalinux earlier than 2019.2) then you can include it in rootfs via petalinux-config -c rootfs command. HTML, CSS, JavaScript are processed on client machine not on server. Except in case you use server side javascript like in case of nodejs. Also not
  10. 1. Why did you set compatible string for amba_pl ? 2. Note since you did not implement write operation make sure you do not open the device in RW mode. 3. What operation does hellosim performs on device file? there should be your start point in tracking the issue. 4. Your issue is in function simmod_read after first printk => you have a null pointer.
  11. Libuio does the mmap and this for user-space. An example can be found here
  12. C++11 is referring to standard not compiler version. There is no C++ 6.7 standard. Please clarify your statements. When you are referring to compiler version(which compiler?) and when you are referring to standard. Probably you are looking for -std=c++11 which probably version 6.7 of your compiler has support for it.
  13. You can have multiple versions installed I was trying to find out which one you need for your project.
  14. Use UG1144 for your version of petailunx and make sure requirements in Installation Requirements section are met.
  15. Hi @SoyaOhnishi In case of petalinux you may not need two cables since fsbl or u-boot can load the bitstream into fpga ("programiming") usually done over USB-JTAG (J17). To include bitststream in boot.bin use petalinux-package command see ug1144 for your version of petalinux. You only need to connect to UART over USB (J14) to see linux console. However if you have a standalone application you need two cables one for USB-JTAG to debug or load bitstream (J17) and one to communicate with your application over UART1 (J14). If boot your application from SD and load it using a f