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.

UNIFLASH, unlock MSP432E41Y from GUI?

Other Parts Discussed in Thread: UNIFLASH, TM4C129ENCPDT, MSP432E401Y, MSP-EXP432E401Y, EK-TM4C1294XL

I'm still hoping for an answer to my question about Unlocking with Uniflash GUI.  Does no one at TI know how Uniflash works?  There doesn't appear to be any documentation for this product.

  • Yes, I know the command line tool can be used to unlock the device, what I want to know is if the GUI can be used to do the same, and if so, how?  Why has TI released a tool with no documentation?

  • Can you please tell me exactly what you can find about unlocking with the GUI?  Searching that linked webpage for either "unlock" or "lock" returns no results for me.

  • Yes, I know the command line tool can be used to unlock the device, what I want to know is if the GUI can be used to do the same, and if so, how?

    The MSP432E and TM4C129 devices are documented as having the same procedure to unlock the device, so if the Unflash GUI supports the unlock for the TM4C129 devices in theory it should support the unlock for MSP432E devices.

    With UniFlash 6.3.0 under Windows 10:

    1. With a TIVA TM4C129ENCPDT and a Stellaris In-Circuit Debug Interface, the Uniflash GUI is showing the option for a Debug Port Unlock
    2. With a TIVA TM4C129ENCPDT and a different Debug Interface (e.g. a XDS110), the Uniflash GUI is not showing the option for a Debug Port Unlock
    3. With a MSP432E401Y and a Stellaris In-Circuit Debug Interface, the Uniflash GUI is not showing the option for a Debug Port Unlock.

    The following command line was able to unlock a MSP432E401Y using the built-in XDS110 on a MSP-EXP432E401Y, using either the Uniflash 4.6.0 or 6.30 installations:

    C:\ti\uniflash_4.6.0\deskdb\content\TICloudAgent\win\ccs_base\common\uscif>dbgjtag.exe -f @xds110 -Y unlock,mode=msp432
    
    Executing the unlock procedure.
    
    Assert and hold reset while powering up the device.
    Press any key to continue.
    
    Release reset.
    Press any key to continue.
    
    Power cycle the board to complete the unlock procedure.

    C:\ti\uniflash_6.3.0\deskdb\content\TICloudAgent\win\ccs_base\common\uscif>dbgjtag.exe -f @xds110 -Y unlock,mode=msp432
    
    Executing the unlock procedure.
    
    Assert and hold reset while powering up the device.
    Press any key to continue.
    
    Release reset.
    Press any key to continue.
    
    Power cycle the board to complete the unlock procedure.

    Given that Uniflash installation has a command line interface which supports unlocking a MSP432E401Y using a XDS110 I looked at what controls the available options in the Uniflash GUI.

    C:\ti\uniflash_6.3.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\propertyDB\TM4Cx_FlashProperties.xml has sections which enable support for a Debug Port Unlock on TM4C devices, but not using a xds connection, under linux nor under osx:

    	<property id="FlashDebugPortUnlockText">
    		<target>TMS470REX</target>
    		<name>The following operation will erase the internal flash and the non-volatile user registers. 
    Often the user registers are used to store the Ethernet MAC address. You should consider 
    noting the current value of the user registers for reprogramming at a later time using the 
    User Register Programming utility.</name>
    		<valueType>Text</valueType>
    		<disableIf>
    			<os>linux</os>
    			<os>osx</os>
    			<connection>xds</connection>
    		</disableIf>
    		<categories>
    			<category>DebugPortUnlock</category>
    		</categories>
    	</property>

    Whereas the C:\ti\uniflash_6.3.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\propertyDB\MSP432E401Y_FlashProperties.xml file has no sections which enable support for Debug Port Unlock.

    I will try modifying the C:\ti\uniflash_6.3.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\propertyDB\MSP432E401Y_FlashProperties.xml and see if that enables support in the GUI.

  • I will try modifying the C:\ti\uniflash_6.3.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\propertyDB\MSP432E401Y_FlashProperties.xml and see if that enables support in the GUI.

    I copied the Debug Port Unlock related sections from the TM4Cx_FlashProperties.xml to MSP432E401Y_FlashProperties.xml file, and also removed the <connection>xds</connection> lines.

    That allowed the Uniflash GUI to display the Debug Port Unlock option for a MSP432E401Y using a XDS110. However, the unlock failed with an error:

    So, just editing the XML wasn't sufficient to allow the Uniflash GUI to allow a device unlock.

  • Chester,

    That's some good detective work.  Thanks for going to that much effort.  It looks like I'll have to stick with the command line to unlock the MSP432E401Y using an XDS110.  Hopefully someone in the tools team can look into this. I wonder if it's an XDS limitation, which would surprise me given that the XDS110 works form the command line.

    -phil

  • I wonder if it's an XDS limitation, which would surprise me given that the XDS110 works form the command line.

    I just tried with a EK-TM4C1294XL with a onboard Stellaris IDCI. Using the Uniflash GUI to attempt an unlock on the EK-TM4C1294XL failed with the same "Error! Module Closed" error as my attempt at editing the MSP432E401Y_FlashProperties.xml above:

    Attempting to unlock the EK-TM4C1294XL with the Uniflash GUI failed with the same error with Uniflash v4.6.0, v5.3.1 or v6.3.0.