SPRUJ28E November 2021 – September 2024 AM68 , AM68A , TDA4AL-Q1 , TDA4VE-Q1 , TDA4VL-Q1
The RAT does not provide any protection against transactions that cross region boundaries, that is, start inside of a region and end outside of it, or start outside of a region and end inside of it. If a boundary crossing transaction is detected, then the transaction will be flagged as an error (exception) and a log will be made. The log consists of a series of MMRs that captures the details of the transaction, including the input address that caused the error. The RAT module can capture one error before it is cleared by software. Here is the list of exception logging registers:
The log also produces an interrupt. To clear the log, software must either read the final error logging register, or manually clear the interrupt status bit. This will clear the error status, and not the actual log MMRs, but it does allow the next error to be captured into the log MMRs. If the status is not cleared and additional errors are detected, they are not logged.
The error reports use the value from a dedicated bootstrap (see Section 6.3.2.2.3) as the value for the R5FSS_RAT_EXCEPTION_LOGGING_HEADER0[23-8] SRC_ID field.