3.3.2. Target interface setup

After the CADI interface for a specific target component is obtained, there are some typical steps that must be performed to prepare the interface for the actual communication between caller and target:

The first method of the CADI interface that must be called after establishing a connection is CADIXfaceGetFeatures(). It returns information on the features supported by the target. These include, for example, the supported types of breakpoints, the number of register groups and memory spaces, and the register ID of the program counter. This information can be used by subsequent CADI method calls. See CADI target characteristics.

Before starting the real interaction with the connected target, the caller must register its CADICallbackObj objects (typically there is only one) to the corresponding CADI interface. The CADIXfaceAddCallback() method in the interface must therefore be called. In addition to a pointer to the callback object, an array of chars is forwarded that contains the enable vector that describes which of the callbacks in the object are permitted to be used by the target.

The enable vector that is forwarded in combination with a callback object is only associated with that specific object. You can connect different callback objects that implement different subsets of callbacks. It is also possible to re-configure a registered object by executing CADIXfaceAddCallback() using the same pointer in combination with a new enable vector.

Copyright © 2008-2010 ARM Limited. All rights reserved.ARM DUI 0444F