Specification of I/O Hardware Abstraction, AUTOSAR R22-11, CP, No.47
AUTOSARが、2022年の版、R22-11公開しました。公開行事の模様は
AUTOSAR R22-11 Release Event 20221208
下記URL順次確認中です。
間違っていたら、いいね を押していただいて、コメント欄にご報告くださると幸いです。
編集リクエストが、構造的な変更をしている最中に、構造的な編集リクエストをしていただくと、
何をどう直したらいいかわからなくなってしまいます。自動修復ツールがつくれていません。ごめんなさい。
文書は検索してダウンロードすることができます。
クラウドサービスにありがちな、あるのにないかのような検索結果が出ることがあります。
要求仕様対応(Requirement and Specification)
一覧
AUTOSAR R22-11 Classic Platform 一覧はこちら。
Classic Platform Release Overview, AUTOSAR R22-11, CP, No.0(2)
AUTOSAR R22-11 マラソン
Qiitaの記事の一覧は作成中です。
AUTOSAR R22-11 一覧（２）
Abstract Platformとの関係
個々のドライバごとの対応関係を明記し、Power Managementという名称に変更をしたい。
<この項は書きかけです。順次追記します。>
文書変更(Document Change)
Changed SWS_IoHwAb_00145 to SWS_IoHwAb_NA_00145
用語(terms)
| Expression | Description | Example |
|---|---|---|
| AUTOSAR | AUTomotive Open System ARchitecture | |
| API | Application Programming Interface | |
| BSW | Basic SoftWare | |
| BSWMD | Basic SoftWare Module Description | |
| C/S | Client/Server | |
| DET | Default Error Tracer | |
| ECU | Electronic Control Unit | |
| HW | HardWare | |
| IoHwAb | Input/Output Hardware Abstraction | |
| ISR | Interrupt Service Routine | |
| MCAL | MicroController Abstraction Layer | |
| OS | Operating System | |
| RTE | RunTime Environment | |
| S/R | Sender/Receiver | |
| SW | SoftWare | |
| SWC | SoftWare Component (see [8] for further information) | |
| XML | eXtensible Markup Language | |
| Callback | Within this document, the term ‘callback’ is used for API services, which are intended for notifications to other BSW modules. | |
| Callout | Callouts are function stubs, which can be filled at configuration time, with the purpose to add functionality to the module that provides the callout. | |
| Class | A class represents a set of signals that has similar electrical characteristics. | Analogue class, Discrete class, … |
| Client / Server communication | This definition is an extract from [9]: Client-server communication involves two entities, the client which is the requirer (or user) of a service and the server that provides the service. The client initiates the communication, requesting that the server performs a service, transferring a parameter set if necessary. The server, in the form of the RTE, waits for incoming communication requests from a client, performs the requested service and dispatches a response to the client's request. So, the direction of initiation is used to categorize whether an AUTOSAR Software Component is a client or a server. | |
| Electrical Signal | An electrical signal is the physical signal on the pin of the ECU. | Physical input voltage at an ECU-Pin |
| ECU pin | An ECU pin is an electrical hardware connection of the ECU with the rest of the electronic system. | |
| ECU Signal | An ECU Signal is the software representation of an electrical signal. An ECU signal has attributes and a symbolic name | Input voltage ,Discrete Output, PWM Input |
| ECU Signal Group | An ECU Signal Group is the software representation Specification of I/O Hardware Abstraction of a group of electrical signals. | |
| Attributes | Characteristics that can be Software (SW) and Hardware (HW) for each kind of ECU signals existing in an ECU. Some of the Attributes are fixed by the port definitions, others can be configured in the I/O Hardware Abstraction. | Range, Lifetime / delay |
| Sender-receiver communication | This definition is an extract from [9]: Sender-receiver communication involves the transmission and reception of signals consisting of atomic data elements that are sent by one component and received by one or more components. A senderreceiver interface can contain multiple data elements. Sender-receiver communication is one-way - any reply sent by the receiver is sent as a separate senderreceiver communication. A port of a component that requires an AUTOSAR sender-receiver interface can read the data elements described in the interface and a port that provides the interface can write the data elements. | |
| Symbolic name | The symbolic name of a ECU signal is used by the I/O Hardware Abstraction to make a link (function, pin) | |
| Range | This is a functional range and not an electrical range. All the range is used either for functional needs or for diagnosis detections For analogue ECU signals [lowerLimit...upperLimit] (Voltage, current). For the particular case of a resistance signal and a timing signal (period), the lowerLimit value can not be negative. | [-12Volts...+12Volts] (voltage) [0,1] (discrete signals) [0…upperLimit] (period timing signal) [-100…100%] (Duty Cycle based timing signal) |
| Resolution | This attribute is for many Classes dependent on the range and the Data Type.Example: (upperLimit - lowerLimit) / (2datatypelength -1) For the others classes, it is known and defined. | [-12 Volts…+12Volts] Data Type : 16 bits Resolution => 24 / 65535 |
| Accuracy | It depends of hardware peripheral used for acquisition and/or generation. | ADC converter could be a 8/10/12/16 bits converter |
| Inversion | Inversion between the physical value and the logical value. This attribute is not visible butdone by I/O Hardware Abstraction to deliver expected values to users. | Physical HighState -> (signal=False) Physical LowState -> (signal=True) |
| Sampling rate | Time period required to get a signal value. | Sampling rate for a sampling windows (burst) |
英日
日本語は仮訳
T.B.D.
参考(reference)
[1] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList.pdf
[2] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[3] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[4] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration.pdf
[5] Glossary, AUTOSAR_TR_Glossary.pdf
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_TR_Glossary.pdf
[6] General Requirements on SPA
AUTOSAR_SRS_SPALGeneral.pdf
[7] Requirements on I/O Hardware Abstraction
AUTOSAR_SRS_IOHWAbstraction.pdf
[8] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate.pdf
[9] Specification of RTE Software
AUTOSAR_SWS_RTE.pdf
[10] Specification of ECU State Manager
AUTOSAR_SWS_ECUStateManager.pdf
[11] Specification of ECU Resource Template
AUTOSAR_TPS_ECUResourceTemplate.pdf
[12] Specification of ADC Driver
AUTOSAR_SWS_ADCDriver.pdf
[13] Specification of DIO Driver
AUTOSAR_SWS_DIODriver.pdf
[14] Specification of ICU Driver
AUTOSAR_SWS_ICUDriver.pdf
[15] Specification of PWM Driver
AUTOSAR_SWS_PWMDriver.pdf
[16] Specification of PORT Driver
AUTOSAR_SWS_PORTDriver.pdf
[17] Specification of GPT Driver
AUTOSAR_SWS_GPTDriver.pdf
[18] Specification of SPI Handler/Driver
AUTOSAR_SWS_SPIHandlerDriver.pdf
[19] Basic Software Module Description Template
AUTOSAR_TPS_BSWModuleDescriptionTemplate.pdf
[20] Specification of Standard Types
AUTOSAR_SWS_StandardTypes.pdf
[21] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[22] Specification of OCU Driver
AUTOSAR_SWS_OCUDriver.doc
関連文書(Related document)
2023年1月 記事数一覧
年末100記事を30点に仕上げる。
2023 書き初め
「はじめてのCAN/CANFD 」 ベクタージャパン ＜エンジニア夏休み企画>【読書感想文】
三方良し Udemy 車載LAN入門講座 CAN通信編
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(1) 著者 ＜エンジニア夏休み企画 読書感想文＞
詳解 車載ネットワーク CAN, CAN FD, LIN, CXPI, Ethernetの仕組みと設計のために(2)参考文献 ＜エンジニア夏休み企画>【読書感想文】
詳解 車載ネットワーク CAN、CAN FD、LIN、CXPI、Ethernetの仕組みと設計のために
最新URL変更記事
Specification of I/O Hardware Abstraction, AUTOSAR 47, R22-11, CP 20230421
https://qiita.com/kaizen_nagoya/items/b0d43e0587b480080094
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20230107
ver. 0.02 Countdown Calendar 変更 20230107
ver. 0.03 ありがとう追記 20230507
最後までおよみいただきありがとうございました。
いいね 💚、フォローをお願いします。
Thank you very much for reading to the last sentence.
Please press the like icon 💚 and follow me for your happy life.