OSEKはもう流行らないのでしょうか。AUTOSAR（64）OSEK（１）

OSEK OSは、AUTOSAR OSの核となっている国際規格です。

AUTOSARが、WTO/TBT違反にならないのは、OSEK OSに基づいているからです。

NM,COMは、OSEK NM, OSEK COMとAUTOSAR COM, AUTOSAR NMに違いがあるそうです。AUTOSARは国際規格の改定を申請したかどうか確認取れていません。

WTO/TBT協定に違反しないためには、
SEK NM, OSEK COMとAUTOSAR COM, AUTOSAR NMの違いの詳細をAUTOSARが公開するとよいでしょう。

では、OSEKはもう流行らないのでしょうか。

どんなものにも、second chanceはあるものです。
OSEKのsecond chanceをさぐってみます。

OSEK: 2013/01/07 
https://researchmap.jp/blogs/blog_entries/view/80826/905e334c1a89a7b2827b6959fea698f9?frame_id=441424

<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.
#  OSEK OSの特徴

## 1 Freestanding env./impl. on C programming language

C言語規格には、OSが起動してから始まるHosted環境と、OSが起動する前から始まる Freestanding環境とがある。
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2596.pdf

>The two forms of conforming implementation are hosted and freestanding. A conforming hosted implementation shall accept any strictly conforming program. A conforming freestanding implemen- tation shall accept any strictly conforming program in which the use of the features specified in the library clause (Clause 7) is confined to the contents of the standard headers float.h,iso646.h, limits.h, stdalign.h, stdarg.h, stdbool.h, stddef.h, stdint.h, and stdnoreturn.h. 

freestanding規格適合は、ヘッダファイルは９つあればいいとさ。stdio.hは、POSIXの機能を利用して実現するらしい。Hostedでは必須。

> 5.1.2 Execution environments
1 Two execution environments are defined: freestanding and hosted. 

実行環境は２つ

>5.1.2.1 Freestanding environment
1 In a freestanding environment (in which C program execution may take place without any ben- efit of an operating system), the name and type of the function called at program startup are implementation-defined. 

freestandingは短く、hostedは長い。

>5.1.2.2 Hosted environment
1 A hosted environment need not be provided, but shall conform to the following specifications if present.
5.1.2.2.1 Program startup
1 The function called at program startup is named main. The implementation declares no prototype for this function. It shall be defined with a return type of int and with no parameters:
int main(void) { /* ... */ }
or with two parameters (referred to here as argc and argv, though any names may be used, as they
are local to the function in which they are declared):
int main(int argc, char *argv[]) { /* ... */ }
or equivalent;10) or in some other implementation-defined manner.

Linux, Unix, Windows, macOSは、Hosted環境で、main関数はOSが起動してから走る。
OSEK OS, AUTOSAR OSは、Freestanding環境で、OSが起動する前に、startup関数が走る。このstartup関数をmainという名前にしても、しなくてもよい。

![autosar.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/51423/0e6f8750-0203-899f-55f4-073f23582016.png)

OSEK OSとAUTOSAR OSの違いは、AUTOSARが拡張部分を持つこと。
![osek.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/51423/754c45ee-2a8b-194e-a382-d21244f5f436.png)

```C:main.c
#include <studio.h>

void main(void){
printf("Hello OS");
}
```

といったプログラムは、厳密にはC言語のHosted環境でのプログラムということになる。

```C:start.c
void start(void){
   init();
   StartOS();
}
```

OSが走るのは、StartOS関数の後。

## 2 割り込み
割り込みは、OSの機能を使わない　NonOS割り込み（分類１）の割り込みと、OSの機能を使うOS割り込み（分類２）の割り込みに分類している。

制御用のNonOS割り込みは、OSの機能よりも優先した設定にする。

OSが割り込みの邪魔をしないような設計になっていると考えることができる。

## 3 タスク
イベント待ちがない基本タスクと、イベント待ちがある拡張タスクとがある。

