Separate density from model-selected erase-unit organization
Density describes the total storage available. Erase organisation describes how that storage is divided into units that an erase operation can affect. Infineon's FL-S flash-array discussion identifies a hybrid organisation and a uniform organisation, with the choice depending on the selected device model. The aggregate capacity therefore does not identify the erase-unit arrangement, even when two candidates appear under the same broad family description.
A hybrid organisation contains different sector roles within the array. A uniform organisation instead gives the array a common sector-size basis. These are meaningful differences for software that expects to modify one region while preserving another. The important comparison is the relationship between the intended update region and the documented erase unit, rather than merely whether enough total storage exists.
Keep the model-dependent organisation attached to the memory identity. A shortened density entry can preserve the total amount of memory while losing this operating distinction. Restoring the exact option is therefore part of defining the erase task, before discussing command handling or host support. The named FL-S prose supplies the architectural distinction without requiring an address-map calculation, sector-count table or extrapolation to every serial NOR family.
Keep the small-sector location separate from the protection boundary
Within the hybrid organisation, parameter-sector location and protection location serve different purposes. Infineon describes TBPARM as defining the logical position of the parameter block. It separately states that TBPROT can be selected independently. One concerns where the small-sector region resides; the other concerns the protection boundary. A top-or-bottom description is incomplete unless it identifies which of those responsibilities it means.
The independence permits parameter storage and protected boot information to occupy different ends of the array in the documented example. It also permits them to be associated at the same end. Those are alternatives in the source, rather than evidence of how an unidentified device is presently configured. Treating the two fields as synonyms would conceal this distinction and could attach a protection assumption to the wrong region.
The uniform-organisation case has a different basis because its sectors do not form the same small-sector parameter region. Infineon states that the parameter-location field has no effect in that organisation. A placement description therefore needs its organisation context as well as its protection context. The distinction identifies which role the field describes; it neither supplies a configuration procedure nor infers an existing setting from an ordering-family label.
Retain ordered erase granularity and protected subregions
An erase-command name does not establish one universal coverage across every ordering option. Infineon states that the sector-erase extent depends on the selected option. Its parameter-sector erase description also limits support according to the configured organisation. The organisation and the permitted erase operation must therefore be read together; sharing a command label is not enough to establish that the same array region will be affected.
Protection adds another boundary inside the requested erase range. The FL-S prose describes cases where a wider erase range contains a protected subregion. In those stated cases, the wider erase is not executed. This is a relationship between command coverage and protected storage, rather than a promise that the unprotected remainder will still be erased. A small protected area can thus matter to a larger requested operation.
A useful comparison identifies three separate scopes: the erase units supplied by the model, the range addressed by the applicable operation, and any protected region within that range. Keeping them separate makes the erase expectation intelligible without reconstructing command bytes or calculating addresses. It also explains why capacity, a familiar erase name and a general protection feature cannot individually establish the behaviour of the exact option being considered.
Treat suspend as limited access rather than completed erase
Erase suspend interrupts a sector operation so that the system can perform permitted work elsewhere. Infineon's explanation allows reading or programming in other sectors after the operation has been suspended. The sector undergoing erase remains a distinct region. Reading within that suspended sector produces undetermined data, so permission to access the device must not be expanded into permission to use final data from the interrupted region.
The source also distinguishes a suspended operation from one that completed while suspension was being requested. These are different states even though the initial request concerned the same erase. Continuing an interrupted erase and observing a completed erase consequently have different meanings. A suspend feature cannot be described simply as making the whole memory ready, because both the operation state and the accessed region remain relevant.
Retain the sector-operation boundary as well. The documented suspend command does not apply to bulk erase in the same way. This keeps the capability tied to its supported operation rather than to a generic interruption label. The practical decision is whether the required concurrent access stays within the allowed region and operation. It does not establish a finished erase, an application recovery sequence or successful data preservation in actual hardware.
Sources and further reading
Infineon 001-98283 Rev. *T, dated 21 April 2025: saved pages 47, 56, 112, 114 and 115 bounded prose on organisation, parameter/protection roles, erase scope and suspend access. No opcodes, address arithmetic, register-writing sequence, table values or diagram interpretation is supplied.