Related
Recommended

SimpleLink™︎ Sub-1 GHz Wireless Microcontroller - Side Note: Recognise your Code Composer Studio Sessions

Jan Cumps

I have been blogging on how to make the two seemingly identical LaunchPads distinct, and how to configure Code Composer Studio to recognise them.

 

 

 

We've coloured the labels of our sender and receiver LaunchPad. We coloured the background of our PuTTY sessions to match the two LaunchPads.

Let's do that last step and also make our two Code Composer Studio sessions stand out.

 

Prerequisite is that you finished this activity: Debug 2 LaunchPads at the Same Time.

 

Start CCS and selct the TX workspace.

Navigate to Window -> Preferences

 

You can set any colours you heart pleases. I've changed Current line highlight and Background color.

I coloured the label on my TX LaunchPad red.

For the Current line highlight i selected RGB 255, 155, 155.

For the Background colour: 255, 234, 234.

 

Open your RX workspace, and do the same.

My settings are 153, 197, 251 and 243, 242, 255.

 

The less you have to think about which editor and PuTTY window belong to what LaunchPad, the more brain bandwidth you have left to come with amazing designs.

 

 

 

Hey, I want my original CCS behaviour back, and I still want to use a separate session for RX and TX

 

That's possible.

Restart Code Composer Studio, select your default workspace, and mark the "default" checkbox.

Press OK, and CCS will from now on, by default, open up your generic workspace, as it did originally.

 

Now, make two copies of the CCS shortcut:

 

Call one CCS TX, and change the Target field to : C:\ti\ccsv6\eclipse\ccstudio.exe -data D:\users\jancu\workspace_v6_tx .

(leave everything up to ccstudio.exe as is, and append -data <your TX workspace that you made in this blog post> ).

 

Do the same with the second copied shortcut, but then for the RX workspace.

 

 

You can keep using your original CCS shortcut for the business as usual behaviour. The two other shortcuts will open your TX and RX session respectively, including the colour coding we set up before.

 

 

SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Check  Received Signal Strength
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Use SmartRF to Try Radio Configs
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Debug 2 LaunchPads at the Same Time
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Recognise your PuTTY Sessions
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Recognise your Code Composer Studio Sessions
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Debug a Sender to Receiver Conversation
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note: Start a Fresh Project
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Create a Transmitter with SmartRF Studio Part 1
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Create a Transmitter with SmartRF Studio Part 2
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 1: Dry Run
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 2: RTOS Integration
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Sensor Controller Engine Part 3: Wake Up Options
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - Side Note : Measure Power Use of Sensor Controller Engine
SimpleLinkTm Sub-1 GHz Wireless Microcontroller - ToolKit for Range Testing

on TI E2E community: How to connect a CC1310 LaunchPad to the SIGFOX network

Anonymous

Top Comments

  • The results of my first debug session - using the Packet send/receive example that comes with TIRTOS:

     

     

    This example sends bursts of 30 values from TX to RX. A very simple scenario - but it shows that it's possible to step-debug trough the communications and compare the results to the source.

  • I've added a section at the end on how you can restore the default behaviour of CCS, and select your separate Transmitter and Receiver IDE sessions via shortcuts.