• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1986 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.

CCS4 GUI freezes shortly after Run commences during debug session

Jim Sopchak
Prodigy 100 points
Other Parts Discussed in Thread: CCSTUDIO

I've been regularly been getting the CCS4 eclipse GUI to freeze when running even the simple
TSK DSP/BIOS example using a BlackHawk XDS560v2 System Trace debugger on my custom
C5515 module.  When I start a debug session, connect to emulator OK, GEL load OK, program
load OK, but after starting Run, the GUI freezes and is unresponsive if I have RTA Printf Logs
open.  The eclipse console window shows the following output if this is the case:

    SEVERE: Unable to get address for symbol: RTDX_HPONLY

If I don't have RTA Printf Logs open, all is well.

If I instead open "Tools->ROV" and view the output of the LOG module all is well.

Why does the CCS4 eclipse GUI freeze if i have RTA Printf Logs open?

The only way to bring the GUI back to life is to pull the (USB) plug on my emulator.

Does anyone know what gives here?

 

-Jim

  • 0
    TI__Guru**** 169864 points

    Jim,

    Would you mind sending us the debug logs as mentioned in this page? This may help us in investigating this further.

    Also, if you can send the exact version of the tools you are using (CCS, BIOS, RTDX, IPC, etc) that would help too.

    Thank you,

    Rafael 

  • 0 in reply to desouza
    Prodigy 100 points

    It would seem as though I worked thru this problem.

    I relocated some LOG_printf( &trace... ) calls from main() to a task.

    The hang problem with the RTA Printf Logs view open has now disappeared.

    For the record, I'm using:

    C5515 DSP configure for 100 MHz CPUCLK

    CCS Version 4.2.4.00033 (Help->About Code Composer Studio)

    DSP-BIOS Version 5.41.10.36

    Other version info:

     Configured features:
      ID: com.ti.ipc_1.0.5.60, Version: 1.0.5.60
      ID: com.ti.ccstudio.msp430, Version: 4.0.0.201106061600
      ID: com.ti.ccstudio.emu.5.0.333.0, Version: 5.0.333.0
      ID: com.ti.cgt.tms470.4.5, Version: 4.5.2
      ID: org.eclipse.cdt, Version: 3.1.0.200606261600
      ID: com.ti.dvt.rov, Version: 2.0.0.201105121115
      ID: com.ti.ccstudio.c5400, Version: 4.0.0.201106061600
      ID: com.ti.ccstudio.product, Version: 4.2.4.00033
      ID: com.ti.ccstudio.msp430.emu, Version: 4.4.9.0
      ID: com.bh.ccstudio.emulation, Version: 4.2.1.050
      ID: com.ti.cgt.c5400.4.2, Version: 4.2.0
      ID: com.ti.ccstudio.tms470, Version: 4.0.0.201106061600
      ID: com.ti.dvt.ccstudio, Version: 2.0.0.201105121115
      ID: com.ti.ccstudio.c2000, Version: 4.0.0.201106061600
      ID: com.ti.ccstudio.c6000, Version: 4.0.0.201106061600
      ID: com.ti.ccstudio.ccsnowflash.emu, Version: 4.2.4.0003
      ID: org.eclipse.tm.terminal, Version: 1.0.0.vTI-201106061600
      ID: com.ti.ccstudio.c5500, Version: 4.0.0.201106061600
      ID: org.eclipse.platform, Version: 3.2.0.vTI-201106061600
      ID: com.ti.cgt.c6000.6.1, Version: 6.1.20
      ID: com.ti.dvt.profileanalysismanager, Version: 2.0.0.201105121115
      ID: com.ti.dvt.via.ccs, Version: 2.0.0.201105121115
      ID: com.ti.dvt.analysis, Version: 2.0.0.201105121115
      ID: com.ti.ccstudio.emu.5.0.429.1, Version: 5.0.429.1
      ID: com.ti.dvt.trace.ccs, Version: 2.1.0.200911121836
      ID: com.ti.ccstudio.hercules.emu, Version: 4.2.4.0002
      ID: com.ti.ccstudio.branding, Version: 4.0.0.201106061600
      ID: com.sd.ccstudio.emulation, Version: 4.2.3.02
      ID: org.eclipse.rcp, Version: 3.2.0.vTI-201106061600
      ID: com.ti.ccstudio.rtsc, Version: 4.0.0.201106061600
      ID: com.ti.dvt.rta, Version: 2.0.0.201105121115
      ID: com.ti.dvt.graph.visualization, Version: 2.0.0.201105121115
      ID: com.ti.dvt.core.ccstudio, Version: 2.0.0.201105121115
      ID: com.ti.dvt.scripting.ui, Version: 1.0.0.200911121836
      ID: com.ti.sdo.grace.dummy_1.0, Version: 1.0.0.0
      ID: com.ti.cgt.c2000.5.2, Version: 5.2.11
      ID: com.ti.dvt.control, Version: 2.0.0.201105121115
      ID: com.ti.ccstudio.utils, Version: 1.0.1
      ID: com.ti.cgt.c5500.4.3, Version: 4.3.9
      ID: com.ti.cgt.msp430.3.2, Version: 3.2.3
      ID: com.ti.bios_6.31, Version: 6.31.4.27
      ID: com.ti.bios_5.41.2.14, Version: 5.41.2.14
      ID: com.ti.bios_5.41, Version: 5.41.10.36
      ID: org.eclipse.rtsc.xdctools.product, Version: 3.16.2.32
      ID: com.ti.bios_6.21.0.13, Version: 6.21.0.13
      ID: com.ti.ipc_1.22, Version: 1.22.3.23
      ID: org.eclipse.rtsc.xdctools.product.ui, Version: 3.20.8.88
      ID: com.ti.bios_6.30, Version: 6.30.3.46
      ID: com.ti.ipc_1.21, Version: 1.21.2.23
      ID: com.xdais_6_25_01_08, Version: 6.25.1.08

  • 0 in reply to Jim Sopchak
    TI__Guru**** 169864 points

    Jim,

    Thank you for reporting back your findings. According to Appendix A-2 of the DSP/BIOS User's Guide, LOG_Printf() can be called from main() but any messages will only be displayed in the host after your code returns from it. Assuming you are not overflowing any buffers, the fact that this function is disrupting the normal execution of your device may be an issue with the API itself. If you have the time you could ask the exact "why" at the BIOS forum.

    Regards,

    Rafael