How renatosoriano/coursera_introduction-to-embedded-systems-software-and-development-environments works
Main Components
• Assignments Modules:
– Assignment 1 (C1M1) for statistical data analysis.
– Assignment 2 (C1M2) which provides a build system that supports two target platforms (host and MSP432) and includes platform-specific files (CMSIS and MSP432 headers).
– Assignment 3 (C1M3) focused on memory allocation and symbol placement analysis.
– Final Assessment that integrates multiple functionalities (extended C-code modules, build system, host and target support).
• Shared/Supporting Materials:
– Course Notes detailing development components, compilation with GCC/Make, and memory management.
– Quick Reference and Syllabus for overall project context.
• External Tools and Environment Requirements:
– GCC and GNU Make (as indicated by the Makefiles and README setup).
– Development environment (Ubuntu with tools like VS Code/Sublime Text and products like VirtualBox, VMware, or Parallels for cross-platform development).
Relationships and Interactions
• Each assignment acts as a standalone module with its own source (in src), header files (in include folders), and build scripts (Makefile, sources.mk).
• All modules use similar conventions for handling CMSIS and MSP432-specific configurations for embedded targets.
• The build system in Assignment 2 and Final Assessment clearly differentiates between compiling for the host system versus the embedded MSP432 target. Represent the two flows:
• One flow for host compilation (simulation on Ubuntu).
• One for cross-compiling to the MSP432, using specific linker scripts (msp432p401r.lds) and startup files.
• Documentation (course notes and README) supports understanding and step-by-step instructions but also interconnects with the assignments via embedded screenshots and explanations.
Architectural Patterns and Design Principles
• Modularity: Each assignment is modular with distinct examples of C programming application (analytics, memory management, build systems).
• Separation of Concerns: The repository separates source code, configuration (headers, linker scripts), and documentation.
• Platform Abstraction: There is a clear abstraction separating host simulation from target (MSP432) code paths, emphasizing the use of configuration macros (e.g., PLATFORM flag in Makefiles).
• Use of standardized directory structures for embedded projects (such as include folders with CMSIS and msp432 directories).