DEENESPTFRRUARHIKOZHNL

Zeigt jedes Requirement mit offenem Review-Bedarf; Quelle, Grund und Verlinkung helfen bei der Priorisierung.

Die Kampagnen-Evidenz für Eclipse S-Core ist als 0019-06 im Arbeitsbestand nachverfolgbar und wird in dieser Berichtslandschaft ausdrücklich mitgeführt.

Erzeugt: 2026-08-21T16:43:07ZWerkzeug: _src/tools/open_reviews_report.pyDatenquelle: _src/spec/records/ und _src/data/records.csv

Offene Reviews — Gesamtuebersicht

Sammelt jedes Requirement mit offenem Review-Bedarf (offenes review_flag, unbestaetigte suspects oder Status ausstehend/proposed) unabhaengig vom Bereich. Ein Eintrag ohne veroeffentlichte Seite ist ein Testfixture oder eine bislang nicht in die API-Referenz aufgenommene Anforderung (z. B. PRS_E2E_*) und wird nur als Record-ID angezeigt.

Offene Reviews: 396Mit veroeffentlichter Seite: 47Ohne veroeffentlichte Seite: 349Quelldokumente: 2

Requirement-IDUeberschriftQuelleKonfidenzReview-GrundUpstreamAnforderungstext
SWS_LOG_00021function CreateLogger [SWS_LOG_00021] Upstream: RS_LT_00003 , RS_LT_00050AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Creates a Logger object, holding the context which is registered in the Logging framework. If no model is available the sink shall be the console per default.
SWS_LOG_00039function Flush [SWS_LOG_00039] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Sends out the current log buffer and initiates a new message stream. Note: Calling ara::log::LogStream::Flush is only necessary if the ara::log::LogStream ob…
SWS_LOG_00040function operator<< [SWS_LOG_00040] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Appends given value to the internal message buffer.
SWS_LOG_00041function operator<< [SWS_LOG_00041] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes unsigned int 8 bit parameter into message.
SWS_LOG_00042function operator<< [SWS_LOG_00042] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes unsigned int 16 bit parameter into message.
SWS_LOG_00043function operator<< [SWS_LOG_00043] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes unsigned int 32 bit parameter into message.
SWS_LOG_00044function operator<< [SWS_LOG_00044] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes unsigned int 64 bit parameter into message.
SWS_LOG_00045function operator<< [SWS_LOG_00045] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes signed int 8 bit parameter into message.
SWS_LOG_00046function operator<< [SWS_LOG_00046] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes signed int 16 bit parameter into message.
SWS_LOG_00047function operator<< [SWS_LOG_00047] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes signed int 32 bit parameter into message.
SWS_LOG_00048function operator<< [SWS_LOG_00048] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes signed int 64 bit parameter into message.
SWS_LOG_00049function operator<< [SWS_LOG_00049] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes float 32 bit parameter into message.
SWS_LOG_00050function operator<< [SWS_LOG_00050] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes float 64 bit parameter into message.
SWS_LOG_00051function operator<< [SWS_LOG_00051] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes null terminated UTF8 string into message.
SWS_LOG_00062function operator<< [SWS_LOG_00062] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Writes ara::core::StringView into message.
SWS_LOG_00063function operator<< [SWS_LOG_00063] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Appends LogLevel enum parameter as text into message.
SWS_LOG_00064function LogFatal [SWS_LOG_00064] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Creates a LogStream object. Returned object will accept arguments via the insert stream operator "@c <<".
SWS_LOG_00065function LogError [SWS_LOG_00065] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Same as Logger::LogFatal().
SWS_LOG_00066function LogWarn [SWS_LOG_00066] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Same as Logger::LogFatal().
SWS_LOG_00067function LogInfo [SWS_LOG_00067] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Same as Logger::LogFatal().
SWS_LOG_00068function LogDebug [SWS_LOG_00068] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Same as Logger::LogFatal().
SWS_LOG_00069function LogVerbose [SWS_LOG_00069] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Same as Logger::LogFatal().
SWS_LOG_00070function IsEnabled [SWS_LOG_00070] Upstream: RS_LT_00003 , RS_LT_00045AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Check current configured log reporting level. Applications may want to check the actual configured reporting log level of certain loggers before doing log da…
SWS_LOG_00124function operator<< [SWS_LOG_00124] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Write a core::ErrorCode instance into the message. When output to the console, the ErrorCode shall be shown in an implementation-defined way as a String hold…
SWS_LOG_00125function operator<< [SWS_LOG_00125] Upstream: RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Write a std::chrono::duration instance into the message.
SWS_LOG_00126function operator<< [SWS_LOG_00126] Upstream: RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Write a core::InstanceSpecifier into the message.
SWS_LOG_00127function operator<< [SWS_LOG_00127] Upstream: RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Write a raw pointer into the message.
SWS_LOG_00128function operator<< [SWS_LOG_00128] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Write a byte sequence into message. This call shall copy the sequence of core::Byte objects as-is into the message.
SWS_LOG_00129function WithLocation [SWS_LOG_00129] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Add source file location into the message.
SWS_LOG_00131function WithLevel [SWS_LOG_00131] Upstream: RS_LT_00003 , RS_LT_00049AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Log message with a programmatically determined log level can be written.
SWS_LOG_00132function WithTag [SWS_LOG_00132] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Add the given single tag to the current message.
SWS_LOG_00133function LogWith [SWS_LOG_00133] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—This function does not participate in overload resolution if any of Attrs.. is not an "Attr" (TBD).
SWS_LOG_00174function LogStream [SWS_LOG_00174] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—The copy constructor is deleted.
SWS_LOG_00175function operator= [SWS_LOG_00175] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—The copy assignment operator is deleted.
SWS_LOG_00176function LogStream [SWS_LOG_00176] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—The move constructor is treated in a way that allows returning an instance from a function. Typically, the move constructor is only declared, but not defined…
SWS_LOG_00177function operator= [SWS_LOG_00177] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—The move assignment operator is deleted.
SWS_LOG_00201function Arg [SWS_LOG_00201] Upstream: RS_LT_00003 , RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a wrapper object for the given arguments. Calling this function shall be ill-formed if any of these conditions are met: • T is not an arithmetic type …
SWS_LOG_00203function operator<< [SWS_LOG_00203] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Log an argument with attributes. When output to the console, the value and all its attributes shall be shown as a single argument.
SWS_LOG_00204function Log [SWS_LOG_00204] Upstream: RS_LT_00003AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Log a modeled message. If this function is called with an argument list that does not match the modeled message, the program is ill-formed.
SWS_LOG_00205function RegisterConnectionStateHandler [SWS_LOG_00205] Upstream: RS_LT_00003 , RS_LT_00050AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Register a callback to be invoked whenever the connection state changes. Only a single function can be installed this way; if a callback was already register…
SWS_LOG_00208function Dflt [SWS_LOG_00208] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kDefault formatting hint.
SWS_LOG_00209function Hex [SWS_LOG_00209] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kHex formatting hint and default precision.
SWS_LOG_00210function Hex [SWS_LOG_00210] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kHex formatting hint and given precision.
SWS_LOG_00211function Dec [SWS_LOG_00211] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kDec formatting hint and default precision.
SWS_LOG_00212function Dec [SWS_LOG_00212] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kDec formatting hint and given precision.
SWS_LOG_00213function Oct [SWS_LOG_00213] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kOct formatting hint and default precision.
SWS_LOG_00214function Oct [SWS_LOG_00214] Upstream: RS_LT_00046AUTOSAR_AP_SWS_LogAndTrace S.NonemediumLegacy-Beschreibung pruefen—Create a Format instance with Fmt::kOct formatting hint and given precision.
PRS_E2E_00070PRS_E2E_00070AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08533E2E Profile 1 shall use the polynomial of CRC-8-SAE J1850, i.e. the polynomial 0x1D (x8 + x4 + x3 + x2 + 1), but with start value and XOR value equal to 0x00
PRS_E2E_00218PRS_E2E_00218AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533, RS_E2E_08543Profile 1 shall provide the following mechanisms: Counter, Timeout monitoring, Data ID, CRC (see
PRS_E2E_00219PRS_E2E_00219AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 2 shall provide the following mechanisms: Sequence Number (Counter), Message Key used for CRC calculation (Data ID), Data ID + CRC, Safety Code (CRC)…
PRS_E2E_00372PRS_E2E_00372AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 4 shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_00394PRS_E2E_00394AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 5 shall provide the following control fields, transmitted at runtime together with the protected data: Counter, CRC, Data ID (see
PRS_E2E_00479PRS_E2E_00479AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 6 shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_00480PRS_E2E_00480AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 7 shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_00503PRS_E2E_00503AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 11 shall provide the following control fields, transmitted at runtime together with the protected data: Counter, CRC, Data ID (see
PRS_E2E_00522PRS_E2E_00522AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08527, RS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 22 shall provide the following control fields, transmitted at runtime together with the protected data: Counter, CRC, Data ID (see
PRS_E2E_00707PRS_E2E_00707AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 44 shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_00736PRS_E2E_00736AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533, RS_E2E_08549Profile 8 shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_00740PRS_E2E_00740AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 4m shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID, Source ID, Mes…
PRS_E2E_00783PRS_E2E_00783AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 7m shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID, Source ID, Mes…
PRS_E2E_00916E2E Profile 1 specific Check Status Mapping since R4AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528E2E Protocol Specification AUTOSAR FO R25-11 Profile Specific State State Machine State E2E_P01ST A TUS_OK, E2E_P01ST A TUS_OKSOMELOST , E2E_P01STATUS_SYNC E…
PRS_E2E_00917E2E Profile 1 specific Check Status Mapping prior to R4AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528Profile Specific State State Machine State E2E_P01ST A TUS_OK, E2E_P01ST A TUS_OKSOMELOST , E2E_P01STATUS_INITIAL E2E_P_OK E2E_P01ST A TUS_WRONGCRC E2E_P_ERR…
PRS_E2E_00918E2E Profile 2 specific Check Status Mapping since R4AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528Profile Specific State State Machine State E2E_P02ST A TUS_OK, E2E_P02ST A TUS_OKSOMELOST , E2E_P02STATUS_SYNC E2E_P_OK E2E_P02ST A TUS_WRONGCRC E2E_P_ERROR …
PRS_E2E_00919E2E Profile 2 specific Check Status Mapping prior to R4AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528Profile Specific State State Machine State E2E_P02ST A TUS_OK, E2E_P02ST A TUS_OKSOMELOST , E2E_P02STATUS_INITIAL E2E_P_OK E2E_P02ST A TUS_WRONGCRC E2E_P_ERR…
PRS_E2E_00920E2E Profile specific Check Status MappingAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528Profile Specific State State Machine State E2E_PyyST A TUS_OK, E2E_PyyST A TUS_OKSOMELOST E2E_P_OK E2E_PyyST A TUS_ERROR E2E_P_ERROR E2E_PyyST A TUS_REPEA TE…
PRS_E2E_00921Mapping between profile independent and specific statesAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08534, RS_E2E_08528Profile independent result Profile specific result with yy one of profiles (01,02,04,05,06,07,08,11,22,44,04m,07m,08m,44m) OK E2E_PyyST A TUS_OK OK E2E_PyyST…
PRS_E2E_01107PRS_E2E_01107AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 08m shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID (see
PRS_E2E_01154PRS_E2E_01154AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P08mProtect, E2E_P08mForward, and E2E_P08mCheck functions “Config” shall have the following members defined in
PRS_E2E_01155PRS_E2E_01155AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08529, RS_E2E_08530, RS_E2E_08533Profile 44m shall provide the following control fields, transmitted at runtime together with the protected data: Length, Counter, CRC, Data ID, Source ID, Me…
PRS_E2E_01159PRS_E2E_01159AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539E2E profiles for methods shall use the function defined in PXXMCALCULA TE_CRC of the SWS CRC supervision for calculating the CRC
PRS_E2E_01160PRS_E2E_01160AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528In E2E profiles for methods, the CRC shall be calculated over the entire E2E header (excluding the CRC bytes) and over the user data
PRS_E2E_01161PRS_E2E_01161AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539In the E2E profiles for methods the Message Type field shall be explicitly transmitted, i.e. it shall be the part of the transmitted E2E header
PRS_E2E_01162PRS_E2E_01162AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539A Message Type field with a value of 0 indicates a request message
PRS_E2E_01163PRS_E2E_01163AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539A Message Type field with a value of 1 indicates a response message
PRS_E2E_01164PRS_E2E_01164AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539A Message Result field with a value of 0 indicates a normal response message
PRS_E2E_01165PRS_E2E_01165AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539A Message Result field with a value of 1 indicates an error response message
PRS_E2E_01166PRS_E2E_01166AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539The Message Result field shall be set to 0 for request messages (i.e., in case the Message Type field is set to 0)
PRS_E2E_01199PRS_E2E_01199AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_PXXmProtect() and E2E_PXXmForward() functions’ ”state” shall have the members defined in
PRS_E2E_01200PRS_E2E_01200AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() functions’ ”state” shall have the members defined in
PRS_E2E_01201PRS_E2E_01201AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The step ”Do Checks” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall set State->Status to one of the following enumeration values (see
PRS_E2E_01202PRS_E2E_01202AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P44mProtect, E2E_P44mForward, and E2E_P44mCheck functions “Config” shall have the following members defined in
PRS_E2E_01203PRS_E2E_01203AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539In the E2E profiles for methods the Message Result field shall be explicitly transmitted, i.e. it shall be the part of the transmitted E2E header
PRS_E2E_01206PRS_E2E_01206AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08539E2E Profiles shall use the CRC functions listed in chapters Chapter 6.7, Chapter 6.10, Chapter 6.11, Chapter 6.14, for calculating the CRC
PRS_E2E_01250PRS_E2E_01250AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_PXXProtect and E2E_PXXForward functions ’state’ shall have the members defined in
PRS_E2E_01251PRS_E2E_01251AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_PXXCheck functions ’State’ shall have the members defined in
PRS_E2E_01252PRS_E2E_01252AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_PXXCheck functions ’State->Status’ enumeration type shall consist of the following enumeration values (see
PRS_E2E_01401Profile 76 CRC Calculation AlgorithmAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08539E2E Profile 76 shall use the Crc_CalculateCRC SAE J1939-76 CRC function for calculating the CRC (Polynomial: 0X6938392D; Autosar notation)
PRS_E2E_01409Profile 76 Protect FunctionAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P76Protect function ’state’ shall have the members defined in
PRS_E2E_01411Profile 76 Check FunctionAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P76Check functions ’State’ shall have the members defined in
PRS_E2E_01413Profile 76 StatusAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P76Check functions ’State->Status’ enumeration type shall consist the following enumeration values (see
PRS_E2E_01415Profile 76 ConfigurationAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537, RS_E2E_08539The E2E_P76Protect and E2E_P76Check functions ’Config’ shall have the following members defined in
PRS_E2E_01447MaxDeltaCounter for Client-Server Communication (server) Replaces: PRS_E2E_CONSTR_06300AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528For Client-Server Communication the MaxDeltaCounter on server-side shall be set to the maximum of the value range of the sequence counter
PRS_E2E_01448MaxDeltaCounter for Client-Server Communication (client) Replaces: PRS_E2E_CONSTR_06303AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528For Client-Server Communication the MaxDeltaCounter on client-side shall be set to
PRS_E2E_01449cyclic call FTTI Replaces: PRS_E2E_UC_00325AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The E2E check function should be invoked at least once within FTTI (FTTI is for the safety goals from which the requirements for this E2E checks are derived)
PRS_E2E_01450cyclic reception Replaces: PRS_E2E_UC_00235AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528The user (caller) of E2E Supervision, in particular the receiver, should provide the error handling mechanisms for the faults detected by the E2E Supervision
PRS_E2E_01451Alignment Replaces: PRS_E2E_UC_00062AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528When using E2E Profiles, messages that have length < 8 bits should be allocated to one byte of a message, i.e. they should not span over two bytes
PRS_E2E_01452Alignment Replaces: PRS_E2E_UC_00063AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528When using E2E Profiles, messages that have length >= 8 bits should start or finish at the byte limit of a message
PRS_E2E_01453length of data Replaces: PRS_E2E_UC_00320AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528When using E2E Profiles, the length of the data to be protected should be multiple of 8 bits
PRS_E2E_01454unused areas of messages Replaces: PRS_E2E_UC_00173AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumNur ein Backend verfuegbarRS_E2E_08528Any sender, which uses the E2E-Profiles, should fill all unused areas of a messages to a default value configured for the message)
PRS_E2E_01455high nibble value at profiles 1 and 11 Replaces: PRS_E2E_UC_00308AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528Any user of Profile 1 or 11 in Nibble Data ID configuration should ensure that: 1. the high nibble of high byte of Data ID is equal to 0 E2E Protocol Specifi…
PRS_E2E_01457Value range of windowSizeValid Replaces: PRS_E2E_CONSTR_03176AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The value of the windowSizeValidattribute shall be greater or equal to
PRS_E2E_01458Dependency between windowSizeInvalid and window- SizeValid Replaces: PRS_E2E_CONSTR_06301AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: windowSizeInvalid <= window- SizeValid
PRS_E2E_01459Dependency between windowSizeInit and windowSize- Valid Replaces: PRS_E2E_CONSTR_06302AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: windowSizeInit <= windowSize- Valid
PRS_E2E_01460Dependency between maxErrorStateValid Replaces: PRS_E2E_CONSTR_03177AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528maxErrorStateInit and maxErrorStateInvalid The following restriction shall be respected: maxErrorStateValid >= maxErrorStateInit >= maxEr- rorStateInvalid >=
PRS_E2E_01461Dependency between minOkStateValid, minOkStateInit and minOkStateInvalid Replaces: PRS_E2E_CONSTR_03178AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: 1 <= minOkStateValid <= minOkStateInit <= minOkStateInvalid
PRS_E2E_01462Dependency between minOkStateInit, maxEr- rorStateInit and windowSizeInit Replaces: PRS_E2E_CONSTR_03179AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: minOkStateInit + maxErrorStateInit <= windowSizeInit
PRS_E2E_01463Dependency between minOkStateValid, maxErrorState- Valid and windowSizeValid Replaces: PRS_E2E_CONSTR_03180AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: minOkStateValid + maxErrorStat- eValid <= windowSizeValid
PRS_E2E_01464Dependency between minOkStateInvalid, maxEr- rorStateInvalid and windowSizeInvalid Replaces: PRS_E2E_CONSTR_03181AUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The following restriction shall be respected: minOkStateInvalid + maxEr- rorStateInvalid <= windowSizeInvalid
PRS_E2E_01466Data Types of PXX_GetHeaderInfoAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The PXX_GetHeaderInfo type shall have the members defined in
PRS_E2E_01468Data Types of PXXm_GetHeaderInfoAUTOSAR_FO_PRS_E2EProtocol.pdf S.22mediumFehlende Leerzeichen pruefenRS_E2E_08528The PXXm_GetHeaderInfo type shall have the members defined in
PRS_E2E_00082PRS_E2E_00082AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08531In E2E Profile 1, the CRC is calculated over: 1. First over the one or two bytes of the Data ID (depending on Data ID configuration), and 2. then over all tr…
PRS_E2E_00125PRS_E2E_00125AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08531In E2E Profile 2, the E2E_P02Check() function shall not modify any bit in Data
PRS_E2E_00126PRS_E2E_00126AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08531In E2E Profile 2, the E2E_P02Protect() function shall perform the activities as specified in Figure 6.67 and Figure
PRS_E2E_00134PRS_E2E_00134AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08531In E2E Profile 2, the E2E_P02Check() function shall perform the activities as specified in Figure 6.71, Figure 6.72 and Figure
PRS_E2E_00196PRS_E2E_00196AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08530The function E2E_P01Check shall 1. Check the CRC 2. Check the Data ID nibble, i.e. compare the expected value with the received value (for E2E_P01_DA T AID_N…
PRS_E2E_00318PRS_E2E_00318AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534The middleware shall determine the DataID, the Message Type, the Message Result, and the SourceID of the currently exchanged information
PRS_E2E_00319PRS_E2E_00319AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534The middleware invokes E2E functions providing them the DataID the Message Type, the Message Result, and the SourceID together with the data
PRS_E2E_00320PRS_E2E_00320AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534On the receiver side, the middleware shall provide the e2eResult determined by E2E to the receiver
PRS_E2E_00322PRS_E2E_00322AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534The e2eResult shall contain information: • e2eStatus: Profile-independent status of the reception on one single Data in one cycle. Possible values are: OK, R…
PRS_E2E_00323PRS_E2E_00323AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534E2E protocol shall provide the following interface: • E2E_check(in dataID, inout serializedData): e2eResult • E2E_protect(in dataID, inout serializedData) • …
PRS_E2E_00324PRS_E2E_00324AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08534, RS_E2E_08542The options for a E2E-protected data shall be available as defined in
PRS_E2E_00401PRS_E2E_00401AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08539, RS_E2E_08531In E2E Profile 5, the CRC shall be calculated over the entire E2E header (excluding the CRC bytes), including the user data extended at the end with the Data ID
PRS_E2E_00421PRS_E2E_00421AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08539, RS_E2E_08531In E2E Profile 6, the CRC shall be calculated over the entire E2E header (excluding the CRC bytes), including the user data extended with the Data ID
PRS_E2E_00527PRS_E2E_00527AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08539, RS_E2E_08531In E2E Profile 22, the CRC shall be calculated over the entire E2E header (excluding the CRC byte), including the user data extended at the end with the corr…
PRS_E2E_00613PRS_E2E_00613AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08531In E2E Profile 2, the E2E_P02Forward() function shall perform the activities as specified in Figure 6.69 and Figure
PRS_E2E_00646PRS_E2E_00646AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P01Protect, E2E_P01Forward and E2E_P01Check functions ’Config’ shall have the following members defined in
PRS_E2E_00648PRS_E2E_00648AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P02Check functions ’State’ shall have the members defined in
PRS_E2E_00651PRS_E2E_00651AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P04Protect, E2E_P04Forward and E2E_P04Check functions ’Config’ shall have the following members defined in
PRS_E2E_00654PRS_E2E_00654AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537, RS_E2E_08539The E2E_P05Protect, E2E_P05Forward and E2E_P05Check functions ’Config’ shall have the following members defined in
PRS_E2E_00657PRS_E2E_00657AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P06Protect, E2E_P06Forward and E2E_P06Check functions ’Config’ shall have the following members defined in
PRS_E2E_00660PRS_E2E_00660AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P07Protect, E2E_P07Forward and E2E_P07Check functions ’Config’ shall have the following members defined in
PRS_E2E_00663PRS_E2E_00663AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P11Protect, E2E_P11Forward and E2E_P11Check functions ’Config’ shall have the following members defined in
PRS_E2E_00666PRS_E2E_00666AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P22Protect, E2E_P22Forward and E2E_P22Check functions ’Config’ shall have the following members defined in
PRS_E2E_00677PRS_E2E_00677AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08534, RS_E2E_08528The mapping between profile independent and profile specific states shall be as described in
PRS_E2E_00678PRS_E2E_00678AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08534, RS_E2E_08548The mapping between communication channel status and state machine states shall be as defined in
PRS_E2E_00706PRS_E2E_00706AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P08Protect, E2E_P08Forward and E2E_P08Check functions ’Config’ shall have the following members defined in
PRS_E2E_00735PRS_E2E_00735AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08528, RS_E2E_08537The E2E_P44Protect, E2E_P44Forward and E2E_P44Check functions ’Config’ shall have the following members defined in
PRS_E2E_00828PRS_E2E_00828AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534For C/S (method) communication the E2E protocol shall provide the following interface: • E2E_check(in dataID, in messageT ype, in messageResult, in sourceID,…
PRS_E2E_00851PRS_E2E_00851AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08537The E2E_P07mProtect, E2E_P07mForward, E2E_P07mSourceCheck and E2E_P07mSinkCheck functions “Config” shall have the following members defined in
PRS_E2E_00852PRS_E2E_00852AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08537The E2E_P04mProtect, E2E_P04mForward, E2E_P04mSourceCheck and E2E_P04mSinkCheck functions “Config” shall have the following members defined in
PRS_E2E_00853PRS_E2E_00853AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534The e2eResult shall contain information: • e2eState: Status of the communication channel exchanging the data. Possible values are: VALID, DEINIT , NODA T A, …
PRS_E2E_00922Mapping between Communication Channel and State Machine StatesAUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08534, RS_E2E_08548Communication channel status Result of E2E_SMCheck VALID E2E_SM_VALID NODA T A E2E_SM_NODA T A DEINIT E2E_SM_DEINIT INIT E2E_SM_INIT INVALID E2E_SM_INVALID
PRS_E2E_01207PRS_E2E_01207AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08531The CRC shall be calculated over the entire E2E header (excluding the CRC bytes) and over the user data
PRS_E2E_01402Profile 76 CRC Calculation over E2E HeaderAUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumNur ein Backend verfuegbarRS_E2E_08539, RS_E2E_08531In E2E Profile 76, the CRC shall be calculated over the entire E2E header (excluding the CRC bytes), including the user data extended at the end
PRS_E2E_01443Interface to middleware Replaces: PRS_E2E_UC_00321AUTOSAR_FO_PRS_E2EProtocol.pdf S.23mediumFehlende Leerzeichen pruefenRS_E2E_08534The middleware should provide, for each exchanged dataRecord, a set of functions: • middleware_send(in dataRecord) • middleware_receive(out dataRecord, out e…
PRS_E2E_00345PRS_E2E_00345AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539Depending on the configuration parameter Config->transitT oInvalidExtended, the E2E State machine shall exhibit the behavior with respect to the function E2E…
PRS_E2E_00354PRS_E2E_00354AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The E2E state machine shall be implemented by the functions E2E_SMCheck() and E2E_SMCheckInit()
PRS_E2E_00375PRS_E2E_00375AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The E2E State machine shall have the behavior with respect to the function E2E_SMCheckInit() as shown in Figure
PRS_E2E_00397PRS_E2E_00397AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profile 5, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented b…
PRS_E2E_00399PRS_E2E_00399AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E Profile 5, the Data ID shall be implicitly transmitted, by adding the Data ID after the user data in the CRC calculation
PRS_E2E_00400PRS_E2E_00400AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08539E2E Profile 5 shall use the Crc_CalculateCRC16() function of the SWS CRC Supervision for calculating the CRC (Polynomial: 0x1021; Autosar notation)
PRS_E2E_00403PRS_E2E_00403AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P05Protect() shall have the overall behavior as shown in Figure
PRS_E2E_00404PRS_E2E_00404AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_P05Protect() shall behave as shown in Figure
PRS_E2E_00405PRS_E2E_00405AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P05Protect() shall behave as shown in Figure
PRS_E2E_00406PRS_E2E_00406AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P05Protect() and in E2E_P05Check shall behave as shown in Figure
PRS_E2E_00407PRS_E2E_00407AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_P05Protect() and E2E_P05Forward() shall behave as shown in Figure
PRS_E2E_00409PRS_E2E_00409AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_P05Protect() and E2E_P05Forward() shall behave as shown in Figure
PRS_E2E_00411PRS_E2E_00411AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P05Check() shall have the overall behavior as shown in Figure
PRS_E2E_00412PRS_E2E_00412AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the check function” in E2E_P05Check() shall behave as shown in Figure
PRS_E2E_00413PRS_E2E_00413AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Counter” in E2E_P05Check() shall behave as shown in Figure
PRS_E2E_00414PRS_E2E_00414AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_P05Check() shall behave as shown in Figure
PRS_E2E_00416PRS_E2E_00416AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks’ in E2E_P05Check() shall behave as shown in Figure
PRS_E2E_00417PRS_E2E_00417AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profile 6, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented b…
PRS_E2E_00419PRS_E2E_00419AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E Profile 6, the Data ID shall be implicitly transmitted, by adding the Data ID after the user data in the CRC calculation
PRS_E2E_00420PRS_E2E_00420AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08539E2E Profile 6 shall use the Crc_CalculateCRC16() function of the SWS CRC Supervision for calculating the CRC (Polynomial: 0x1021; Autosar notation)
PRS_E2E_00423PRS_E2E_00423AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P06Protect() shall have the overall behavior as shown in Figure
PRS_E2E_00424PRS_E2E_00424AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_P06Protect() shall behave as shown in Figure
PRS_E2E_00425PRS_E2E_00425AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Length” in E2E_P06Protect() and E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00426PRS_E2E_00426AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P06Protect() shall behave as shown in Figure
PRS_E2E_00427PRS_E2E_00427AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P06Protect() and E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00428PRS_E2E_00428AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_P06Protect() and E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00429PRS_E2E_00429AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_P06Protect() and E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00430PRS_E2E_00430AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P06Check() shall have the overall behavior as shown in Figure
PRS_E2E_00431PRS_E2E_00431AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify Inputs” in E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00432PRS_E2E_00432AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Length” in E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00433PRS_E2E_00433AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Counter” in E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00434PRS_E2E_00434AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00436PRS_E2E_00436AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks” in E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00466PRS_E2E_00466AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step E2E_SMAddStatus(ProfileStatus, State) in E2E_SMCheck() shall behave as shown in Figure
PRS_E2E_00467PRS_E2E_00467AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step E2E_SMClearStatus(State, Config) in E2E_SMCheck() shall behave as shown in Figure
PRS_E2E_00469PRS_E2E_00469AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute offset” in E2E_P05Protect(), E2E_P05Forward() and E2E_P05Check() shall behave as shown in Figure
PRS_E2E_00470PRS_E2E_00470AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute offset” in E2E_P06Protect(), E2E_P06Forward() and E2E_P06Check() shall behave as shown in Figure
PRS_E2E_00504PRS_E2E_00504AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profile 11, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented …
PRS_E2E_00505PRS_E2E_00505AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539In the E2E Profile 11 with DataIDMode set to E2E_P11_DA T AID_BOTH, the Data ID shall be implicitly transmitted, by adding first the Data ID low byte, then t…
PRS_E2E_00506PRS_E2E_00506AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539In E2E Profile 11 with DataIDMode set to E2E_P11_DA T AID_NIBBLE, the lower nibble of the high byte of the DataID shall be placed in the transmitted data at …
PRS_E2E_00507PRS_E2E_00507AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profile 11, the Data IDs shall be globally unique within the network of communicating system (made of several ECUs each sending different data)
PRS_E2E_00508PRS_E2E_00508AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08539E2E Profile 11 shall use the Crc_CalculateCRC8 function of the SWS CRC Supervision for calculating the CRC (CRC-8-SAE J1850)
PRS_E2E_00509PRS_E2E_00509AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P11Protect() shall have the overall behavior as shown in Figure
PRS_E2E_00510PRS_E2E_00510AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_P11Protect() shall behave as shown in Figure
PRS_E2E_00511PRS_E2E_00511AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step „Write DataIDNibble” in E2E_P11Protect() shall behave as shown in Figure
PRS_E2E_00512PRS_E2E_00512AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P11Protect() shall behave as shown in Figure
PRS_E2E_00513PRS_E2E_00513AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P11Protect() and in E2E_P11Check shall behave as shown in Figure
PRS_E2E_00514PRS_E2E_00514AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_P11Protect() and E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00515PRS_E2E_00515AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_P11Protect() and E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00516PRS_E2E_00516AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P11Check() shall have the overall behavior as shown in Figure
PRS_E2E_00517PRS_E2E_00517AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the check function” in E2E_P11Check() shall behave as shown in Figure
PRS_E2E_00518PRS_E2E_00518AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step "Read Counter" in E2E_P11Check() shall behave as shown in Figure
PRS_E2E_00519PRS_E2E_00519AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_P11Check() shall behave as shown in Figure
PRS_E2E_00521PRS_E2E_00521AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks’ in E2E_P11Check() shall behave as shown in Figure
PRS_E2E_00523PRS_E2E_00523AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profile 22, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented …
PRS_E2E_00524PRS_E2E_00524AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E Profile 22, the Data ID shall be implicitly transmitted, by adding the Data ID after the user data in the CRC calculation
PRS_E2E_00525PRS_E2E_00525AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profiles 2 and 22, the Data ID Lists shall be globally unique within the network of communicating system (made of several ECUs each sending differ…
PRS_E2E_00526PRS_E2E_00526AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08528, RS_E2E_08539E2E Profile 22 shall use the Crc_CalculateCRC8H2F() function of the SWS CRC Supervision for calculating the CRC (Polynomial 0x2F , see also SWS_E2E_00117)
PRS_E2E_00528PRS_E2E_00528AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P22Protect() shall have the overall behavior as shown in Figure
PRS_E2E_00529PRS_E2E_00529AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_P22Protect() shall behave as shown in Figure
PRS_E2E_00530PRS_E2E_00530AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P22Protect() and E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_00531PRS_E2E_00531AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P22Protect(), E2E_P22Forward() and in E2E_P22Check shall behave as shown in Figure
PRS_E2E_00532PRS_E2E_00532AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_P22Protect() and E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_00533PRS_E2E_00533AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_P22Protect() and E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_00534PRS_E2E_00534AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P22Check() shall have the overall behavior as shown in Figure
PRS_E2E_00535PRS_E2E_00535AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the check function” in E2E_P22Check() shall behave as shown in Figure
PRS_E2E_00536PRS_E2E_00536AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Counter” in E2E_P22Check() shall behave as shown in Figure
PRS_E2E_00537PRS_E2E_00537AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_P22Check() shall behave as shown in Figure
PRS_E2E_00539PRS_E2E_00539AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks’ in E2E_P22Check() shall behave as shown in Figure
PRS_E2E_00582PRS_E2E_00582AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read DataIDNibble” in E2E_P11Check() shall behave as shown in Figure
PRS_E2E_00583PRS_E2E_00583AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The following two Data ID modes shall be supported: 1. E2E_P11_DA T AID_BOTH: both bytes of the 16 bit Data ID are used in the CRC calculation: first the low…
PRS_E2E_00607PRS_E2E_00607AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step E2E_SMClearRemainingStatus(Config, State, NextState) in E2E_SMCheck() shall have the following behavior: Figure
PRS_E2E_00619PRS_E2E_00619AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_P05Forward() shall behave as shown in Figure
PRS_E2E_00620PRS_E2E_00620AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P05Forward() shall behave as shown in Figure
PRS_E2E_00621PRS_E2E_00621AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P05Forward() shall behave as shown in Figure
PRS_E2E_00622PRS_E2E_00622AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P06Forward() shall have the overall behavior as shown in Figure
PRS_E2E_00623PRS_E2E_00623AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00624PRS_E2E_00624AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00625PRS_E2E_00625AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P06Forward() shall behave as shown in Figure
PRS_E2E_00630PRS_E2E_00630AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P11Forward() shall have the overall behavior as shown in Figure
PRS_E2E_00631PRS_E2E_00631AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00632PRS_E2E_00632AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step „Write DataIDNibble” in E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00633PRS_E2E_00633AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00634PRS_E2E_00634AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P11Forward() shall behave as shown in Figure
PRS_E2E_00635PRS_E2E_00635AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P22Forward() shall have the overall behavior as shown in Figure
PRS_E2E_00636PRS_E2E_00636AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_00637PRS_E2E_00637AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_00639PRS_E2E_00639AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P05Forward() shall have the overall behavior as shown in Figure
PRS_E2E_00640PRS_E2E_00640AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539If DataIDMode is set to E2E_P01_DA T AID_NIBBLE, the CRC calculation shall be done by first calculating over the low byte of the Data ID, then a zero-byte (0…
PRS_E2E_00675PRS_E2E_00675AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539By Config->transitT oInvalidExtended==0 (false): The state machine shall behave according to Figure 6.131. There is no direct transition from E2E_SM_NODA T A…
PRS_E2E_00676PRS_E2E_00676AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539By Config->transitT oInvalidExtended==1 (true): The state machine shall behave according to Figure 6.132. The direct transition from E2E_SM_NODA T A to E2E_S…
PRS_E2E_01156PRS_E2E_01156AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In E2E profiles for methods, the counter on the sender side shall be initialized with 0 for the first transmission request of a data element the counter and …
PRS_E2E_01157PRS_E2E_01157AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profiles for methods, the Data ID shall be explicitly transmitted, i.e. it shall be the part of the transmitted E2E header
PRS_E2E_01167PRS_E2E_01167AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profiles for methods, the Source ID shall be explicitly transmitted, i.e. it shall be the part of the transmitted E2E header
PRS_E2E_01169PRS_E2E_01169AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The function E2E_PXXmProtect() shall have the overall behavior as shown in Figure
PRS_E2E_01170PRS_E2E_01170AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01171PRS_E2E_01171AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Compute offset” in E2E_PXXmProtect(), E2E_PXXmForward(), E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01172PRS_E2E_01172AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write Length” in E2E_PXXmProtect() and E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01173PRS_E2E_01173AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write Counter” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01174PRS_E2E_01174AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write DataID” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01175PRS_E2E_01175AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write SourceID” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01176PRS_E2E_01176AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write Message Type” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01177PRS_E2E_01177AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write Message Result” in E2E_PXXmProtect() shall behave as shown in Figure
PRS_E2E_01178PRS_E2E_01178AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Compute CRC” in E2E_PXXmProtect(), E2E_PXXmForward(), E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01179PRS_E2E_01179AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write CRC”in E2E_PXXmProtect() and E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01180PRS_E2E_01180AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Increment Counter” in E2E_PXXmProtect() and E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01181DraftAUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The function E2E_PXXmForward() shall have the overall behavior as shown in Figure
PRS_E2E_01182DraftAUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01183DraftAUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write Counter” in E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01184DraftAUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Write DataID” in E2E_PXXmForward() shall behave as shown in Figure
PRS_E2E_01185PRS_E2E_01185AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539"The function E2E_PXXmSourceCheck() for the client side shall have the overall behavior as shown in Figure
PRS_E2E_01186PRS_E2E_01186AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Verify inputs of the function” in E2E_PXXmSourceCheck() shall behave as shown in Figure
PRS_E2E_01187PRS_E2E_01187AUTOSAR_FO_PRS_E2EProtocol.pdf S.24mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read Length” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01189PRS_E2E_01189AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read DataID” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01190PRS_E2E_01190AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read SourceID” in E2E_PXXmSourceCheck() shall behave as shown in Figure
PRS_E2E_01191PRS_E2E_01191AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read Message Type” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01192PRS_E2E_01192AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read Message Result” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01193PRS_E2E_01193AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read CRC” in E2E_PXXmSourceCheck() and E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01194PRS_E2E_01194AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Do Checks” in E2E_PXXmSourceCheck() shall behave as shown in Figure
PRS_E2E_01195PRS_E2E_01195AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The function E2E_PXXmSinkCheck() for the server side shall have the overall behavior as shown in Figure
PRS_E2E_01196PRS_E2E_01196AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Verify inputs of the check function” in E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01197PRS_E2E_01197AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Read SourceID” in E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01198PRS_E2E_01198AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The step ”Do Checks” in E2E_PXXmSinkCheck() shall behave as shown in Figure
PRS_E2E_01205PRS_E2E_01205AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profiles, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented by…
PRS_E2E_01209PRS_E2E_01209AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_PXXProtect() shall have the overall behavior as shown in Figure
PRS_E2E_01210PRS_E2E_01210AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_PXXProtect() shall behave as shown in Figure
PRS_E2E_01211PRS_E2E_01211AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute offset” in E2E_PXXProtect(), E2E_PXXForward() and E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01212PRS_E2E_01212AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Length” in E2E_PXXProtect() and E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01213PRS_E2E_01213AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_PXXProtect() shall behave as shown in Figure
PRS_E2E_01214PRS_E2E_01214AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write DataID” in E2E_PXXProtect() shall behave as shown in Figure
PRS_E2E_01215PRS_E2E_01215AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_PXXProtect(), E2E_PXXForward() and in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01216PRS_E2E_01216AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_PXXProtect() and E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01217PRS_E2E_01217AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_PXXProtect() and E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01218PRS_E2E_01218AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_PXXForward() shall have the overall behavior as shown in Figure
PRS_E2E_01219PRS_E2E_01219AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01220PRS_E2E_01220AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write DataID” in E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01221PRS_E2E_01221AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_PXXCheck() shall have the overall behavior as shown in Figure
PRS_E2E_01222PRS_E2E_01222AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the check function” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01223PRS_E2E_01223AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Length” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01224PRS_E2E_01224AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Counter” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01225PRS_E2E_01225AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read DataID” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01226PRS_E2E_01226AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01227PRS_E2E_01227AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks” in E2E_PXXCheck() shall behave as shown in Figure
PRS_E2E_01228PRS_E2E_01228AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the forward function” in E2E_PXXForward() shall behave as shown in Figure
PRS_E2E_01253Compute Offset of Protect FunctionAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute Offset of the protect function” in E2E_P22Protect(), E2E_P22Forward() and E2E_P22Check() shall behave as shown in Figure
PRS_E2E_01254Compute CRC - Data ID (Protect and Check Function)AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC - Data ID” in E2E_P22Protect() and E2E_P22Check() shall behave as shown in Figure
PRS_E2E_01255Compute CRC - Data ID (Forward Function)AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC - Data ID” in E2E_P22Forward() shall behave as shown in Figure
PRS_E2E_01400Profile 76 Initialization of counterAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In E2E Profile 76, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented …
PRS_E2E_01403Profile 76 Check functionAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P76Check() shall have the overall behavior as shown in Figure
PRS_E2E_01405Profile 76 Verification of inputs of Check functionAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the check function” in E2E_P76Check() shall behave as shown in Figure
PRS_E2E_01406Profile 76 Read CounterAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read Counter” in E2E_P76Check() shall behave as shown in Figure
PRS_E2E_01407Profile 76 Read CRCAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Read CRC” in E2E_P76Check() shall behave as shown in Figure
PRS_E2E_01408Profile 76 Perform checksAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Do Checks’ in E2E_P76Check() shall behave as shown in Figure
PRS_E2E_01420Profile 76 Protect FunctionAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The function E2E_P76Protect() shall have the overall behavior as shown in Figure
PRS_E2E_01422Profile 76 Verification of Inputs of Protect FunctionAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Verify inputs of the protect function” in E2E_P76Protect() shall behave as shown in Figure
PRS_E2E_01424Profile 76 Write CounterAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write Counter” in E2E_P76Protect() shall behave as shown in Figure
PRS_E2E_01427Profile 76 Compute CRCAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P76Protect() and in E2E_P76Check shall behave as shown in Figure
PRS_E2E_01429Profile 76 Write CRCAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Write CRC” in E2E_P76Protect() shall behave as shown in Figure
PRS_E2E_01430Profile 76 Increment CounterAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Increment Counter” in E2E_P76Protect() shall behave as shown in Figure
PRS_E2E_01433Profile 76 Compute CRCAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539The step ”Compute CRC” in E2E_P76Check() shall behave as shown in Figure
PRS_E2E_01437Parameter Config->combinedNoDataInitCountAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539Depending on the configuration parameter Config->combinedNoDataInitCount, the E2E_SMClearStatus shall exhibit the behavior with respect to the function E2E_S…
PRS_E2E_01438Uniqueness of Data IDs Replaces: PRS_E2E_UC_01204AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In E2E profiles, the Data IDs should be globally unique within the network of communicating system (made of several ECUs each sending different data)
PRS_E2E_01439Uniqueness of Data IDs Replaces: PRS_E2E_UC_01158AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profiles for methods, the Data IDs should be globally unique within the network of communicating systems (made of several ECUs each sending differ…
PRS_E2E_01440Uniqueness of Data IDs Replaces: PRS_E2E_UC_01168AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profiles for methods, the Source IDs should be globally unique within the network of communicating systems (made of several ECUs)
PRS_E2E_01441Uniqueness of Data IDs Replaces: PRS_E2E_UC_00463AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profile 5, the Data IDs should be globally unique within the network of communicating system (made of several ECUs each sending different data)
PRS_E2E_01442Uniqueness of Data IDs Replaces: PRS_E2E_UC_00464AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08539In the E2E profile 6, the Data IDs should be globally unique within the network of communicating system (made of several ECUs each sending different data)
PRS_E2E_01444Some/IP coverage Replaces: PRS_E2E_UC_00239AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08540, RS_E2E_08541For profiles 1, 2, 4, 5, 6, 7, 11, and 22 the E2E CRC should be calculated over the following parts of the serialized SOME/IP message. 1. Request ID (Client …
PRS_E2E_01445E2E for methods Replaces: PRS_E2E_USE_00741AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08540For profiles 4m, 7m, 8m and 44m the E2E CRC shall be calculated over the following parts of the serialized SOME/IP message. 1. Payload [variable size]
PRS_E2E_01446Some/IP coverage Replaces: PRS_E2E_UC_00238AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08540, RS_E2E_08541The E2E header should be placed after the Return Code depending on the chosen Offset value. The default Offset is 64 bit, which puts the E2E header exactly a…
PRS_E2E_01465transfer counter from request to response Replaces: PRS_E2E_UC_00606AUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumNur ein Backend verfuegbarRS_E2E_08541When a client sends a request to the server, the server should use the received counter as sequence counter for the response, no matter if regular response o…
PRS_E2E_01471PXX_GetHeaderInfoAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The function E2E_PXXGetHeaderInfo() shall behave as shown in Figure
PRS_E2E_01472PXXm_GetHeaderInfoAUTOSAR_FO_PRS_E2EProtocol.pdf S.25mediumFehlende Leerzeichen pruefenRS_E2E_08539The function E2E_PXXmGetHeaderInfo() shall behave as shown in Figure
PRS_E2E_00012PRS_E2E_00012AUTOSAR_FO_PRS_E2EProtocol.pdf S.29mediumNur ein Backend verfuegbarRS_E2E_08528The internal Supervision mechanisms error detection and reporting shall be implemented according to the pre-defined E2E Profiles specified in this document
PRS_E2E_00673PRS_E2E_00673AUTOSAR_FO_PRS_E2EProtocol.pdf S.29mediumNur ein Backend verfuegbarRS_E2E_08528The AUTOSAR E2E-Protocol shall use the error codes defined in
PRS_E2E_00739PRS_E2E_00739AUTOSAR_FO_PRS_E2EProtocol.pdf S.29mediumFehlende Leerzeichen pruefenRS_E2E_08528The MessageT ype argument of the E2E_PXXmProtect, E2E_PXXmForward, and E2E_PXXmCheck functions shall be set to one of the following enumeration values (see
PRS_E2E_00743PRS_E2E_00743AUTOSAR_FO_PRS_E2EProtocol.pdf S.30mediumFehlende Leerzeichen pruefenRS_E2E_08528The MessageResult argument of the E2E_PXXmProtect, E2E_PXXmForward, and E2E_PXXmCheck functions shall be set to one of the following enumeration values (see
PRS_E2E_00075PRS_E2E_00075AUTOSAR_FO_PRS_E2EProtocol.pdf S.84mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 1, on the sender side, for the first transmission request of a data element the counter shall be initialized with 0 and shall be incremented b…
PRS_E2E_00076PRS_E2E_00076AUTOSAR_FO_PRS_E2EProtocol.pdf S.84mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 1, on the receiver side, by evaluating the counter of received data against the counter of previously received data, the following shall be de…
PRS_E2E_00163PRS_E2E_00163AUTOSAR_FO_PRS_E2EProtocol.pdf S.84mediumNur ein Backend verfuegbarRS_E2E_08528There shall be following four inclusion modes for the two-byte Data ID into the calculation of the one-byte CRC: 1. E2E_P01_DA T AID_BOTH: both two bytes (do…
PRS_E2E_00085PRS_E2E_00085AUTOSAR_FO_PRS_E2EProtocol.pdf S.85mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 1, with E2E_P01DataIDMode equal to E2E_P01_DA T AID_BOTH or E2E_P01_DA T AID_AL T the length of the Data ID shall be 16 bits (i.e. 2 byte)
PRS_E2E_00169PRS_E2E_00169AUTOSAR_FO_PRS_E2EProtocol.pdf S.85mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 1, with E2E_P01DataIDMode equal to E2E_P01_DA T AID_LOW, the high byte of Data ID shall be set to 0x00
PRS_E2E_00306PRS_E2E_00306AUTOSAR_FO_PRS_E2EProtocol.pdf S.85mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 1, with E2E_P01DataIDMode equal to E2E_P01_DA T AID_NIBBLE, the high nibble of the high byte shall be 0x0
PRS_E2E_00190PRS_E2E_00190AUTOSAR_FO_PRS_E2EProtocol.pdf S.86mediumFehlende Leerzeichen pruefenRS_E2E_08528E2E Profile 1 shall use the Crc_CalculateCRC8 () function of the SWS CRC Supervision for calculating CRC checksums
PRS_E2E_00195PRS_E2E_00195AUTOSAR_FO_PRS_E2EProtocol.pdf S.88mediumNur ein Backend verfuegbarRS_E2E_08528The function E2E_P01Protect() shall: 1. write the Counter in Data, 2. write DataID nibble in Data, if E2E_P01_DA T AID_NIBBLE configuration is used 3. comput…
PRS_E2E_00608PRS_E2E_00608AUTOSAR_FO_PRS_E2EProtocol.pdf S.92mediumFehlende Leerzeichen pruefenRS_E2E_08528The function E2E_P01Forward() shall calculate the e2e header data based on the current value of the IN parameter ForwardStatus
PRS_E2E_00609PRS_E2E_00609AUTOSAR_FO_PRS_E2EProtocol.pdf S.92mediumFehlende Leerzeichen pruefenRS_E2E_08528If ForwardStatus equals to E2E_P_OK the function E2E_P01Forward() shall: 1. write the Counter in Data 2. write DataID nibble in Data, if E2E_P01_DA T AID_NIB…
PRS_E2E_00610PRS_E2E_00610AUTOSAR_FO_PRS_E2EProtocol.pdf S.92mediumFehlende Leerzeichen pruefenRS_E2E_08528If ForwardStatus equals to E2E_P_REPEA TED the function E2E_P01Forward() shall : 1. decrement the Counter 2. write Counter in Data 3. write DataID nibble in …
PRS_E2E_00611PRS_E2E_00611AUTOSAR_FO_PRS_E2EProtocol.pdf S.93mediumFehlende Leerzeichen pruefenRS_E2E_08528If ForwardStatus equals to E2E_P_WRONGSEQUENCE the function E2E_P01Forward() shall use counter + MaxDeltaCounterInit : 1. calculate Counter = Counter + MaxDe…
PRS_E2E_00612PRS_E2E_00612AUTOSAR_FO_PRS_E2EProtocol.pdf S.93mediumFehlende Leerzeichen pruefenRS_E2E_08528If ForwardStatus equals to E2E_P_ERROR the function E2E_P01Forward() shall use DataID + 1: 1. DataID = DataID+1 2. write the Counter in Data 3. write DataID …
PRS_E2E_00644PRS_E2E_00644AUTOSAR_FO_PRS_E2EProtocol.pdf S.101mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P01Protect and E2E_P01Forward functions ’state’ shall have the members defined in
PRS_E2E_00645PRS_E2E_00645AUTOSAR_FO_PRS_E2EProtocol.pdf S.101mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P01Check functions ’State’ shall have the members defined in
PRS_E2E_00588PRS_E2E_00588AUTOSAR_FO_PRS_E2EProtocol.pdf S.102mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P01Check function ’State->Status’ enumeration type shall have the following enumeration values (see
PRS_E2E_00121PRS_E2E_00121AUTOSAR_FO_PRS_E2EProtocol.pdf S.108mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the layout of the data buffer (Data) shall be as depicted in Figure
PRS_E2E_00123PRS_E2E_00123AUTOSAR_FO_PRS_E2EProtocol.pdf S.108mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the Counter shall be the low nibble (Bit 0...Bit 3) of Data[1]
PRS_E2E_00128PRS_E2E_00128AUTOSAR_FO_PRS_E2EProtocol.pdf S.108mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the range of the value of the Counter shall be [0...15]
PRS_E2E_00129PRS_E2E_00129AUTOSAR_FO_PRS_E2EProtocol.pdf S.108mediumFehlende Leerzeichen pruefenRS_E2E_08528When the Counter has reached its upper bound of 15 (0xF), it shall restart at 0 for the next call of the E2E_P02Protect() from the sending SW-C
PRS_E2E_00117PRS_E2E_00117AUTOSAR_FO_PRS_E2EProtocol.pdf S.109mediumFehlende Leerzeichen pruefenRS_E2E_08528E2E Profile 2 shall use the Crc_CalculateCRC8H2F() function of the SWS CRC Supervision for calculating CRC checksums
PRS_E2E_00119PRS_E2E_00119AUTOSAR_FO_PRS_E2EProtocol.pdf S.109mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the specific Data ID used to calculate a specific CRC shall be of length 8 bit
PRS_E2E_00120PRS_E2E_00120AUTOSAR_FO_PRS_E2EProtocol.pdf S.109mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the specific Data ID used for CRC calculation shall be selected from a pre-defined DataIDList[16] using the value of the Counter as an index
PRS_E2E_00118PRS_E2E_00118AUTOSAR_FO_PRS_E2EProtocol.pdf S.110mediumFehlende Leerzeichen pruefenRS_E2E_08528E2E Profile 2 shall use 0xFF as the start value CRC_StartValue8 for CRC calculation
PRS_E2E_00122PRS_E2E_00122AUTOSAR_FO_PRS_E2EProtocol.pdf S.110mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the CRC shall be Data[0]
PRS_E2E_00124PRS_E2E_00124AUTOSAR_FO_PRS_E2EProtocol.pdf S.110mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, both the E2E_P02Protect() and the E2E_P02Forward() function shall not modify any bit of Data except the bits representing the CRC and the C…
PRS_E2E_00127PRS_E2E_00127AUTOSAR_FO_PRS_E2EProtocol.pdf S.111mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Protect() function shall increment the Counter of the state (E2E_P02ProtectStateT ype) by 1 on every transmission request from t…
PRS_E2E_00130PRS_E2E_00130AUTOSAR_FO_PRS_E2EProtocol.pdf S.111mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the E2E_P02Protect() function shall update the Counter (i.e. low nibble (Bit 0...Bit 3) of Data byte 1) in the data buffer (Data) after inc…
PRS_E2E_00132PRS_E2E_00132AUTOSAR_FO_PRS_E2EProtocol.pdf S.112mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, after determining the specific Data ID, the E2E_P02Protect() and E2E_P02Forward() functions shall calculate the CRC over Data[1], Data[2], …
PRS_E2E_00133PRS_E2E_00133AUTOSAR_FO_PRS_E2EProtocol.pdf S.112mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the E2E_P02Protect() and E2E_P02Forward() functions shall update the CRC (i.e. Data[0]) in the data buffer (Data) after computing the CRC
PRS_E2E_00614PRS_E2E_00614AUTOSAR_FO_PRS_E2EProtocol.pdf S.113mediumNur ein Backend verfuegbarRS_E2E_08528In E2E Profile 2, the E2E_P02Forward() function shall increment the Counter according to Figure
PRS_E2E_00135PRS_E2E_00135AUTOSAR_FO_PRS_E2EProtocol.pdf S.120mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the local variable DeltaCounter shall be calculated by subtracting LastValidCounter from Counter in Data, considering an overflow due to th…
PRS_E2E_00136PRS_E2E_00136AUTOSAR_FO_PRS_E2EProtocol.pdf S.120mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, MaxDeltaCounter shall specify the maximum allowed difference between two Counter values of two consecutively received valid messages
PRS_E2E_00137PRS_E2E_00137AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, MaxDeltaCounter shall be incremented by 1 every time the E2E_P02Check() function is called, up to the maximum value of 15 (0xF)
PRS_E2E_00138PRS_E2E_00138AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall set Status to E2E_P02ST A TUS_NONEWDA T A if the attribute NewDataAvailable is FALSE
PRS_E2E_00139PRS_E2E_00139AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall determine the specific Data ID from DataIDList using the Counter of the received Data as index
PRS_E2E_00140PRS_E2E_00140AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall calculate CalculatedCRC over Data[1], Data[2], ... Data[Config->DataLength/8-1] of the data buffer (Data)…
PRS_E2E_00141PRS_E2E_00141AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall set Status to E2E_P02ST A TUS_WRONGCRC if the calculated CalculatedCRC value differs from the value of th…
PRS_E2E_00142PRS_E2E_00142AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall set Status to E2E_P02ST A TUS_INITIAL if the flag WaitForFirstData is TRUE
PRS_E2E_00143PRS_E2E_00143AUTOSAR_FO_PRS_E2EProtocol.pdf S.121mediumFehlende Leerzeichen pruefenRS_E2E_08528In E2E Profile 2, the E2E_P02Check() function shall clear the flag WaitForFirstData if it returns with Status E2E_P02ST A TUS_INITIAL
PRS_E2E_00145PRS_E2E_00145AUTOSAR_FO_PRS_E2EProtocol.pdf S.122mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall • set Status to E2E_P02ST A TUS_WRONGSEQUENCE; and • re-initialize SyncCounter with SyncCounterInit if the calculated value…
PRS_E2E_00146PRS_E2E_00146AUTOSAR_FO_PRS_E2EProtocol.pdf S.122mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall set Status to E2E_P02ST A TUS_REPEA TED if the calculated DeltaCounter equals
PRS_E2E_00147PRS_E2E_00147AUTOSAR_FO_PRS_E2EProtocol.pdf S.122mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall set Status to E2E_P02ST A TUS_OK if the following conditions are true: • the calculated DeltaCounter equals 1; and • the va…
PRS_E2E_00298PRS_E2E_00298AUTOSAR_FO_PRS_E2EProtocol.pdf S.122mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall • re-initialize SyncCounter with SyncCounterInit; and • set Status to E2E_P02ST A TUS_SYNC; if the following conditions are…
PRS_E2E_00148PRS_E2E_00148AUTOSAR_FO_PRS_E2EProtocol.pdf S.123mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall set Status to E2E_P02ST A TUS_OKSOMELOST if the following conditions are true: • the calculated DeltaCounter is greater-tha…
PRS_E2E_00149PRS_E2E_00149AUTOSAR_FO_PRS_E2EProtocol.pdf S.123mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall set the value LostData to (DeltaCounter - 1) if the calculated DeltaCounter is greater-than 1 but less-than or equal to Max…
PRS_E2E_00150PRS_E2E_00150AUTOSAR_FO_PRS_E2EProtocol.pdf S.123mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall re-initialize MaxDeltaCounter with MaxDelta- CounterInit if it returns one of the following Status: • E2E_P02ST A TUS_OK; o…
PRS_E2E_00299PRS_E2E_00299AUTOSAR_FO_PRS_E2EProtocol.pdf S.123mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall • decrement SyncCounter by 1 and set Status to E2E_P02ST A TUS_SYNC if the following conditions are true: • the calculated …
PRS_E2E_00151PRS_E2E_00151AUTOSAR_FO_PRS_E2EProtocol.pdf S.124mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall set LastValidCounter to Counter of Data if it returns one of the following Status: • E2E_P02ST A TUS_OK; or • E2E_P02ST A T…
PRS_E2E_00300PRS_E2E_00300AUTOSAR_FO_PRS_E2EProtocol.pdf S.124mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall reset the NoNewOrRepeatedDataCounter to 0 if it returns one of the following status: • E2E_P02ST A TUS_OK; or • E2E_P02ST A…
PRS_E2E_00301PRS_E2E_00301AUTOSAR_FO_PRS_E2EProtocol.pdf S.124mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E_P02Check() function shall increment NoNewOrRepeatedData- Counter by 1 if it returns the Status E2E_P02ST A TUS_NONEWDA T A or E2E_P02ST A TUS_REPEA T…
PRS_E2E_00647PRS_E2E_00647AUTOSAR_FO_PRS_E2EProtocol.pdf S.125mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P02Protect and E2E_P02Forward functions ’state’ shall have the members defined in
PRS_E2E_00589PRS_E2E_00589AUTOSAR_FO_PRS_E2EProtocol.pdf S.126mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P02Check functions ’State->Status’ enumeration type shall consist of the following enumeration values (see
PRS_E2E_00667PRS_E2E_00667AUTOSAR_FO_PRS_E2EProtocol.pdf S.127mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P02Protect, E2E_P02Forward and E2E_P02Check functions ’Config’ shall have the following members defined in
PRS_E2E_00652PRS_E2E_00652AUTOSAR_FO_PRS_E2EProtocol.pdf S.141mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P05Protect and E2E_P05Forward functions ’state’ shall have the members defined in
PRS_E2E_00653PRS_E2E_00653AUTOSAR_FO_PRS_E2EProtocol.pdf S.141mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P05Check functions ’State’ shall have the members defined in
PRS_E2E_00591PRS_E2E_00591AUTOSAR_FO_PRS_E2EProtocol.pdf S.142mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P05Check functions ’State->Status’ enumeration type shall consist the following enumeration values (see
PRS_E2E_00655PRS_E2E_00655AUTOSAR_FO_PRS_E2EProtocol.pdf S.153mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P06Protect and E2E_P06Forward functions ’state’ shall have the members defined in
PRS_E2E_00656PRS_E2E_00656AUTOSAR_FO_PRS_E2EProtocol.pdf S.153mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P06Check functions ’State’ shall have the members defined in
PRS_E2E_00592PRS_E2E_00592AUTOSAR_FO_PRS_E2EProtocol.pdf S.154mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P06Check functions ’State->Status’ enumeration type shall consist of the following enumeration values (see
PRS_E2E_00540PRS_E2E_00540AUTOSAR_FO_PRS_E2EProtocol.pdf S.164mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E Profile variant 11A is defined as follows: 1. CRC is the 0th byte in the signal group (i.e. starts with bit offset 0) 2. Alive counter is located in …
PRS_E2E_00541PRS_E2E_00541AUTOSAR_FO_PRS_E2EProtocol.pdf S.165mediumFehlende Leerzeichen pruefenRS_E2E_08528The E2E Profile variant 11C is defined as follows: 1. CRC is the 0th byte in the signal group (i.e. starts with bit offset 0) 2. Alive counter is located in …
PRS_E2E_00661PRS_E2E_00661AUTOSAR_FO_PRS_E2EProtocol.pdf S.180mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P11Protect and E2E_P11Forward functions ’State’ shall have the members defined in
PRS_E2E_00662PRS_E2E_00662AUTOSAR_FO_PRS_E2EProtocol.pdf S.180mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P11Check functions ’State’ shall have the members defined in
PRS_E2E_00594PRS_E2E_00594AUTOSAR_FO_PRS_E2EProtocol.pdf S.181mediumNur ein Backend verfuegbarRS_E2E_08528The E2E_P11Check functions ’State->Status’ shall consist of the following enumeration values (see
PRS_E2E_00596PRS_E2E_00596AUTOSAR_FO_PRS_E2EProtocol.pdf S.227mediumNur ein Backend verfuegbarRS_E2E_08528The E2E State Machine uses the following enumeration values to indicate its current status as defined in
PRS_E2E_00668PRS_E2E_00668AUTOSAR_FO_PRS_E2EProtocol.pdf S.238mediumNur ein Backend verfuegbarRS_E2E_08528The E2E State Machines ’Config’ object shall have the members as defined in
PRS_E2E_00669E2E State Machine State TypeAUTOSAR_FO_PRS_E2EProtocol.pdf S.239mediumNur ein Backend verfuegbarRS_E2E_08528The E2E State Machines ’State’ object shall have the members defined in
PRS_E2E_00597PRS_E2E_00597AUTOSAR_FO_PRS_E2EProtocol.pdf S.241mediumNur ein Backend verfuegbarRS_E2E_08528The E2E State Machine uses the following enumeration values as input from the Profile specific check functions as defined in
PRS_E2E_00598Mapping Profile 1 to State MachineAUTOSAR_FO_PRS_E2EProtocol.pdf S.241mediumNur ein Backend verfuegbarRS_E2E_08528The mapping between Profile 1 specific check states to the input for the E2E State Machine since R4.2 is described in
PRS_E2E_00599Mapping Profile 2 to State MachineAUTOSAR_FO_PRS_E2EProtocol.pdf S.242mediumNur ein Backend verfuegbarRS_E2E_08528The mapping between Profile 2 specific check states to the input for the E2E State Machine since R4.2 is described in
PRS_E2E_00641Mapping Profile 1 to State MachineAUTOSAR_FO_PRS_E2EProtocol.pdf S.242mediumNur ein Backend verfuegbarRS_E2E_08528The mapping between Profile 1 specific check states to the input for the E2E State Machine prior to R4.2 is described in
PRS_E2E_00600Mapping Profile 4,5,6,7,8,11,22,44,4m,7m,8m,44m to State Ma- chineAUTOSAR_FO_PRS_E2EProtocol.pdf S.243mediumNur ein Backend verfuegbarRS_E2E_08528The mapping between Profile 4 specific check states to the input for the E2E State Machine is described in
PRS_E2E_00670Mapping Profile 2 to State MachineAUTOSAR_FO_PRS_E2EProtocol.pdf S.243mediumNur ein Backend verfuegbarRS_E2E_08528The mapping between Profile 2 specific check states to the input for the E2E State Machine prior to R4.2 is described in
PRS_E2E_01456Data ID values Replaces: PRS_E2E_UC_00317AUTOSAR_FO_PRS_E2EProtocol.pdf S.261mediumNur ein Backend verfuegbarRS_E2E_08527When using E2E Profile Variants 1/11A and 1/11C in one bus/system, the following should be respected: 1. 1/11A data should use IDs that are < 256 (this means…