sbobrowicz

Forum Managers
  • Content count

    271
  • Joined

  • Last visited

  • Days Won

    18

sbobrowicz last won the day on May 28

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,669 profile views
  1. Step 8 here: http://www.instructables.com/id/Zybot-Getting-Started-Guide/ That project is broken up into several different instructables, all of which are listed here: http://www.instructables.com/id/The-Zybot/
  2. I think @D@n is correct, that is a program meant to run on microblaze (or maybe picoblaze). I would bet that the .mcs wraps up the bit and fw files so that they are programmed into the correct Flash addresses. This is a common solution for packaging microblaze projects that utilize a bootloader because the processor program cannot fit inside the FPGA's Block RAM.
  3. All of our examples for the ZYBO are found here: https://reference.digilentinc.com/reference/programmable-logic/zybo/start?redirect=1 . I'd recommend running through the getting started guides there to get a first touch with the tools. To answer your question, XPAR_SCUGIC_SINGLE_DEVICE_ID and XPAR_XUARTPS_1_INTR are found in xparameters_ps.h, and XPAR_XUARTPS_0_DEVICE_ID should be found in xparameters.h . I also think you should be using XPAR_XUARTPS_1_DEVICE_ID instead. Note that the first block of the #ifdef is not active, so those 4 do not need to exist (the #ifdef is detecting whether or not your code is being built for a Zynq system or a microblaze system).
  4. You are correct, Pmod WIFI is not suitable for Linux. Microchip does not provide linux drivers for the Wifi solution we used on it. I'd recommend using either a USB Wifi dongle, or a module that can be plugged into a pmod port and uses the SDIO interface (TI and Cypress make them I believe). This board from avnet should do the trick: https://www.avnet.com/shop/us/p/kits-and-tools/development-kits/avnet-engineering-services-ade--1/aes-pmod-wilink8-g-3074457345623507290 . I think you will have to buy the WL1835MODGBMOCR board separately though, which will put the total price in the $60 range :(.
  5. The blinking DONE LED is concerning... That means the FPGA is being programmed, then immediately reset. This can happen when powering from USB due to the ZYBO trying to draw too much current. How are you powering the ZYBO? What do you see at the UART terminal when that occurs? Please also provide the output of dmesg when you use your workaround.
  6. Hi Lightning, I peaked at the EETI_eGTouch_Programming_Guide.pdf included with the touchscreen driver, and it looks like there are a good deal of kernel dependencies (including uinput). I would bet that you will need to rebuild the kernel, and also manually copy the generated .ko files where they need to be in the linaro file system. The kernel source used for that project can be downloaded from the instructables page for the Zybot. Use it rebuild the uImage and the modules with the needed changes.
  7. The easiest way to get started with Linux on the Zedboard is to use Petalinux and the ZedBoard BSP provided by Xilinx. To download the latest version of Petalinux and the ZedBoard BSP, go here: https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html . Complete instructions for installing the latest version of petalinux (2017.1) and using the ZedBoard BSP are found in the Petalinux Reference Guide here: https://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_1/ug1144-petalinux-tools-reference-guide.pdf .
  8. As Jon mentioned, we have not made the jump to petalinux 2017.1 yet, so I won't be able to answer any questions on that version of the tools until I get some more more hands on experience with it. What I do know is that since 2016.4, the project structure and method for modifying the device tree have changed significantly. Be sure to read the 2017.1 petalinux reference guide carefully, especially if you are leaning on experience from previous versions of the tools.
  9. @Avery Here are the answers to your questions: 1) Yes, pin T19 attached to the PL of the Zynq can be used to control the HPD signal. See the HDMI section of the PYNQ-Z1 reference manual for some more info: https://reference.digilentinc.com/reference/programmable-logic/pynq-z1/reference-manual#hdmi 2) Sorry, we don't have any CEC demos.
  10. @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/ .
  11. 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?
  12. 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
  13. 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?
  14. 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.
  15. Please don't post any more in this thread since the accelerometer question over USB uart has been answered.