28HS01GTAM03 datasheet(63/138 Pages) INFINEON

63 / 138 page

Datasheet

63 of 138

002-18216 Rev. *W

2022-01-18

256Mb/512Mb/1Gb SEMPER™ Flash

Octal interface, 1.8V/3.0V

Features

4.11.2

Erase 256KB sector transaction

The Erase 256KB Sector (ER256_4_0) transaction sets all bits in the addressed sector to 1 (all bytes are FFh) (see

Transaction table on page 95).

A device configuration option (CFR3V[3]) determines if the Hybrid Sector Architecture is in use. When CFR3V[3] =

0, 4KB sectors overlay a portion of the highest or lowest address 128KB or 64KB of the device address space. If a

sector erase command is applied to a 256KB sector that is overlaid by 4KB sectors, the overlaid 4KB sectors are

not affected by the erase. Only the visible (non-overlaid) portion of the 128KB or 192KB sector is erased. When

CFR3V[3] = 1, there are no 4KB sectors in the device address space and the Sector Erase command always

operates on fully visible 256KB sectors.

When BLKCHK is enabled an erase transaction first evaluates the erase status of the sector. If the sector is found

to erased, the erase operation is aborted. The erase operation is only executed if programmed bits are found in

the sector. Disabling BLKCHK executes an erase operation unconditionally.

4.11.3

Erase chip transaction

The Erase Chip (ERCHP_0_0) transaction sets all bits to 1 (all bytes are FFh) inside the entire flash memory array

(see Transaction table on page 95).

An Erase Chip transaction can be executed only when the Block Protection (BP2, BP1, BP0) bits are set to 0’s. If

the BP bits are not zero, the transaction is not executed and ERSERR status fail bit is not set. The transaction will

skip any sectors protected by the Advance Sector Protection DYB or PPB and the ERSERR status fail bit will not

be set.

4.11.4

Erase persistent protection bit (PPB) transaction

The Erase PPB (ERPPB_0_0) transaction sets all PPB bits to 1 (see Transaction table on page 95). This

transaction will abort if PPB bits are protected by ASPPPB (ASPO[3]), ASPPRM (ASPO[0]) and PPBLCK (PPLV[0])

bit.

4.11.5

Erase status and count

4.11.5.1

Evaluate erase status transaction

The Evaluate Erase Status (EVERS_4_0) transaction verifies that the last erase operation on the addressed sector

was completed successfully. If the selected sector was successfully erased, then the erase status bit (STR2V[2]) is

set to 1. If the selected sector was not completely erased STR2V[2] is 0. The Write/Program Enable transaction (to

set the WRPGEN bit) is not required before this transaction. However, the RDYBSY bit is set by the device itself

and cleared at the end of the operation, as visible in STR1V[0] when reading status (see Transaction table on

page 95).

The Evaluate Erase Status transaction can be used to detect when erase operations that have failed due to loss

of power, reset, or failure during the erase operation. The transaction requires tEES to complete and update the

erase status in STR2V. The RDYBSY bit (STR1V[0]) can be read to determine when the Evaluate Erase Status trans-

action is completed. If a sector is found not erased with STR2V[2] = 0, the sector must be erased again to ensure

reliable storage of data in the sector.

4.11.5.2

Sector erase count transaction

The Sector Erase Count (SEERC_4_0) transaction outputs the number of erase cycles for the addressed sector.

The erase cycle count is stored in the Sector Erase Count (SECV[22:0]) Register, and can be read by using the Read

Any Register transaction. The RDYBSY bit is set by the device itself and cleared at the end of the operation, as

visible in STR1V[0] when reading status (see Transaction table on page 95).

The transaction requires tSEC to complete and update the SECV[22:0] Register. The RDYBSY bit (STR1V[0]) may be

read to determine when the Sector Erase Count Transaction finished. The SECV[23] bit is used to determine if the

reported sector erase count is corrupted and was reset.

28HS01GTAM03 Datenblatt(PDF) 63 Page - Infineon Technologies AG

28HS01GTAM03 Datenblatt(HTML) 63 Page - Infineon Technologies AG

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 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datenblatt Download

Link URL