DEENESPTFRRUARHIKOZHNL
CLASSIC Modul: fee Rolle: constitutive Konfidenz: 95%

SNIP_CLASSIC_FEE_SECTION_8_3_3_Fee_Write

Quelle: SWS_FlashEEPROMEmulation.pdf (Seite 28) • Ziel-Anforderung: SWS_Std_00005

Wortlaut

8.3.3 Fee_Write [SWS_Fee_00088] Definition of API function Fee_Write Upstream requirements: SRS_MemHwAb_14010 ⌈ Service Name Fee_Write Syntax Std_ReturnType Fee_Write ( uint16 BlockNumber, const uint8* DataBufferPtr ) Service ID [hex] 0x03 Sync/Async Asynchronous Reentrancy Non Reentrant BlockNumber Number of logical block, also denoting start address of that block in EEPROM. Parameters (in) DataBufferPtr Pointer to data buffer Parameters (inout) None Parameters (out) None Return value Std_ReturnType E_OK: The requested job has been accepted by the module. E_NOT_OK: The requested job has not been accepted by the module. Description Service to initiate a write job. Available via Fee.h ⌋ [SWS_Fee_00024] Upstream requirements: SRS_MemHwAb_14006 ⌈The function Fee_Write shall take the block start address and calculate the corresponding memory write address. The block address offset shall be fixed to zero.⌋ [SWS_Fee_00025] Upstream requirements: SRS_MemHwAb_14010 ⌈If the current module status is MEMIF_IDLE or if the current module status is MEMIF_BUSY_INTERNAL, the function Fee_Write shall accept the write request, copy the given / computed parameters to module internal variables, initiate a write job, set the FEE module status to MEMIF_BUSY, set the job result to MEMIF_JOB_ PENDING and return with E_OK.⌋ [SWS_Fee_00174] ⌈If the current module status is MEMIF_UNINIT or MEMIF_BUSY, the function Fee_Write shall reject the job request and return with E_NOT_OK.⌋ [SWS_Fee_00026] Upstream requirements: SRS_MemHwAb_14010, ⌈The FEE module shall execute the write operation asynchronously within the FEE module’s main function.⌋ [SWS_Fee_00123] Upstream requirements: SRS_BSW_00406 ⌈If development error detection is enabled for the module: the function Fee_Write shall check if the module state is MEMIF_UNINIT. If this is the case, the function Fee_ Write shall raise the development error FEE_E_UNINIT.⌋ [SWS_Fee_00144] ⌈The function Fee_Write shall check if the module state is MEMIF_BUSY. If this is the case, the function Fee_Write shall reject the write request, raise the runtime error FEE_E_BUSY and return with E_NOT_OK.⌋ [SWS_Fee_00138] Upstream requirements: SRS_BSW_00323 ⌈If development error detection is enabled for the module: the function Fee_Write shall check that the given block number is valid (i.e. it has been configured). If this is not the case, the function Fee_Write shall raise the development error FEE_E_ INVALID_BLOCK_NO.⌋ [SWS_Fee_00139] Upstream requirements: SRS_BSW_00323 ⌈If development error detection is enabled for the module: the function Fee_Write shall check that the given data pointer is valid (i.e. that it is not NULL). If this is not the case, the function Fee_Write shall raise the development error FEE_E_PARAM_ POINTER.⌋ [SWS_Fee_00163] ⌈If a write request is rejected by the function Fee_Write, i.e. requirements [SWS_Fee_00123], [SWS_Fee_00144], [SWS_Fee_00138] or [SWS_Fee_00139] apply, the function Fee_Write shall not change the current module status or job result.⌋

Versionen & Provenienz · Zugeordnete Anforderungen

Diese Angaben zeigt der Versions-Explorer.

Begründung & Zuweisungs-Evidenz

Cited verbatim in the snippet (deterministic citation).

Dokumenten-Herkunft & Rückverfolgbarkeit

Spezifikations-Dokument SWS_FlashEEPROMEmulation.pdf
Dokumentseite Seite 28
Ziel-Modul fee (classic)
Ziel-Anforderung SWS_Std_00005
Semantische Rolle constitutive
Automatisierungs-Konfidenz 0.95