4.8. ECT authentication requirements

This section describes the functionality that must be available in the ECT to permit authentication using the signals described in the CoreSight Architecture Specification, and describes how they must be connected. If a system does not support this level of control, then simplifications of the system design can be made.

The device does not require any inputs capable of disabling it as a whole. While it is possible for the device to be invasive, by asserting interrupts, it must continue to function when DBGEN is LOW, because it might be required for non-invasive debugging, for example to communicate profiling events or a trigger condition. As a result, individual trigger inputs and outputs must be masked as required.

Copyright © 2004-2009 ARM. All rights reserved.ARM DDI 0314H