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.

CCS/TMS320F28062: the chip is locked when program

Part Number: TMS320F28062
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Recently, we have often found that the chip is locked, and the power supply has been very noticeable.
Locking has occurred with both CCS 5.3 and 6.2.
The memory is almost full,
I am worried that the password area will be written when it is compiled.
Whether the password area in the compiled MAP file will be occupied.
Are there any other possible reasons for this question? How to find it? Thank you!

Eric

  • I regret I don’t understand your questions well. 

    Recently, we have often found that the chip is locked, and the power supply has been very noticeable.

    What do you mean by " noticeable "? Are you saying it is noisy?

    The memory is almost full,

    Which memory? Flash? What do you mean by "almost full"?

    I am worried that the password area will be written when it is compiled.

    If a password section has been defined in the Linker command file, it cannot be accidentally overwritten. See linker command files in C2000ware for example.

    Whether the password area in the compiled MAP file will be occupied.

    Question not clear. Please clarify.

    Are there any other possible reasons for this question? How to find it? Thank you!

    What is the past history of these devices? Were they ever programmed and successfully working? 

    Or did you face an issue while programming them for the first time? 

    Does your COFF file have passwords? 

    If your devices are locked and you are unable to connect/unlock them via CCS, I am afraid your only choice is to replace the parts. Devices may become inadvertently locked if the Erase/Program operation is disturbed due to a brown-out/black-out condition. This could also happen if the devices are current-starved during erase/program operation. See https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/826343

  • We have added one of the following files:

    .sect "CsmPwlFile"
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
      .word 0xFFFF
     
      .sect ".flashaflag"
      .word 0xAAAA
      .end
    However, the password protection area is not cleared. Is it because the program takes up a lot of space, and it is locked in the password protection area?
     
    The following is the code to clear the password protected area:
    .sect "csm_rsvd"
      .loop (3F7FF5h - 3F7F80h + 1)
      .int 0x0000
      .endloop
     
       Do not know if this can avoid accidental coverage problems?

    There is always a part of the definition of the password in the CMD file.
        CSM_RSVD : origin = 0x3F7F80, length = 0x000076
        BEGIN : origin = 0x3F7FF6, length = 0x000002
        CSM_PWL : origin = 0x3F7FF8, length = 0x000008
     
    Our previous projects were also used like this, and there was no frequent lock-up. Do you think the password protected area has not been cleared? Is this a possible reason?

    Thank you

    Eric

  • If the password section has been correctly defined in the linker command file and the "CsmPwlFile" section has all 0xFFFFs, the password locations cannot be simply overwritten with some other value because the application code is "large". If there is insufficient memory to accommodate a section, CCS will give an error and not build the .out file. Please read my first reply carefully. You still haven’t answered any of my questions in that post.

  • Thanks for your advice
    Because the problem happened by chance, I will confirm it to HW.

    Thank you.

    Eric Hung