• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1316 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Crash of CCS Ver.5.3.0.00090 with XDS100v2 on connect of second DSP in a chain of two

Wolfgang
Prodigy 80 points

I recently bought a XDS100v2 (Blackhawk, Model D) and downloaded the CCS V5 (meanwhile with latest updates installed).

I've a custom board with two DSPs in a chain (hardware out of doubt as full functioning with CCS V3.3 and a BH560 emulator) were the JTAG chain is o.k. (as assumed by CCS V5 & XDS100v2).

I can connect to the first DSP in the chain, download a program and run it !

Unfortunately when I try to connect the second CPU the hole CCS crashes without any error message.

Has someone an Idea where to start.

Regards, Wolfgang

 

  • 0
    TI__Genius 16460 points

    Are there any crash dump logs created? (see here ). If there are, would you be able to attach them to this thread?

    If there are not crash dump logs, it would be useful to get a Debug Server log from the debug session where CCS crashes. That is described in the same wiki topic.

     

  • 0 in reply to AndyW
    Prodigy 80 points

    7571.#hs_err_pid5920.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    #
    # An unexpected error has been detected by Java Runtime Environment:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x3a81c2df, pid=5920, tid=5644
    #
    # Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode windows-x86)
    # Problematic frame:
    # C 0x3a81c2df
    #
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #
    --------------- T H R E A D ---------------
    Current thread (0x2e038400): JavaThread "polling thread" daemon [_thread_in_native, id=5644, stack(0x36bc0000,0x36cc0000)]
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    If that give's any insight ...

    Regards, Wolfgang

     

  • 0 in reply to Wolfgang
    TI__Genius 16460 points

    Thank you for tracking that down. Unfortunately, the java crash log didn't have anything useful. It is unusual that there is no .dmp file generated.  The next thing that might help is the Debug Server Log. You basically enable the logging, recreate the crash, and collect the log file. The file will be big.  If you are able to post that here we will see where that points.

  • 0 in reply to AndyW
    Prodigy 80 points

    Excuse, I didn't realise the dmp-file.

    Also find attached the log file.6281.#DebugServer20121218074658.txt1768.#MyLog.txt

  • 0 in reply to Wolfgang
    Prodigy 80 points

    Now I'm currious about the findings...

    Personally I don't like software that isn't capable of handling exceptions properly.

    Not a good start with CCS V5.

    Thanks for your help indeed,

    Wolfgang

     

  • 0 in reply to Wolfgang
    TI__Genius 16460 points

    Wolfgang,

    We had a look at this and believe the combination of emulators and devices is causing a problem. You're using a device that isn't officially supported by the XDS100v2.

    What seems to be happening is there is a problem when the connect to the 2nd core is attempted. Whatever that issue is causes CCS to try to disconnect the 2nd core. The disconnect sends the software down a bad path and it crashes.

    If you connect to the cores in the reverse order (2nd, then 1st), do either of the connects succeed?

  • 0 in reply to AndyW
    Prodigy 80 points

    Hello Andy,

    There's no way (or as you called it only "bad paths") to successfully connect to the 2nd core. (Of course there's a way: CCS V3.3 & BH560 ;-)

    Disregarding if I first connect the first core it crashes on the connect of the second or

    if I directly connect to the second it crashes.

    Are there good paths in the software leading to a connect to both ?

    Regards, Wolfgang

     

  • 0 in reply to Wolfgang
    TI__Genius 16460 points

    Wolfgang,

    I don't have a workaround for you. I have filed a defect against the C64x emulation driver (defect reference number: SDSCM00046041 ).

    While the XDS100v2 you are using does not officially support this device, you are likely to encounter the same problem on other emulators.