Search the Community

Showing results for tags 'zybo z7-20'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. I would like to have two HDMI inputs on the Zybo Z7-20. I see in the user manual the following about the Zybo Z7-20 board: But I am still unclear as to if it's possible to have the HDMI TX act as an HDMI RX instead. Thank you, aowens
  2. Hello everyone, I have just started a project with the Zybo Z7-20 board and I am trying to build a simple system using Vivado IP Integrator. I have added the Zybo Z7-20 board files to the Vivado but the board still does not appear in the presets for Zynq Processing System. Also I was not able to find any presets tcl file for the board in the internet. Does any one know where can I find this presets tcl file for the board is there any reference Vivado project for the board to start with?
  3. Hello all, I'd like to connect a Pmod peripheral to the JF connector of Zybo z7-20, however, looks like the board files do not include this interface. When I open a new block design on Vivado, the "board" tab shows only JA through JE connectors. Do I have to manually map it? Maybe use the master xdc file? I'm using Vivado 2018.2 and the "new" board files from github. Thanks!
  4. I have problems with HDMI demo on ZYBO Z7-20, The demo runs well but the resolutions are not correct its kind of crops the stream, the other problem is that on photos and videos red lines appear on edges of the objects and gradients, this happens on videos and photos and not on text, for example if I watch a youtube most of corners of objects get this red lines and other texts for example video description looks normal
  5. Hi everyone, Hardware: Zybo Z7-20, PCam 5C, sd card Software: SDSoC 2017.4, reVISION platform for Zybo Z7-20 (release, v2017.2-3) The “Simple Filter2d Live I/O demo for Pcam5C” is perfectly working (following the readme in reVISION download archive). This code is the starting point for my application. My C++ skills are far from expert level and also quite rusty. I’m developing a live video application for my master thesis. The current step is to implement motion detection. The (simple) concept is to compute the difference between a background image and the current video frame: Initialize: first frame --> (to grey scale) --> (optional: resize) --> gaussian blur ==> background image Loop: frame --> difference to background image --> threshold --> dilate --> find contours ==> list of contours Question: I’m stuck right at the first part, the initialization. The image is already grey scale. The resizing I currently omitted. So the only remaining task is Gaussian blurring. At runtime, when xf::GaussianBlur is called, the program goes into loop, infinitely throwing the following error: Even the first print statement after xf::GaussianBlur is not reached. Since xf::GaussianBlur tries to create hls::streams for both the xf::Mat parameters, I thought that the src matrix might be empty. But printing the first 40 pixels (not included in the code below) yields reasonable values… Any help appreciated! The code (that differs from "Live I/O demo"): Additional #defines in platform.h: // parameters for xf::Mat template with 1 channel. #define XFMAT_1C XF_8UC1,MAX_HEIGHT,MAX_WIDTH,XF_NPPC1 #define GAUSSBLUR_MAX_KERNELSIZE 30 // guessed #define GAUSSBLUR_MAX_SIGMA 10 // guessed #define GAUSSBLUR_SIGMA 2.0 // guessed Code in main.cpp: /* [The initialization stuff: v4l2 input, terminal, drm output, switches&buttons, ncurses] */ // Start capturing frames from video input (Pcam 5C on CSI port). v4l2_helper_start_cap(&v4l2_help); // Get the first frame - a grey-scale image (Y) (from YUV image???). unsigned int v4l2_buf_index = v4l2_helper_readframe(&v4l2_help); uint8_t* firstFrame = (uint8_t*) v4l2_help.buffers[v4l2_buf_index].start[V4L2_FORMAT_Y_PLANE]; xf::Mat<XFMAT_1C> xFirstFrame(vActiveIn, hActiveIn, (void*)firstFrame); // Store first frame as background frame. xf::Mat<XFMAT_1C> xBackground (xFirstFrame.rows, xFirstFrame.cols); xf::GaussianBlur<GAUSSBLUR_MAX_KERNELSIZE, GAUSSBLUR_MAX_SIGMA, XFMAT_1C>(xFirstFrame, xBackground, GAUSSBLUR_SIGMA); // for debugging: mvprintw( 11, 0, "xBackground:"); wrefresh(mywin); for(size_t i = 0; i < 40; i++) { mvprintw( 11, 16 + 4*i, "%u ", xBackground.copyFrom()[i] ); } wrefresh(mywin); /* Loop is commented. Only the cleanup remains at the end: endwin(), etc. */
  6. Hello everyone! I wanted to challenge myself and I tried implementing an I2C master capable of configuring SSM2603. I've been so far unsuccessful, not even an ACK shows up when attempting a read. Here's the wave I'm generating (I'm trying to read reg 0x6) compared with the phases as described in the datasheet. They look the same both in Post-implementation timing simulation and when checking the probes. The ACKs from master side A(M) and ~(A(M) are given unconditionally for the time being. Question 1: do you see any issue here? Question 2: The tool infers OBUFT for ac_sda and OBUF for ac_scl, but I get this warning, is it important? Question 3: lastly, do I still have to generate other signals like MCLK, BCLK, PBLRC and so on to be able to read registers over I2C? As you can see from the code I handle them, but I cannot tell from the datasheet whether they are independent.