5 Code Composer Studio tricks that even Ki-Soo Lee himself doesn't know

Guest blog authored by  in celebration of Ki-Soo Lee Day Monday, April 25th. #KiSooLeeDay

1. Use the Git plug-in


Software geeks have known it forever that version control is your friend. And this friend is available to firmware gurus too: The Eclipse Git Team Provider.

Get yourself a GitHub account and you’ll never ever have to fear again to start that refactoring exercise that you know your project will need.


2. Install a PDF viewer

It’s nice to view your datasheets from within the IDE. From there you can create a folder named documentation under your project root (and exclude it from build). Then add a link to all the documents relevant to the project. Use the New --> File --> Advanced --> Link to File in the File System option to hook a link to the files into the project.

Next, install a PDF viewer. There are several options available. I use PDF4Eclipse. Double-click on the document in the Project explorer and it opens in the editor pane.


3. Use the todo/task view

This one is very simple to perform. To execute it: When there something in your code that needs attention later, just add a todo comment.

Example:


Then add the task view to your IDE via View --> Other --> Generic --> Task.


4. Use the graph view to show memory content

To see your memory content as a graph (very useful if you have an array of samples), right click on the array in debug mode --> from Variables or Expression Window --> and select Graph.

Additional details are in the CCS Help. Go to Help --> Search and type "graph" in the search box.


5. Use the telnet client

There's a terminal emulator inside Code Composer Studio. It's available via View --> Other --> Terminal.

This is extremely handy as you can now read output and send input while debugging. You don’t have to leave the editor.


Happy Ki-Soo Lee Day!