Erasing blocks is permitted with a minimum granularity of 'erase_unit'.

Note

: if 'erasable' is 0–i.e. the 'erase' operation isn't available–then 'erase_unit' (see below) is immaterial and should be 0.

Definition at line 56 of file Driver_Storage.h.

Minimum erase size in bytes.

The offset of the start of the erase-range should also be aligned with this value. Applicable if the 'erasable' attribute is set for the block.

Note

: if 'erasable' (see above) is 0–i.e. the 'erase' operation isn't available–then 'erase_unit' is immaterial and should be 0.

Definition at line 68 of file Driver_Storage.h.

This storage block can hold program data; the processor can fetch and execute code sourced from it.

Often this is accompanied with the device being 'memory_mapped' (see ARM_STORAGE_INFO).

Definition at line 63 of file Driver_Storage.h.

Writing to ranges is permitted with a minimum granularity of 'program_unit'.

Writes are typically achieved through the ProgramData operation (following an erase); if storage isn't erasable (see 'erasable' above) but is memory-mapped (i.e. 'memory_mapped'), it can be written directly using memory-store operations.

Definition at line 59 of file Driver_Storage.h.

The entire block can be protected from program and erase operations.

Once protection is enabled for a block, its 'erasable' and 'programmable' bits are turned off.

Definition at line 65 of file Driver_Storage.h.

Minimum protectable size in bytes.

Applicable if the 'protectable' attribute is set for the block. This should be a divisor of the block's size. A block can be considered to be made up of consecutive, individually-protectable fragments.

Definition at line 73 of file Driver_Storage.h.