| |||
| Home > Customizing a Debug Interface configuration > Customizing a RealView ICE Debug Interface configuration > Considerations when customizing RealView ICE Debug Interface configurations | |||
Be aware of the following when configuring devices:
Autoconfiguration does have side effects and might be intrusive. Where this is not acceptable, you must manually add the devices to the scan chain.
Autoconfiguring a CoreSight system is a two-stage process:
Autoconfigure the scan chain to detect the CoreSight DAP.
If the CoreSight DAP contains a ROM table, then read the ROM table of the to determine the devices that are connected to it.
If the CoreSight DAP does not contain a ROM table, then manually add the devices that are connected to it. As a minimum, you have only to add the target processor if you do not want to capture trace information.
If you want to view the CoreSight topology in RealView Debugger, then you must assign CoreSight Associations to your Debug Interface configuration.
Search for "association file", including
the quotes, in the ARM Information Center for more details about
CoreSight Association files.
Autoconfiguration does not work for development platforms containing non-ARM targets. In this case, you must manually add all devices to the scan chain.
Where a target runs at much lower CPU clock speed than an ARM architecture-based processor, the JTAG clock speed for a multiprocessor platform might be lower than a platform containing only ARM architecture-based processors.
In general, the JTAG clock speed over the 20 pin JTAG connection can be set to no more than one eighth of the slowest CPU on the JTAG scan chain in the multiprocessor platform. If your platform supports RTCK (return clock), then you might be able to take advantage of Adaptive Clocking.
When setting up a custom RealView ICE connection you might also want to set some of the RealView Debugger settings. For example, if you are using Running System Debug (RSD) you also have to disable vector catch and semihosting.
Table 2.2 lists the recommended settings to use for an ARM Integrator™ development board.
Table 2.2. Recommended settings for an ARM Integrator development board
| Setting | Value |
|---|---|
| Reset Type | nSRST+nTRST |
| Perform TAP Reset on first connect | Selected |
| Reset On Disconnect (Default) | Deselected |
| nSRST Hold Time (ms) | 100 |
| nSRST Post Reset Delay (ms) | 1000 |
| nTRST Hold Time (ms) | 100 |
| nTRST Post Reset Delay (ms) | 100 |
| TAP reset via State Transitions | Selected |
| Target nSRST + nTRST Linked | Deselected |
| Post Reset State (device-specific setting) | STOPPED |
the following in the RealView Debugger RTOS Guide:
RealView ICE and RealView Trace User Guide.
| Copyright © 2002-2009 ARM Limited. All rights reserved. | ARM DUI 0182K |
| Non-Confidential | |
 PDF version | |
| Home > Customizing a Debug Interface configuration > Customizing a RealView ICE Debug Interface configuration > Considerations when customizing RealView ICE Debug Interface configurations |