## 4 レディキューのいらないBCC1、ECC1
基本タスクで優先度ごとに１タスクに限定しているBCC１では、レディキューは要らない。１つのタスクがあるか、ないかだけだから。優先度配列を用意すればよい。

拡張タスクで優先度ごとに１タスクに限定しているECC1でも、レディキューは要らない。１つのタスクがあるか、ないかだけだから。優先度配列を用意すればよい。
Wikipedia
https://en.wikipedia.org/wiki/OSEK

# 課題
いきなり課題でごめんなさい。
##課題1 すべてがISOにはなっていない。
OSEKの文書がすべてISOの文書になったわけではありません。

OSEK Run Time Interface (ORTI)とMODISTARC が国際規格になっていません。

そこで、ISOの前のOSE/VDX当時の文書に戻って考えてみましょう。

## 課題2 古い文書がない
OSEK/VDX文書の半分くらいがWebにない。

Archive上に　OSEK VDX Portal を設けてくださっています。 
https://web.archive.org/web/20110825001222/http://portal.osek-vdx.org/index.php?option=com_frontpage&Itemid=1

リンク切れで文書がないのが半分くらい。
あるいは、時々リンク切れになることがある。

# OSEK
## ISO OSEK
ISO 17356-1:2005
Road vehicles — Open interface for embedded automotive applications — Part 1: General structure and terms, definitions and abbreviated terms
https://www.iso.org/standard/33006.html

ISO 17356-2:2005
Road vehicles — Open interface for embedded automotive applications — Part 2: OSEK/VDX specifications for binding OS, COM and NM
https://www.iso.org/standard/33007.html

ISO 17356-3:2005
Road vehicles — Open interface for embedded automotive applications — Part 3: OSEK/VDX Operating System (OS)
https://www.iso.org/standard/40079.html

ISO 17356-4:2005
Road vehicles — Open interface for embedded automotive applications — Part 4: OSEK/VDX Communication (COM)
https://www.iso.org/standard/40118.html

ISO 17356-5:2006
Road vehicles — Open interface for embedded automotive applications — Part 5: OSEK/VDX Network Management (NM)
https://www.iso.org/standard/40184.html

ISO 17356-6:2006
Road vehicles — Open interface for embedded automotive applications — Part 6: OSEK/VDX Implementation Language (OIL)
https://www.iso.org/standard/40080.html

### ISO OSEK MAP
|ISO|OSEK|
|:--|:--|
|ISO 17356-1:2005Road vehicles — Open interface for embedded automotive applications — Part 1: General structure and terms, definitions and abbreviated terms|
|ISO 17356-2:2005 Road vehicles — Open interface for embedded automotive applications — Part 2: OSEK/VDX specifications for binding OS, COM and NM|
|ISO 17356-3:2005 Road vehicles — Open interface for embedded automotive applications — Part 3: OSEK/VDX Operating System (OS)| OSEK OS|
|ISO 17356-4:2005 Road vehicles — Open interface for embedded automotive applications — Part 4: OSEK/VDX Communication (COM)| OSEK COM|
|ISO 17356-5:2006 Road vehicles — Open interface for embedded automotive applications — Part 5: OSEK/VDX Network Management (NM)| OSEK NM|
|ISO 17356-6:2006 Road vehicles — Open interface for embedded automotive applications — Part 6: OSEK/VDX Implementation Language (OIL)| OIL(OSEK implementation language)|

|OSEK|ISO|
|:--|:--|
|OSEK Binding Specification|part 2|
|OSEK OS|part 3|
|OSEK COM|part 4|
|OSEK NM|part 5|
|OIL|part 6|
|OSEK Run Time Interface (ORTI)|-|
|MODISTARC specifications|-|

## OSEK before ISO
OSEK VDX Portal
https://web.archive.org/web/20110825001222/http://portal.osek-vdx.org/index.php?option=com_frontpage&Itemid=1

OSEK OS 2.2.3
https://www.irisa.fr/alf/downloads/puaut/TPNXT/images/os223.pdf

