IDT Error Management
Revision 1.5
Integrated Device Technology, Inc.
CPS-16/12/8 User Manual
5 - 5
July 10, 2012
5.1.1.4 Configuration Errors
The device supports the ability to detect the following configuration errors. If configuration error reporting is
enabled each of the errors defined below will sent to the Error Log when detected.
Table 5.5 Configuration Errors and Codes -- Group Number 0x5
Error
Code
Description
Multicast mask config
error
0x50
Triggered whenever a direct write to a route table is attempted with
an invalid mask number. A 'NO_ROUTE' will be written into the
route table instead.
Triggered if the user attempts to program the domain table with a
multicast mask number.
Triggered whenever the mcast_msk_port_csr is written to with an
invalid mask.
Triggered when the mcast_assoc_sel_csr is written to with an
invalid mask number.
Triggered if a write-to-verify command in the mcast_assoc_op_csr
results in an access to the domain table. This is because the
domain table can only store ports and no-routes (not multicast
masks).
Reads of invalid values also trigger this error.
Port config error
0x53
Triggered when a direct write to a route table is attempted with an
invalid PORT number. A 'NO_ROUTE' will be written into the
route table instead. This is also triggered whenever the
mcast_msk_port_csr is written to that contains an invalid egress
port number.
This error is also triggered when an attempt is made to configure
the part to use an invalid output trace port.
Force Local config
error
0x54
Triggered whenever a 'FORCE_LOCAL' value is used in an
attempt to be program the device route table. A 'NO_ROUTE' will
be written into the device route table instead.
Route Table conf error
0x55
Triggered whenever a route table (or pointer table) is read and its
value reference results in an illegal port value. A value of 8'ff will
be returned to the user to indicate a failure occurred.
Multicast translation
config error
0x56
Triggered if the user accesses a multicast register and a bit is high
that does not correspond to a valid port on the device. The write
will still occur, and any other valid ports will be changed.
Triggered if the above scenario occurs during a write of the
CPSC_INPUT_PORTS and CPSC_OUTPUT_PORTS registers
as well.
