sbobrowicz

Forum Managers
  • Content count

    262
  • Joined

  • Last visited

  • Days Won

    18

sbobrowicz last won the day on April 27

sbobrowicz had the most liked content!

6 Followers

About sbobrowicz

  • Rank
    Community Super-Star

Profile Information

  • Gender
    Male
  • Location
    Pullman, WA

Recent Profile Visitors

2,384 profile views
  1. @zygot valid discussion, but move it to another thread in the General Discussion section of this forum. dlgeng has a good technical question and shouldn't be forced to sift through all this side chatter to get to relevant information. This is a warning for this and future posts in the technical forum section. @dlgeng Here are some boards from some other companies, but they are pricey or require direct quotes: http://www.hitechglobal.com/FMCModules/FMC_4SFP+_Module.htm http://www.hitechglobal.com/FMCModules/x10SFP+_FMC_Module.htm http://www.vadatech.com/product.php?product=292&catid_prev=0&catid_now=0 http://www.fastertechnology.com/products/fmc/fm-s14.html I would recommend contacting companies directly and asking if they will provide you with an academic discount based on your work. Another option you could consider is contacting the Xilinx University Program, they might sponsor you and help you get some better pricing. You should also try reaching out to the NetFPGA group and seeing if they will sponsor your work. They provide preferential pricing on the SUME to projects that they feel contribute to their community. More info on this here: http://store.digilentinc.com/netfpga-sume-virtex-7-fpga-development-board/ .
  2. Have you tried verifying the video output pipeline and your code for reading the video from SD? Maybe just try displaying the SD card image directly on the video output (BTW, HDMI or VGA?). This will help narrow the problem. I'm curious to know what method you are using to read the video from SD, but if you are confident that is not the issue you don't need to go into detail. Are you using an embedded Linux platform or just running standalone?
  3. I think your latest issue is caused by a bug in the uvc gadget driver. I think you need to apply this patch to the kernel: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg89422.html
  4. I've used SDSoC, but have no straight-up HLS experience. I assume the goal here is to produce an ip core that has an axi input stream and an axi output stream, and treats the input stream as a video feed, converting it to black and white and then equalizing the luminance. Does that sound right? What are you using for your input video stream in your block diagram? How is the output stream connected?
  5. petalinux

    Here was the message that seemed to help out that I provided over a private message: Typically, the image.ub file contains the device tree, ramdisk, and kernel. When wanting to boot into the ramdisk file system (instead of linaro), you only need to copy boot.bin and image.ub to the first partition of your SD. This of course means you will need to build everything you want in your file system using petalinux, which can be a chore if you are planning on using a lot of third party libraries and programs. So if you want to boot into Linaro, you should follow the section titled: "Configuring SD Card ext filesystem Boot" in the petalinux RG (pg 61). Be careful to skip step 9 of the section titled "PetaLinux Configuration and Build System Image" and step 3 of "Copying Image Files". This is because those steps will replace your linaro file system with one created by petalinux. If you skip them, then the kernel will just boot whatever file system is present on the second partition, in your case, Linaro. When you follow those steps, image.ub only contains the kernel and device tree, not the ramdisk. This should work for your purposes.
  6. Please don't post any more in this thread since the accelerometer question over USB uart has been answered.
  7. Here was the message that seemed to help out that I provided over a private message: Typically, the image.ub file contains the device tree, ramdisk, and kernel. When wanting to boot into the ramdisk file system (instead of linaro), you only need to copy boot.bin and image.ub to the first partition of your SD. This of course means you will need to build everything you want in your file system using petalinux, which can be a chore if you are planning on using a lot of third party libraries and programs. So if you want to boot into Linaro, you should follow the section titled: "Configuring SD Card ext filesystem Boot" in the petalinux RG (pg 61). Be careful to skip step 9 of the section titled "PetaLinux Configuration and Build System Image" and step 3 of "Copying Image Files". This is because those steps will replace your linaro file system with one created by petalinux. If you skip them, then the kernel will just boot whatever file system is present on the second partition, in your case, Linaro. When you follow those steps, image.ub only contains the kernel and device tree, not the ramdisk. This should work for your purposes.
  8. Glad we are making progress :). First, make sure JP2 and JP3 are not loaded with a jumper. Also, make sure you connect the host PC to the USB OTG port (J13), not the UART or PROG port :). Are you certain The USB OTG device is not getting attached? When you load the driver do you see anything new in /dev or some child directory? Maybe in configfs? If things are not binding as expected, then the first place to look is the device tree. If you attach yours to a post I will check that the USB nodes look correct. They have changed a lot with the newer versions of the kernel, and I can see you are using a newer kernel. Does the gadget need to be called out explicitly in the device tree? This very well could be that the gadget just doesn't do anything initially. It seems there is a nice user space library for this gadget here: libguvc . Maybe you could try installing that library and running through one of the examples (though I don't know where you plan to get the video feed from). And did you ever get the USB mass storage gadget working? Xilinx seems to have verified this before, so I feel like it should be much easier to figure out. This could help make sure the issue is specific to the webcam gadget. Basically it will rule out a lot of issues quickly.
  9. Have you had any luck getting the USB mass storage gadget working? This might help isolate if this is a more general problem or specific to the usb webcam gadget. You might also try adding in some additional debugging options to the kernel. In particular, it would be useful to know which symbol can't be found. A little bit of googling, suggests you might try running depmod on the .ko objects you are loading, to help find where the missing dependency is.
  10. Also, did you set dr_mode to "device" in your device tree?
  11. I'll be straight up with you, I've never used any of the linux USB gadget drivers before, so I'm probably not going to be much help. Maybe someone else will chime in who has some experience with this. Your question is actually not specific to Digilent or Xilinx materials, so you might have some success reaching out to the larger, more general linux community. You could try linuxquestions.org or even stack overflow. Basically just ask around about how to use the linux usb webcam gadget driver on an embedded ARM target. K, I just found this post that might help too, it is Xilinx specific: https://forums.xilinx.com/t5/Zynq-All-Programmable-SoC/ZC702-as-UVC-Device-USB-Webcam/td-p/563957 I also noticed that it looks like Xilinx also suggests you insert configfs.ko... Make sure you have set the following to 'M' (not '*') in the menuconfig: <M> USB Gadget Drivers <M> USB functions configurable through configfs
  12. Hello, I just checked the kernel source, it looks like the kernel for the zybot demo should already have the correct drivers installed. Are you using the binaries included with this download?: https://cdn.instructables.com/ORIG/F2M/U15B/IMGJA59B/F2MU15BIMGJA59B.zip If not, please try using those binaries. If that doesn't fix the problem, please reboot the zybo (with the wifi adapter already installed) and then execute dmesg at the terminal. Copy the output into a file and please attach it to your next post.
  13. Assuming Xillinux uses an X server based desktop environment, you could use xdotool. You will need to get it installed though. Edit: Really sorry, just reread your original post... your options at this point are probably to continue debugging xdotool, or trying something like suggested in the following post: https://unix.stackexchange.com/questions/164262/can-i-simulate-mouse-movements-via-terminal-without-xdotool
  14. We haven't made the jump to petalinux 2016.4 yet, mainly because it has significant changes. The changes are actually a huge positive and I'm excited that they finally tied it together with yocto in a useful way, but it will take us some time to port our existing materials and learn the new processes required. What this means is I don't have much experience in 2016.4 and don't have it working on my system, so I can't get you a quick answer. What happens when you do a search for ssl (or SSL) from the rootfs menuconfig? I think you can activate the search by hitting either the '/' key or '?'. That would be my first move... I poked around a (non-working) install of petalinux I found on a VM and it looks like there are recipes included for openssl in the poky distribution. Unfortunately I don't know for certain how to get at those layers from the petalinux rootfs menuconfig. I also found something called wolfssl, which is an openssl alternative... have you tried using that? I was also gonna suggest you post on the Xilinx forum, but I saw you already did :). It seems they suggest that you have to hack the petalinux install in order to do this, which doesn't seem right to me... I'm gonna follow-up there. https://forums.xilinx.com/t5/Embedded-Linux/OpenSSL-in-Petalinux-2016-4/td-p/761164
  15. It looks like the resource center was mistakenly missing a bunch of links. Thanks for pointing this out, I've added links for everything we have so far. I'm very sorry for any confusion and delay this caused. Follow the petalinux quick start guide (now on the resource center) and you will be able to boot into a pre-built linux image. If you want a shortcut, just copy these two files to a microSD (FAT formatted) and use it to boot the Arty Z7 into Linux: https://github.com/Digilent/petalinux-bsps/raw/master/projects/Digilent-Arty-Z7-Linux-BD-v2016.2/pre-built/linux/images/BOOT.BIN https://github.com/Digilent/petalinux-bsps/raw/master/projects/Digilent-Arty-Z7-Linux-BD-v2016.2/pre-built/linux/images/image.ub The linux_bd project is just the Vivado block diagram project we created the petalinux BSP project around. It is useful to start from it if you want to make some changes to the FPGA design used in your petalinux system, but was not intended to be documented as completely as our "Example Projects". The FIXME in the reference manual was a reminder to update the SDSoC hardware platform status and that accidentally got left in. I've removed it. Thanks for pointing this out as well.