OSEK COM 2.2.2
https://ptabdata.blob.core.windows.net/files/2017/IPR2017-01519/v7_BMW%20EXHIBIT%201008.pdf

OSEK Binding Specification Version 1.4.2 
https://d1.amobbs.com/bbs_upload782111/files_15/ourdev_446262.pdf

OIL: OSEK Implementation Language Version 2.5
July 1, 2004
http://www.irisa.fr/alf/downloads/puaut/TPNXT/images/oil25.pdf

OSEK NM 2.5.2
https://web.archive.org/web/20120105152556/http://portal.osek-vdx.org/files/pdf/specs/deprecated/nm252.pdf
## table of the documents.
OSEK Run Time Interface (ORTI)
Part A: Language Specification
https://web.archive.org/web/20120118075446/http://portal.osek-vdx.org/files/pdf/specs/deprecated/orti-a-21.pdf

OSEK Run Time Interface (ORTI)
Part B: OSEK Objects and Attributes
https://zbook.org/read/10d413_osek-run-time-interface-orti-2-rts-software-org.html

## Deprecated releases of OSEK specifications

|Title|Document|
|:--|:--|
|OSEK OS Version 2.2.2  ;  Version 2.2.1  ;  Version 2.2  ;  Version 2.1r1|2.2.3|
|OSEK COM Version 3.0.2  ;  Version 3.0.1  ;  Version 3.0  ;  Version 2.2|2.2.2|
|OSEK NM	Version 2.5.2  ;  Version 2.5.1  ;  Version 2.5|2.5.2|
|OSEK Implementation Language (OIL) Version 2.4.1  ;  Version 2.4  ;  Version 2.3|2.5|
|OSEK RTI  (ORTI) Part A Version 2.1|2.1|
|OSEK RTI  (ORTI) Part B Version 2.1|2.2|
|Binding Document Version 1.4.1  ;  Version 1,4  ;  Version 1.3|1.3, 1.4.2|
|OSEK/VDX time triggered operating system n/a||
|OSEK/VDX fault tolerant communication n/a||

MODISTARC specifications

|Title|Document|
|:--|:--|
| OSEK/VDX Conformance Testing Methodology	Version 2.0 ||	 
| OSEK/VDX Operating System Test Plan	Version 2.0|2.0|
| OSEK/VDX Operating System Test Procedure	Version 2.0|2.0|
| OSEK/VDX Communication Test Plan	Version 2.0||
| OSEK/VDX Communication Test Procedure	Version 2.0 ||
| OSEK/VDX Communication Test Suites	Version 2.0||
| OSEK/VDX Network Management Test Plan	Version 2.0 ||
| OSEK/VDX Network Management Test Procedure	Version 2.0||
| OSEK/VDX direct Network Management Test Suites	Version 2.0||
|OSEK/VDX indirect Network Management Test Suites	Version 2.0||

# Related document
## 1
OSEK/VDX-based Dynamic Network Management on Automotive Network
https://www.researchgate.net/publication/224501466_OSEKVDX-based_Dynamic_Network_Management_on_Automotive_Network

Comparison of two types of OSEK network management for CAN
Publisher: IEEE, Chang-Wan Son; Suk-Hyun Seo; Jin-Ho Kim; Key Ho Kwon; Jae Wook Jeon; Sung-Ho Hwang
https://ieeexplore.ieee.org/document/5214720

## 2
A method of implementing network management without OSEK/VDX ^OS, Jin-Ho Kim
School of Information and Communication Engineering, Sung Kyun Kwan University, Suwon, South Korea
; Suk-Hyun Seo; Tae-Yoon Moon; Sung-Ho Hwang; Jae Wook Jeon
https://ieeexplore.ieee.org/document/4406852

