CRITICAL WARNINGS from the AWS SHELL static partition

0

Hi,
We are seeing some critical warnings from the AWS SHELL region. So far I can see, we are not doing anything to cause them. Can you check and advise whether these are expected in general or something we are doing that is causing them. Also, how to fix them.

CRITICAL WARNING: \[Board 49-67] The board_part definition was not found for xilinx.com:f1_cl:part0:1.0. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO0_I_REG conflicts with its current constrained placement (SLICE_X149Y278). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO1_I_REG conflicts with its current constrained placement (SLICE_X149Y278). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO2_I_REG conflicts with its current constrained placement (SLICE_X151Y293). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO3_I_REG conflicts with its current constrained placement (SLICE_X162Y294). The conflicting constraint will be removed.
CRITICAL WARNING: \[Place 30-73] Invalid constraint on register 'WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO0_I_REG'. It has the property IOB=TRUE, but it is not driving or driven by any IO element.
CRITICAL WARNING: \[Place 30-73]\ Invalid constraint on register 'WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO1_I_REG'. It has the property IOB=TRUE, but it is not driving or driven by any IO element.
CRITICAL WARNING: \[Place 30-73] Invalid constraint on register 'WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO2_I_REG'. It has the property IOB=TRUE, but it is not driving or driven by any IO element.
CRITICAL WARNING: \[Place 30-73] Invalid constraint on register 'WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO3_I_REG'. It has the property IOB=TRUE, but it is not driving or driven by any IO element.
CRITICAL WARNING: \[Place 30-73] Invalid constraint on register 'WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/QSPI_LEGACY_MD_GEN.QSPI_CORE_INTERFACE_I/LOGIC_FOR_MD_12_GEN.SPI_MODE_CONTROL_LOGIC_I/RATIO_NOT_EQUAL_4_GENERATE.SCK_O_NQ_4_NO_STARTUP_USED.SCK_O_NE_4_FDRE_INST'. It has the property IOB=TRUE, but it is not driving or driven by any IO element.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/QSPI_LEGACY_MD_GEN.QSPI_CORE_INTERFACE_I/LOGIC_FOR_MD_12_GEN.SPI_MODE_CONTROL_LOGIC_I/RATIO_NOT_EQUAL_4_GENERATE.SCK_O_NQ_4_NO_STARTUP_USED.SCK_O_NE_4_FDRE_INST conflicts with its current constrained placement (SLICE_X160Y216). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_ila_cap_ctrl/u_cap_addrgen/i_intcap.icap_addr_reg[1]. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_ila_cap_ctrl/u_cap_addrgen/i_intcap.icap_addr_reg[4]. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_ila_cap_ctrl/u_cap_addrgen/i_intcap.icap_addr_reg[1]. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_ila_cap_ctrl/u_cap_addrgen/i_intcap.icap_addr_reg[4]. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_trig/U_TM/N_DDR_MODE.G_NMU[4].U_M/allx_typeA_match_detection.ltlib_v1_0_0_allx_typeA_inst/DUT/I_WHOLE_SLICE.G_SLICE_IDX[7].U_ALL_SRL_SLICE/I_IS_TERMINATION_SLICE_W_OUTPUT_REG.DOUT_O_reg. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-850] Failed to place register with ASYNC_REG property shape that starts with register WRAPPER_INST/SH/SH/MGT_TOP/SH_ILA_0/inst/ila_core_inst/u_trig/U_TM/N_DDR_MODE.G_NMU[4].U_M/allx_typeA_match_detection.ltlib_v1_0_0_allx_typeA_inst/DUT/I_WHOLE_SLICE.G_SLICE_IDX[7].U_ALL_SRL_SLICE/I_IS_TERMINATION_SLICE_W_OUTPUT_REG.DOUT_O_reg. This is likely caused by merging with other shapes due to some register in the chain may belong to other shapes. Reason: Routing contention at pips pin element OUTMUXA
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/QSPI_LEGACY_MD_GEN.QSPI_CORE_INTERFACE_I/LOGIC_FOR_MD_12_GEN.SPI_MODE_CONTROL_LOGIC_I/RATIO_NOT_EQUAL_4_GENERATE.SCK_O_NQ_4_NO_STARTUP_USED.SCK_O_NE_4_FDRE_INST conflicts with its current constrained placement (SLICE_X160Y216). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO0_I_REG conflicts with its current constrained placement (SLICE_X149Y278). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO1_I_REG conflicts with its current constrained placement (SLICE_X149Y278). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO2_I_REG conflicts with its current constrained placement (SLICE_X151Y293). The conflicting constraint will be removed.
CRITICAL WARNING: \[Shape Builder 18-539] Setting IOB or IOB_TRI_REG property to TRUE for instance WRAPPER_INST/SH/SH/AXI_QUAD_SPI/U0/NO_DUAL_QUAD_MODE.QSPI_NORMAL/IO3_I_REG conflicts with its current constrained placement (SLICE_X162Y294). The conflicting constraint will be removed.

Edited by: fpgamagic on Jan 18, 2019 11:47 AM

Edited by: fpgamagic on Jan 18, 2019 11:48 AM

Edited by: fpgamagic on Jan 18, 2019 11:51 AM

asked 5 years ago241 views
1 Answer
0

Hi fpgamagic,

It is safe to waive the CRITICAL WARNINGS from the SHELL region that you have mentioned in the post.

There have beed couple of similar posts related to CRITICAL WARNINGS. You can check them here

https://forums.aws.amazon.com/thread.jspa?messageID=828801&#828801
https://forums.aws.amazon.com/thread.jspa?messageID=867232&#867232

Let us know if you face some issues.

Thanks,
Sunil.

AWS
answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions