• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1403 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/LAUNCHXL-CC1352R1: Long time program loading and very slow debugging.

Robert Galon
Intellectual 435 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: SYSCONFIG

Tool/software: Code Composer Studio

Hi!

Environment:

CC1352R1 HW Rev. B.
CCS 10
SDK 4.20.00.35

I mainly working on library with lots of metaprogramming and std types (tuples, pairs, arrays etc.). My CCS project include and use that library, but also add TI-RTOS Events, Tasks, GPIO, RF etc. For both projects I'm using GCC 9.2.1 compiler and C++17 with stdc++_nano and rdimon_nano libraries.

Problem:

I'm working on project which grow up greatly recently, we added lots of metaprogramming and C++17 code. I haven't been debugging for a while because of changes to project, but recently when I started again I discovered that debugging took really long time (flashing only is still fast and nice). Firstly it's taking really long to load all stuff: loading program (my .out), loading symbols (my .out), loading symbols (driverlib.out), and then CCS is freezed on main() function for ~10 minutes. After this all I can start debugging, but unfortunately debugging has become very slow, every step over taking time and IDE is non responsible all the time.

Steps taken:

I already tried to set higher JTAG frequency in target config file, disable semihosting and verification in debug configuration but nothings helped.

What can I do to speed up debugging and why it's become that slow?

  • 0
    TI__Guru**** 463831 points

    Hello Robert,

    Robert Galon said:
    I haven't been debugging for a while because of changes to project, but recently when I started again

    Did you update the version of the tools since then? Or were you using CCS 10 & GCC 9.2.1 before when debugging was faster?

    Robert Galon said:
    Firstly it's taking really long to load all stuff: loading program (my .out), loading symbols (my .out), loading symbols (driverlib.out), and then CCS is freezed on main() function for ~10 minutes. After this all I can start debugging, but unfortunately debugging has become very slow, every step over taking time and IDE is non responsible all the time.

    If just loading symbols is also very slow, then the issue is not related to JTAG connection or verification etc. It is an overall slow IDE environment. What is the HW specs of your machine? Also, have you try disabling any antivirus/security software just to check if those could be having an impact?

    Thanks

    ki 

  • 0 in reply to Ki
    Intellectual 435 points

    Hi ki.

    That's good point, before I was using CCS 9.x (difficult to say which exactly) but with same compiler, I will check if on previous CCS version debugging is faster. I don't have any security software. 

    My PC:
    OS: Windows 10 Pro 64Bit
    CPU: Xeon E5-1620
    GPU: Quadro K2000
    RAM: 16GB

  • 0 in reply to Robert Galon
    TI__Guru**** 463831 points

    Robert Galon said:
    I will check if on previous CCS version debugging is faster.

    Please keep us posted.

    Robert Galon said:
    My PC:
    OS: Windows 10 Pro 64Bit
    CPU: Xeon E5-1620
    GPU: Quadro K2000
    RAM: 16GB

    You specs look good. There is certainly no bottleneck there.

    How big are the *.out file being loaded?

  • 0 in reply to Ki
    Intellectual 435 points

    I had problems with CCS9 so I haven't test this yet. My project doesn't work with older SDK (sysconfig version error).

    Also I'm testing CCS10 but without my library separately, now I put all of my code inside one project (based on Hello example). I have some conclusions with std::tuple but I need to test it more (maybe it's just accident). I'll give feedback if I have some more specific info.

    My out files are exactly:

    30884 KB for Debug and
    20777 KB for Run build (-O2)