EK_LM4F232 for CCS4 and FreeRTOS 7.1.1

This port is written for the TI Stellaris LM4F232H5QD Evaluation Board using Code Composer Studio 4.  It creates several tasks which demonstrate the operation of FreeRTOS semaphores, signalling from an ISR, Cortex-M4F FPU register context switching, and I/O with the UART and OLED.  It creates a CLI on the EK-LM4F232 ICDI UART which allows executing commands. The commands supported are: 

  •     color:    Controls the color mode on the OLED.
  •     cpu:       Shows CPU utilization.
  •     fputest:  Performs an FPU context switch test for the specified number of seconds.  Can be ran multiple times to create additinal tasks.
  •     free:       Reports free heap memory available.
  •     tasks:    Displays a list of currently running tasks

To use this port:

  1. Ensure Code Composer Studio 4 is installed in your Windows environment.
  2. Install the Evaluation Board ICDI drivers from the kit provided by TI.
  3. Ensure the EK-LM4F232H5QD Eval Board is plugged into a USB port and the drivers have detected it.
  4. Determine the COM port assigned to the Eval Board ICDI UART (using Windows Device Manager / Ports (COM & LPT).
  5. Launch Windows Hyperterm or other terminal emulation program and configure it for 115200 baud on the ICDI com port.
  6. Extract the LM4F232_CCS4.zip file to a directory in Windows and launch Code Composer Studio.  
  7. From the Project menu of CCS4, choose "Import Existing CCS/CC# Eclipse Project"
  8. Browse to the FreeRtosLm4f project directory where the files were extracted and click Finish.
  9. Right-click on the "Prj" project and select "Set as Active Project".
  10. From the Project menu, select "Build Active Project".
  11. From the Target menu, select "Debug Active Project' or click the "Debug Launch" icon on the toolbar.  CCS will download the application to FLASH using the 1st 
  12. From the Target menu, select "Run" or click the Run icon on the toolbar.  The demo should now be running with activity on the OLED, user LED and com port.
  13. Type commands at the CLI to test functionality.

I hope this is useful!





Please sign in to leave a comment.