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.

Debug Crash after upgrade to CCSv5.2?

Guru 15580 points
Other Parts Discussed in Thread: OMAPL138

After upgrading to CCS V5.2 today I can no longer launch a debug session. I receive the following error window.

After hitting "OK" , CCS crashes.

Can someone please provide some guidance that will let us continue our work?

  • Hi Mike,

    how did you preform the upgrade?  From which former version?  COuld you please send any error logs as well as the contents of your installjammer registry directory (under program files or program files(x86).?

    Would you be willing to do a fresh 5.2 installation into a new directory?  Am I correct in understanding every project and workspace is crashing launching the debugger?  What target do you use?

    Best Regards,
    Lisa

  • Lisa,

    Lisa TI said:
    how did you preform the upgrade?

    I was one of the unfortunate few that upgraded via Help->Check for updates (see forum posts).

    Lisa TI said:
    From which former version?

    V5.1.something.

    Lisa TI said:
    COuld you please send any error logs as well as the contents of your installjammer registry directory (under program files or program files(x86).?

    attached.8081.6FB2A0F-6221-089D-769D-562B138A744D.zip

    Lisa TI said:
    Would you be willing to do a fresh 5.2 installation into a new directory?

    I am in the process of downloading the 1.2GB file now. This is a 1 hour download for me.

    Lisa TI said:
    Am I correct in understanding every project and workspace is crashing launching the debugger?

    I only have one project under development at the moment. It crashes consistently.

    Lisa TI said:
    What target do you use?

    0728.usbstk5515_RevA.zip

  • Hi Mike,

    yes, unfortunately as you gathered from some of the other threads, we are currently having some problems we are uncovering with some upgrade paths.

    I have flagged the post and logs for development and your patience having to go through a complete installation is appreciated.

    Should there be any feedback re your logs we will certainly post.

    Sorry for any inconvenience.

    Best Regards,

    Lisa

  • Lisa,

    Error during de-install. Is it OK to re-install?

    in fact, all of these files still exist

  • Hi Mike,

    yes.  The best steps to take would be to manually remove the old installation folders/tree and install to a new directory.  If the installjammer registry logs you sent us were complete, you could also clear this directory before doing the fresh install.

    Please keep us informed how it goes.

    Best Regards,
    Lisa

  • Lisa,

    Could you be a bit more explicit? Are you suggesting that I delete the entire tree down to C:/ti (CCS is currently installed in C:\ti\ccsv5)?

  • Lisa,

    The saga continues. After uninstalling and then re-installing CCS5.2 I attempted to add the discovered new products. However, the process hangs at the window below:

    And when I try to cancel the process I get the following:

    So far this upgrade has cost me almost an entire day. Please pass my frustration back to the development *management*.

  • ...and the saga continues further. 

    After spending several hours upgrading, de-installing, downloading, decompressing, re-installing......

    THE SAME PROBLEM EXISTS!!!!!

    DOES TI ACTUALLY TEST THIS CODE BEFORE RELEASING IT???

  • Mike,

    Your issue sounds very similar to mine.  I was able to connect after the upgrade and it was related to my ccxml file.  See my post(s) at http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/193073/690917.aspx#690917  Maybe something there can help you.

    My final working targetConfig.ccxml file was as follows (for an OMAPL138)

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>

    <configurations XML_version="1.2" id="configurations_0">

    <configuration XML_version="1.2" id="Blackhawk LAN560 Emulator_0">

            <instance XML_version="1.2" desc="Blackhawk LAN560 Emulator_0" href="connections/BH-LAN560_Connection.xml" id="Blackhawk LAN560 Emulator_0" xml="BH-LAN560_Connection.xml" xmlpath="connections"/>

            <connection XML_version="1.2" id="Blackhawk LAN560 Emulator_0">

                <instance XML_version="1.2" href="drivers/tixds560icepick_c.xml" id="drivers" xml="tixds560icepick_c.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds560c674x.xml" id="drivers" xml="tixds560c674x.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds560pru.xml" id="drivers" xml="tixds560pru.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds560arm9.xml" id="drivers" xml="tixds560arm9.xml" xmlpath="drivers"/>

                <instance XML_version="1.2" href="drivers/tixds560etb11.xml" id="drivers" xml="tixds560etb11.xml" xmlpath="drivers"/>

                <property Type="choicelist" Value="0" id="dataFileRequired">

                    <choice value="specify custom">

                        <property Type="filepathfield" Value="..\..\..\Users\David McCreight\AppData\Local\.TI\213602635\0\0\BrdDat\ccBoard0.dat" id="dataFile"/>

                    </choice>

                </property>

                <property Type="stringfield" Value="0" id="portAddr1"/>

                <platform XML_version="1.2" id="platform_0">

                    <instance XML_version="1.2" desc="OMAPL138_0" href="devices/OMAPL138.xml" id="OMAPL138_0" xml="OMAPL138.xml" xmlpath="devices"/>

                </platform>

            </connection>

        </configuration>

    </configurations>

  • David,

    Thanks for the suggestion. However, I have found that if I edit the target file (change something, then change it back to what it was), then save it, CCS will load and run a debug session.

    Looks like TI really mangled this release (V5.2).

  • Hi Mike,

    so are you up and running and ok then?  I do know we have seen cases where the ccxml did have to be regenerated ...

    Best REgards,
    Lisa

  • Hi,

    MikeH said:

    However, I have found that if I edit the target file (change something, then change it back to what it was), then save it, CCS will load and run a debug session.

    Sorry about the trouble; this was added to the release notes for CCSv5.2.0 but I may also add a sitcky post to the forum. The same issue happens for OMAP4430 and OMAP4460 devices.

    Regards,

    Rafael

  • Rafael,

    desouza said:
    but I may also add a sitcky post to the forum

    I would highly recommend that you do something to prevent additional lost time by others. No offense, but this is inexcusable.

    desouza said:
    The same issue happens for OMAP4430 and OMAP4460 devices.

    It also happens to the C5515 device (which I am currently using).

  • Lisa TI said:
    so are you up and running and ok then?

    Yes. See the fix posted by Rafael.