How autoas/ssas-public works
Main Components
a. Infrastructure Layer (infras/)
• Communication Stack
• AUTOSAR Communication Modules (CanIf, CanTp, LinIf, LinTp, PduR, Com)
• Network Protocols (SOME/IP, DoIP, SD, TCP/IP)
• Diagnostic Stack (Dcm, Dem)
• Memory Stack (NvM, Fee, Ea)
• System Services (OS, File System, Shell, Timer, Trace)
• Libraries (CRC, DDS, Memory Pool, Utils)
b. MCAL Layer (infras/mcal/)
• Hardware Abstraction (Eep, Fls)
c. Application Layer (app/)
• Main Application
• Bootloader
• Platform-specific code
• Example Applications
d. Tools Layer (tools/)
• Generators
• GUI Tools (asone)
• Libraries (CanLib, LinLib, DevLib)
• JSON Editor
┌─────────────────────────────────────────────────────────┐
• Application Layer │
• (Application, Bootloader, Examples) │
• ┤
• RTE Layer │
• ┤
• Services Layer │
• ┌─────────────┐ ┌──────────────┐ ┌──────────────────┐ │
• Communication│ │ Diagnostics │ │ Memory Services │ │
• (COM/NM) │ │ (DCM/DEM) │ │ (NVM/FEE) │ │
• ┘ └──────────────┘ └──────────────────┘ │
• ┤
• MCAL Layer │
• (Hardware Abstraction - CAN, LIN, EEP, FLS) │
• ┘
Key Relationships
• Data flow between communication modules (CAN/LIN → TP → PDU Router → COM/DCM)
• Diagnostic request/response paths
• Memory management flow
• Tool integration points
Additional Elements
• Version information (AUTOSAR 4.4)
• External interfaces (hardware abstraction points)
• Configuration flow from tools to modules
Implementation Details
Remember to include the tools layer as a separate section showing how it interfaces with the main architecture, particularly the configuration and simulation aspects.