Skip to content

Commit 2986f0b

Browse files
simon-p-2000simon-p-2000
authored
Merge pull request #77 from CSA-FEDERATE/Add_AGL
add new BB_AutomotiveGradeLinux
2 parents 45fc9ee + 100f5fb commit 2986f0b

File tree

1 file changed

+171
-0
lines changed

1 file changed

+171
-0
lines changed

‎WorkInProgress/BB-SC/2a-OSLayer/Linux/BB_AutomotiveGradeLinux.md‎

Lines changed: 171 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,171 @@
1+
2+
# AGL Automotive Grade Linux
3+
4+
## BB Tags(s)
5+
<!-- Tag(s) define in which area(s) (cloud, in-vehicle) the BB is executed, and what type of BB it is (tool, process, microservice) -->
6+
BB-SC, BB-EST, BB-EST-TC
7+
8+
## Functional Clusters
9+
<!-- In which Functional Cluster the BB be located; if none of the existing fit new required -->
10+
11+
## Layer
12+
<!-- AppLayer, MWLayer, OSLayer, HWLayer -->
13+
APPLayer, MWLayer, OSLayer
14+
15+
## BB Usage
16+
<!-- example on how to use BB or link to documentation -->
17+
18+
## Known Implementation
19+
https://github.com/orgs/agl-ic-eg/repositories?type=all
20+
21+
## ID (unique name)
22+
23+
## Description
24+
<!-- General Description of the BB -->
25+
Automotive Grade Linux is a collaborative, open source project that brings together automakers, suppliers, and technology companies
26+
for the purpose of building Linux-based, open source software platforms for automotive applications that can serve as de facto industry standards.
27+
28+
AGL address all software in the vehicle: infotainment, instrument cluster, heads-up-display (HUD), telematics, connected car,
29+
advanced driver assistance systems (ADAS), functional safety, and autonomous driving.
30+
31+
[source:](https://docs.automotivelinux.org/en/master/##01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images/)
32+
33+
## Rationale
34+
<!-- Explanation why we need the BB; what problem want to be solved -->
35+
Adopting a shared platform across the industry reduces fragmentation and allows automakers and suppliers to reuse the same code base, which leads to rapid innovation and faster time-to-market for new products.
36+
37+
AGL is a Linux Foundation project and its goals are as follows:
38+
39+
Build a single platform for the entire industry
40+
Develop 70 to 80% of the starting point for a production project
41+
Reduce fragmentation by combining the best of open source
42+
Develop an ecosystem of developers, suppliers, and expertise that all use a single platform
43+
44+
[source:](https://docs.automotivelinux.org/en/master/##01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images/)
45+
46+
47+
## Governance Applicable S-BB(s)
48+
<!-- Reference to e.g. UN/EU CRA Cyber Resilience Act; UNECE 156 - Software update and software update management system
49+
Reference to defined S-BB(s)
50+
Reference to e.g. IS026262, AUTOSAR Spec. X -->
51+
TBD
52+
53+
## Compose BB(s)
54+
<!-- Link to required BB(s)
55+
E.g. BB-SC StateManagement
56+
BB is a composition of other BBs -->
57+
[Yocto Project](https://www.yoctoproject.org/)
58+
[QEMU](https://www.qemu.org/)
59+
60+
## What is needed to Design and Implement
61+
<!-- e.g. we expect to have a certain HW capability and or SW environment or Tool support, or a documentation, or an extra audit, or Test, or Compiler, or Prog. Language, … -->
62+
Linux Build System
63+
64+
## What is needed to build and run
65+
<!-- e.g. we expect to have a certain HW capability, or Runtime Environment, or Pre-configuration, or Code-signing, or Test, … -->
66+
67+
See supported [Hardware](https://docs.automotivelinux.org/en/master/#02_Hardware_Support/01_Supported_Hardware_Overview/
68+
69+
70+
## Non-Functional Requirements
71+
<!-- With respect to Safety, Security, Realtime, … -->
72+
TBD
73+
74+
## Dependencies to other Clusters
75+
<!-- Other clusters are needed. FC Security, FC Storage, …
76+
e.g. If FC Security : Security BBs are needed but you can choose for example crypto BB-SC from company A or crypto BB-SC from company B; several compositions may work -->
77+
TBD
78+
79+
## Vehicle API Relevant
80+
<!-- If “Yes exists” – where – e.g. COVESA VSS
81+
If “No” – nothing more to do
82+
If “Yes, proposal for additional Signals/Information – what should be made available, and where e.g. via (COVESA) VSS/VISS -->
83+
Yes - Demonstrator use COVESA VSS implementation
84+
85+
## Author/Company
86+
VIF
87+
88+
## Priority
89+
<!-- High, Medium, Low -->
90+
91+
## Related Project(s)
92+
<!-- If Yes – e.g. The BB should be used/added in the Eclipse Blueprint A – for demo purposes, show added value,
93+
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework -->
94+
TBD
95+
96+
97+
## Availability of Source Code
98+
<!-- Yes / License (e.g. Yes/MIT)
99+
No – Commercial Closed Source -->
100+
YES GPL, MIT
101+
102+
## Availability of API
103+
<!-- Yes / License (e.g. Yes/Apache 2.0)
104+
No - Commercial -->
105+
TBD
106+
107+
## Type of API
108+
<!-- Web API, Library/Framework API, Operating System API, Database API, Remote API, Hardware API, Other -->
109+
TBD
110+
111+
## Potential obstacles
112+
TBD
113+
114+
## Maturity Badges
115+
<!-- taken over from Eclipse SDV Process
116+
See Definition of Badges and their Flavors
117+
https://gitlab.eclipse.org/eclipse-wg/sdv-wg/sdv-technical-alignment/sdv-technical-topics/sdv-process/sdv-process-definition/-/wikis/Definition%20of%20Badges%20and%20their%20Flavors
118+
119+
120+
| | Documentation | Requirements | Coding Guidelines | Testing | Release Process |
121+
| --------- |:-------------:|:------------:|:-----------------:|:-------:|:---------------:|
122+
| Gold | Badgelevel | Badgelevel | Badgelevel | Badgelevel | Badgelevel |
123+
| Silver | Badgelevel | Badgelevel | Badgelevel | Badgelevel | Badgelevel |
124+
| Bronze | Badgelevel | Badgelevel | Badgelevel | Badgelevel | Badgelevel |
125+
| No | Badgelevel | Badgelevel | Badgelevel | Badgelevel | Badgelevel |
126+
| NotDefined| Badgelevel | Badgelevel | Badgelevel | Badgelevel | Badgelevel |
127+
128+
Options:
129+
NotDefined/No/Bronze/Silver/Gold
130+
131+
Example:
132+
| | Documentation | Requirements | Coding Guidelines | Testing | Release Process |
133+
| --------- |:-------------:|:------------:|:-----------------:|:-------:|:---------------:|
134+
| Level | [Gold](urlToDoc)| No | Notdefined | Bronze | [Silver](urlToDoc) |
135+
136+
137+
-->
138+
TBD
139+
140+
## State (+ date of last change)
141+
142+
<!--
143+
- Incubating (no code yet)
144+
- Implementation started
145+
- First public release available
146+
- Used in production by 1 OEM
147+
- Used in production by >1 OEM
148+
- Abandoned
149+
-->
150+
Used in production by >1 OEM
151+
[last change May 2025 visted 16.06.2025](https://github.com/orgs/agl-ic-eg/repositories?type=all)
152+
153+
## System Context
154+
155+
<!--
156+
OS and runtime/framework requirements
157+
158+
eg.
159+
160+
- AGL
161+
- QNX
162+
- ROS-based
163+
- container runtime
164+
- web assembly
165+
- web service
166+
-->
167+
AGL Automotive Grade Linux
168+
169+
## Bazel compliance status
170+
<!-- The S-CORE project requires all BB contributions to be ready for BAZEL compliant (https://github.com/bazelbuild/bazel)-->
171+
TBD

0 commit comments

Comments
 (0)