• Content Count

  • Joined

  • Last visited

About john_joe

  • Rank

Recent Profile Visitors

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

  1. Rebuilding the petalinux using the solution from @Andy7777 did solve the problem.
  2. Hello everyone, I retargeted Pynq v2.5 on the Zybo Z7-20 and tested few things and it is working fine, for example, accessing jupyter or adding custom overlays, etc. However, when I try to use it as a USB host (I am shorting jumper JP1) it does not recognize a pendrive. I try lsusb and it shows nothing. I was able to mount the pendrive using a PYNQ-Z2 image v2.5 and the pendrive is mounted. Is there any way to solve this? Thank you.
  3. Thank you @JColvin. I tested it and is working fine.
  4. Thank you. Indeed I used it with a raspberry pi without problem with a charger outputting 5V and 1A. I was a bit reluctant to connect the Zybo, as it is way more expensive than a raspberry pi zero.
  5. Hello everyone, that question may sound stupid, but is that possible to power up the Zybo-Z7 directly from the USB charger? The reason for that is that I want to boot the board uinsg SD Card and use some peripherals including HDMI-in and HDMI-out and the current from the usb port is not enough. Will charging the usb port directly to one charger such as the one from mobile phones damage the board? I do apologise if that question is obvious or stupid and I appreciate any reply. Thank you
  6. Dear all, I am working with a video processing platform based on this project: I am using a Zybo Z7-20 and I am successful to make a simple passthrough buffer using VDMA. The project is described in the link above. However, when I create a project for a simple RGB2GRAY in Vivado HLS to insert block into the previous platform, I can't make it work (link for second project here: Using linux I can't co-simulate C/RTL in Vivado HLS, but if I use windows this is not an issue. I don't really know why, but it is topic for another question. I generate the Vivado HLS block with ap_start hardwired to 1. Sometimes when I compile Vivado SDK I got some distortions with pixel flickering, but sometimes I can't even see any signals on the screen. I am really lost as I don't understand what is happening. Without the HLS block I have no problems, but after inserting it is completely messed up. I am enclosing the Vivado IP integrator block in PDF, as well the application code (hello.cpp) in the Xilinx SDK. What I also tried instead of hardwiring the HLS block (using #pragma HLS INTERFACE ap_ctrl_none port=return) was to assign ap_start to 1 using a constant or connecting to a GPIO and driving it to 1 in the Xilinx SDK. None methods worked. I am also attaching the whole project on this link: I am using Vivado 2018.3. Please, I really need help and I do appreciate any feedback on this issue. Thank you very much indeed. design_1.pdf hello.cpp
  7. Hi @jpeyron, thank you very much for that information. This needs a careful examination. Thank you.
  8. Hi @jpeyron, actually I was a little bit confused as VGA is output only, right? What I need to do is something close to this: input video source -> adjust resolution -> RGB2DVI, where input video source has VGA (640x480) resolution and RGB2DVI has 1920x1080 resolution. Thank you
  9. Hi @jpeyron, Can I use this Pmod VGA to output VGA video stream from a video source (for instance media player) and output the video to the RGB2DVI IP-Core? Thank you
  10. Hi @jpeyron,, many thanks for the support. Unfortunately your bitstream file does not work on my board. I also generated the bitstream from your project. No signal is detected on my screen. I am frustrated because I can't understand why. However, I was able to get the board working with this project that I found on Github: Best regards.
  11. Dear @jpeyron, To summarize my problem: On nexys video: Clocking Wizard: PLL and RGB2DVI:PLL ==> bitstream is generated but no signal detected on screen and ILA core clock stopped Clocking Wizard:MMCM or RGB2DVI:MMCM ==> unroutable placement error message On zybo z7-20 : Clocking Wizard: PLL and RGB2DVI:MMCM ==> bitstream is generated and project works perfectly. Video is streamed on the screen. I am without understanding why the Nexys Video does not work. PS: I am not sure if it is relevant but I am using Vivado 2018.3 on a Windows 10 machine. The RGB2DVI version is 1.4 and DVI2RGB version is 1.9 Thank you.
  12. Dear @jpeyron, thank you! The Nexys Video HDMI project works as well as the default demo from the board. Regarding to the simple pass through buffer, when the clocking wizard and RGB2DVI is both configured as PLL the bit-stream is successfully generated. I am even able to see the ILA core with a message "no content". However, when I press play the "ILA clock stopped" message is shown and no signal detected is displayed on the screen. Otherwise, if the MMCM is setted instead in the DVI2RGB, the bad routing message is displayed and I am not able to generate the bit-stream. I really need this simple project working instead a larger one such as the demo that comes available from the link you posted. I am curious why this project, properly re-targeted to a Zybo Z7-20, runs without any problem. One more time, I do appreciate your support.
  13. Interesting that I re-targeted the project to a Zybo Z7-20 and the project runs without problem when RGB2DVI is marked as PLL and I can reproduce the screen of my laptop on the monitor at 1080p.
  14. Hi everyone, thank you for the explanations and details already here. I have a Nexys Video that I received today and I have the following diagram for the passthrough buffer. My clock wizard is setup to 125Mhz. DVI2RGB is for 1080p clk >= 125MHz. Same for RGB2DVI. My problem is: If I set RGB2DVI as PLL I got the following error: [Labtools 27-3428] Ila core [hw_ila_1] clock has stopped. Unable to arm ILA core. Otherwise, if MCMM is setted, than I get this error: [Place 30-149] Unroutable Placement! A MMCM / (BUFIO/BUFR) component pair is not placed in a routable site pair. The MMCM component can use the dedicated path between the MMCM and the (BUFIO/BUFR) if both are placed in the same clock region or if they are placed in horizontally adjacent clock regions. If this sub optimal condition is acceptable for this design, you may use the CLOCK_DEDICATED_ROUTE constraint in the .xdc file to demote this message to a WARNING. However, the use of this override is highly discouraged. These examples can be used directly in the .xdc file to override this clock rule. < set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets hdmi_i/dvi2rgb_0/U0/TMDS_ClockingX/I] > Could anyone, please help me? Best regards, Carlos I have the following xdc constraints: [Labtools 27-3428] Ila core [hw_ila_1] clock has stopped. Unable to arm ILA core. ### This file is a general .xdc for the Nexys Video Rev. A ### To use it in a project: ### - uncomment the lines corresponding to used pins ### - rename the used ports (in each line, after get_ports) according to the top level signal names in the project ## Clock Signal set_property -dict { PACKAGE_PIN R4 IOSTANDARD LVCMOS33 } [get_ports { clk }]; #IO_L13P_T2_MRCC_34 Sch=sysclk create_clock -add -name sys_clk_pin -period 10.00 -waveform {0 5} [get_ports clk] ## System Reset set_property -dict { PACKAGE_PIN B22 IOSTANDARD LVCMOS12 } [get_ports { rst }]; #IO_L20N_T3_16 Sch=btnc ## HDMI in set_property -dict { PACKAGE_PIN W4 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_clk_n }]; #IO_L12N_T1_MRCC_34 Sch=hdmi_rx_clk_n set_property -dict { PACKAGE_PIN V4 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_clk_p }]; #IO_L12P_T1_MRCC_34 Sch=hdmi_rx_clk_p create_clock -period 6.734 -waveform {0 3.367} [get_ports { hdmi_in_clk_p }]; set_property -dict { PACKAGE_PIN AB12 IOSTANDARD LVCMOS25 } [get_ports { hdmi_in_hpa }]; #IO_L7N_T1_13 Sch=hdmi_rx_hpa set_property -dict { PACKAGE_PIN Y4 IOSTANDARD LVCMOS33 } [get_ports { hdmi_in_ddc_scl_io }]; #IO_L11P_T1_SRCC_34 Sch=hdmi_rx_scl set_property -dict { PACKAGE_PIN AB5 IOSTANDARD LVCMOS33 } [get_ports { hdmi_in_ddc_sda_io }]; #IO_L10N_T1_34 Sch=hdmi_rx_sda set_property -dict { PACKAGE_PIN AA3 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_n[0] }]; #IO_L9N_T1_DQS_34 Sch=hdmi_rx_n[0] set_property -dict { PACKAGE_PIN Y3 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_p[0] }]; #IO_L9P_T1_DQS_34 Sch=hdmi_rx_p[0] set_property -dict { PACKAGE_PIN Y2 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_n[1] }]; #IO_L4N_T0_34 Sch=hdmi_rx_n[1] set_property -dict { PACKAGE_PIN W2 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_p[1] }]; #IO_L4P_T0_34 Sch=hdmi_rx_p[1] set_property -dict { PACKAGE_PIN V2 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_n[2] }]; #IO_L2N_T0_34 Sch=hdmi_rx_n[2] set_property -dict { PACKAGE_PIN U2 IOSTANDARD TMDS_33 } [get_ports { hdmi_in_data_p[2] }]; #IO_L2P_T0_34 Sch=hdmi_rx_p[2] ## HDMI out #set_property -dict { PACKAGE_PIN AA4 IOSTANDARD LVCMOS33 } [get_ports { hdmi_tx_cec }]; #IO_L11N_T1_SRCC_34 Sch=hdmi_tx_cec set_property -dict { PACKAGE_PIN U1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_clk_n }]; #IO_L1N_T0_34 Sch=hdmi_tx_clk_n set_property -dict { PACKAGE_PIN T1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_clk_p }]; #IO_L1P_T0_34 Sch=hdmi_tx_clk_p set_property -dict { PACKAGE_PIN AB13 IOSTANDARD LVCMOS25 } [get_ports { hdmi_out_hpd }]; #IO_L3N_T0_DQS_13 Sch=hdmi_tx_hpd set_property -dict { PACKAGE_PIN Y1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_n[0] }]; #IO_L5N_T0_34 Sch=hdmi_tx_n[0] set_property -dict { PACKAGE_PIN W1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_p[0] }]; #IO_L5P_T0_34 Sch=hdmi_tx_p[0] set_property -dict { PACKAGE_PIN AB1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_n[1] }]; #IO_L7N_T1_34 Sch=hdmi_tx_n[1] set_property -dict { PACKAGE_PIN AA1 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_p[1] }]; #IO_L7P_T1_34 Sch=hdmi_tx_p[1] set_property -dict { PACKAGE_PIN AB2 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_n[2] }]; #IO_L8N_T1_34 Sch=hdmi_tx_n[2] set_property -dict { PACKAGE_PIN AB3 IOSTANDARD TMDS_33 } [get_ports { hdmi_out_data_p[2] }]; #IO_L8P_T1_34 Sch=hdmi_tx_p[2] ## Configuration options, can be used for all designs set_property CONFIG_VOLTAGE 3.3 [current_design] set_property CFGBVS VCCO [current_design]