• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 80 subscribers
  • Views 230 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Locking (and unlocking) MSP432P4111 with uniflash CLI

Seth Hammond
Prodigy 101 points
Other Parts Discussed in Thread: UNIFLASH

I am trying to lock the MSP432P4111 chip on my embedded application but am finding resistance. I am able to lock the MSP432P4111 from the uniflash GUI by doing the following:

1. Check the checkbox for "Allow one-time device locking (only available during active debug session)"

2. Lock Device

The unlock feature doesn't work, we aren't sure why but that is less important than locking (we are able to use FlashProArm to erase the device).

When I create the standalone package in uniflash we are able to run the dslite.bat file to flash the software onto the device which is great. But then I go to lock the device with the command line it fails. Here is my command line response and call:

standalone_package>ccs_base\DebugServer\bin\DSLite.exe flash --config=user_files\configs\msp432p4111.ccxml -b LockDevice
CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
CORTEX_M4_0: GEL Output: Halting Watchdog Timer
Failed: Performing operation failed

This has the same response with Lock as well as LockDevice. Also I am using the XDS110. We need this to work so that we can lock the device at the factory and move production along with automation.

  • 0
    TI__Mastermind 32930 points

    I will move your thread to other topic. Hope they can answer your question.

  • 0
    TI__Guru**** 421740 points

    HI Seth,

    What version of UniFlash are you using?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 101 points

    UniFlash 7.2.0

  • +1 in reply to Seth Hammond
    TI__Genius 11005 points

    Seth,

    You mentioned you were turning on the "Allow one-time device locking (only available during active debug session)" option in the GUI. Can you try doing the same in the CLI command as well?

    To do that, add the following to your command:

    -s FlashEnableDeviceSecurityCheckbox=1

    Please see if this works for you. Also, you can try adding -e to the command to turn on verbose output. Depending on the implementation of LockDevice, you might get additional output this way.

    Thanks,

    Ricky

  • +1 in reply to Ricky Lau
    Prodigy 101 points

    Hi, This resolved my issue thank you! Here is the command I used to get reliable locking after flashing with the command line:

    C:\Users\sawye\Downloads\uniflash_windows_standalone\ccs_base\DebugServer\bin>DSLite.exe flash -c C:\Users\sawye\Downloads\uniflash_windows_standalone\user_files\configs\msp432p4111.ccxml -s FlashEnableDeviceSecurityCheckbox=1 -e -a LockDevice

    I am unable to do the MassErase function as it gives an error after locking but I am not so much concerned as it seems to be a not functional bug that doesn't even work in the GUI (The Unlock button next to the Lock button doesn't work).

**Attention** This is a public forum