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 4.0 crashes with DM6437 EVM board

Other Parts Discussed in Thread: CCSTUDIO

I have a CCS 4 problem.

First question: Is there a description somewhere on how to use CCS 4 to load a prebuilt executable onto an EVM board (without having a project etc)?

Main issue: Connecting CCS 4 to the EVM board crashes.
I have a Spectrum Digital DM6437 EVM board. With CCStudio 3.3. I built the NDK helloWorld for that board (packages\ti\ndk\example\network\helloWorld) and everything works. I followed instructions on migrating legacy CCStudio projects and successfully built the new CCStudio 4.0 helloWorld project. I created a target configuration file (attached file: Testing9.ccxml), picking the connection "Spectrum Digital DSK-EVM-eZdsp onboard USB Emulator" and then adding the board "EVMDM6437". These settings seemed closest to the setup that works in CCStudio 3.3. Then I launch this target configuration ... which pops up the transient dialog box "DSK STARTUP Waiting for USB enumeration" (just like CCStudio 3.3) ... and then I am in the debug view (attached file: Screenshot1.png). If I choose "Target->Connect Target" the ide crashes (attached file: DebugServer.dll20100108153359.dmp).

If I use CCS 3.3 to load the helloWorld executable (that was built by CCS 4) it runs fine.


Retry: I cleaned everything (new workspace, new migration of legacy helloWorld.pjt, new Testing9.ccxml) and after the debug view pops up the transient dialog box "DSK STARTUP Waiting for USB enumeration" then the ide crashes (attached file: DebugServer.dll20100108161248.dmp) the difference is that this time I didn't get to try to select "Connect Target". I restarted the ide and exported the error log (attached file: PDEErrorLog.log)

CCS Version: 4.0.2.01003
Code Gen Tools: 6.1.11
DSP/BIOS Version: 5.41.00.06

Reproduce: Import the legacy .pjt file into CCS 4 (attached file: reproduceableTestCase.zip). Delete remaining "helloWorld.pjt" "helloWorld.cmd" "migration.log". Build. Debug (creating Target Configuration).

CCS4ProblemFiles.zip
  • Hi,

    Is there any feedback on this issue? Thanks...Bob

     

  • Hi Bob,

    Looking at your dump files, the issue points to ctools as a possible cause. Could you try disabling it and see if you can then connect to your board? We have seen this workaround help in similar cases. If this works for you, then we know where the cause of the crash was.

    See the last post here for more details on disabling ctools.

     

    Thanks

    ki

  • That fixed the problem ... I can now communicate with the board, debug, etc etc. Thanks.

    Just to recap in this thread... When not running CCSv4 I renamed the file "ctools.dll" to something that would not load (e.g. ctoolsDOTdll.SAVE) in the directory

    <INSTALL DIR>\ccsv4\emulation\analysis\bin

    Then I started CCSv4.