SPRUIM2H May 2020 – October 2023 AM2431 , AM2432 , AM2434 , AM6411 , AM6412 , AM6421 , AM6422 , AM6441 , AM6442
Each CBASS crossbar IP may generate up to two interrupts:
The illegal transactions triggering default_err_intr can be caused by multiple reasons:
When CBASS detects an illegal transaction, it terminates the transaction gracefully to avoid a system hang. In addition, the CBASS sends return status back to the initiator with error status. If this illegal transaction is a read transaction, the read data is returned with all zeros. If this illegal transaction is a write transaction, this write transaction is terminated and returns a write error back to initiator. The interrupt and illegal transaction logging can be found in the CBASS’s err_regs region.
For any transaction blocked by the firewall, the transaction is terminated gracefully and the initiator will receive error status for the blocked transaction. If this blocked transaction is read, the read data is returned with all zeros. If this blocked transaction is a write transaction, this write transaction is terminated and returns a write error back to the initiator. The default_exp interrupt and the blocked transaction information can be found in the glb_regs region.
CBASS Name | default_err_intr supported | default_exp Interrupt supported |
---|---|---|
CBASS0 | Yes | Yes |
MCU_CBASS0 | Yes | No |
CBASS_INFRA1 | Yes | Yes |
CBASS_FW0 | Yes | No |
CBASS_DBG0 | Yes | No |
The CBASS default_err_intr is located in the err_regs region, which includes the CBASS ERR Registers.
The CBASS default_exp_intr is located in the glb_regs region, which includes the CBASS_GLB Registers and MCU_CBASS GLB Registers.