4.3. Access to debug components

Both externally hosted debug agents and on-chip debug agents require access to debug components. For example, a debug monitor. Within CoreSight, these debug components are provided on a dedicated bus, the Debug APB that ensures a clear separation between system memory space and debug memory space. External tools can directly access debug components through the APB-AP within the DAP, on-chip agents must navigate the system memory bus first before being multiplexed with external debug access in the APB-MUX. Both of the memory mapped regions that is debug space within system memory and direct access to debug memory have the same offsets. However, system memory typically places this debug region at non-zero offset. This section describes:

Copyright © 2004, 2007, 2010 ARM Limited. All rights reserved.ARM DGI 0012D
Non-ConfidentialID062610