This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello.
After performing the "Permanently Disabling Debug" once in page 540 in datasheet, can we unlock the device using the way described 4.3.4.3 in datasheet?
If yes, are there any way to do unlock described 4.3.4.3 in datasheet by XDS debugger?
Or, are there any tools which can execute sequence described 4.3.4.3 in datasheet?
Regards,
U-SK
Hi Charles,
Thank you for your reply.
These solutions you mentioned are perform chapter 4.3.4.3 in datasheet, right?
And let me ask one more question.
If execute only protection described chapter 8.2.3.3 is performed at once, are there any way to unlock the device?
Regards,
U-SK
Hi,
U-SK said:These solutions you mentioned are perform chapter 4.3.4.3 in datasheet, right?
Yes, your understanding is correct.
U-SK said:If execute only protection described chapter 8.2.3.3 is performed at once, are there any way to unlock the device?
Once it is in execute-only protection, you will not be able view the content of the flash memory. It is different than permanently disabling JTAG access. Although the flash memory is not readable, the debugger can still connect to the device. You don't need to 'unlock' the device in execute-only mode. You simply just erase the flash or load a new program.
Hi U-SK,
I'm sorry to give you the wrong answer. You are right that in execute-only mode you cannot erase. You will need to 'unlock' the device using either the LM flash programmer or Uniflash.
Hi Charles,
Thank you for your reply.
In case Execution only mode, Uniflash and LM Flasher can unlock with same way as the solution in the below post?
https://e2e.ti.com/support/microcontrollers/other/f/908/p/922318/3407328#3407328
Regards,
U-SK
Hi U-SK,
That is correct. The unlock is a mass-erase operation. If you have data in the EEprom then it will get erased too. Same for the non-volatile registers such as BOOTCFG, USER_REG1 and USER_REG2.