## 3
Software Development of OSEK/VDX Direct Network Management
https://www.semanticscholar.org/paper/Software-Development-of-OSEK%2FVDX-Direct-Network-Juang/fdbfccafae28a3719d7ace89d24b07bc2ce05886
## reference on 3
### 3.1
ldquoOpen Systems and their interfaces to electronics in Motor Vehiclesrdquo (OSEK) is a real-time operating system used in vehicle systems. OSEK is a standard operating system used by many
https://www.semanticscholar.org/paper/Analysis-of-implementing-OSEK-NM-with-two-types-of-Son-Kim/69ed87cbc7d0844658f1a43843c337e5e08f2a30
### reference on 3.1
#### 3.1.1
Trends in Automotive Communication Systems
N. Navet, F. Simonot-Lion
Computer Science
Proceedings of the IEEE 2005 TLDR
The context of in-vehicle embedded systems and, in particular, the requirements imposed on the communication systems are introduced and the current efforts of the automotive industry on middleware technologies are reviewed. 
#### 3.1.1.2
Reuse of CAN-Based Legacy Applications in Time-Triggered Architectures
R. Obermaisser
Engineering, Computer Science
IEEE Transactions on Industrial Informatics 2006 TLDR
A validation setup with a time-triggered protocol (TTP) cluster demonstrates that the CAN emulation can handle CAN-based legacy software and a real-world communication matrix provided by the automotive industry. 
#### 3.1.1.3
New demands for invehicle networks
M. Krug, A. Schedl
Computer Science
EUROMICRO 97. Proceedings of the 23rd EUROMICRO Conference: New Frontiers of Information Technology (Cat. No.97TB100167) 1997 TLDR
This paper introduces new demands of safety-critical communication networks in vehicles, exercises the applicability of existing in-vehicle networks and analyses a new approach which is derived from various existing solutions of fault-tolerant communication systems in the field. 
#### 3.1.1.4
An overview of controller area network
M. Farsi, K. Ratcliff, Manuel Barbosa Engineering 1999
The controller area network is a well-established networking system specifically designed with real-time requirements in mind. Developed in the 1980s by Robert Bosch, its ease of use and low cost has… Expand
### 3.1.6
Development of communication framework for unmanned ground vehicle
S. Lee, Dong Myung Lee, J. Lee
Engineering 2008 International Conference on Control, Automation and Systems 2008
This article introduces new concepts for the communication framework of unmanned ground vehicles (UGV). Despite the incompatibility of communication with other UGVs which conform 
### 3.1.8
Expanding Automotive Electronic Systems
G. Leen, D. Heffernan Computer Science Computer 2002 TLDR
Introducing multimedia and telematics to vehicles will increase productivity and provide entertainment for millions, and X-by-wire solutions will make computer diagnostics a standard part of mechanics' work and may even create an electronic chauffeur. 
### 3.1.9
Fuzzy surface-based control for uncertain unified chaotic systems
S. Dadras, H. Momeni, V. J. Majd
Computer Science 2008 International Conference on Control, Automation and Systems
2008

