Maciej Piechotka

Members
  • Content count

    6
  • Joined

  • Last visited

  1. My own project. Strangely it happens when I drag'n'drop 'HDMI In' connector from the 'Board' panel. If I create manually connector named 'DDC' the warning is gone.
  2. I'm trying to use HDMI port on my Zybo board. On Vivaldo 2017.2 I run into problems when generating bitstream: [DRC NSTD-1] Unspecified I/O Standard: 3 out of 141 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value. This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: hdmi_in_ddc_scl_io, hdmi_in_ddc_sda_io, and hdmi_in_hpd_led_tri_io[0]. [DRC UCIO-1] Unconstrained Logical Port: 11 out of 141 logical ports have no user assigned specific location constraint (LOC). This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all pin locations. This design will fail to generate a bitstream unless all logical ports have a user specified site LOC constraint defined. To allow bitstream creation with unspecified pin locations (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks UCIO-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: hdmi_in_ddc_scl_io, hdmi_in_ddc_sda_io, hdmi_in_data_p[2:0], hdmi_in_data_n[2:0], hdmi_in_clk_n, hdmi_in_clk_p, and hdmi_in_hpd_led_tri_io[0]. How should I specify correct constraints? What have I done wrong (i.e. why they aren't specified automatically)?
  3. @jpeyron I know those documents. However after reading them many times I find them both too detailed and underspecified. For example: I assume the format is RGB not RBG (as documented) on output. Otherwise both IP and interface are misnamed. It still don't answer if the VSYNC is kept high through the whole period or is it a pulse? With regard to VDMA what format is it stored in? I assume it is just a bitmap but are RGB aligned to 1 byte (3 byte addressing) or 4 bytes [After a though - AXI is power of 2 so it must be 32-bit aligned]? What happens if the data is shorter then VSIZE or HSIZE [EDIT: It seems that it sends VDMAIntErr]? I assume it goes to next stride (EDIT: no it does not] but is it possible to recover original resolution or do I need to count manually? What is memory coherence when using SoC HS Axi by VDMA. I assume, though I haven't found it documented anywhere, that HS AXI will reply on BRESP after it hits data accessible by other ports and CPU (assuming that non-cached access is used). In other words if there is write W1 and read R1 the R1 happens-after W1 (in memory model sense) iff BRESP for W1 has been issued. But does the VDMA waits synchronously on it before proceeding to next frame [i.e. is there a system membar between frames]?
  4. Thanks @jpeyron. I know about those examples but, well, examples are not reference documentation. I didn't know about Video In to AXI Stream component but even building atop the example I would need to know how to program the VDMA and since I want to access frames in different way then write them it doesn't fully help.
  5. @D@n Thanks. I know what the signal are and why they were needed. For now I hoped to avoid and use ready components such as Digilent dvi2rgb. With regard to AXI - sorry I haven't clarified. I was hoping to use SystemC Xilinx abstraction and library which has AXI4M_bus_port - but no real description of how it behaves. I have read the spec. Similarly I need to use it in a sense as on Zybo board memory is exposed as 4+1 AXI Slave interfaces.
  6. Hi, I'm new to FPGAs and I have trouble finding documentation. In particular: How exactly VSync and HSync is handled for HDMI input? What can I assume about them? I'd like to create a AXI Master to store input in DDR. However I cannot find a reference for AXI4M_bus_port - how is timing handled for write_burst? Are there any guaranteed on ordering of stores through AXI Master to DDR? Matt