We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
In self-hosted debug scenarios, is it feasible to configure the cross-trigger pathway (via CTI/CTM) to halt multiple cores simultaneously? Our experimental results on ARMv9 show that configuring CTI triggers can indeed force cores to stop execution. However, we are uncertain whether this state qualifies as a "halt" (i.e., cores entering debug state), because: According to protocol specifications, self-hosted debug operates through debug exceptions (e.g., breakpoints triggering software handlers), without requiring cores to enter a hardware-controlled debug state.
HiMy name is Stephen and I work at Arm.Yes, CTI/CTM can be used to halt multiple cores simultaneously. Halting debug is intended to be handled by an external debugger (e.g. Arm DS Debugger & DSTREAM-ST) because a halted core cannot restart itself without some outside intervention.By contrast, self-hosted debug is usually implemented through the generation and handling of debug exceptions, and does not normally require entering the "halt" state. See:
https://developer.arm.com/documentation/102120/0101/AArch64-debug
If you need more information, I suggest you "Open a Support Case" using the link at the bottom of this web page.Hope this helpsStephen