• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 359 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F280039C: Adding password lock to device

Hang Yang
Expert 3031 points
Part Number: TMS320F280039C
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Hi all,

I am asking for my customer. 

They have successfully configured DCSM using syscfg, device locking and unlocking are functioning normally.

However, when they add password lock, a verification problem occurs when loading the program:

 

(The first line of the error: Error during Flash verification, Address 0x00078021, Expected 0x0000FFFF, Read 0x00000000)

Are there any steps additional to selecting "Enable password lock permanently" in syscfg to enable password lock?

Thanks,

Hang.

 

  • 0
    TI__Mastermind 28220 points

    Hi Hang,

    What version of C2000Ware is the customer using? Was PSWDLOCK set to "disable PSWDLOCK permanently" when they originally programmed their .out file? If so they will not be able to enable PSWDLOCK on the same device. If programming the zone header using SysConfig, PSWDLOCK must be enabled on the first program. Apologies for the inconvenience.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    TI__Expert 3031 points

    Hi Jones,

    I updated to newest syscfg and ccs, and redo the dcsm config in syscfg based on the driverlib dcsm example, now the verification problem is gone.

    When I add flash0 sector0 to zone1 and enable password lock and jtag lock, everything is fine.

    Then I let zone1 grab everything(All flash sector, all ram) in a new block, the loading is successful, however, when I tried to unlock the board, a low power mode error occurs when I connect to CPU1, and clicking "yes" won't help.

    I've config correct the jtag password in the target configuration （I deliberately config a wrong password and a different error occurs）.

    Then I let zone1 grab only flash bank 0 (On a new board), same thing happens.

    The final link pointer for both board is 3ff8.

    Also, I am using intel hex and load program using CCS. The hex parameters are: --memwidth=16 --romwidth=16 --diag_wrap=off --intel

    Below are my project files in case you want to reproduce the problem(use the CPU1_LAUNCHXL_FLASH build config): 

    zone 1 grab flash0 sector0 only(successful):

    https://tidrive.ext.ti.com/a/JPqr0Rj6q-I2-qvG/fb61ba6d-0361-459a-96b4-c50a65b9806f?l

    zone 1 grab everything(low power mode error):

    https://tidrive.ext.ti.com/a/LBNXvhATV4w-E1ep/3bffd195-1ddb-4e06-a558-02e6e0bf6b33?l

    Thanks,

    Hang.

  • +1 in reply to Hang Yang
    TI__Mastermind 28220 points

    Hi Hang,

    This issue is most likely due to the device booting from flash instead of wait boot mode. If you are booting from flash and connect to the device via JTAG, an ECSL trip will occur if the program counter is fetching an instruction from a secure region of memory. If you configure the device to wait boot mode this issue will not occur. If you want to boot from flash without the ECSL trip occurring, you can perform an ECSL unlock in the CCS On-Chip flash tool.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    TI__Expert 3031 points

    Thank you Jones,

    Wait-boot solved the problem.

  • 0 in reply to Hang Yang
    TI__Mastermind 28220 points

    Hi Hang, glad to hear it. I will close this thread.

    Thank you,

    Luke