2.3.1 Debug interface protocols - about

LISA components can expose aspects of their internal state so that they become visible and usable in the debugger. Some aspects are supported by the native LISA language, and some are supported by debug interface protocols.

Registers and other state variables
See the LISA+ resource REGISTER declaration, especially the read_function and write_function attributes.
Memories and other memory-like objects
See the LISA+ resource MEMORY declaration, especially the read_function and write_function attributes.
See CADIProtocol and CADIDisassemblerProtocol.
Instruction count
See CADIProtocol.
Setting, configuring and clearing of breakpoints
For example, code breakpoints, register breakpoints, watchpoints. See CADIProtocol.
Single stepping and instruction stepping support.
See CADIProtocol.

If displaying and editing memory and registers are sufficient, you need not implement CADIProtocol and CADIDisassemblerProtocol. The component must implement them to enable the other debug features.

CADIProtocol and CADIDisassemblerProtocol permit you to implement the features on a Component Architecture Debug Interface (CADI) interface level, where the component code takes responsibility for the implementation of these interfaces.

Non-ConfidentialPDF file icon PDF version100964_1110_00_en
Copyright © 2014–2020 Arm Limited or its affiliates. All rights reserved.