A log of my experience.
I tried Energia and CCS Cloud but ran into their limitations.
Apparently CCS Cloud is usually for running their example projects. My code initially used the TI MSPWare.DriverLib libraries, and the Energia SPI librares. I had difficulties using those libraries in CCS Cloud. I started with an example project for DriverLib. It was configured for the MSP430FR4133 chip, and I could not seem to reconfigure the project for the MSP430FR2433 chip on the MSP-EXP430FR2433 Launchpad.
So I decided to byte the bullet and use CCS Desktop. It is not a big leap for Eclipse IDE users, since apparently CCS is based on Eclipse.
Install dependent library.
sudo apt install libc6-i386
Download and extract the installer.
Execute the installer. It has a .bin suffix that is foreign to Linux, so you can’t just click on it.
cd <install location> ./cc*.bin
Expect it to take a while, since it is downloading over the net. I assume you install to default ~/ti
cd ~/ti/ccsv8/install_scripts sudo ./install_drivers.sh
Expect the command to return quickly. I think it sets up udev for the USB link to your Launchpad.
After this, expect an icon for Code Composer Studio on your desktop, that works.
This worked for me on Ubuntu 16.04, CCS 8.1.0
Initial experience with CCS Desktop
It almost immediately asked me to update, which I did, although it seemed to be only Help files.
In the initial “Getting Started” screen, I chose “Would you like to use CCS in ‘Simple’ mode?”.
Now since I had previously used a DriverLib example project while evaluating CCS Cloud,
(You can program at the HAL level, using names of registers and bits, or use DriverLib, which abstracts the hardware to a higher level. I had already coded to use DriverLib, and implemented my own library for SPI that used DriverLib.)
I used “Resource Explorer” to navigate to and download that same example project.
Import example project from MSPWare
In the "Getting Started" panel, choose "Resource Explorer" Choose "MSP430Ware" icon Navigate to "Libraries/Driver Library/MSP430FR2xx_4xx/ Example Projects/00_EMPTY_Project/emptyProject Select emptyProject (single click on it) Choose the "Import to IDE" icon in upper right.
(Don’t choose “Download and Install” icon. Apparently that downloads ALL the example projects for MSPWare, quite a lot.)
Expect the “emptyProject” project to appear in the IDE in the “Project Explorer” panel.
Put your own source in the project
I copied my /src folder from a github repository into the project. Use copy and paste.
Choose the “Build” icon (looks like a hammer.)
Now I ran into the compile error I had with CCS Cloud: the project is configured for the wrong target FR4133 instead of FR2433, and the macro symbol ESUCI_A1_BASE was missing. (This in only because I foolishly used a high numbered device that is present on some chips and not on others. Use low numbered devices, UCA0 or UCB0 instead of UCA1).
Retarget the project
This is more or less standard Eclipse stuff.
Click on the project ("emptyProject" row) with the right mouse button. Expect a pulldown. Choose "Properties" Expect a dialog. Left mouse button click on "General" Expect the right panel to change. Under the "Project" tab, in the "Variant" field, choose the down arrow. Expect a list of chips. Select "MSP430FR2433" (the one on the MSP-EXP430FR2433 LaunchPad) Choose "Apply and Close"
Now if you rebuild, expect a cleaner compile. (In my case, I forgot to delete the main.c from the example, and had provided a duplicate main.c in my own /src.)
Another reason I wanted to switch from CCS Cloud or Energia to CCS Desktop is for more sophisticated debugging. The CCS Cloud debugger is limited.
Plug in the USB cable of the Launchpad. Choose the "Debug" icon (looks like a bug.) Expect a dialog saying "Initializing debugger first time..." Expect another dialog saying "Loading program..." Expect main.c to open in the edit panel, with the first line of code highlighted. Expect the icons in the toolbar to include "Step into", "Step over", etc.
You can also change the Eclipse “Perspective” using an icon in the upper right. You can change from the “Simple” perspective (because I chose “Simple” from the Getting Started panel) to the “CCS Debug” perspective, which will let you examine memory etc.
You are on your way…