EmbDev.net

Forum: FPGA, VHDL & Verilog ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Junior H. (Company: University) (junior_hpc)

2015-10-22 14:37

Rate this post

•	▲ useful ▼ not useful

Hello. I have this working code.

library ieee;
use ieee.std_logic_1164.all;
use ieee.std_logic_unsigned.all;
use ieee.numeric_std.all;
entity xillydemo is
    PCIE_PERST_B_LS : IN std_logic;
    PCIE_REFCLK_N : IN std_logic;
    PCIE_REFCLK_P : IN std_logic;
    PCIE_RX_N : IN std_logic_vector(3 DOWNTO 0);
    PCIE_RX_P : IN std_logic_vector(3 DOWNTO 0);
    GPIO_LED : OUT std_logic_vector(3 DOWNTO 0);
    PCIE_TX_N : OUT std_logic_vector(3 DOWNTO 0);
    PCIE_TX_P : OUT std_logic_vector(3 DOWNTO 0));
end xillydemo;
architecture sample_arch of xillydemo is
  component xillybus
    port (
      PCIE_PERST_B_LS : IN std_logic;
      PCIE_REFCLK_N : IN std_logic;
      PCIE_REFCLK_P : IN std_logic;
      PCIE_RX_N : IN std_logic_vector(3 DOWNTO 0);
      PCIE_RX_P : IN std_logic_vector(3 DOWNTO 0);
      GPIO_LED : OUT std_logic_vector(3 DOWNTO 0);
      PCIE_TX_N : OUT std_logic_vector(3 DOWNTO 0);
      PCIE_TX_P : OUT std_logic_vector(3 DOWNTO 0);
      bus_clk : OUT std_logic;
      quiesce : OUT std_logic;
      user_r_mem_8_rden : OUT std_logic;
      user_r_mem_8_empty : IN std_logic;
      user_r_mem_8_data : IN std_logic_vector(7 DOWNTO 0);
      user_r_mem_8_eof : IN std_logic;
      user_r_mem_8_open : OUT std_logic;
      user_w_mem_8_wren : OUT std_logic;
      user_w_mem_8_full : IN std_logic;
      user_w_mem_8_data : OUT std_logic_vector(7 DOWNTO 0);
      user_w_mem_8_open : OUT std_logic;
      user_mem_8_addr : OUT std_logic_vector(4 DOWNTO 0);
      user_mem_8_addr_update : OUT std_logic;
      user_r_read_32_rden : OUT std_logic;
      user_r_read_32_empty : IN std_logic;
      user_r_read_32_data : IN std_logic_vector(31 DOWNTO 0);
      user_r_read_32_eof : IN std_logic;
      user_r_read_32_open : OUT std_logic;
      user_r_read_8_rden : OUT std_logic;
      user_r_read_8_empty : IN std_logic;
      user_r_read_8_data : IN std_logic_vector(7 DOWNTO 0);
      user_r_read_8_eof : IN std_logic;
      user_r_read_8_open : OUT std_logic;
      user_w_write_32_wren : OUT std_logic;
      user_w_write_32_full : IN std_logic;
      user_w_write_32_data : OUT std_logic_vector(31 DOWNTO 0);
      user_w_write_32_open : OUT std_logic;
      user_w_write_8_wren : OUT std_logic;
      user_w_write_8_full : IN std_logic;
      user_w_write_8_data : OUT std_logic_vector(7 DOWNTO 0);
      user_w_write_8_open : OUT std_logic);
  end component;
  component fifo_8x2048
    port (
      clk: IN std_logic;
      srst: IN std_logic;
      din: IN std_logic_VECTOR(7 downto 0);
      wr_en: IN std_logic;
      rd_en: IN std_logic;
      dout: OUT std_logic_VECTOR(7 downto 0);
      full: OUT std_logic;
      empty: OUT std_logic);
  end component;
  component fifo_32x512
    port (
      clk: IN std_logic;
      srst: IN std_logic;
      din: IN std_logic_VECTOR(31 downto 0);
      wr_en: IN std_logic;
      rd_en: IN std_logic;
      dout: OUT std_logic_VECTOR(31 downto 0);
      full: OUT std_logic;
      empty: OUT std_logic);
  end component;
