• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 488 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: CCS on MacOS Mojave drains a lot of battery.

Hamza Kadhum
Intellectual 945 points

Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1

Tool/software: Code Composer Studio

Hi,


CCS version 9.2
macOS Mojave version 10.14.2

I have recently installed CCS on my Macbook Pro with MacOS Mojave. I have tried to run some examples and it works fine but I realized that running CCS drained more battery than any other IDE I have used before. 
I tried an example on my launchxl-CC26x2R1 through CCS during 40-60 minutes time and my battery went from 90% to 50%. Running CCS utilize 120% of the proccessor (activity control) and energy consumption spikes. 

Any suggestions on how to resolve this issue? 


Best regards,
H

  • 0
    TI__Guru**** 171839 points

    H,

    I didn't notice anything particularly different in Mojave, but what do you see when you issue the command "top" at a terminal? 

    One subprocess that usually tends to use some resources and/or CPU is the node.js, used by the Getting Started page, TI Resource Explorer, ROV2, etc. Opening one of these views spawns a process called "node". In my case I don't see it using resources, but I will leave it idly running and take note of any behaviour change. 

    Unfortunately I don't use CCS on macOS enough to have a clear distinction between releases, but hopefully other developers may report their impressions on this thread as well. 

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 163175 points

    H,

    I am running CCS on Mojave.  I am generally plugged in so I haven't experienced the battery drain.  As far as CPU load as Rafael metnioned Resource Explorer is one that can do that, mainly when it starts up and is parsing its database (not sure if the load would show up under CCS or node in activity monitor).  

    Most of the time for me CCS is using 1 to 2% of the CPU if it is just sitting there.  When the indexer is running that spikes up to 20% for me but I have seen that go a lot higher.  During a build I will get up to 100% of CPU (but usually just for a second or 2 and it drops back).

    You could try disabling the indexer to see if that helps.  Go to preferences.  Click show advanced settings at the bottom.  Type index in the search box

    I don't like to turn that off as is disables a lot of advanced editor features but it is worth a try.

    When I launch a debug session I see the CPU go up to 160%.  Comes back down but does stay active while running.  Basically the debugger continually polls the target for status.  Usually for me that is under 10%.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 945 points

    Hi guys! 

    Thank you for your input! 

    I managed to solve the problem by deleting all files related to CCS and reinstall custom CCS (with packages and library that i need) and now it works flawless! 

    Regards,
    H