Autosar Srs Ttcan
Autosar Srs Ttcan
Autosar Srs Ttcan
AUTOSAR CP R20-11
1 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
Disclaimer
This work (specification and/or software implementation) and the material contained
in it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR
and the companies that have contributed to it shall not be liable for any use of the
work.
The material contained in this work is protected by copyright and other types of
intellectual property rights. The commercial exploitation of the material contained in
this work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the
work may be utilized or reproduced, in any form or by any means, without permission
in writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.
2 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
Table of Contents
1 Scope of document ................................................................................................ 4
6 References ........................................................................................................... 13
6.1 Deliverables of AUTOSAR ............................................................................ 13
6.2 Related standard and norms ........................................................................ 13
3 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
1 Scope of document
This document specifies the additional TTCAN requirements for the CAN BSW stack.
4 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
In requirements, the following specific semantics are used (taken from Request
for Comment RFC 2119 from the Internet Engineering Task Force IETF)
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. Note that the requirement
level of the document in which they are used modifies the force of these words.
MUST: This word, or the terms "REQUIRED" or "SHALL", mean that the
definition is an absolute requirement of the specification.
MUST NOT: This phrase, or the phrase „SHALL NOT“, means that the
definition is an absolute prohibition of the specification.
SHOULD: This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a particular item,
but the full implications must be understood and carefully weighed before
choosing a different course.
SHOULD NOT: This phrase, or the phrase "NOT RECOMMENDED" mean
that there may exist valid reasons in particular circumstances when the
particular behavior is acceptable or even useful, but the full implications
should be understood and the case carefully weighed before implementing
any behavior described with this label.
MAY: This word, or the adjective „OPTIONAL“, means that an item is truly
optional. One vendor may choose to include the item because a particular
marketplace requires it or because the vendor feels that it enhances the
product while another vendor may omit the same item. An implementation,
which does not include a particular option, MUST be prepared to interoperate
with another implementation, which does include the option, though perhaps
with reduced functionality. In the same vein an implementation, which does
include a particular option, MUST be prepared to interoperate with another
implementation, which does not include the option (except, of course, for the
feature the option provides.)
5 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
6 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
4 Requirements Specification
4.1 Functional requirements
4.1.2.1 Configuration
7 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
configurable.
The configuration parameters shall be allowed to be of types Pre-Compile-
Time.
Rationale: Parameters like e.g. “operation mode” , “master/slave”, “trigger” etc. need
to be configured.
Use Case: See Rationale.
Dependencies: --
Supporting Material: RS Features: RS_BRF_00312 [5]
⌋(RS_BRF_01744)
8 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
9 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
11 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
5 Requirements Tracing
Requirement Description Satisfied by
RS_BRF_01328 AUTOSAR RTE shall support scheduling of SRS_TtCan_41007
executable entities on defined events
RS_BRF_01432 AUTOSAR services shall support system SRS_TtCan_41005,
time services SRS_TtCan_41006
RS_BRF_01464 AUTOSAR services shall support SRS_TtCan_41004
standardized handling of watchdogs
RS_BRF_01560 AUTOSAR communication shall support SRS_TtCan_41003
mapping of signals into transferrable
protocol data units
RS_BRF_01592 AUTOSAR communication shall offer data SRS_TtCan_41010,
transfer on user request, time based, and SRS_TtCan_41011
requested via the underlying bus
RS_BRF_01640 AUTOSAR communication shall support SRS_TtCan_41013
transmit and receive cancelation
RS_BRF_01744 AUTOSAR communication shall support SRS_TtCan_41001,
TTCAN SRS_TtCan_41002,
SRS_TtCan_41012,
SRS_TtCan_41014
RS_BRF_02168 AUTOSAR diagnostics shall provide a SRS_TtCan_41008,
central classification and handling of SRS_TtCan_41009
abnormal operative conditions
12 of 13 Document ID 441:AUTOSAR_SRS_TTCAN
Requirements on TTCAN
AUTOSAR CP R20-11
6 References
6.1 Deliverables of AUTOSAR
[7] ISO 11898-4 (2004-08-01), Road vehicles – Controller Area Network (CAN)
Part4: Time triggered communication
13 of 13 Document ID 441:AUTOSAR_SRS_TTCAN