• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 1298 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.

CCS/UNIFLASH: 'MassErase()' not found for CC1310 in UniFlash after 4.2.0

Dylan Anthony
Prodigy 30 points
Part Number: UNIFLASH
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

When attempting to perform any operation on a locked CC1310, I get a "This device is locked" dialog with no descriptive text, and a Yes/No option.  Clicking yes gives me a 'MassErase()' not found error.  I experience this issue on macOS, Windows 10, and Ubuntu 16.04 with both UniFlash 4.2.1 and 4.2.2.  4.2.0 appears to work fine.  I found another post about this but no one seems to have ever responded.  This isn't listed as a known issue for 4.2.2 but it probably should be.

  • 0
    TI__Guru**** 162895 points

    Dylan,

    I am attempting to reproduce this.  For me I am able to perform this action in 4.2.2.

    I will download the offline version and try that.  My first test was with the cloud version.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 30 points
    Hi John,

    Thanks for the quick response. I tried the online version and got the same error. I was using and XDS100v3. Out of curiosity I also just attempted with an XDS200 and got the same results. I'm currently testing on macOS High Sierra 10.13.3. Let me know if there is any more information I can give you to assist with reproducing it.
  • 0 in reply to Dylan Anthony
    TI__Guru**** 162895 points
    Dylan,

    The desktop version is working fine for me as well. My macOS version is a bit older 10.13.2. However I don't think that is the issue as you can see this on Windows as well. I will see if I have the correct adapters to test out an XDS100v3, at a minimum I should be able to try an XDS200. I have been using XDS110.

    Regards,
    John
  • 0 in reply to JohnS
    TI__Guru**** 162895 points
    I just tried an XDS200 and that worked for me as well. Must be something different in our installations somehow.
  • 0 in reply to JohnS
    TI__Guru**** 162895 points

    Let's test something out.  

    I want to confirm that the correct GEL file is getting loaded by your install of UniFlash.  GEL files contain some scripts that get run to assist with different actions.  There is actually a MassErase() function in one of the GEL files that is getting loaded.  I don't think this file is getting loaded in your case.

    Go to <install dir>/deskdb/content/TICloudAgent/osx/ccs_base/emulation/gel

    There should be cc26x0.gel and cc26x0_xds.gel.  The first one should be specified in the ccxml (target configuration file) and it actually loads the second one.  The cc26x0_xds.gel file contains the MassErase() function.

    Can you check if both the files are present in your install?  And then open the _xds one and make sure that it has a MassErase function

    hotmenu MassErase()

    Assuming that is all ok can you send my your ccxml file.  You can get it from uniflash by clicking on the download ccxml link at the top

  • 0 in reply to JohnS
    Prodigy 30 points

    My mac is currently back on 4.2.0 for work, but I checked out the Windows install's gel files and did find that hotmenu MassErase(), so that's good.

    Also, note that I can erase the flash of an unlocked chip.  When doing so I get the following in the console, so it looks like MassErase works under normal circumstances, just not after getting that device locked message.

    [3/26/2018, 12:48:22 PM] [INFO] Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    [3/26/2018, 12:48:27 PM] [INFO] Cortex_M3_0: MassErase(): Initializing.
    [3/26/2018, 12:48:28 PM] [INFO] Cortex_M3_0: MassErase(): Issuing Board Reset.
    [3/26/2018, 12:48:32 PM] [INFO] Cortex_M3_0: MassErase(): Mass erase complete.
    [3/26/2018, 12:48:39 PM] [INFO] Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    [3/26/2018, 12:48:44 PM] [INFO] Cortex_M3_0: MassErase(): Initializing.
    [3/26/2018, 12:48:45 PM] [INFO] Cortex_M3_0: MassErase(): Issuing Board Reset.
    [3/26/2018, 12:48:50 PM] [INFO] Cortex_M3_0: MassErase(): Mass erase complete.

    I'm attaching the ccxml as requested.  The forum won't let me upload it with that extension so I appended a .txt to it.

    Fullscreen CC1310F128.ccxml.txt Download 
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="configuration_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v3 USB Debug Probe" href="connections/TIXDS100v3_Dot7_Connection.xml" id="Texas Instruments XDS100v3 USB Debug Probe" xml="TIXDS100v3_Dot7_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v3 USB Debug Probe">
        	
        		   <instance XML_version="1.2" href="drivers/tixds100v2icepick_c.xml" id="drivers" xml="tixds100v2icepick_c.xml" xmlpath="drivers"/>
        	
        		   <instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>
        	
        		   <instance XML_version="1.2" href="drivers/tixds100v2cortexM.xml" id="drivers" xml="tixds100v2cortexM.xml" xmlpath="drivers"/>
        	
            
                  <property Type="choicelist" Value="2" id="The Converter Usage">
  <choice Name="Generate 1149.7 2-pin advanced modes" value="enable">
    <property Type="choicelist" Value="1" id="The Converter 1149.7 Frequency">
      <choice Name="Overclock with user specified value" value="unused">
        <property Type="choicelist" Value="5" id="-- Choose a value from 1.0MHz to 50.0MHz"/>
      </choice>
    </property>
    <property Type="choicelist" Value="5" id="The Target Scan Format"/>
  </choice>
</property>
            
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="CC1310F128" href="devices/cc1310f128.xml" id="CC1310F128" xml="cc1310f128.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

  • 0 in reply to Dylan Anthony
    TI__Guru**** 162895 points
    Ok. I will need to lock my device and try. We must be doing something different in 4.2.2 in the locked case. Once I can reproduce I will ping our team here to figure out what has changed.
  • 0 in reply to JohnS
    TI__Guru**** 162895 points
    Looks like a bug in 4.2.2. I have filed UNIFLASH-995 to track it. Keep using 4.2.0 to work around it for now and we will get the fix queued up for the next release.

    Regards,
    John