Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

26HS01GTAM03 Datasheet(PDF) 75 Page - Infineon Technologies AG

Part # 26HS01GTAM03
Description  256Mb/512Mb/1Gb SEMPER??Flash HYPERBUS??interface, 1.8V/3.0V
PDF  166 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  INFINEON [Infineon Technologies AG]
Direct Link  http://www.infineon.com
Logo INFINEON - Infineon Technologies AG

26HS01GTAM03 Datasheet(HTML) 75 Page - Infineon Technologies AG

Back Button 26HS01GTAM03 Datasheet HTML 71Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 72Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 73Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 74Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 75Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 76Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 77Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 78Page - Infineon Technologies AG 26HS01GTAM03 Datasheet HTML 79Page - Infineon Technologies AG Next Button
Zoom Inzoom in Zoom Outzoom out
 75 / 166 page
background image
Datasheet
75 of 166
002-12337 Rev. *Y
2022-01-18
256Mb/512Mb/1Gb SEMPER™ Flash
HYPERBUS™ interface, 1.8V/3.0V
Features
4.11.6
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).
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.7
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.
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.8
Erase persistent protection bit (PPB) transaction
The Erase PPB transaction sets all PPB bits to 1. This transaction will abort if PPB bits are protected by ASPPPB
(ASPO[3]), ASPPRM (ASPO[0]) and PPBLCK (PPLV[0]) bit.
4.11.9
Erase status and count
4.11.9.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.
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.9.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 Sector Erase Count (SECV[22:0]) Register, and can be read by using the Read
Any Register transaction (RDARG_4_0). 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.
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 is finished. The SECV[23] bit is used to determine if
the reported sector erase count is corrupted and was reset.



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


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com