Technical data

CHALLENGE/Onyx Diagnostic Road Map 6-37
cache41 (sd_hitwb) - Secondary Hit Writeback Test
This verifies the hit writeback cache operation. It verifies that the data can be written back
from the secondary, or in the case where the primary data is more current, that the data is
written from the primary to memory. Also checked is the fact that the cache lines are not
invalidated as with the hit writeback invalidate cache operation. Instead, it checks that the
lines are set to the clean exclusive state.
Possible errors:
0105067: Initialization error, unexpected Cache write through to memory
addr = %x
expected = %x, actual = %x, XOR %x
Seconday TAG %x
0105068: SCache error during Primary Cache dirty line writeback to Scache
0105069: Data not written back from Scache to Memory on Hit Writeback Cache OP
addr = %x
expected = %x, actual = %x, XOR %x
Seconday TAG %x
010506a: Initialization error, unexpected Cache write through to memory
addr = %x
expected = %x, actual = %x, XOR %x
Seconday TAG %x
010506b: SCache state error during Hit Writeback on S-Cache dirty line
010506c: Error in Primary Cache TAG after a Hit Writeback cache Op on the SCache
addr %x
Expected cache state: Dirty Exclusive
Primary Data TAG %x
010506d: Data not written back from D-Cache to Memory on a Hit Writeback on the
S-Cache
addr = %x
expected = %x, actual = %x, XOR %x
Seconday TAG %x
Primary Data TAG %x
For errors 0105068 and 010506b, the following additional information is provided:
Error in Secondary Cache TAG State field
OR Error in Secondary Cache TAG physical tag field
OR Error in Secondary Cache TAG Virtual Address field
Address 0x%08x\nSecondary TAG Data 0x%08x
Expected Cache State: 0x%x = [STATE]
STATE is one of the decoded cache states: Invalid, Clean Exclusive, Dirty Exclusive, Shared,
and Dirty Shared.