robotics-university.com | Hello my friends, I hope you are always in good condition. Now, on this article, I will give information about an integrated development environment (IDE) software that provided by Texas Instruments (TI). The IDE that I mean is Code Composer Studio or sometime I call it with CoCo Studio. Figure 1 show us the CoCo Studio opening display.
Figure 1. Code Composer Studio - Opening display
Figure 2. Code Composer Studio - main page
What Can We Do with Code Composer Studio?
Once you open the Code Composer Studio, you can do all of activities below:
I. Preparation – Learning before working
1. Learn how to use Coco Studio to get started build an embedded systems project by browse and read project example, training, and documentations.
Figure 3. Resource Explorer feature
2. Learn how to perform various tasks from video tips
Figure 4. Video tips feature
II. Getting Started to Develop an Embedded Systems Project
1. Install additional tools (For instance: SimpleLink SDK, MSP432Ware, FreeRTOS, etc.) after knowing the function if it applied to a special project from Resource Explorer and Video tips.
Figure 5. Install additional tools
2. Create new project or import existing example project from Resource Explorer
Figure 6. Create a new project
Figure 7. Import existing project
3. Write your program on the text-editor.
Figure 8. Write program on the text-editor
4. Build/Compile your program when it is finish created.
Figure 9. Step to build/compile program
5. Debug your program to know if your program still has errors or not.
Figure 10. Step to debug program
6. Load your program to the microcontroller chip.
Figure 11. Step to load program to the microcontroller chip
III. Access Technical Support Forum
If there are some difficulties when you working with Code Composer Studio, you can try to get the solution by ask about your problem to the support forum (E2E forums) or by read topics discussion on that forum which has related with your problem, in order your problem solved.
Figure 12. Support forum feature
IV. Trace the Energy consumption of your embedded systems
EnergyTrace software for MSP430 MCUs, MSP432 MCUs, CC13xx wireless MCUs and CC26xx wireless MCUs is an energy-based code analysis tool that measures and displays the energy profile of an application and helps optimize it for ultra-low-power consumption.
Figure 13. Energy Trace technology feature
V. Using Analysis and Optimization Tools
CCS includes several productivity tools and views to help you analyze and optimize your application. Some of these are described below.
1. ULP (Ultra-Low Power) Advisor (for MSP430 MCU)
ULP Advisor is a static code analysis tool that scans source code against a thorough set of low-power coding rules to help squeeze every last nano amp out of your application. ULP Advisor is enabled by default for MSP430 projects and can be enabled for ARM projects. The analysis runs as part of the build. Any notifications and remarks to highlight areas of code that can be further optimized will be displayed in the Advice view.
Figure 14. Advice tab - Power ULP Advice (for MSP430 MCU)
Selecting an item in the Advice view will open detailed information on the rule that triggered the advice as well as example code that shows how to improve the application for better power usage. It is then up to the developer to either act on the advice or leave their application as-is.
Figure 15. Detail information of an item on the Advice tab
2. Optimizer Assistant
Optimizer Assistant is a static code analysis tool that scans source code and provides advice on how the code could be changed to improve performance. In addition it can also help with determining the ideal set of build options for obtaining the best optimization while staying within code size constraints. The initial analysis of the source code takes place automatically during the build and any advice will display in the Advice view. Selecting an item in the Advice view will open up a window providing more information on how the code may be improved.
Figure 16. Advice tab - Optimization advice
To determine the ideal set of build options for your project, select the Optimizer Assistant from the View menu. Click on Start Analysis to begin the analysis.
Figure 17. Optimizer assistant
3. Code Generation Tools XML Processing Utilities
This is a package of command line utilities used to process the XML files that come from the TI code generation tools. Use it to do things like build a spreadsheet that details the size of all the sections, or figure out how much of the memory map is taken up by specific libraries.
4. Memory Allocation view
The Memory Allocation View in Code Composer Studio provides a graphical representation of how much memory is consumed by your application. To open the view go to the CCS menu View and select Memory Allocation. By default, the view shows the memory used relative to the total available memory for the project that is active in the Project Explorer view. You can expand each memory region to see how much memory each individual section or sub-section is using.
Figure 18. Memory Allocation tab
5. Stack Usage View
The Stack Usage View in Code Composer Studio (available in CCS 6.2 and higher) provides a static view of stack usage for your application. The information is generated on project build and displayed as a function call tree with stack usages for each function in a horizontal bar graph. To open the view go to the CCS menu View and select Stack Usage.
Figure 19. Stack usage tab
The view shows Exclusive Size and Inclusive Size by function. The Exclusive Size is the amount of stack required by that function, ignoring any functions it may call. The Inclusive Size is the amount of stack required by that function, plus the amount of stack required by all the functions called by that function, applied recursively. So, if f1 calls f2, which calls f3, which calls f4, and so on, the amount of stack required by each of those functions is added in for the Inclusive Size.
The size values shown in the view are in bytes. The color shading indicates whether you are close to the limit of available stack space (shown as yellow) or not (shown as green). To avoid hitting the limit, you could free up some stack usage or increase the system stack size.