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.

Reliable crash CCSv5.2 + C6678 Functional Simulator

Hello,

I've a project which reliably crashes CCS 5.2 + TI Keystone1 Emulators win32 1.0.4.0. The project is an adapted sample which uses DMA on all 8 cores. When I click on "Terminate" while all 8 cores are processing, first the simulator crashes and aftwards CCS. (it would be really great if CCS could be made more robust in regards to Emulator/Simulator problems - usually a hanging Emulator blocks the whole user interface thread).

Is this a known bug, or should I provide the project plus a more detailed description?

- Clemens

  • Hi Clemens,

    If you can provide this project, that'd be great. Actually I probably just need to *.out file to run on the simulator. If you don't want to post this file publicly, start a private conversation with me and we'll figure out how to hand off the file

    Thanks

    ki

  • Hi Ki-Soo Lee,

    These are the steps required to reproduce the crash:
    1. Launch the C6678 Functional Simulator Little Endian TargetConfiguration (included in zip-file)
    2. Group all cores, Run->Load->Load program -> EDMA3LLDTest.out
    3. Start all cores by clicking on the "Resume" Button
    4. When the first few "Delay: xx ms" messages appear (after a few seconds) press the "Terminate" Button
    5. First gti_sim_server.exe crashes, this causes the whole CCS to crash.
    Beside the issue with the crashing simulator, it would be really great if CCS could be made more robust in regard to simulator/emulator stability issues.
    I typically restart CCS 5.2 about 5-10x a day :/

    7140.testcase.zip

    Thanks for taking a look, Clemens

  • Clemens,

    Thank you for the excellent test case! It really helps to get a clear, reproducible test case. I was able to reproduce the crash. Actually the issue seems to happen even if you don't load any program but just run the group and then terminate.

    I also reproduced with 5.2.1.

    I filed a bug for this. The tracking ID is: SDSCM00044686

    Thanks

    ki

  • Hi Ki,

    This looks very similar to the consistent CCS crash we are seeing with 5.2.1 and C6657 Device Functional Similator, Little Endian. What is the ETA of the resolution for SDSCM00044686? Is it possible to get a patch for it in advance so we can move forward?

    Please let me know.

    Thanks,

    Ying

  • Hi Ying,

    It has been fixed in CCSv5.3.0. The 5.3.0 beta is now available and I believe it is in there if you wish to try it out

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/216229.aspx

    Thanks

    ki