When you check your design, the Interface Designer applies design rules to your
configuration settings. The following tables show some of the error and warning
messages you may encounter and explains how to fix them.
gpio_rule_input_mode (error)
| Message |
For input mode, input must be configured |
| To fix |
You need to configure the input parameters. |
|
|
| Message |
For input mode, input pin name must be configured |
| To fix |
Specify a name for the input pin. |
|
|
| Message |
Input pin name with square bracket does not match a bus name with
index |
| To fix |
Ensure the output enable pin name is in <BUS_NAME>[<IDX>] format.
Example: my_bus[2]. Or remove the square bracket if the pin is not part of a
bus. |
|
|
| Message |
For input mode, weak_pulldown Pull Option is not supported |
| To fix |
Disable weak pull down. |
gpio_rule_input_register (error)
| Message |
Input clock pin name has illegal character |
| To fix |
If you are using the register option, you need to specify a valid clock
pin name. |
gpio_rule_input_register (warning)
| Message |
Input clock pin name is empty |
| To fix |
If you have a GPIO block in inout mode, you get this message if you do
not specify an input pin name or if you use invalid characters in the name.
You should specify a name to use the pin as bidirectional. |
|
|
| Message |
Alternate input connection cannot be registered |
| To fix |
When you are using an alternate connection type. you cannot use the
register. Set Register Option to
none. |
gpio_rule_output_mode (error)
| Message |
For output mode, output must be configured |
| To fix |
You need to configure the output parameters. |
|
|
| Message |
For output mode without constant output, output pin name must be
configured |
| To fix |
For GPIO output blocks, you can drive them as 0 or a 1 with the
Constant Output option. In that mode, you do not
need to specify an output pin name. If you are using Constant
Output set to none (as you would for
a regular output pin), you need to specify a pin name. |
|
|
| Message |
Output pin name with square bracket does not match a bus name with
index |
| To fix |
Ensure the output enable pin name is in <BUS_NAME>[<IDX>] format.
Example: my_bus[2]. Or remove the square bracket if the pin is not part of a
bus. |
gpio_rule_inout_mode (error)
| Message |
For inout mode, both output and output enable must be
configured |
| To fix |
When using a GPIO block in inout mode, you need to set the options for
the output and output enable (as well as the input). |
|
|
| Message |
For inout mode, both output pin name and output enable pin name must be
configured |
| To fix |
Specify a valid name for the output pin and output enable
pin. |
|
|
| Message |
Output enable pin name with square bracket does not match a bus name
with index |
| To fix |
You probably used a bracket [ or ] in the pin name. Rename the pin
without brackets. |
|
|
| Message |
For input used in inout mode, weak_pulldown Pull Option is not
supported |
| To fix |
You get this message if you enable internal weak pull-down for LVDS as
GPIO in inout mode. Disable weak pull down if you use inout mode. |
gpio_rule_clkout_mode (error)
| Message |
For clkout mode, output must be configured |
| To fix |
When using a GPIO block in clkout mode, you need to set all of the
options. |
|
|
| Message |
For clkout mode, output clock pin name must be configured |
| To fix |
When using a GPIO block in clkout mode, you need to specify a valid pin
name for the ouput clock. |
gpio_rule_output_clock (error)
| Message |
Output is registered but clock pin name is invalid |
| To fix |
If you choose register or
inv_register as the Register
Option, then you also need to specify an output clock pin
name. |
|
|
| Message |
Output enable is registered but clock pin name is invalid |
| To fix |
If you are using a GPIO in inout mode, you need to specify the output
enable pin name if you set the output enable to
register. |
|
|
| Message |
Output clock pin name is not the same as output enable clock pin
name |
| To fix |
For a GPIO block in inout mode, you need to use the same pin names for
the output clock pin and the output enable clock pin. |
|
|
| Message |
Output clock inversion is not the same as output enable clock
inversion |
| To fix |
For a GPIO block in inout mode, if you invert the output clock pin you
also need to invert the output enable clock pin. Similarly, if you do not
invert the output clock pin, you cannot invert the output enable clock
pin. |
gpio_rule_unused_mode (error)
| Message |
For unused (none) mode, its state needs to be configured |
| To fix |
If you set a GPIO block mode to none, you need
to set the Unused State. The default is input with
weak pull-up. You can change this setting globally by clicking the GPIO
category in the Design Explorer and setting the Unused
State option. |
gpio_rule_input_alt_conn (error)
| Message |
Connection type <type> is not supported by <resource> |
| To fix |
If you want to use the alternate function of a GPIO block, you need to
choose a resource that supports it. For example, global clock (GCLK) is only
supported on the P pin. You can filter for resources by alternate function
in the Resource Assigner. |
|
|
| Message |
<resource> only supports normal connection type |
| To fix |
You need to choose a different connection type or assign a different
resource that supports the connection type you want to use. You can filter
for resources by alternate function in the Resource Assigner. |
gpio_rule_input_alt_conn (warning)
| Message |
Connection type <type> is not supported by <resource> |
| To fix |
For a GPIO block in inout mode, you get a warning if you do not specify
the input pin name. Specify the input pin name to use the block as
bidirectional or leave it empty to use it as open-drain. |
|
|
| Message |
<resource> only supports normal connection type |
| To fix |
The software thinks you are creating an open-drain if you leave the
input pin name empty, so this choice is valid, but it lets you know that you
made this selection in case you really want to use it as
bidirectional. |
gpio_rule_ddio_resource (error)
| Message |
Double Data I/O must be assigned to resource that supports
DDIO |
| To fix |
To use the DDIO feature, you need to pick a resource that supports it.
You can filter for resources by DDIO in the Resource Assigner
Features column. |
gpio_rule_ddio_resource (warning)
| Message |
Double Data I/O must be assigned to resource that supports
DDIO |
| To fix |
You get this error if you use a resource that does not support DDIO but
have not yet specified an input pin name. Either turn off DDIO or choose a
resource that supports it. You can filter for resources by DDIO in the
Resource Assigner Features column. |
gpio_rule_ddio_input (error)
| Message |
Input with DDIO requires register option to be set |
| To fix |
If you are using DDIO, you must set the the Register
Option to register. |
gpio_rule_ddio_input (warning)
| Message |
Input with DDIO requires register option to be set |
| To fix |
For a GPIO block in inout mode, if the Double-Data I/O
Option is other than none, you need
to choose register as the Register
Option. You get this warning when you have set some options
for the input pin but have not yet specified a pin name. |
gpio_rule_ddio_output (error)
| Message |
Output with DDIO requires register option to be set |
| To fix |
To use DDIO you must set the Double-Data I/O
Option set to something other than
none. |
gpio_rule_ddio_pin_name (error)
| Message |
Double Data I/O must have both HI and LO input pin names
defined |
| To fix |
When using DDIO, you need to specify pin names for the Pin
Name (HI) and Pin Name
(LO). |
gpio_rule_ddio_pin_name (warning)
| Message |
Double Data I/O must have both HI and LO input pin names
defined |
| To fix |
For a GPIO block in inout mode, if the Double-Data I/O
Option is other than none, you need
to specify pin names for the Pin Name (HI) and
Pin Name (LO). You get this warning when you have
set some options for the input pin but have not yet specified these pin
names. |
gpio_rule_alt_conn (warning)
| Message |
Connection type <type> must be used by valid PLL |
| To fix |
The GPIO is connected to a PLL clock input but is the resource you
assigned does not support the pll_clkin alternate function. Choose a
different resource that supports it. You can filter resources by alternate
function in the Resource Assigner. |
|
|
| Message |
Connection type <type> cannot be used on an unbonded
resource |
| To fix |
You get this error if the resource you choose is not available in the
FPGA/package combination you are using. Choose
another resource. |
|
|
| Message |
pll_clkin connection to PLL clock source not being used in
<instance> |
| To fix |
The GPIO block is set to be a PLL reference clock (pll_clkin connection
type) but the PLL is not configured to use it. Make sure that the clock you
are choosing in the PLL is associated with this GPIO's resource. |
|
|
| Message |
pll_clkin connection to PLL clock source but none of the external clock
source in PLL <instance> is selected |
| To fix |
The GPIO block is set to be a PLL reference clock (pll_clkin connection
type) but the PLL is not configured to use it. In the PLL block, choose
external or dynamic as the Clock Source and make sure that the clock you are
choosing is associated with this GPIO's resource. |
|
|
| Message |
pll_clkin connection to PLL clock source but PLL Clock source on
<instance> is set to core |
| To fix |
The GPIO block is set to be a PLL reference clock (pll_clkin connection
type) but the PLL is not configured to use it. In the PLL block, choose
external or dynamic as the Clock Source and make sure that the clock you are
choosing is associated with this GPIO's resource. |
|
|
| Message |
Connection type <type> cannot be used on an unbonded MIPI
resource |
| To fix |
The MIPI TX Instance that associated to this GPIO is unbonded. Choose
an available MIPI resource. |
|
|
| Message |
A MIPI Tx must be configured when <type> connection type driving
MIPI Tx is set |
| To fix |
You receive this message when you set the connection type in GPIO but
did not create a MIPI TX Instance that should be driving this GPIO. Check
the MIPI TX Instance associated to this GPIO (Hardware / GPIO Resource
dependent). |
gpio_rule_resource (error)
| Message |
Resource name is empty |
| To fix |
You need to choose a valid resource. |
|
|
| Message |
Resource is not a valid GPIO device instance |
| To fix |
You need to choose a valid resource. |
|
|
| Message |
Resource is not a valid LVDS GPIO device instance |
| To fix |
You need to choose a valid LVDS as GPIO resource. |
gpio_rule_resource_excluded (error)
| Message |
Resource <resource> is excluded in Package Planner. Please use
another resource |
| To fix |
The pins for the affected resource have been excluded in the Package
Planner, and cannot be assigned. Remove the excluded setting in the Package
Planner or choose another resource. |
gpio_rule_io_standard_bank (warning)
| Message |
Mismatch voltage in I/O standard assignment in bank (<voltage>) and
instance (<io_std>) |
| To fix |
You get this error when the voltage for the I/O bank does not match the
I/O standard you chose for the GPIO. Either change the I/O bank voltage or
choose a compatible I/O standard. |
gpio_rule_cfg_drive_strength (error)
| Message |
Resource <resource> does not support Drive Strength feature. It will
be ignored. |
| To fix |
Confirm the drive strengths that are allowed for the I/O standard you
want to use. |
gpio_rule_transmit_toggling (warning)
| Message |
Bank <name> has <int> lvds gpio in inout/output mode that exceed
max limit of <int> which can result in LVTTL/LVCMOS simultaneous
switching noise |
| To fix |
Avoid using lvds gpio in output/inout mode more than the specified
maximum count in the same bank. |
gpio_rule_cfg_io_standard_valid (error)
| Message |
Unsupported I/O standard |
| To fix |
The I/O standard you chose is not supported. Choose another
one. |
gpio_rule_cfg_slew_rate (error)
| Message |
Resource <name> does not support Slew Rate feature. It will be
ignored |
| To fix |
LVDS as GPIO resources do not support slew rate. Either disable that
option or choose another resource. |
gpio_rule_cck_pin (error)
| Message |
The CCK pin cannot be used in user mode when LVDS Tx is
configured |
| To fix |
You cannot use the CCK pin in user mode when you have any LVDS TX
configured in Q100F3 packages. |
gpio_rule_cfg_input_ddio (warning)
| Message |
Resource <resource> does not support Double Data I/O feature. The LO
pin name will be ignored |
| To fix |
You get this message when set the LO pin name in resource that does not
support it. Change to a resource that supports the double data I/O feature
if you want to use the feature, else disable it. |
gpio_rule_cfg_input_ddio (error)
| Message |
Resource <resource> does not support Double Data I/O feature. Please
set the Double Data I/O Option to none or choose another resource. |
| To fix |
You get this error when the GPIO resource does not support it. Change
to a resource that supports the double data I/O feature if you want to use
the feature. |
gpio_rule_cfg_output_ddio (warning)
| Message |
Resource <resource> does not support Double Data I/O feature. The LO
pin name will be ignored |
| To fix |
You get this message when set the LO pin name in resource that does not
support it. Change to a resource that supports the double data I/O feature
if you want to use the feature, else disable it. |
gpio_rule_cfg_output_ddio (error)
| Message |
Resource <resource> does not support Double Data I/O feature. Please
set the Double Data I/O Option to none or choose another resource. |
| To fix |
You get this error when the GPIO resource does not support it. Change
to a resource that supports the double data I/O feature if you want to use
the feature. |
gpio_rule_cfg_pull_option (warning)
| Message |
Resoure <name> does not support weak pull down for Pull Option
feature. It will be ignored |
| To fix |
You get this error when enable weak pull down option in a resource that
does not support it. Change to a resource that supports the weak pull-down
feature if you want to use the feature, else disable it. |
gpio_rule_cfg_schmitt_trigger (warning)
| Message |
Resource <name> does not support Schmitt Trigger feature. It will be
ignored |
| To fix |
You get this error when enable Schmitt Trigger option in a resource
that does not support it. Change to a resource that supports the Schmitt
Trigger feature if you want to use the feature, else disable it. |
gpio_rule_inst_name (error)
| Message |
GPIO name <instance name> is used |
| To fix |
You need to define a unique instance name. |
|
|
| Message |
Instance name is empty |
| To fix |
You need to choose a valid resource. |