Fault caused by accessing a locked CoreSight register without unlocking it
Article ID: 103490206
Published date: 22 Nov 2017
Last updated: -
Applies to: CoreSight Debug and Trace
Which fault is caused by accessing a locked CoreSight register without unlocking it?
The CoreSight 'lock' function is described in CoreSight v1.0 Architecture Spec, section 3.6.4 as:
"Write access to the component is blocked. All writes to control registers are ignored. Reads are permitted."
Therefore reads will succeed and writes will fail silently without any error response (which means without any fault).