When using the UniFlash GUI, it is not possible to resume execution after program after it is flashed. This is despite the "Run Target After Program Load/Flash Operation" checkbox is enabled and "remain connected after operations" checkbox is disabled. While the UniFlash GUI remains up, the XDS110 indicator light indicates an open XDS110 connection despite the status indicator indicating UniFlash is disconnected from the target. When the UniFlash GUI is closed, then XDS110 indicator light changes to show that the connection is closed and the target will resume execution as desired.

CCS IDE does not have this issue. After flashing the program, the target can be run. If the target is not executed but the target is disconnected, the XDS110 connection is closed and the target will resume execution independently. It is not necessary to terminate the debug session.

I assume it is intended desire to have UniFlash operate differently. However, the "Run Target After Program Load/Flash Operation" option does not seem to be taking effect.

The issue appears related to this older thread: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/821450/ccs-cc1352p-uniflash-ccs-flashing-why-doesn-t-the-device-reset-and-run-directly-after

Likely the "board reset (free run)" option works because it closes the XDS110 connection.

Issue was reproduced with a CC2340R5 (same as the customer who reported the issue).