SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
Error logging is implemented only at slave NIUs. Because the interconnect does not support master NIU error logging, an erroneous packet must be created and sent to one of the slave NIUs. The slave NIU that receives an erroneous packet is predictable but can change per master (see Table 14-23).
Master | Connectivity and Holes Errors Logged Into Slave NIUs |
---|---|
All initiators except DSP1_CFG and DSP2_CFG | GPMC_TARG |
DSP1_CFG | EVE1_TARG |
DSP2_CFG |
The slave NIU can be configured to report standard errors (errors generated within the interconnect):
By default, all slave NIUs are configured with standard and custom error levels set to FAULT. The errors are reported on the two flag muxes (see Figure 14-7), depending on the access type, application or debug. For more information, see Section 14.2.3.8.3, Flag Mux Error Logging.
The slave NIU power-disconnect component also has error logging enabled, because in this case the slave NIU is in a clock domain that is switched off and therefore cannot catch the error. By nature, this component can generate only standard errors. By default, it is configured with the error level set to FAULT.
Wake up on demand: If an error packet reaches a slave NIU that is set with MDiscBehave = 1 (wake up on demand), then the active signal is asserted and L3 processes the error generation when the slave is awake. Although this is inefficient, it simplifies NIU implementation and should not be a problem because errors are supposed to occur only during software debug.