Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.

FSDev_NOR_PhyWr()

void FSDev_NOR_PhyWr (CPU_CHAR *name_dev,

void *p_src,

CPU_INT32U start,

CPU_INT32U cnt,

FS_ERR *p_err);

 

File

Called from

Code enabled by

fs_dev_nor.c

Application

N/A

Write to a NOR device from a buffer.

Arguments

name_dev

Device name (see Note).

p_src

Pointer to source buffer.

start

Start address of write (relative to start of device).

cnt

Number of octets to write.

p_err

Pointer to variable that will the receive return error code from this function:

FS_ERR_NONE
Octets written successfully.
FS_ERR_NAME_NULL
Argument name_dev passed a NULL pointer.
FS_ERR_NULL_PTR
Argument p_src passed a NULL pointer.
FS_ERR_DEV_INVALID
Argument name_dev specifies an invalid device.
FS_ERR_DEV_NOT_OPEN
Device is not open.
FS_ERR_DEV_NOT_PRESENT
Device is not present.
FS_ERR_DEV_INVALID_LOW_FMT
Device needs to be low-level formatted.
FS_ERR_DEV_IO
Device I/O error.
FS_ERR_DEV_TIMEOUT
Device timeout.

Returned Value

None.

Notes/Warnings

The device must be a NOR device (e.g., “nor:0:”).

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 octet location(s) modified are not validated as being outside any existing file system or low-level format information.

During a program operation, only 1 bits can be changed; a 0 bit cannot be changed to a 1. The application must know that the octets being programmed have not already been programmed.

  • No labels