UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 20000

LogiCORE SPI-4.2 (POS-PHY L4) - NGDBuild: "WARNING" and "INFO" messages appear when NGDBuild is run with SPI-4.2 Core

Description

When I implement an SPI-4.2 design through NGDBuild, several "WARNING" and "INFO" messages appear.

Solution

INFO messages

One or more of the following messages might appear:

"INFO:NgdBuild:738 - A case sensitive search for the INST, PAD, or NET element referred to by a constraint entry in 'spi4_core1_top.ucf' that accompanies this design has failed, while a case insensitive search is in progress. The result of the case insensitive search will be used, but messages will accompany each and every use of a case insensitive result. Constraints are case sensitive with respect to user-specified identifiers, which includes names of logic elements in a design."

"INFO:NgdBuild:740 - Line 217 in 'spi4_core1_top.ucf': Found case insensitive match for NET name 'srcclk_fiforeset'. NET is "spi4_core1_pl4_src_top_master_addr0/U0/SrcCLK_FifoReset'."

"INFO:NgdBuild:740 - Line 218 in 'spi4_core1_top.ucf': Found case insensitive match for NET name 'srcffclk_fiforeset'. NET is 'spi4_core1_pl4_src_top_master_addr0/U0/SrcFFCLK_FifoReset'."

"INFO:XdmHelpers:851 - TNM "TSClk", used in period specification "TS_TSClk", was traced into DCM_ADV instance "spi4_core1_pl4_src_top_master_addr0/U0/clk0/tsd". The following new TNM groups and period specifications were generated at the DCM_ADV output(s):

CLK0: TS_spi4_core1_pl4_src_top_master_addr0_U0_clk0_TSClk_dcmo=PERIOD spi4_core1_pl4_src_top_master_addr0_U0_clk0_TSClk_dcmo TS_TSClk*1.000000 HIGH 50.000000%"

"INFO:XdmHelpers:851 - TNM "RDClk_P", used in period specification "TS_RDClk_P", was traced into DCM_ADV instance "spi4_core1_pl4_snk_top0/U0/clk0/rdclk_dcm0". The following new TNM groups and period specifications were generated at the DCM_ADV output(s):

CLK0: TS_spi4_core1_pl4_snk_top0_U0_clk0_SnkClk_dcmo=PERIOD spi4_core1_pl4_snk_top0_U0_clk0_SnkClk_dcmo TS_RDClk_P/2.000000 HIGH 50.000000% INPUT_JITTER 300.000000 pS"

"INFO:XdmHelpers:851 - TNM "SysClk_P", used in period specification "TS_SysClk_P", was traced into DCM_ADV instance "spi4_core1_pl4_src_top_master_addr0/U0/clk0/tdd". The following new TNM groups and period specifications were generated at the DCM_ADV output(s):

CLK0: TS_spi4_core1_pl4_src_top_master_addr0_U0_clk0_SrcClk_dcmo=PERIOD spi4_core1_pl4_src_top_master_addr0_U0_clk0_SrcClk_dcmo TS_SysClk_P/2.000000 HIGH 50.000000% INPUT_JITTER 200.000000 pS"

These INFO messages are informational messages that explain what the tool (NGDBuild) has found and briefly explain how the tool will handle these cases. They are not errors or warnings, and they can be safely ignored.

WARNING messages that can be ignored

One or more messages with a WARNING applied to different signals might appear:

WARNING:NgdBuild:440 - FF primitive 'pl4_implv4_128b_stat19479_9_pl4_snk_top0/U0/clkdomain0/srts/output_ff' has unconnected output pin.

WARNING:NgdBuild:440 - FF primitive 'pl4_implv4_128b_stat19479_9_pl4_src_top0/U0/sync0/ssses/output_ff' has unconnected output pin.

WARNING:NgdBuild:440 - FF primitive 'core1_pl4_src_top_master_addr0/U0/core0/data0/u10/dip4_val/FF5' has an unconnected output pin.

WARNING:NgdBuild:454 - logical net 'core1_pl4_snk_top0/U0/core0/queue0/rrdadrx/FIFO_addr_gray_ffs(0)' has no load.

WARNING:NgdBuild:454 - logical net 'core1_pl4_snk_top0/rdclk180_gp' has no load.

WARNING:NgdBuild:454 - logical net 'core1_pl4_snk_top0/snkcaldataout<7>' has no load.

The above warnings regarding unconnected output pins and no load can be safely ignored. These signals are not being used and will be trimmed out appropriately during the mapping phase of the implementation tool.

WARNING messages that CANNOT be ignored:

Sink Core: (IOSTANDARD warnings)

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "SnkIdelayRefClk_ibufg0".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "RStat_ibuf0".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "RStat_ibuf1".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "RSClk_ibuf0".

Source Core: (IOSTANDARD warnings)

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "pl4_src_clk0/sysclk_ibufg0".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "TStat_ibuf0".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "TStat_ibuf1".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "pl4_src_clk0/TSClk_ibuf0".

Example design: (IOSTANDARD warnings)

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "CalClk_ibufg0".

WARNING:NgdBuild:488 - Attribute value "default" is not an accepted value for attribute "IOSTANDARD" on "LoopbackClk_ibufg0".

In the v7.0 of the SPI-4.2 Core, the I/O Standards are not defined in either the netlists or in the UCF; therefore, all differential signals default to LVDS 2.5 Volt without the internal device termination. All single-ended signals will default to LVCMOS.

The above "IOSTANDARD" attribute warnings must be addressed by specifying the proper I/O standard of the reported input and output buffers. To define the I/O standard for these buffers, add new constraints to the UCF file.

For example, to define the I/O standard for the RSClk output buffer, add the following constraint to the UCF:

INST "RSClk_ibuf0" IOSTANDARD = LVTTL;

In Virtex-4, the ISE tool defaults all single-ended nondeclared I/O to LVCMOS25, which is not supported for the SPI-4.2 Core. Please refer to (Xilinx Answer 20017) for a list of I/O standards supported by the SPI-4.2 Core and information on defining the I/O standards in the UCF.

In the next SPI-4.2 Core release, the I/O standards will be pre-defined.

AR# 20000
Date Created 09/03/2007
Last Updated 12/15/2012
Status Active
Type General Article