...
void FSDev_NOR_PhyEraseBlk (CPU_CHAR *name_dev,
...
CPU_INT32U start,
...
CPU_INT32U size,
...
FS_ERR *p_err);
...
File |
...
Called from |
...
...
Code enabled by |
...
...
|
...
...
Application |
...
...
N/A |
Anchor
Arguments
...
name_dev
Device name (see Note).
...
start
Start address of block (relative to start of device).
Anchor
size
Size of block, in octets.
...
p_err
Pointer to variable that will the receive return error code from this function:
...
class | WebWorks_Indent_1 |
---|
...
...
FS_ERR_NONE
...
class | WebWorks_Indent_2 |
---|
...
...
Block erased successfully.
...
class | WebWorks_Indent_1 |
---|
...
FS_ERR_NAME_NULL
...
class | WebWorks_Indent_2 |
---|
...
Argument name_dev
passed a NULL pointer.
...
...
FS_ERR_DEV_INVALID
...
...
Argument name_dev
specifies an invalid device
...
...
FS_ERR_DEV_NOT_OPEN
...
class | WebWorks_Indent_2 |
---|
...
...
Device is not open.
...
class | WebWorks_Indent_1 |
---|
...
FS_ERR_DEV_NOT_PRESENT
...
class | WebWorks_Indent_2 |
---|
...
...
Device is not present.
...
class | WebWorks_Indent_1 |
---|
...
FS_ERR_DEV_INVALID_LOW_FMT
...
...
Device needs to be low-level formatted.
...
...
FS_ERR_DEV_IO
...
class | WebWorks_Indent_2 |
---|
...
Device I/O error.
...
class | WebWorks_Indent_1 |
---|
...
FS_ERR_DEV_TIMEOUT
...
class | WebWorks_Indent_2 |
---|
...
Device timeout.
...
...
Returned Value
Anchor
Notes/Warnings
...
The device must be a NOR device (e.g., “nor“nor:0:
”). Anchor
Care should be taken if this function is used while a file system exists on the device, or if the device is low-level formatted. The erased block is not validated as being outside any existing file system or low-level format information.