CMSIS-Pack  Version 1.2
Delivery Mechanism for Software Packs
 All Pages
SequenceNameEnum

Predefined set of basic operations executed by the debugger.

Tokens representing a sequence name.

Token Description Parents Category
DebugPortStart Connect to the target debug port and power it up. It is executed after having acquired access to the debug port. The parent <debugport> is the default debug port for this sequence. This sequence must not contain access port and memory accesses. <debugport> Override
DebugPortStop Power down and disconnect from the target debug port. It is executed as the last step during target disconnection unless another debugger is still connected to this port. The parent <debugport> is the default debug port for this sequence. This sequence must not contain access port and memory accesses. <debugport> Override
DebugStart Initialize the target debug system. It is executed after having connected and powered up a debug connection's default debug port. <debug> Override
DebugStop Uninitialize the target debug system. It is executed as the last step during shutting down a debug connection, but before powering down and disconnecting any debug port which is no longer required for a concurrent debug connection. <debug> Override
TraceStart Device specific settings to be applied when configuring the target for trace capture. It is executed before enabling the target's standard CoreSight trace components. The type of trace to apply this sequence for is determined by the parent element of the sequence. <serialwire>, <traceport>, <tracebuffer> Extension
TraceStop Device specific settings to be applied when disabling trace capture. It is executed after disabling the target's standard CoreSight trace components. The type of trace to apply this sequence for is determined by the parent element of the sequence. <serialwire>, <traceport>, <tracebuffer> Extension
ResetSystem Executes a system-wide reset. <debug> Override
ResetProcessor Executes a processor reset. <debug> Override
ResetHardware Resets the device via its reset line. <debug> Override
ResetHardwareHold Asserts the device's reset line and holds it. This sequence is executed when a debugger needs to perform functionality while the target is held under reset. <debug> Override
ResetHardwareRelease Deasserts the device's reset line. This sequence is executed when a debugger releases the target from reset after being held there by a ResetHardwareHold sequence. <debug> Override
ResetSetCatch Configures where a processor is caught if a debugger requests it to stop after reset. It is for example used to stop it after having executed its bootloader. A debugger calls this sequence before performing a reset. If it is implemented, it is required to implement a ResetClearCatch sequence to free any used debug resources. <debug> Override
ResetClearCatch Cleans up settings done in a ResetSetCatch sequence. This sequence is only executed if a debugger requests the target to stop after reset. It is executed after the core has stopped after reset. <debug> Override
RecoveryConfigure Configure custom logic of a device to recover gracefully from a lost connection, e.g. after waking up from a low power mode. <debug> Override
RecoveryAcknowledge Acknowledge recovery from a lost connection, e.g. after waking up from a low power mode. Such functionality needs to be supported by the targeted device. <debug> Override
CodeAreaRemap Remaps an application code memory area to the reset vector. It is used for devices which map the code memory area to the reset vector only after having executed for example a bootloader. If stopping such targets after reset and downloading/verifying application code against its binary file, the real memory contents differs from the content of the binary. The sequence is executed before a debugger verifies the application code download. <debug> Extension