A.7.1. Authentication asynchronous bridge signals

Table A.34 shows the authentication asynchronous bridge signals.

Table A.34. Authentication asynchronous bridge signals

NameTypeClock domainDescription
clksInputclksAuthentication clock.
clkmInputclkmAuthentication clock.
resetsnInputclksAuthentication reset.
resetmnInputclkmAuthentication reset.
dbgensInputclksInvasive debug enable.
nidensInputclksNon-invasive debug enable.
spidensInputclksSecure invasive debug enable.
spnidensInputclksSecure non-invasive debug enable.
dbgswensInputclksInvasive software debug enable.
dbgenmOutputclkmInvasive debug enable.
nidenmOutputclkmNon-invasive debug enable.
spidenmOutputclkmSecure invasive debug enable.
spnidenmOutputclkmSecure non-invasive debug enable.
dbgswenmOutputclkmInvasive software debug enable.

Cross-domain connections

The authentication asynchronous bridge can be configured as a separate master interface component and slave interface component. If you configure the bridge in this way, then you must connect the two components as Table A.35 shows.

Table A.35 shows authentication asynchronous bridge cross-domain connections.

Table A.35. Authentication asynchronous bridge cross-domain connections

Slave component signal TypeMaster component signalType
authm_req_async Outputauths_req_asyncInput
authm_ack_asyncInputauths_ack_asyncOutput
authm_fwd_data_asyncOutputauths_fwd_data_asyncInput

Copyright © 2011-2013, 2015 ARM. All rights reserved.ARM DDI 0480G
Non-ConfidentialID042315