A fuzzy system is used instead of sign function in the sliding mode control to reduce the chattering phenomenon on the sliding surface to determine stability of the fuzzy sliding control law. 
Available: http://www.lin-subbus.org [12] MPC565 Reference Manual 2006
OSEK/VDX Open Systems in Automotive Networks
### 3.1.11
New Demands for In-Vehicle Networks
23 rd EUROMICRO Conference '97 New Frontiers of Information Technology
1997
## 3.2
Design of automotive CAN network management based on OSEK standard
Li Yanwen, Gong Jinfeng, Z. Hongwei, Rong Hui
Engineering
Proceedings of 2011 International Conference on Electronic & Mechanical Engineering and Information Technology 2011
Combined with the study of OSEK network management, the design of CAN network management was mainly introduced in the paper. The design include message, correspondence between message and can frame,
## 3.3
Comparison of two types of OSEK network management for CAN
C. Son, S. Seo, Jinho Kim, K. Kwon, J. Jeon, Sung-Ho Hwang
Engineering 2009 IEEE International Symposium on Industrial Electronics 2009
As the number of electronic control units (ECUs) in vehicles increases, ECUs can create a large and complicated in-vehicle network. Therefore, in-vehicle networks need a network management algorithm… 
### 3.4
Timing analysis of worst case with direct NM of OSEK NM
C. Son, Jinho Kim, T. Moon, K. Kwon, Sung-Ho Hwang, J. Jeon
Engineering 2008 International Conference on Control, Automation and Systems 2008
This paper presents the worst case network situation and the analyzed result for timing test on real embedded system. Timing is critical fact in a specific network. As the needs that vehicle is more… 
### 3.5
Wrapping a real-time operating system with an OSEK compliant interface — a feasibility study
J. Denil, S. Demeyer, P. D. Meulenaere, Kris Vanstechelman, Kurt Maudens
Computer Science
2009 Seventh Workshop on Intelligent solutions in Embedded Systems
2009
TLDR
A feasibility study is reported on to wrap a proprietary real-time operating system with an OSEK compliant interface, and the typical trade-offs one has to make when adopting an incremental migration strategy towards a standard compliant interface are evaluated. 
### 3.6
Notes on DSRC & WAVE Standards Suite: Its Architecture, Design, and Characteristics
Y. Morgan Computer Science IEEE Communications Surveys & Tutorials 2010 TLDR
This paper focuses on the core design aspects of DSRC which is called Wireless Access in Vehicular Networks (WAVE), and describes some of the lessons learned from particular design approaches. 
### 3.7
ITRI WAVE/DSRC Communication Unit
Hsia-Hsin Li, K. Lin
Computer Science 2010 IEEE 71st Vehicular Technology Conference 2010
We prepared three demonstration scenarios to show IWCU capacity, the Dynamic Traffic Warning (V2R) scenario, Video Streaming (V2R) scenario and Vehicle Alert (V2V).
### 3.8
Design of automotive CAN network management based on OSEK standard
Yanwen Li, Jinfeng Gong, Hongwei Zhang, Hui Rong
Computer Science EMEIT 2011
## 4
OSEK/VDX
https://ptolemy.berkeley.edu/projects/chess/design/2012/lectures/EE249_14_OSEKstandard.pdf

Research for CAN Node Fault Rapid Detection Based on OSEK Network Management
https://www.scientific.net/AMM.128-129.975

The Research of Electronical Control System Based on OSEK/VDX
https://www.scientific.net/AMM.16-19.100

ORIENTAIS: Formal Verified OSEK/VDX Real-Time Operating System
Publisher: IEEE
https://ieeexplore.ieee.org/document/6299224?denied=

On the Implementation of the OSEK/VDX Operating System on Advanced Microcontrollers
https://ieeexplore.ieee.org/document/4400392

Design and Implementation of OSEK/VDX System Generation for Automotive Domain Software Development Platfor
https://link.springer.com/chapter/10.1007/978-3-642-24267-0_12

Verifying OSEK/VDX Applications: A Sequentialization-Based Model Checking Approach
https://www.jstage.jst.go.jp/article/transinf/E98.D/10/E98.D_2015EDP7043/_article

Modeling and verifying the code-level OSEK/VDX operating system with CSP
https://www.researchgate.net/publication/221494553_Modeling_and_verifying_the_code-level_OSEKVDX_operating_system_with_CSP

Standardisation of Open Systems and Corresponding Interfaces for Automotive Electronics OSEK/VDX
https://www.sciencedirect.com/science/article/pii/S1474667017405866

Modeling OSEK/VDX OS Requirements in C
https://www.computer.org/csdl/proceedings-article/apsec/2017/3681a398/12OmNzn392K

A case study: SOFL + model checking for OSEK/VDX application
https://dspace.jaist.ac.jp/dspace/handle/10119/14073

Investigation of Real-Time Operating Systems : OSEK/VDX and Rubus
Pontus Evertsson
https://core.ac.uk/download/pdf/289940543.pdf

OSEK / VDX - SlideShare  JOLLUSUDARSHANREDDY
https://www.slideshare.net/JOLLUSUDARSHANREDDY/osek-vdx

