UM1635 datasheet(13/42 Pages) STMICROELECTRONICS

13 / 42 page

DocID024604 Rev 2

13/42

UM1635

API specification

If the selected main array blocks or the shadow row is locked for erasing, those blocks or

the shadow row is not erased, but ‘FlashErase()’ still returns C90FL_OK. User needs to

check the erasing result with the ‘BlankCheck()’ function.

It is impossible to erase any Flash block or shadow row when a program or erase operation

is already in progress on C90FL2 module. ‘FlashErase()’ returns C90FL_ERROR_BUSY

when trying to do so.

In addition, when ‘FlashErase()’ is running, it is unsafe to read the data from the Flash

partitions having one or more blocks being erased. Otherwise, it causes a Read-While-Write

error.

Assumptions

It assumes that the Flash block is initialized using the ‘FlashInit()’ API. User provides the

correct ssdConfig parameters to FlashErase() as returned by FlashInit().

2.6.3

BlankCheck()

Description

This function checks on the specified Flash range in the main array or shadow row for blank

state. If the blank checking fails, the first failing address and the failing data in Flash block is

saved.

Prototype

UINT32 BlankCheck (PSSD_CONFIG pSSDConfig,

UINT32 dest,

UINT32 size,

UINT32 * pFailAddress,

UINT64 *pFailData,

void (*CallBack) (void ));

Table 10. Bit allocation for blocks in middle address space

MSB

LSB

bit 31

…

bit 4

bit 3

bit 2

bit 1

bit 0

reserved

…

reserved

block 1

block 0

Table 11. Bit allocation for blocks in high address space

MSB

LSB

bit 31

…

bit 6

bit 5

bit 4

…

bit 1

bit 0

reserved

…

reserved

block 5

block 4

…

Block 1

Block 0

UM1635 Datasheet(PDF) 13 Page - STMicroelectronics

UM1635 Datasheet(HTML) 13 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

Datasheet Download

Link URL