The following are the typical situations under which unsecuring can be required:
- The user develops some main IP, and then
outsources peripheral functions to a subcontractor who must be able to run the
user code during debug and can halt while the main IP code is running. If ECSL
is not unlocked, then Code Composer Studio™ IDE connections get disconnected,
which can be inconvenient for the user. Note that unlocking ECSL does not enable
access to the secure code but only avoids disconnection of Code Composer Studio™
IDE (JTAG).