Code Composer Studio V5.1 crashes during connecting to TMDXEVM6678L Eval Board

Jens Baumann

Other Parts Discussed in Thread: CCSTUDIO

Hello,

I uses Code Composer Studio (CCS5.1.0.09000_win32, 90 day trail ) on Windows 7 32Bit. I just install the Code Composer Studio and the Bios (bios_mcsdk_02_00_04_16_setupwin32) to directory C:\TI. No additional plugins are installed. I setup a new target Configuration file (see below) forTMDXEVM6678L Eval Board using the Blackhawk XDS560v2-USB Mezzanine Emulator.I run the connection test successfully (see below) . After launching the configuration I try to connect to the CPU. Then CCS crashes. I run CCS as administrator.

I save a crash dump file as descibed in http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Crash_Dump_File. I attach the dump file. I need to rename the .dmp with .txt in order to attach the file.

Crash Dump

1667.DebugServer20111208145459.dmp.txt

Target Configuration File:

Fullscreen 4744.XDS560_C6678.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="Blackhawk XDS560v2-USB Mezzanine Emulator_0">
        <instance XML_version="1.2" desc="Blackhawk XDS560v2-USB Mezzanine Emulator_0" href="connections/BH-XDS560v2-USB_Mezzanine.xml" id="Blackhawk XDS560v2-USB Mezzanine Emulator_0" xml="BH-XDS560v2-USB_Mezzanine.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Blackhawk XDS560v2-USB Mezzanine Emulator_0">
            <instance XML_version="1.2" href="drivers/tixds560icepick_d.xml" id="drivers" xml="tixds560icepick_d.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560c66xx.xml" id="drivers" xml="tixds560c66xx.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560cs_dap.xml" id="drivers" xml="tixds560cs_dap.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560csstm.xml" id="drivers" xml="tixds560csstm.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560etbcs.xml" id="drivers" xml="tixds560etbcs.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320C6678_0" href="devices/C6678.xml" id="TMS320C6678_0" xml="C6678.xml" xmlpath="devices"/>
            <device HW_revision="1" XML_version="1.2" description="C66x core" id="TMS320C6678_0" partnum="TMS320C6678" simulation="no">
                    <router HW_revision="1.0" XML_version="1.2" description="ICEPick_D Router" id="IcePick_D_0" isa="ICEPICK_D">
                        <property Type="filepathfield" Value="..\..\emulation\boards\evmc6678l\gel\evmc6678l.gel" id="GEL File"/>
                    <subpath id="subpath_0">
                            <cpu HW_revision="1.0" XML_version="1.2" description="C66xx CGEM+FP CPU" id="C66xx_0" isa="TMS320C66XX">
                                <property Type="filepathfield" Value="..\..\emulation\boards\evmc6678l\gel\evmc6678l.gel" id="GEL File"/>
                            </cpu>
                        </subpath>
                    </router>
                </device>
            </platform>
        </connection>
    </configuration>
</configurations>

Log from Connection Test:

0842.connection_test_log.TXT

I also perfom a cTools/Trace Loggin:

I do the following steps:

- start CCS

- open CCS debug perspective

- open Target Configuration View

- launch XDS560_5F00_C6678.ccxm

- connect to first CPU

Fullscreen 8015.ti_trace_log_1282011_2016.txt Download

M     16:09:28:936 | JTRACE: TraceInit()
M     16:09:28:947 | Trace JNI: connecting channel server
M     16:09:28:949 | Trace Factory: Calling CreateTraceFactory
M     16:09:28:951 | Trace Factory: CreateTraceFactory pStaticFactory=0x2e29f918    refcount=1
M     16:09:28:951 | Trace Factory: calling CreateChannelServer  m_channelServer=0x0
M     16:09:28:951 | Trace Factory: Reusing environment from previous session.
M     16:09:28:951 | Trace Factory: dlltype=1, familySupport=0, receiverSupport=(null)
M     16:09:28:961 | Trace Factory: CreateChannelServer  - connect existing
    E 16:09:30:989 | Trace Factory: Channel server creation failed.
    E 16:09:30:989 | Trace JNI: Channel server creation failed..
M     16:09:30:989 | Trace JNI: connecting channel server - DONE 
M     16:10:42:205 | cTools: cToolsMgrIF is created
M     16:10:42:207 | cTools: main Thread ID 3172 .
M     16:10:42:207 | cTools: cToolsJobMgrIF is created
M     16:10:50:770 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:50:770 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:50:770 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:50:770 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:091 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:091 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:091 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:091 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:111 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:112 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:112 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:112 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:131 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:131 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:131 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:131 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:149 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:150 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:150 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:150 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:168 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:168 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:168 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:168 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:187 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:187 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:187 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:187 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:206 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:206 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:206 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:206 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:51:458 | JTRACE: CTraceEventHandler::Lock(): Thread 5732 attempting to lock...
M     16:10:51:458 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 5732.
M     16:10:51:458 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 is trying to remove lock owned by thread 5732 ... 
M     16:10:51:459 | JTRACE: CTraceEventHandler::Unlock(): Thread 5732 successfully removed lock.
M     16:10:56:501 | cTools: In GetcToolsDBMgrIFEx
M     16:10:56:501 | cTools: Create database for XML file C:\TI\ccsv5\ccs_base\emulation\analysis\bin\../xmldb/aet_config/3000.xml
M     16:10:56:501 | cToolsDBMgr: Load DB 1 from C:\TI\ccsv5\ccs_base\emulation\analysis\bin\../xmldb/aet_config/3000.xml.
M     16:10:56:503 | cTools: Calling CreateSystem for ctoolsndbg with TA 0x37fe4378 using CPU 0.
M     16:10:56:504 | cToolsIF: CreateSystem() is passed
M     16:10:56:506 | cTools: CreateSystem done.
M     16:10:56:507 | cTools: IsTargetSupported EntityName=ctoolsndbg.
M     16:10:56:508 | cTools: IsTargetSupported action count=0.
M     16:10:56:516 | JobMgr: Device Identifier loaded

