SNIP_CLASSIC_EA_SECTION_7_1_5_Managing_block_consistency_information

7.1.5 Managing block consistency information [SWS_Ea_00046] Upstream requirements: SRS_MemHwAb_14014 ⌈The Ea module shall manage for each block the information, whether this block is "correct" from the point of view of the EA module or not. This consistency information shall only concern the internal handling of the block, not the block’s contents.⌋ [SWS_Ea_00047] Upstream requirements: SRS_MemHwAb_14014 ⌈When a block write operation is started the EA module shall mark the corresponding block as inconsistent 1. Upon the successful end of the block write operation, the EA module shall mark the block as consistent (again).⌋ Note: This internal management information should not be mixed up with the validity information of a block which can be manipulated by using the Ea_InvalidateBlock ser- 1This does not necessarily mean a write operation on the physical device. If there are other means to detect the consistency of a logical block, changing the management information stored with the block shall be avoided. vice, i.e. the EA module shall be able to distinguish between an inconsistent block and a block that has been deliberately invalidated by the upper layer.