An OSEK-compliant RTOS for the C16x
https://www.embedded.com/an-osek-compliant-rtos-for-the-c16x/

C165 / C167 Using the SSC (SPI) in a Multimaster System
https://www.infineon.com/dgdl/Ap1603210_Using_SSC.pdf?fileId=db3a304412b407950112b41dfeb231af

Verifying OSEK/VDX automotive applications: A Spin-based model checking approach
https://onlinelibrary.wiley.com/doi/abs/10.1002/stvr.1662

Migrating a OSEK run-time environment to the OVERSEE platform
Andreas Platschek
https://static.lwn.net/images/conf/rtlws-2011/proc/Platschek.pdf

Labs Real-Time OS : OSEK/VDX Jean-Luc Béchennec 
http://igm.univ-mlv.fr/~masson/Teaching/IMC5-1EO/osek.pdf

Property-based Code Slicing for Efficient Verification of OSEK/VDX  Operating Systems
https://archive.org/details/arxiv-1301.0042

The OSEK/VDX standard - EE Times India
https://archive.eetindia.co.in/www.eetindia.co.in/ARTICLES/2000MAR/EEIOL_2000MAR03_EMS_INTD_TA.pdf%3FSOURCES=DOWNLOAD

OSEK/VDX conformance testing-MODISTARC Publisher: IET
https://ieeexplore.ieee.org/document/744167


Final Public Report on MODISTARC project - OSEK/VDX
https://www.yumpu.com/en/document/view/48102200/final-public-report-on-modistarc-project-osek-vdx

Methods and tools for the validation of OSEK/VDX based distributed architectures
https://cordis.europa.eu/project/id/FP4_25332

Embedded Systems: Architecture, Programming and Design
https://books.google.co.jp/books?id=pWlbvW0H3IAC&pg=PA495&lpg=PA495&dq=OSEK/VDX++MODISTARC+OSEK+Run+Time+Interface&source=bl&ots=vRwHsc25Uu&sig=ACfU3U0Ot46ECXsDkHZMnSlVnIsWmuDrYQ&hl=en&sa=X&ved=2ahUKEwjcrYXQn73zAhVDE6YKHV14BjcQ6AF6BAgUEAM#v=onepage&q=OSEK%2FVDX%20%20MODISTARC%20OSEK%20Run%20Time%20Interface&f=false

# Programming in the Osek/Vdx Environment
https://jp1lib.org/book/684692/ec6f61?id=684692&secret=ec6f61

## openOSEK.
http://www.openosek.org/tikiwiki/tiki-index.php

## FreeOSEK
http://opensek.sourceforge.net/

# 参考資料(Reference)
aspberry Pi 3 Model B+ 向けにリアルタイムOSを実装してみた話
https://qiita.com/tenkoh2/items/baa8e0b6c09669793b4f

[メモ] TrampolineRTOSでLチカ (OSEK/VDX & AUTOSAR APIにあわせたRTOS)
https://qiita.com/mt08/items/65f2ac9bbdae09a34470

MacでLego Mindstorms NXT環境構築 in 2018
https://qiita.com/vivid344/items/2f23f846cd3b135c5a74

ETロボコン開発環境構築 for Mac
https://qiita.com/tac0x2a/items/b1d82050c660935765ef

