How saharelnagar/ota_graduationproject2020 works
Project type and purpose
• This is an embedded, multi-ECU system implementing Over-The-Air (OTA) firmware updates for a smart vehicle.
• Key subsystems are:
• GateWay_ECU — a TI TM4C123-based CAN gateway running AUTOSAR-style BSW, RTE, and application SW-C modules handling download, decryption, storage, and distribution of updates.
• STM_ECU — an STM32F4-based LCD controller with its own bootloader and display application.
• TivaC_ECU — another TM4C123-based module with bootloader and gateway code (parallel or legacy).
• Telematics Unit — an ESP8266/ESP32 Arduino sketch connecting to the cloud to fetch updates.
File structure
• GateWay_ECU/software/BSW, RTE, SW_C → layered AUTOSAR BSW (MCAL, Communication, Memory, Infrastructure), RTE interface, and Software Components (Decryption_SWC, DownloadUpdate_SWC, StoreUpdate_SWC, TransmitECUsUpdate_SWC).
• GateWay_ECU/software/build → Code Composer Studio project for TM4C.
• STM_ECU folder: Atollic projects for LCD application and bootloader, plus resource packages for UI pages.
• TivaC_ECU: Keil/UVision and project structure mirroring GateWay functionality and bare-metal driverlib.
• Telematics Unit: single Arduino .ino sketch.
README
• Title “OTA_GraduationProject2020” confirms an OTA update use case for vehicle electronics.
Main components and their interactions
a. Hardware nodes:
• Telematics Unit (ESP32)
• CAN Bus (physical network)
• Gateway ECU (TM4C123)
• Secondary ECUs: STM_ECU (STM32F4 LCD), TivaC_ECU (TM4C123)
• Non-volatile Flash memory on each ECU
• Cloud update server (external service)
b. Software layers inside each ECU:
• MCAL/DriverLib → direct hardware interfaces (CAN driver, UART, GPIO, Flash/Eeprom)
• BSW modules → CANIf, MemIf, Ea/Eep/Fls/Fee, NvM, Platform/Infrastructure
• RTE → virtual bus abstracting inter-SWC calls
• SW-C modules → DownloadUpdate, Decryption, StoreUpdate, TransmitECUsUpdate
• Bootloader (separate build target)
• Application (LCD or gateway logic)
c. Data flows:
• Cloud → Telematics Unit over Wi-Fi (HTTP/MQTT)
• Telematics Unit → Gateway ECU over UART or CAN
• Gateway ECU SW-C DownloadUpdate → decrypt → write to Flash via MemIf/Eep → confirm
• Gateway ECU → Broadcast new firmware packages to STM_ECU & TivaC_ECU over CAN
• Each ECU’s bootloader verifies and flashes new application image
Architectural patterns and technologies
• AUTOSAR-inspired layered architecture in GateWay_ECU (separation of MCAL, BSW, RTE, SW-Cs)
• Bare-metal RTOS-less approach with startup code, interrupt handlers
• Bootloader-application separation
• CAN network for intra-vehicle communication
• Wi-Fi/Arduino for telematics/cloud link
• Use of CCS and Keil toolchains