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.

Debug Configuration Flash Setting Code Security Passwords sufficient to unlock password protected processor?

Are the Debug Configuration Flash Setting Code Security Passwords sufficient to unlock a password protected processor?  I ask because I see that there is a Unlock_CSM() method in the .gel file for my 28335 processor.  I'm using CCS 6.1.1 and the Blackhawk USB200 JTAG Emulator.

  • Hi, not sure I understood the question but yes, Unlock_CSM() method in gel file should be sufficient to unlock the device as long as this has correct passwords.

    Regards,

    Vivek Singh
  • My question wasn't clearly worded. What is the purpose of the Debug Configuration Flash Setting Code Security Passwords? If I set the Debug Configuration Flash Setting Code Security Passwords to my passwords, will I be able to connect to my protected processor without changing the .gel file? It seems like the passwords are in two places, and I don't understand why.
    Best,
    Scott
  • Hi Scott,

    What is the purpose of the Debug Configuration Flash Setting Code Security Passwords?

    Where is this setting? If it's part of CCS flash plug-in then it's used for unlocking the device during flash operations only.

      If I set the Debug Configuration Flash Setting Code Security Passwords to my passwords, will I be able to connect to my protected processor without changing the .gel file?

    Unlocking the device using either of these method only happens once you are connected to device via CCS (JTAG). So this does not help in connecting to secure device. You need to use "Branch to Check boot mode" or "Wait-In-Reset" option. Following is what we have in TRM of this device (section 4.1 Functional Description)

    .

    Regards,

    Vivek Singh