## 自己参照(self reference)
OSEKはもう流行らないのでしょうか。AUTOSAR（64）OSEK(1) 
https://qiita.com/kaizen_nagoya/items/b87687254b11f30cc2ee
OSEKを図から理解 OSEK(2) 
https://qiita.com/kaizen_nagoya/items/f87a7ff5aeb63803a022
OSEK OS（AUTOSAR OS）をざっくり理解するには OSEK(3) 
https://qiita.com/kaizen_nagoya/items/c68c0b86b97d4a90e6e2
calloutとcallback, OSEK/VDX OS and AUTOSAR OSEK(4) 
https://qiita.com/kaizen_nagoya/items/b95b81354d07b9172a56
OSEK/VDX ISO and 2.23 OSEK(5) 
https://qiita.com/kaizen_nagoya/items/4d6bcec01e0132f9c41c
OSEK/VDX OSEK(6) 
https://qiita.com/kaizen_nagoya/items/a7720994f2178a15be81
ISO OSEK/VDX and ISO Linux OS 同梱ソースをC++またはRUSTで書く企画　OSEK(7) 
https://qiita.com/kaizen_nagoya/items/27899e936c90b415d700
OSEK 記事で views 100,000を目指して　OSEK(8) 
https://qiita.com/kaizen_nagoya/items/ff45ee55566eeff5f62e
自動車用OSを網羅する OSEK(9) 
https://qiita.com/kaizen_nagoya/items/a61144daf500a3f2b4f4
Smallest Set Profile and Automotive Profile, OSEK(10) 
https://qiita.com/kaizen_nagoya/items/0c5484f6562cc259e7f0
Exclusive Area, OSEK(11)　
https://qiita.com/kaizen_nagoya/items/d87ff4e08378dbcf68a7
自動車のソフトウェア、例えばAUTOSAR の仕事を始めてする方に, OSEK(12) 
https://qiita.com/kaizen_nagoya/items/1832634788c23498e054
名古屋で自動車関係のソフトウェア設計する際にあるといいかもしれない知識, OSEK(13) 
https://qiita.com/kaizen_nagoya/items/9f01d55e4bd0bd931c96
single task os and data, OSEK(14) 
https://qiita.com/kaizen_nagoya/items/6acbd5d2cfd3ed8bca60
AUTOSARといえば O で始まる用語は? OSEK(15) 
https://qiita.com/kaizen_nagoya/items/06c969fe5c4b3e7319e0
Automotive Software Expert Examination Exercise, Examples or Extract. OSEK(16) 
https://qiita.com/kaizen_nagoya/items/1762e0612ef01e036efb
自動運転資料集(1) OSEK(17) 
https://qiita.com/kaizen_nagoya/items/42eb2129e281f25eaab8
TOPPERS of the YearとAUTOSAR, AUTOSAR(39), OSEK(18) 
https://qiita.com/kaizen_nagoya/items/f241bb4a819733110b7a
Autosar 2.0を読む, AUTOSAR(25), OSEK(19) 
https://qiita.com/kaizen_nagoya/items/b44a1047c2c517d522fe
IT関連技術でお世話になった方々, OSEK(20) 
https://qiita.com/kaizen_nagoya/items/8a5bf487594cd106e8b8
AUTOSARの４つの入力, OSEK(21)  
https://qiita.com/kaizen_nagoya/items/72cef6028b9697f7968e
AUTOSAR これだけ知っていればなんとかなる。OSEK(22) 
https://qiita.com/kaizen_nagoya/items/7a63e706bfb8f331cfe4
AUTOSAR based on ISO, OSEK(23) 
https://qiita.com/kaizen_nagoya/items/867a709cdf6f4dbdecc6
AUTOSARと国際規格。AUTOSAR（65), OSEK(24)  
https://qiita.com/kaizen_nagoya/items/4ddba03efb942969b125
AUTOSAR入門, AUTOSAR(16), OSEK(25) 
https://qiita.com/kaizen_nagoya/items/5e43b8ef0935c32ee11d
AUTOSAR 記事1000までの道, OSEK(26) 
https://qiita.com/kaizen_nagoya/items/785473512f5f7f85a6bf
Autosarの課題, OSEK(27)  
https://qiita.com/kaizen_nagoya/items/617d10b0e34143030600
AUTOSAR: The past 20 years and he next 10 years, OSEK(28) 
https://qiita.com/kaizen_nagoya/items/2dab0707c01059c152c4
Autosar文書を読む（準備), OSEK(29)　
https://qiita.com/kaizen_nagoya/items/5f547173544703d267aa
AUTOSARが手に取るように分かるようになる。AUTOSAR(29), OSEK(30)
https://qiita.com/kaizen_nagoya/items/ae092ea6aef89cdc15df
posixとethernet, osekとTCP/IP, osek(31) 
https://qiita.com/kaizen_nagoya/items/73b79a4a56f433bd53c0
斉藤直希「組み込み向けリアルタイムOSの基礎知識を整理する」を整理する, OSEK(32) 
https://qiita.com/kaizen_nagoya/items/d305e83b37d0c57dceb3
TOPPERS活用アイデア・アプリケーション開発コンテスト受賞作品紹介　まとめ作成中, OSEK(33)
https://qiita.com/kaizen_nagoya/items/72b882d96b2841f25faf
はじめてのAUTOSAR(classic platform) ＜エンジニア夏休み企画>【読書感想文】, OSEK(34) 
https://qiita.com/kaizen_nagoya/items/696ad320f76f284664d7
AUTOSARとSimulink: Adaptive Platform, Classic Platformとマルチコア・共通化, OSEK(35) 
https://qiita.com/kaizen_nagoya/items/d613b0b14bfd91989a13
AUTOSAR Abstract Platformへの道（詳細編）, OSEK(36)
https://qiita.com/kaizen_nagoya/items/cb217133884fa0a2c704
building block：AUTOSAR Abstruct Platform , OSEK(37),
https://qiita.com/kaizen_nagoya/items/bf7c17624f648fb9f392
系建築家(system architect)になるには, OSEK(38) 
https://qiita.com/kaizen_nagoya/items/8c341e69233cb32f6275
自己紹介 OSEK(39) 
https://qiita.com/kaizen_nagoya/items/90aa368f296613ec93b5
AUTOSAR 「完全に理解した」, OSEK(40) 
https://qiita.com/kaizen_nagoya/items/51983798ad7902b33cb1

