ipbus(_ported)_dpram slave: Critical warning in Vivado 2018.3
Closed this issue · 2 comments
tswilliams commented
Vivado 2018.3 prints the following critical warning during synthesis of designs using the ipbus_dpram and ipbus_ported_dpram slaves with DATA_WIDTH = 32 (the default value):
CRITICAL WARNING: [Synth 8-507] null range (-1 downto 0) not supported [/data/tsw/firmware/ipbus-dev-dpram2018.3bug-20180503/src/ipbus-firmware/components/ipbus_slaves/firmware/hdl/ipbus_ported_dpram.vhd:108]
CRITICAL WARNING: [Synth 8-507] null range (-1 downto 0) not supported [/data/tsw/firmware/ipbus-dev-dpram2018.3bug-20180503/src/ipbus-firmware/components/ipbus_slaves/firmware/hdl/ipbus_ported_dpram.vhd:108]
CRITICAL WARNING: [Synth 8-507] null range (-1 downto 0) not supported [/data/tsw/firmware/ipbus-dev-dpram2018.3bug-20180503/src/ipbus-firmware/components/ipbus_slaves/firmware/hdl/ipbus_dpram.vhd:76]
CRITICAL WARNING: [Synth 8-507] null range (-1 downto 0) not supported [/data/tsw/firmware/ipbus-dev-dpram2018.3bug-20180503/src/ipbus-firmware/components/ipbus_slaves/firmware/hdl/ipbus_dpram.vhd:76]
(Problem reported by Marian Krivda and Luis Moreno.)
tswilliams commented
N.B. Although Vivado 2018.3 reports this as a critical warning, the 'null range' aggregate assignment does not adversely affect the implementation of the dual-port RAM slaves.
tswilliams commented
All done. Closing.