DPP on EK-TM4C123GXL

Table of Contents

• Features Demonstrated
• Running the Example
• Unit Testing
• QP/Spy Software Tracing

This example implements the Dining Philosophers Problem sample application on the EK-TM4C123GLX board (ARM Cortex-M4F).

EK-TM4C123GXL board

The DPP example is located in the directory qpcpp/examples/arm-cm/dpp_ek-tm4c123gxl, which is organized as follows:

qpcpp/                    // QP/C++ installation directory
 +-examples/              // QP/C++ examples directory (applications)
 | +-arm-cm/              // QP/C++ examples for ARM Cortex-M
 | | +-dpp_ek-tm4c123gxl/ // DPP example on the EK-TM4C123GLX board
 | | | +-lint/            // PC-Lint version (static analysis of the application code)
 | | | | +-lin.bat        // batch file for running the PC-Lint
 | | | | +-options.lnt    // PC-Lint options file for the DPP application code
 | | | +-qk/              // QK version
 | | | | +-arm/           // ARM-KEIL toolchain
 | | | | | +-dpp-qk.uvprojx // uVision project
 | | | | +-gnu/           // GNU-ARM toolchain
 | | | | | +-Makefile     // Makefile for building the project
 | | | | +-iar/           // IAR-ARM toolchain
 | | | | | +-dpp-qk.eww   // IAR EW-ARM workspace
 | | | | +-ti/      // TI-ARM toolchain (CCS)
 | | | | | +-.ccsproject  // CCS project
 | | | | | +-.cproject    // C Eclipse project
 | | | | | +-.project     // Eclipse project
 | | | | +-bsp.cpp        // BSP for the QK kernel
 | | | | +-main.cpp       // main() for the QK kernel
 | | | +-qv/              // QV version
 | | | | +-arm/           // ARM-KEIL toolchain
 | | | | | +-dpp-qk.uvprojx // uVision project
 | | | | +-gnu/           // GNU-ARM toolchain
 | | | | | +-Makefile     // Makefile for building the project with GNU-ARM
 | | | | +-iar/           // IAR-ARM toolchain
 | | | | | +-blinky-qk.eww  // IAR EW-ARM workspace
 | | | | +-bsp.cpp        // BSP for the QV kernel
 | | | | +-main.cpp       // main() for the QV kernel
 | | | +-qxk/             // QXK version
 | | | | +-arm/           // ARM-KEIL toolchain
 | | | | | +-dpp-qk.uvprojx // uVision project
 | | | | +-gnu/           // GNU-ARM toolchain
 | | | | | +-Makefile     // Makefile for building the project
 | | | | +-iar/           // IAR-ARM toolchain
 | | | | | +-dpp-qk.eww   // IAR EW-ARM workspace
 | | | | +-ti/            // TI-ARM toolchain (CCS)
 | | | | | +-.ccsproject  // CCS project
 | | | | | +-.cproject    // C Eclipse project
 | | | | | +-.project     // Eclipse project
 | | | | +-bsp.cpp        // BSP for the QXK kernel
 | | | | +-main.cpp       // main() for the QXK kernel
 | | | | +-test.cpp       // extended (blocking) test threads
 | | | +-qspyview/        // visualization and monitoring for the DPP example
 | | | | +-dpp.tcl        // QSpyView specialization for the DPP
 | | | | +-qspyview.bat   // batch file for launching QSpyView for DPP

Features Demonstrated

• cooperative QV kernel
  • with ARM-KEIL toolchain
  • with GNU-ARM toolchain
  • with IAR-ARM toolchain
  • with TI-ARM toolchain (CCS)
• preemptive run-to-completion QK kernel
  • with ARM-KEIL toolchain
  • with GNU-ARM toolchain
  • with IAR-ARM toolchain
  • with TI-ARM toolchain (CCS)
• preemptive dual-mode QXK kernel
  • with ARM-KEIL toolchain
  • with GNU-ARM toolchain
  • with IAR-ARM toolchain
  • with TI-ARM toolchain (CCS)
• QP/Spy software tracing (output)
• QP/Spy software tracing (input QS-RX)
• Unit Testing with QUTest
• Windows emulation with GUI (multithreaded)
• Windows emulation with GUI (single threaded, win32-qv)

Running the Example

Once programmed into the board, the example rapidly toggles the Blue LED from the idle loop (blue LED glows) and toggles the Red and Green LEDs as the Philosophers change their state. Additionally, you can depress and hold the SW1 button (left) to PAUSE the application (Table transitions into the "paused" state). Releasing the SW1 button causes transition back to the "serving" state.

Unit Testing

The examples demonstrates the QUTest unit tests for the application.

QP/Spy Software Tracing

The application also demonstrates QP/Spy software tracing output and input. To exercise this feature, you need to build and upload the Spy build configuration into the board.