Ethernet 記事一覧　Ethernet(0)
https://qiita.com/kaizen_nagoya/items/88d35e99f74aefc98794

Wireshark 一覧 wireshark(0)、Ethernet(48) 
https://qiita.com/kaizen_nagoya/items/fbed841f61875c4731d0

線網（Wi-Fi）空中線(antenna)(0) 記事一覧(118/300目標)
https://qiita.com/kaizen_nagoya/items/5e5464ac2b24bd4cd001

C++ Support(0)　
https://qiita.com/kaizen_nagoya/items/8720d26f762369a80514

Coding Rules(0) C Secure , MISRA and so on
https://qiita.com/kaizen_nagoya/items/400725644a8a0e90fbb0

Autosar Guidelines C++14 example code compile list(1-169)
https://qiita.com/kaizen_nagoya/items/8ccbf6675c3494d57a76

Error一覧(C/C++, python, bash...) Error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8

なぜdockerで機械学習するか 書籍・ソース一覧作成中 (目標100)
https://qiita.com/kaizen_nagoya/items/ddd12477544bf5ba85e2

言語処理100本ノックをdockerで。python覚えるのに最適。:10+12
https://qiita.com/kaizen_nagoya/items/7e7eb7c543e0c18438c4

プログラムちょい替え（0）一覧:4件
https://qiita.com/kaizen_nagoya/items/296d87ef4bfd516bc394

一覧の一覧( The directory of directories of mine.) Qiita(100)
https://qiita.com/kaizen_nagoya/items/7eb0e006543886138f39

プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945

小川清最終講義、小川清最終講義（再）計画, Ethernet(100) 英語(100) 安全(100)
https://qiita.com/kaizen_nagoya/items/e2df642e3951e35e6a53

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on the individual's experience. It has nothing to do with the organization or business to which I currently belong.
### 文書履歴
ver. 0.01 初稿　20211008 20:00
ver. 0.02 ISO追記 20211008 21:00
ver. 0.03 OSEK document list 20211008 22:00
ver. 0.04 C言語、POSIX、基本タスク、拡張タスク追記 20211008 23:00
ver. 0.05 Freestanding HOSTED 図追記　20211008 24:00
ver. 0.06 Wikipedia 追記 20211009 12:00
ver. 0.06 表追記 20211009 17;00
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
####  Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.