You copied the Doc URL to your clipboard.

Why are CoreSight debuggers unable to discover the memory-mapped Activity Monitor Unit (AMU) which does not have a CoreSight ROM table entry?

Article ID: 212206171

Published date: 06 Jun 2018

Last updated: -

Applies to: Cortex-A

Problem/Question

Why are CoreSight debuggers unable to discover the memory-mapped Activity Monitor Unit (AMU) which does not have a CoreSight ROM table entry?

Scenario

This issue might be noticed during execution of the CoreSight system discovery algorithm. This could be executed by production debug tools (like Arm DS-5/D-STREAM) or by CoreSight integration test deliverables which contain discovery tests for pre-silicon verification.

Answer

The Activity Monitor Unit (AMU) is not a debug feature. Therefore, is not expected to be discoverable by CoreSight debug agents. This means processors which include an AMU do not have any CoreSight ROM entries corresponding to AMU components.

For DSU based processors which include AMU, such as Cortex-A75, AMU appears in the Debug APB memory map merely because AMU needs to be accessible by external agents, and DSU has no other memory-mapped slave port which could provide such access.

Workaround

N/A

Example

N/A

Related Information

N/A

Was this page helpful? Yes No