#rLoop Pod Firmware Lachlan Grogan

Please make sure you review our code standards and contributing document. Also check out our Confluence Avionics pages.

Setup Development Tools:

The project uses the Texas Instruments Code Composer Studio (TI CCS) integrated development environment.

1. Get TI CCS V6.1.2.00015 or latest version from the tools folder for any platform here.
2. When installing make sure you have setup for TI RM4 support.

GIT:

The project uses Git for source code management Git documentation. The source code resides in a Github repository.

1. Install Git Desktop
2. Clone github.com:rLoopTeam/eng-software-pod into a folder.

CCS - Initial Use

CCS relies on the notion of a workspace, you need to create a workspace folder and then import the projects into the folder.

1. Create a folder at FIRMWARE\WORKSPACE or FIRMWARE\VERIFICATION\WORKSPACE
2. Open CCSV6
3. When prompted, enter the full path to the workspace folder on your local drive.
4. Choose File->Import and select any of the firmware projects under the firmware root or any projects under the verification root.
5. Paths should be good to go.
6. Avoid committing anything from the WORKSPACE folders. The .gitignore file is set up to handle this automatically.

Compiler Version

We are using the TI ARM v15.12.3.LTS (Long Term Support) C Compiler which has already been configured in the project files.

1. Open a CCSV6 workspace
2. Choose Help -> Install new Software
3. From the drop down list box "work with:" Choose --All Available Sites--
4. Expand TI Compiler Updates
5. Select ARM Compiler Tools Version 15.12.3
6. Choose Next/Finish and follow the prompts

Project Description

• At the top level of the directory there’s FIRMWARE, APPLICATIONS, PodAppLayer, etc. FIRMWARE contains our code that will be on the pod, the others are primarily for emulation with CCS/VS.
• Most of the time, FIRMWARE can be thought of as our root.
• Code not specific to our hyperloop pod (e.g. TSYS01 temp sensor's driver), is located in COMMON_CODE.
• Within that dir, code is divided up between what is 'RM4' specific (our mcu) versus code that can be used with various mcu’s, 'MULTICORE’.
• PROJECT_CODE is where code unique to our pod should be.
• VERIFICATION will eventually be filled with files meant to test the code in COMMON_CODE and PROJECT_CODE.
• Names of particular drivers/nodes are prepended with a part number. Go to FIRMWARE/COMMON_CODE/MULTICORE/.
• Everything begins with LCCM (think "Lachlan's Common Core Module") with a product number attached to it, and then a double underscore.
• Next is the category it's under, in this case 'MULTICORE', and another double underscore.
• Filenames end with a description of the hardware or what exactly the code is doing, e.g. 'TSYS01' or 'Software_CRC'

rPod Toolbox Notes

The rPod Toolbox is a VB.NET application developed in tandem with the embedded firmware. It can be found in eng-software-pod\APPLICATIONS\LAPP188__RLOOP__RPOD_CONTROL\bin\Debug\LAPP188__RLOOP__RPOD_CONTROL.exe It is dependent on proprietary libraries so you will not be able to compile it from scratch. To use it with the TI Launchpad hardware, your computer will need to be on a 192.168.0.0/24 subnet and you'll need libpcap installed. Many of the functions in the rPod Control Toolbox are available with the react-groundstation as well.