sbobrowicz

Members
  • Content count

    398
  • Joined

  • Last visited

  • Days Won

    28

sbobrowicz last won the day on June 15

sbobrowicz had the most liked content!

7 Followers

About sbobrowicz

  • Rank
    Prolific Poster

Contact Methods

  • Website URL
    www.elite-embedded.com

Profile Information

  • Gender
    Male
  • Location
    Seattle, WA

Recent Profile Visitors

4463 profile views
  1. K, so it looks like you have it nailed down to petalinux 2017.4 not working on your system (since the xilinx-zc702 also seems to fail). Also, whatever issue you are running into seems to have been resolved in 2018.1. I don't like punting people to other places, but at this point I'd recommend reaching out on the Xilinx forums and seeing what they have to say. You should also try opening a support ticket with them. The fact that it seems to have been fixed in 2018.1 suggests that someone over there knows what is going on. Be sure to provide error.txt to them. We can keep trying here too... It looks like yocto has generated an invalid git command for the 5 repos that throw errors. The command tries to fetch a remote branch directly onto the current branch, which is not allowed. Perhaps the git repo is in a different state than yocto expects for some reason. Another possibility is that your git configuration is not compatible with the version of yocto present in 2017.4. Can you provide ~/.gitconfig, and any other git configuration files you might have on your system (you might want to strip them of personal info, your call)? Also, what version of git are you using?
  2. sbobrowicz

    Can't get Digilent/Petalinux-Zybo-Z7-20 to work

    Any flickering on the LEDs, or does DONE go low? What branch and commit are you checked out at? For comparison, try downloading the BSP from the release tab in github and building using that flow.
  3. sbobrowicz

    Program code on PetaLinux

    @theAsker Please provide more information about what you mean when you say you cannot write to the XADC registers. Are you receiving an error? Also, I'm not certain your addresses in the code above are correct. For one, in the commented out line where you try to enable the core, you write to address 0x02, which doesn't make sense since the registers are 32-bits (they should all be 4-byte aligned: 0x00,0x04,0x08,0x0C...)
  4. sbobrowicz

    Can't get Digilent/Petalinux-Zybo-Z7-20 to work

    @fandrei What do you have connected to the Zybo (USB devices, Monitor, network, etc.)? Also, how are you powering the board? Something like this can occur commonly if attempting to power from USB, so you should power from an external 5V regulator. Does the DONE LED go low when the processor freezes, or does the power LED flicker?
  5. sbobrowicz

    Petalinux-Zybo-Z7-20 project doesn't build

    @fandrei Not that I am aware of, but feel free to start one up here Update: still working on the push, hopefully it will come soon
  6. sbobrowicz

    Arty Z7 USB

    What about USB Flash drives, do those work in Linux? The Wifi dongles require building in some drivers and adding firmware images to the rootfs, so this will help indicate if the problem is with your device tree config. Also, have you tried using this project? https://github.com/Digilent/Petalinux-Arty-Z7-20 That might be an easier starting point for you because the USB host functionality is validated already. I can also help you build in the needed drivers and firmware.
  7. @MauroChimenti K, so it looks like you got the fetches for the digilent-apps working. Can you provide project-spec/configs/config for your project? I just want to make sure the URLs in it have not been modified somehow. Typically the tools reach out to petalinux.xilinx.com, so I find the author.xilinx.com domain suspicious. I can't access it either (in a browser). I also want to check your TMPDIR setting. Are you using a VPN or any other service that might be playing with your connection? Also, is your petalinux project (or the entire VM) on a NFS file server? How many processors and how much RAM have you allocated to your VM? Last, how much disk space have do you have free on your VM, and on the disk which your VM resides? Most problems like this boil down to a unique host system setup, or a dirty project. To clean your petalinux project completely, just try manually deleting all folders except the project-spec folder. Also, delete the meta-plnx-generated folder.
  8. sbobrowicz

    USB-OTG on Zedboard running Arch Linux

    Try replacing the usb phy node with: usb_phy0: usb_phy@0 { compatible = "ulpi-phy"; #phy-cells = <0>; reg = <0xe0002000 0x1000>; view-port = <0x0170>; drv-vbus; }; And update the phy handle property in the usb controller: usb-phy = <&usb_phy0>;
  9. sbobrowicz

    PCAM 5C Petalinux support Zybo Z7-20

    @mmongu Turns out the ov5640 Linux driver wasn't in a state to be working correctly, except for with a specific set of platforms (Pcam 5C not included). I've put together some patches to increase its compatibility and am working on getting them upstreamed. For now, I'm just going to add a branch on the Digilent linux repo that contains the necessary changes. Then I will push an update to the Zybo Z7-20 petalinux project to point at the newer kernel and that includes a demo for displaying video from the Pcam. I should be done with this soon, I'm shooting for the end of the weekend. Don't hold me to that though, it may bleed into next week.
  10. sbobrowicz

    AXI SPI on adrv9361z7035 (formerly PicoZed SDR)

    You'll have to ask ADI (or the maker of the dev board) to make a BSP for you, or you will have to make the petalinux project yourself. UG1144 from Xilinx is the right place to start to learn how to create a Petalinux project from scratch. Make sure you use the version of that document that is targeted for 2017.1, it can change A LOT between releases.
  11. sbobrowicz

    Petalinux-Zybo-Z7-20 project doesn't build

    @fandrei I'm sorry, I forgot to mention a key step that is actually a lot of work, and the cause of the issue you are having. The Digilent u-boot and linux kernel repos will need to be merged with the recent changes to the Xilinx u-boot and Linux kernel repos. You can probably skip the u-boot merges, but it seems the linux kernel will need a merge. It also seems that they are expecting a branch called "xlnx_rebase_v4.14" to exist, which is new to 2018.1 (in the past they always assumed the master branch). Please run petalinux-config and see if you can override the branch anywhere, probably in the section where you set the remote linux repo. Good news is that I happen to be working on a merge right now that should work for you and will end up pushed to the digilent repo. When it goes live I will let you know and tell you what commit to point at. If you want to give the merge a shot yourself, let me know, and I can give you some pointers.
  12. sbobrowicz

    Program code on PetaLinux

    You should not use mmap or try to access the XADC drivers directly from user space, just use the IIO files. Here is the IIO documentation: https://01.org/linuxgraphics/gfx-docs/drm/driver-api/iio/core.html#industrial-i-o-devices You should try accessing /dev/iio:deviceX as described in that document. Turns out the kernel should ensure the adc is sampled at a constant rate and then inserted into a buffer that can be read using that file. The sampling_frequency file in /sys/bus/ also seems to control the sampling rate (not sure if you can change it or not for the Xilinx driver). There is complete documentation there, and also some third party libraries that might help you out (see libiio).
  13. sbobrowicz

    Petalinux-Zybo-Z7-20 project doesn't build

    Thanks for posting the solution. As for updating to 2018.1, I haven't used it yet, so I can't accurately answer your question. In previous versions, I was able to just open the project in the newer version and it was updated automatically, but I can't guarantee that will be the case here.
  14. sbobrowicz

    Petalinux boot up on Zybo S7 from SD Card.

    @rpickeri As a general rule, you should only manually modify files in the meta-user folder. All other files should have a petalinux-config front end and/or be automatically generated by Petalinux, meaning if you modify them your changes may be overwritten by the tools. The more standard approach to what you are doing is to export the HDF from Vivado, but then skip Xilinx SDK entirely. Instead, import the HDF directly into Petalinux, which will automatically generate FSBL, device-tree, BOOT.bin, etc.. In fact, petalinux calls many of the same tools internally as SDK, including the device tree generator. For info on importing the HDF into your project, see UG1144 from Xilinx. I also recently described how device tree modification works here:
  15. sbobrowicz

    USB-OTG on Zedboard running Arch Linux

    It could be the device tree, can you provide the node for the USB controller? I'm not familiar with the archlinux docs and images you are using, so I can't really say off the top what is wrong. You could use the Petalinux BSP (which includes pre-built images) from Xilinx as an example of a working linux system with USB host. That could help you pinpoint what is wrong in the archlinux image.