-- Synplicity black box declaration
  attribute syn_black_box : boolean;
  attribute syn_black_box of fifo_32x512: component is true;
  attribute syn_black_box of fifo_8x2048: component is true;
  type demo_mem is array(0 TO 31) of std_logic_vector(7 DOWNTO 0);
  signal demoarray : demo_mem;
  signal bus_clk :  std_logic;
  signal quiesce : std_logic;
  signal reset_8 : std_logic;
  signal reset_32 : std_logic;
  signal ram_addr : integer range 0 to 31;
  signal user_r_mem_8_rden :  std_logic;
  signal user_r_mem_8_empty :  std_logic;
  signal user_r_mem_8_data :  std_logic_vector(7 DOWNTO 0);
  signal user_r_mem_8_eof :  std_logic;
  signal user_r_mem_8_open :  std_logic;
  signal user_w_mem_8_wren :  std_logic;
  signal user_w_mem_8_full :  std_logic;
  signal user_w_mem_8_data :  std_logic_vector(7 DOWNTO 0);
  signal user_w_mem_8_open :  std_logic;
  signal user_mem_8_addr :  std_logic_vector(4 DOWNTO 0);
  signal user_mem_8_addr_update :  std_logic;
  signal user_r_read_32_rden :  std_logic;
  signal user_r_read_32_empty :  std_logic;
  signal user_r_read_32_data :  std_logic_vector(31 DOWNTO 0);
  signal user_r_read_32_eof :  std_logic;
  signal user_r_read_32_open :  std_logic;
  signal user_r_read_8_rden :  std_logic;
  signal user_r_read_8_empty :  std_logic;
  signal user_r_read_8_data :  std_logic_vector(7 DOWNTO 0);
  signal user_r_read_8_eof :  std_logic;
  signal user_r_read_8_open :  std_logic;
  signal user_w_write_32_wren :  std_logic;
  signal user_w_write_32_full :  std_logic;
  signal user_w_write_32_data :  std_logic_vector(31 DOWNTO 0);
  signal user_w_write_32_open :  std_logic;
  signal user_w_write_8_wren :  std_logic;
  signal user_w_write_8_full :  std_logic;
  signal user_w_write_8_data :  std_logic_vector(7 DOWNTO 0);
  signal user_w_write_8_open :  std_logic;
  xillybus_ins : xillybus
    port map (
      -- Ports related to /dev/xillybus_mem_8
      -- FPGA to CPU signals:
      user_r_mem_8_rden => user_r_mem_8_rden,
      user_r_mem_8_empty => user_r_mem_8_empty,
      user_r_mem_8_data => user_r_mem_8_data,
      user_r_mem_8_eof => user_r_mem_8_eof,
      user_r_mem_8_open => user_r_mem_8_open,
      -- CPU to FPGA signals:
      user_w_mem_8_wren => user_w_mem_8_wren,
      user_w_mem_8_full => user_w_mem_8_full,
      user_w_mem_8_data => user_w_mem_8_data,
      user_w_mem_8_open => user_w_mem_8_open,
      -- Address signals:
      user_mem_8_addr => user_mem_8_addr,
      user_mem_8_addr_update => user_mem_8_addr_update,
      -- Ports related to /dev/xillybus_read_32
      -- FPGA to CPU signals:
      user_r_read_32_rden => user_r_read_32_rden,
      user_r_read_32_empty => user_r_read_32_empty,
      user_r_read_32_data => user_r_read_32_data,
      user_r_read_32_eof => user_r_read_32_eof,
      user_r_read_32_open => user_r_read_32_open,
      -- Ports related to /dev/xillybus_read_8
      -- FPGA to CPU signals:
      user_r_read_8_rden => user_r_read_8_rden,
      user_r_read_8_empty => user_r_read_8_empty,
      user_r_read_8_data => user_r_read_8_data,
      user_r_read_8_eof => user_r_read_8_eof,
      user_r_read_8_open => user_r_read_8_open,
      -- Ports related to /dev/xillybus_write_32
      -- CPU to FPGA signals:
      user_w_write_32_wren => user_w_write_32_wren,
      user_w_write_32_full => user_w_write_32_full,
      user_w_write_32_data => user_w_write_32_data,
      user_w_write_32_open => user_w_write_32_open,
      -- Ports related to /dev/xillybus_write_8
      -- CPU to FPGA signals:
      user_w_write_8_wren => user_w_write_8_wren,
      user_w_write_8_full => user_w_write_8_full,
      user_w_write_8_data => user_w_write_8_data,
      user_w_write_8_open => user_w_write_8_open,
      -- General signals
      PCIE_PERST_B_LS => PCIE_PERST_B_LS,
      PCIE_REFCLK_N => PCIE_REFCLK_N,
      PCIE_REFCLK_P => PCIE_REFCLK_P,
      PCIE_RX_N => PCIE_RX_N,
      PCIE_RX_P => PCIE_RX_P,
      GPIO_LED => GPIO_LED,
      PCIE_TX_N => PCIE_TX_N,
      PCIE_TX_P => PCIE_TX_P,
      bus_clk => bus_clk,
      quiesce => quiesce
--  A simple inferred RAM
  ram_addr <= conv_integer(user_mem_8_addr);
  process (bus_clk)
  begin
    if (bus_clk'event and bus_clk = '1') then
      if (user_w_mem_8_wren = '1') then 
        demoarray(ram_addr) <= user_w_mem_8_data;
      end if;
      if (user_r_mem_8_rden = '1') then
        user_r_mem_8_data <= demoarray(ram_addr);
      end if;
    end if;
  end process;
  user_r_mem_8_empty <= '0';
  user_r_mem_8_eof <= '0';
  user_w_mem_8_full <= '0';
--  32-bit loopback
  fifo_32 : fifo_32x512
    port map(
      clk        => bus_clk,
      srst       => reset_32,
      din        => user_w_write_32_data,
      wr_en      => user_w_write_32_wren,
      rd_en      => user_r_read_32_rden,
      dout       => user_r_read_32_data,
      full       => user_w_write_32_full,
      empty      => user_r_read_32_empty
  reset_32 <= not (user_w_write_32_open or user_r_read_32_open);
  user_r_read_32_eof <= '0';
--  8-bit loopback
  fifo_8 : fifo_8x2048
    port map(
      clk        => bus_clk,
      srst       => reset_8,
      din        => user_w_write_8_data,
      wr_en      => user_w_write_8_wren,
      rd_en      => user_r_read_8_rden,
      dout       => user_r_read_8_data,
      full       => user_w_write_8_full,
      empty      => user_r_read_8_empty
    reset_8 <= not (user_w_write_8_open or user_r_read_8_open);
    user_r_read_8_eof <= '0';
end sample_arch;


Why if I try to push user_w_write_8_data to user_r_read_8_data I get 
error but if I try to push a stitic value to user_r_read_8_data it 
works?

This works:

process (bus_clk)
    if (bus_clk'event and bus_clk = '1') then
      if (user_w_mem_8_wren = '1') then 
        user_r_read_8_data <= "00000001";
      end if;
    end if;
  end process;



This works too:

process (bus_clk)
    if (bus_clk'event and bus_clk = '1') then
      if (user_w_mem_8_wren = '1') then 
        tmp <= user_w_write_8_data;
      end if;
    end if;
  end process;



But this does not work:

process (bus_clk)
    if (bus_clk'event and bus_clk = '1') then
      if (user_w_mem_8_wren = '1') then 
        user_r_read_8_data <= user_w_write_8_data;
      end if;
    end if;
  end process;


This is the error I get:

ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[0].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[1].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[2].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[3].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[4].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[5].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[6].
[Opt 31-37] Multi-driver net found in the design: fifo_8/U0/inst_fifo_gen/gconvfifo.rf/grf.rf/gntv_or_sync_fifo.mem/gbm.gbmg.gbmga.ngecc.bmg/inst_blk_mem_gen/gnativebmg.native_blk_mem_gen/valid.cstr/ramloop[0].ram.r/prim_noinit.ram/dout[7].


Can somebody explain me why the last code does not work?

Report post Edit Move Thread sperren Anmeldepflicht aktivieren Anpinnen Delete topic Thread mit anderem zusammenführen Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Lothar M. (Company: Titel) (lkmiller) (Moderator)

2015-10-22 17:33

Rate this post

•	▲ useful ▼ not useful

What do you do with tmp in the second case? Nothing? Then it is simply 
optimized away...

Obviously the signal in question is connected to an output port. And you 
additionally drive a value on it. That's the multisource.

What toolchain and what target do you use?

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Junior H. (Company: University) (junior_hpc)

2015-10-23 08:56

Rate this post

•	▲ useful ▼ not useful

Hello. I use Vivado suite 2015 on Xilinx Artix 7. Well, in both second 
and third case, I copy the value of user_w_write_8_data in an other 
variable/signal. Can you please give me more details about this issue? 
By signal in question, do you mean user_r_read_8_data? Thanks.

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Junior H. (Company: University) (junior_hpc)

2015-10-23 10:01

Rate this post

•	▲ useful ▼ not useful

Lothar M. wrote:

> Obviously the signal in question is connected to an output port. And you
> additionally drive a value on it. That's the multisource.

Actually, what I want to do is to take the value of user_w_write_8_data 
and put it in user_r_read_8_data. Is there any solution for this 
problem?

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Achim S. (Guest)

2015-10-23 12:43

Rate this post

•	▲ useful ▼ not useful

Junior H. wrote:
> Actually, what I want to do is to take the value of user_w_write_8_data
> and put it in user_r_read_8_data. Is there any solution for this
> problem?

You should configure your fifo_8 as "fist word fall through fifo" (maybe 
in your toolchain the parameter of the fifo-generator is called slightly 
different). Then - in case the fifo is empty prior to the write access - 
the write data appears at the fifo output immediately after writing it.

If the fifo is not empty prior to the write access, then of course the 
"old" data remains at the fifo output (until you activate the read 
enable input for the required number of cycles). That's just ordinary 
fifo-functionality. If you want a different behaviour, you should not 
use a fifo ;-)

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Chris (Guest)

2015-10-23 21:19

Rate this post

•	▲ useful ▼ not useful

If you want to read on the PC from your FPGA, you have to reconnect the 
loopback FIFO. In this FIFO you put in the data from the PC, and if the 
PC wants to read from the FPGA, it reads what in the FIFO is.
So, the xillydemo example does exactly what you want. If you want to put 
some other data into the FIFO, you have to disconnect the 
user_w_write_8_data (and enable signal) from the FIFO, and connect 
whatever you want to transmit with it.

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Junior H. (Company: University) (junior_hpc)

2015-11-13 16:23

Rate this post

•	▲ useful ▼ not useful

Chris wrote:
> If you want to read on the PC from your FPGA, you have to
> reconnect the
> loopback FIFO. In this FIFO you put in the data from the PC, and if the
> PC wants to read from the FPGA, it reads what in the FIFO is.
> So, the xillydemo example does exactly what you want. If you want to put
> some other data into the FIFO, you have to disconnect the
> user_w_write_8_data (and enable signal) from the FIFO, and connect
> whatever you want to transmit with it.

Achim S. wrote:
> Junior H. wrote:
>> Actually, what I want to do is to take the value of user_w_write_8_data
>> and put it in user_r_read_8_data. Is there any solution for this
>> problem?
>
> You should configure your fifo_8 as "fist word fall through fifo" (maybe
> in your toolchain the parameter of the fifo-generator is called slightly
> different). Then - in case the fifo is empty prior to the write access -
> the write data appears at the fifo output immediately after writing it.
>
> If the fifo is not empty prior to the write access, then of course the
> "old" data remains at the fifo output (until you activate the read
> enable input for the required number of cycles). That's just ordinary
> fifo-functionality. If you want a different behaviour, you should not
> use a fifo ;-)

Thank you for the answers. BTW, I am newbie. I understood the idea but I 
don't have idea how to implement it. Could you give me an hint? Code 
examples would be perfect. Thanks

Report post Edit Delete Quote selected text Reply Reply with quote

Re: ImplementationOpt Design[Opt 31-37] Multi-driver net found in the design

von Junior H. (Company: University) (junior_hpc)

2015-11-19 10:03

Rate this post

•	▲ useful ▼ not useful

Chris wrote:
> If you want to read on the PC from your FPGA, you have to reconnect the
> loopback FIFO. In this FIFO you put in the data from the PC, and if the
> PC wants to read from the FPGA, it reads what in the FIFO is.
> So, the xillydemo example does exactly what you want. If you want to put
> some other data into the FIFO, you have to disconnect the
> user_w_write_8_data (and enable signal) from the FIFO, and connect
> whatever you want to transmit with it.

My idea is to put some other data on tmp signal and then put tmp into 
the FIFO. As you suggested me, I disconnected the user_w_write_8_data 
and put tmp instead of user_w_write_8_data. Now, my FIFO is like this:

fifo_8 : fifo_8x2048
    port map(
      clk        => bus_clk,
      srst       => reset_8,
      din        => tmp,
      wr_en      => user_w_write_8_wren,
      rd_en      => user_r_read_8_rden,
      dout       => user_r_read_8_data,
      full       => user_w_write_8_full,
      empty      => user_r_read_8_empty


Few questions. What do you mean by
> (and enable signal) ?
Do you mean tmp signal?

Report post Edit Delete Quote selected text Reply Reply with quote

Watch this topic |

Disable multi-page view

Please log in before posting. Registration is free and takes only a minute.

Existing account

Do you have a Google/GoogleMail account? No registration required!
Log in with Google account

No account? Register here.

Contact – Data privacy information – Advertising on EmbDev.net