Skip to content

Project Specification

The project specification is described in the following sections.

Constraints

  • The code delivered to github.com compiles without error and can be flashed to the target device.
  • The program must run without error on the target device.
  • Your Zephyr RTOS workspace uses the T3 topology. Each application (e.g. “Blinky” or “BikeComputer”) is delivered as a separate application using the same manifest. These applications are located at the root of the workspace root folder, in a folder named after the application (like “blinky” or “bike_computer”).
  • The manifest folder is named “manifest-repo”.

Note that any major deviation from these rules may lead to the project not being considered for the lecture grade.

Phase A: Project infrastructure

Requirements for all phases

  • Requirement: The folder structure is identical to the one documented in the different codelabs. For instance, the blinky application program is located in the {{ blinky }} folder at the root of the workspace.
  • Requirement: Your GitHub repository exists and has been shared. It follows all rules and directives defined under project organization.
  • Requirement: A tag named “Phase-X” is added to your github repository for each phase.

Expected Deliverables/Requirements

  • Deliverables/Requirements of the Getting Started codelab.

  • Deliverable/Requirements of the Improving Software Quality codelab.

  • The test programs are added as part of the Blinky program under the blinky folder.

  • Deliverable: The Github workflow is configured correctly and runs without error. It includes the build of the “ptr_test” program that you have developed. The “ptr_test” program includes the tests described in the unique_ptr and raw pointers exercises.