Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

CODECOMPOSER: CCS 20 on windows10

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi Team,

I installed the new released CCS 20.0.0 and there are the three questions as following:


1. By default, all debug probe drivers such as Jlink, xds110, and blackhawk are all installed. If provide installation options,

users can choose to install as needed.

2. The sysconfig stetup is too slow and has noticeable lag, which needs to be optimized. This has always been the case, and the previous CCS12 had the same appearance.

3. The Energy Trace interface is not user-friendly. Can it be made to collect data in real-time and stop when needed? 

Just like silicon labs Energy Profiler or Nordic Power Profiler:

  

https://www.silabs.com/developer-tools/simplicity-studio/energy-profiler

https://docs.nordicsemi.com/bundle/nrf-connect-ppk/page/overview.html

Regards,

Kevin

  • Hi Kevin

    Thank you for the feedback on CCS 20.

    1. By default, all debug probe drivers such as Jlink, xds110, and blackhawk are all installed. If provide installation options,

    users can choose to install as needed.

    Yes this is something we used to have more options with earlier CCS versions. We felt simplifying things would improve the user experience but of course we can always revisit this.

    2. The sysconfig stetup is too slow and has noticeable lag, which needs to be optimized. This has always been the case, and the previous CCS12 had the same appearance.

    Yes there should not be much difference regarding this when using CCS 20 or prior versions. The more complex the sysconfig file, the longer will take to open. The SDK itself can also have a lot of impact on this. 

    3. The Energy Trace interface is not user-friendly. Can it be made to collect data in real-time and stop when needed? 

    I will provide this feedback to the trace team. Thanks

    ki

  • Yes this is something we used to have more options with earlier CCS versions. We felt simplifying things would improve the user experience but of course we can always revisit this.

    I filed a ticket for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12145

    I will provide this feedback to the trace team. Thanks

    I spoke to the trace team and they are aware of this limitation. Real-time collection and update of data is on the roadmap (though the timelines are still not fixed yet).