Hope anyone could help? Thanks

Jens.

over 13 years ago

0 Lisa TI over 13 years ago

TI__Guru*** 130875 points

Hi Jens,

thanks for the information we will look into this. Would you be able to try a couple further things?

- uninstall the MCSDK and retest

- install the MCSDK, but during installation make sure to select not to install the MSA

- rename ctools.dll and retest.

Please keep us posted.

Best Regards,
Lisa

0 Jens Baumann over 13 years ago in reply to Lisa TI

Prodigy 105 points

Hello Lisa,

thank you for your quick reply,

- uninstall the MCSDK and retest

--> do not help

- install the MCSDK, but during installation make sure to select not to install the MSA

--> do not help

--> I didn't find MSA Entry. Do you mean MCSA. MCSA was unchecked by default.

- rename ctools.dll and retest.

--> I found two files:

1. C:\TI\ccsv5\ccs_base\emulation\Blackhawk\Utility\BHProbe.2\bin

2. C:\TI\ccsv5\ccs_base\emulation\analysis\bin

Renaming the first file doesn't help. But after renaming both files I could connect to the CPU. Also loading a programm and debugging works.

Do I need ctools.dll?

Best Regards,

Jens

0 Lisa TI over 13 years ago in reply to Jens Baumann

TI__Guru*** 130875 points

Hi Jens,

by renaming ctools you will unfortunately loose some of the high level debug features such as watchpoints and a some of the views. However CCS should, as you have found out, otherwise run normally.

This comes from a bug that we have been working to fix but unfortunately seems to possibly have persisted into the latest versions.

Thanks for sending the logs in the initial post. They may be of assistance to us working on the issue.

I am glad you are at a point where you can continue to load and debug code and sorry for any inconvenience the issue causes you.

Best Regards,
Lisa

0 Matthew Waddell over 13 years ago in reply to Lisa TI

Intellectual 255 points

Hi Lisa,

I've also experienced this issue, but with a Blackhawk Xds560 USB v2 System Trace (Code Composer Studio 5.1.0.09000). Thank you for the workaround: After renaming "ccs_base\emulation\analysis\bin", I am able to connect. I am still stuck, however as I'd like to be able some of the higher level debug features. You mentioned that this is related to a bug that is currently being worked on. Could you give some idea as to what state the bug fix is currently in?

The steps to reproduce:

Switch to CCS Debug perspective
Launch target configuration
Connect to target
<The crash occurs>

Here are the crash logs and ccxml: 3113.DebugServerCrash.zip

Thanks,

_matt

0 Jens Baumann over 13 years ago in reply to Matthew Waddell

Prodigy 105 points

Hi Lisa,

now I'm working with the latests CCS Version V5.2.0.00069 but the bug ist still active. Do have an idea when the bug will be fixed?

thanks

jens

0 AndyW over 13 years ago in reply to Jens Baumann

TI__Genius 16490 points

Jens

There are several files being loaded from a CCS3.3 install you have. Could you check if there are any components on your PATH environment variable that refer to C:\CCStudio_v3.3\ ? If there are, please remove them and see if this helps with the problem. Alternately, you can just rename C:\CCStudio_v3.3 to something else temporarily.

0 Jens Baumann over 13 years ago in reply to AndyW

Prodigy 105 points

Hi Andy,

thanks for the quick reply. Renaming the CCS V3 install directory helps a little bit. Now I can launch the target configuration and i can connect to the target. But loading a programm to the dsp fails. Fails means that nothing happens. No loading operation or any error message. I also tried to rename the ctools.dll as described in a previous post. But it doesn't help. Also a complete deinstall of CCS V3 doesn't help.

On a second machine I have installed CCS V5.1.0.09000. With this version I can connect and load a program to the target after renaming the CSS V3 install folder.

Both Version runs with a full floating license.

Jens

0 AndyW over 13 years ago in reply to Jens Baumann

TI__Genius 16490 points

Jens,

I don't think ctools or a license issue would explain what you describe.

When you re-installed, do you use the default install path (c:\ti), or did yo install into C:\program files? Installing into \program files is not recommended on windows7 because this version of eclipse wants to write certain configuration data to the installation folder. Windows7 doesn't like data being written to the installation folder.

Could you generate a debug server log for the load failure (Go to the help -> CCS support menu, enable Debug server logging to a file, execute the operation, and post the log here)?

0 Jens Baumann over 13 years ago in reply to AndyW

Prodigy 105 points

Hi Andy,

sorry false alarm. In the startup settings of eclipse I deactivated the Code Composer entries. After reactivating them it works. thanks.

Code Composer Studio™︎

Code Composer Studio forum

Code Composer Studio V5.1 crashes during connecting to TMDXEVM6678L Eval Board