A.8.37. CADI::CADIExecSingleStep()

This function returns immediately and a separate notification informs the debugger that the execution state has changed. Typically this call results in the modeChange() callback (if enabled) for CADI_EXECMODE_Run followed by CADI_EXECMODE_Stop.

virtual CADIReturn_t CADI::CADIExecSingleStep(uint32_t instructionCount,
                                              int8_t stepCycle,
                                              int8_t stepOver) =0;

where:

instructionCount

is the number of instructions to be executed.

Some targets can not step a specific number of instructions safely (into a delay slot, for example). In this case, the target can step additional instructions to enable it to stop at a safe place.

stepCycle

specifies (for targets that have exposed multiple pipe stages) whether the step merely clocks the device (stepCycle == yes) or flushes the pipe (stepCycle == no).

For other kinds of targets, this argument is ignored (stepCycle = no is assumed).

stepOver

enables the target to handle stepping over a call.

It is especially useful for an emulator with no available breakpoints. In this case the target must step until the call returns or a breakpoint is hit.

Note

Because this call returns immediately, the return value indicates whether the target believes that it can perform the operation and not whether the operation was completed successfully.

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