Sorry, your browser is not supported. We recommend upgrading your browser. We have done our best to make all the documentation and resources available on old versions of Internet Explorer, but vector image support and the layout may not be optimal. Technical documentation is available as a PDF Download.

JavaScript seems to be disabled in your browser.
You must have JavaScript enabled in your browser to utilize the functionality of this website.

You copied the Doc URL to your clipboard.

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

Question

Which fault is caused by accessing a locked CoreSight register without unlocking it?

Answer

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).

Related information

N/A

Was this page helpful? Yes No