ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
// ***************************************************************************
|
|
|
|
// ***************************************************************************
|
2023-07-06 13:54:40 +00:00
|
|
|
// Copyright (C) 2019-2023 Analog Devices, Inc. All rights reserved.
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
//
|
|
|
|
// In this HDL repository, there are many different and unique modules, consisting
|
|
|
|
// of various HDL (Verilog or VHDL) components. The individual modules are
|
|
|
|
// developed independently, and may be accompanied by separate and unique license
|
|
|
|
// terms.
|
|
|
|
//
|
|
|
|
// The user should read each of these license terms, and understand the
|
|
|
|
// freedoms and responsibilities that he or she has by using this source/core.
|
|
|
|
//
|
|
|
|
// This core is distributed in the hope that it will be useful, but WITHOUT ANY
|
|
|
|
// WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
|
|
|
|
// A PARTICULAR PURPOSE.
|
|
|
|
//
|
|
|
|
// Redistribution and use of source or resulting binaries, with or without modification
|
|
|
|
// of this file, are permitted under one of the following two license terms:
|
|
|
|
//
|
|
|
|
// 1. The GNU General Public License version 2 as published by the
|
|
|
|
// Free Software Foundation, which can be found in the top level directory
|
|
|
|
// of this repository (LICENSE_GPL2), and also online at:
|
|
|
|
// <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
|
|
|
|
//
|
|
|
|
// OR
|
|
|
|
//
|
|
|
|
// 2. An ADI specific BSD license, which can be found in the top level directory
|
|
|
|
// of this repository (LICENSE_ADIBSD), and also on-line at:
|
|
|
|
// https://github.com/analogdevicesinc/hdl/blob/master/LICENSE_ADIBSD
|
|
|
|
// This will allow to generate bit files and not release the source code,
|
|
|
|
// as long as it attaches to an ADI device.
|
|
|
|
//
|
|
|
|
// ***************************************************************************
|
|
|
|
// ***************************************************************************
|
|
|
|
|
|
|
|
`timescale 1ns/100ps
|
|
|
|
|
|
|
|
module system_top (
|
|
|
|
|
|
|
|
inout [14:0] ddr_addr,
|
|
|
|
inout [ 2:0] ddr_ba,
|
|
|
|
inout ddr_cas_n,
|
|
|
|
inout ddr_ck_n,
|
|
|
|
inout ddr_ck_p,
|
|
|
|
inout ddr_cke,
|
|
|
|
inout ddr_cs_n,
|
|
|
|
inout [ 3:0] ddr_dm,
|
|
|
|
inout [31:0] ddr_dq,
|
|
|
|
inout [ 3:0] ddr_dqs_n,
|
|
|
|
inout [ 3:0] ddr_dqs_p,
|
|
|
|
inout ddr_odt,
|
|
|
|
inout ddr_ras_n,
|
|
|
|
inout ddr_reset_n,
|
|
|
|
inout ddr_we_n,
|
|
|
|
|
|
|
|
inout fixed_io_ddr_vrn,
|
|
|
|
inout fixed_io_ddr_vrp,
|
|
|
|
inout [53:0] fixed_io_mio,
|
|
|
|
inout fixed_io_ps_clk,
|
|
|
|
inout fixed_io_ps_porb,
|
|
|
|
inout fixed_io_ps_srstb,
|
|
|
|
|
|
|
|
inout [14:0] gpio_bd,
|
|
|
|
|
|
|
|
output hdmi_out_clk,
|
|
|
|
output hdmi_vsync,
|
|
|
|
output hdmi_hsync,
|
|
|
|
output hdmi_data_e,
|
|
|
|
output [23:0] hdmi_data,
|
|
|
|
|
|
|
|
output spdif,
|
|
|
|
|
|
|
|
inout iic_scl,
|
|
|
|
inout iic_sda,
|
|
|
|
|
|
|
|
input rx_ref_clk_p,
|
|
|
|
input rx_ref_clk_n,
|
|
|
|
input rx_device_clk_p,
|
|
|
|
input rx_device_clk_n,
|
|
|
|
output rx_sync0_p,
|
|
|
|
output rx_sync0_n,
|
|
|
|
output rx_sync1_p,
|
|
|
|
output rx_sync1_n,
|
|
|
|
input rx_sysref_p,
|
|
|
|
input rx_sysref_n,
|
|
|
|
input [ 3:0] rx_data_p,
|
|
|
|
input [ 3:0] rx_data_n,
|
|
|
|
|
|
|
|
inout adc_fdb,
|
|
|
|
inout adc_fda,
|
|
|
|
inout adc_pdwn,
|
|
|
|
|
|
|
|
// DAQ board's ADC SPI
|
|
|
|
|
|
|
|
output spi_adc_csn,
|
|
|
|
output spi_adc_clk,
|
|
|
|
output spi_adc_mosi,
|
|
|
|
input spi_adc_miso,
|
|
|
|
|
|
|
|
// DAQ board's clock chip
|
|
|
|
|
|
|
|
output spi_clkgen_csn,
|
|
|
|
output spi_clkgen_clk,
|
|
|
|
output spi_clkgen_mosi,
|
|
|
|
input spi_clkgen_miso,
|
|
|
|
|
|
|
|
// DAQ board's vco chip
|
|
|
|
|
|
|
|
output spi_vco_csn,
|
|
|
|
output spi_vco_clk,
|
|
|
|
output spi_vco_mosi,
|
|
|
|
|
|
|
|
// AFE board's DAC
|
|
|
|
|
|
|
|
inout afe_dac_sda,
|
|
|
|
inout afe_dac_scl,
|
|
|
|
output afe_dac_clr_n,
|
|
|
|
output afe_dac_load,
|
|
|
|
|
|
|
|
// AFE board's ADC
|
|
|
|
|
|
|
|
output afe_adc_sclk,
|
|
|
|
output afe_adc_scn,
|
2019-05-24 06:56:25 +00:00
|
|
|
input afe_adc_sdi,
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
output afe_adc_convst,
|
|
|
|
|
|
|
|
// Laser driver differential line
|
|
|
|
|
|
|
|
output laser_driver_p,
|
|
|
|
output laser_driver_n,
|
|
|
|
|
|
|
|
output laser_driver_en_n,
|
|
|
|
input laser_driver_otw_n,
|
|
|
|
|
|
|
|
// GPIO's for the laser board
|
|
|
|
|
|
|
|
inout [13:0] laser_gpio,
|
|
|
|
|
|
|
|
// Vref selects for AFE board
|
|
|
|
|
2019-07-18 13:02:35 +00:00
|
|
|
output [ 7:0] tia_chsel
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
);
|
|
|
|
|
|
|
|
// internal signals
|
|
|
|
|
|
|
|
wire [63:0] gpio_i;
|
|
|
|
wire [63:0] gpio_o;
|
|
|
|
wire [63:0] gpio_t;
|
|
|
|
wire rx_ref_clk;
|
|
|
|
wire rx_sync;
|
|
|
|
wire rx_sysref;
|
|
|
|
wire rx_device_clk;
|
|
|
|
wire laser_driver;
|
|
|
|
|
|
|
|
// instantiations
|
|
|
|
|
|
|
|
IBUFDS_GTE2 i_ibufds_rx_ref_clk (
|
|
|
|
.CEB (1'd0),
|
|
|
|
.I (rx_ref_clk_p),
|
|
|
|
.IB (rx_ref_clk_n),
|
|
|
|
.O (rx_ref_clk),
|
|
|
|
.ODIV2 ());
|
|
|
|
|
|
|
|
OBUFDS i_obufds_rx_sync0 (
|
|
|
|
.I (rx_sync),
|
|
|
|
.O (rx_sync0_p),
|
|
|
|
.OB (rx_sync0_n));
|
|
|
|
|
|
|
|
OBUFDS i_obufds_rx_sync1 (
|
|
|
|
.I (rx_sync),
|
|
|
|
.O (rx_sync1_p),
|
|
|
|
.OB (rx_sync1_n));
|
|
|
|
|
|
|
|
IBUFGDS i_rx_device_clk (
|
|
|
|
.I (rx_device_clk_p),
|
|
|
|
.IB (rx_device_clk_n),
|
|
|
|
.O (rx_device_clk));
|
|
|
|
|
|
|
|
IBUFDS i_rx_sysref (
|
|
|
|
.I (rx_sysref_p),
|
|
|
|
.IB (rx_sysref_n),
|
|
|
|
.O (rx_sysref));
|
|
|
|
|
|
|
|
// laser driver
|
|
|
|
|
|
|
|
OBUFDS i_obufds_laser_driver (
|
|
|
|
.I (laser_driver),
|
|
|
|
.O (laser_driver_p),
|
|
|
|
.OB (laser_driver_n));
|
|
|
|
|
|
|
|
// GPIO connections to the FMC connector
|
|
|
|
|
2022-04-14 13:13:22 +00:00
|
|
|
ad_iobuf #(
|
|
|
|
.DATA_WIDTH(20)
|
|
|
|
) i_fmc_iobuf (
|
2019-05-09 12:28:17 +00:00
|
|
|
.dio_t ({gpio_t[51:38], 3'b0, gpio_t[34:32]}),
|
|
|
|
.dio_i ({gpio_o[51:32]}),
|
|
|
|
.dio_o ({gpio_i[51:32]}),
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
.dio_p ({
|
|
|
|
laser_gpio, // 51:38
|
|
|
|
afe_adc_convst, // 37 - output only
|
|
|
|
afe_dac_load, // 36 - output only
|
|
|
|
afe_dac_clr_n, // 35 - output only
|
|
|
|
adc_pdwn, // 34
|
|
|
|
adc_fdb, // 33
|
|
|
|
adc_fda // 32
|
|
|
|
}));
|
|
|
|
|
2019-05-09 12:28:17 +00:00
|
|
|
assign gpio_i[63:52] = 12'b0;
|
|
|
|
assign gpio_i[31:15] = 17'b0;
|
|
|
|
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
// GPIO connections for the carrier
|
|
|
|
|
2022-04-14 13:13:22 +00:00
|
|
|
ad_iobuf #(
|
|
|
|
.DATA_WIDTH(15)
|
|
|
|
) i_iobuf_bd (
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
.dio_t (gpio_t[14:0]),
|
|
|
|
.dio_i (gpio_o[14:0]),
|
|
|
|
.dio_o (gpio_i[14:0]),
|
|
|
|
.dio_p (gpio_bd));
|
|
|
|
|
|
|
|
// block design instance
|
|
|
|
|
|
|
|
system_wrapper i_system_wrapper (
|
|
|
|
.ddr_addr (ddr_addr),
|
|
|
|
.ddr_ba (ddr_ba),
|
|
|
|
.ddr_cas_n (ddr_cas_n),
|
|
|
|
.ddr_ck_n (ddr_ck_n),
|
|
|
|
.ddr_ck_p (ddr_ck_p),
|
|
|
|
.ddr_cke (ddr_cke),
|
|
|
|
.ddr_cs_n (ddr_cs_n),
|
|
|
|
.ddr_dm (ddr_dm),
|
|
|
|
.ddr_dq (ddr_dq),
|
|
|
|
.ddr_dqs_n (ddr_dqs_n),
|
|
|
|
.ddr_dqs_p (ddr_dqs_p),
|
|
|
|
.ddr_odt (ddr_odt),
|
|
|
|
.ddr_ras_n (ddr_ras_n),
|
|
|
|
.ddr_reset_n (ddr_reset_n),
|
|
|
|
.ddr_we_n (ddr_we_n),
|
|
|
|
.fixed_io_ddr_vrn (fixed_io_ddr_vrn),
|
|
|
|
.fixed_io_ddr_vrp (fixed_io_ddr_vrp),
|
|
|
|
.fixed_io_mio (fixed_io_mio),
|
|
|
|
.fixed_io_ps_clk (fixed_io_ps_clk),
|
|
|
|
.fixed_io_ps_porb (fixed_io_ps_porb),
|
|
|
|
.fixed_io_ps_srstb (fixed_io_ps_srstb),
|
|
|
|
.gpio_i (gpio_i),
|
|
|
|
.gpio_o (gpio_o),
|
|
|
|
.gpio_t (gpio_t),
|
|
|
|
.hdmi_data (hdmi_data),
|
|
|
|
.hdmi_data_e (hdmi_data_e),
|
|
|
|
.hdmi_hsync (hdmi_hsync),
|
|
|
|
.hdmi_out_clk (hdmi_out_clk),
|
|
|
|
.hdmi_vsync (hdmi_vsync),
|
|
|
|
.iic_main_scl_io (iic_scl),
|
|
|
|
.iic_main_sda_io (iic_sda),
|
|
|
|
.rx_data_0_n (rx_data_n[0]),
|
|
|
|
.rx_data_0_p (rx_data_p[0]),
|
|
|
|
.rx_data_1_n (rx_data_n[1]),
|
|
|
|
.rx_data_1_p (rx_data_p[1]),
|
|
|
|
.rx_data_2_n (rx_data_n[2]),
|
|
|
|
.rx_data_2_p (rx_data_p[2]),
|
|
|
|
.rx_data_3_n (rx_data_n[3]),
|
|
|
|
.rx_data_3_p (rx_data_p[3]),
|
|
|
|
.rx_ref_clk (rx_ref_clk),
|
|
|
|
.rx_device_clk (rx_device_clk),
|
|
|
|
.rx_sync_0 (rx_sync),
|
|
|
|
.rx_sysref_0 (rx_sysref),
|
|
|
|
.spdif (spdif),
|
|
|
|
.laser_driver (laser_driver),
|
|
|
|
.laser_driver_en_n (laser_driver_en_n),
|
|
|
|
.laser_driver_otw_n (laser_driver_otw_n),
|
2019-07-18 13:02:35 +00:00
|
|
|
.tia_chsel (tia_chsel),
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
.iic_dac_scl_io (afe_dac_scl),
|
|
|
|
.iic_dac_sda_io (afe_dac_sda),
|
|
|
|
.spi0_clk_i (spi_adc_clk),
|
|
|
|
.spi0_clk_o (spi_adc_clk),
|
|
|
|
.spi0_csn_0_o (spi_adc_csn),
|
|
|
|
.spi0_csn_i (1'b1),
|
|
|
|
.spi0_sdi_i (spi_adc_miso),
|
|
|
|
.spi0_sdo_i (spi_adc_mosi),
|
|
|
|
.spi0_sdo_o (spi_adc_mosi),
|
|
|
|
.spi1_clk_i (spi_clkgen_clk),
|
|
|
|
.spi1_clk_o (spi_clkgen_clk),
|
|
|
|
.spi1_csn_0_o (spi_clkgen_csn),
|
|
|
|
.spi1_csn_i (1'b1),
|
|
|
|
.spi1_sdi_i (spi_clkgen_miso),
|
|
|
|
.spi1_sdo_i (spi_clkgen_mosi),
|
|
|
|
.spi1_sdo_o (spi_clkgen_mosi),
|
|
|
|
.spi_vco_csn_i (1'b1),
|
|
|
|
.spi_vco_csn_o (spi_vco_csn),
|
|
|
|
.spi_vco_clk_i (1'b0),
|
|
|
|
.spi_vco_clk_o (spi_vco_clk),
|
|
|
|
.spi_vco_sdo_i (1'b0),
|
|
|
|
.spi_vco_sdo_o (spi_vco_mosi),
|
|
|
|
.spi_vco_sdi_i (1'b0),
|
|
|
|
.spi_afe_adc_csn_i (1'b1),
|
|
|
|
.spi_afe_adc_csn_o (afe_adc_scn),
|
|
|
|
.spi_afe_adc_clk_i (1'b0),
|
|
|
|
.spi_afe_adc_clk_o (afe_adc_sclk),
|
|
|
|
.spi_afe_adc_sdo_i (1'b0),
|
2019-05-24 06:56:25 +00:00
|
|
|
.spi_afe_adc_sdo_o (),
|
|
|
|
.spi_afe_adc_sdi_i (afe_adc_sdi));
|
ad_fmclidar1_ebz: Initial commit
This commit was created by squashing the following commits, these
messages were kept just for sake of history:
ad9694_500ebz: Mirror the SPI interface to FMCB
ad9694_500ebz: Set transceiver reference clock to 250
ad9694_500ebz: Allow to configure number of lanes, number of converters
and sample rate
axi_ad9694: Fix number of lanes, it must be 2
ad9694_500ebz: Update the mirrored spi pin assignments
ad9694_500ebz: Gate SPI MISO signals based on chip-select
ad9694_500ebz: Set channel pack sample width
ad9694_500ebz: Change reference clock location
ad9694_500ebz: Remove transceiver memory map arbitration
ad9694_500ebz: Ensure ADC FIFO DMA_DATA_WIDTH is not larger ADC_DATA_WIDTH
ad9694_500ebz: Adjust breakout board pin locations
ad_fmclidar1_ebz: Rename the ad9694_500ebz project
ad_fmclidar1_ebz: Fix lane mapping
ad_fmclidar1_ebz: Delete deprecated files
ad_fmclidar1_ebz: Integrate the axi_laser_driver into the design
ad_fmclidar1_ebz: OTW is an active low signal
ad_fmclidar1_ebz: zc706: Fix iic_dac signals assignment
ad_fmclidar1_ebz: Switch to util_adcfifo
ad_fmclidar1_ebz: Enable synced capture for the fifo
ad_fmclidar1_ebz/zc706: Enable CAPTURE_TILL_FULL
ad_fmclidar1_ebz/zc706: Reduce FIFO size to 2kB
ad_fmclidar1_ebz: Laser driver runs on ADC's core clock
ad_fmclidar1_ebz_bd: Delete the FIFO instance
Because the DMA transfers are going to be relatively small (< 2kbyte),
the DMA can handle the data rate, even when the frequency of the laser
driver pulse is set to its maximum value. (200 kHz)
The synchronization will be done by connecting the generated pulse to
the DMA's SYNC input. Although, to support 2 or 1 channel scenarios, we
need to use the util_axis_syncgen module to make sure that the DMA
catches the pulse, in cases when the pulse width is too narrow. (SYNC is
captures when valid and ready is asserted)
Also we have to reset the cpack IP before each pulse, to keep the DMA buffer's
relative starting point in time fixed, when only 2 or 1 channel is
active.
2017-11-10 13:22:16 +00:00
|
|
|
|
|
|
|
endmodule
|