SPRUIU1C July 2020 – February 2024 DRA821U , DRA821U-Q1
When a transaction is flushed (because it has timed out or the gasket is in flush mode), the gasket proxies back transactions to the initiator. When the transaction is completely flushed, it is popped from the relevant scoreboard. If, after a transaction has started (or completed) flushing, a response comes back for that transaction, it triggers an Unexpected Response.
If a transaction has been flushed, the ID is re-allocated to a new transaction, then a response comes for the old, timed-out transaction, it can cause faults in the system. For this reason, the timeout value should be sufficiently large that, if reached, it is expected that a response for the original transaction never returns.
For writes, the gasket sends a single write status transaction for all of the remaining bytes in the transaction. The status will have sstatus set to 0x3 (Timeout Error).
For reads, the gasket sends however many read data phases are required to fulfill the remaining bytes of the command. The data will be all 0 and the rstatus set to 0x3 (Timeout Error).