2.5. Disconnecting from a target

There are several ways to disconnect when working with a target.
Choosing the most appropriate method depends on:

the number of Code windows

which window has the focus when the disconnection
option is used

the state of the connected processor, and process
if running

the desired state of the processor, or process,
following disconnection.

Code windows are not closed on disconnecting but their contents
might change depending on the data they contain. For example any
loaded images are unloaded and so associated source files close
and entries displayed in a Register, Memory, or Process Control
pane are cleared whereas entries in the Watch pane remain unchanged.
This behavior depends on the update options you set for the window
and the disconnect state of the target processor.

If you are working with projects, any open projects do not
close if you disconnect from a debug target. Even where a project
is bound to the connection, it does not close if you disconnect. However,
it is unbound and its details are no longer shown in the Process Control
pane.