USBD ROM Stack  2.0
ROM based USB device stack
Data Fields
USBD_MSC_INIT_PARAM_T Struct Reference

Mass Storage class function driver initialization parameter data structure. More...

#include <C:/Data/nxp/GIT/lpcopen_v3/lpcopen_version3/LPC43xx_18xx/lpc43xx_18xx/LPC_USBD_Lib/mw_usbd/mw_usbd_mscuser.h>

Data Fields

uint32_t mem_base
 
uint32_t mem_size
 
uint8_t * InquiryStr
 
uint32_t BlockCount
 
uint32_t BlockSize
 
uint32_t MemorySize
 
uint8_t * intf_desc
 
void(* MSC_Write )(uint32_t offset, uint8_t **src, uint32_t length, uint32_t high_offset)
 
void(* MSC_Read )(uint32_t offset, uint8_t **dst, uint32_t length, uint32_t high_offset)
 
ErrorCode_t(* MSC_Verify )(uint32_t offset, uint8_t buf[], uint32_t length, uint32_t high_offset)
 
void(* MSC_GetWriteBuf )(uint32_t offset, uint8_t **buff_adr, uint32_t length, uint32_t high_offset)
 
ErrorCode_t(* MSC_Ep0_Hdlr )(USBD_HANDLE_T hUsb, void *data, uint32_t event)
 
uint64_t MemorySize64
 

Detailed Description

Mass Storage class function driver initialization parameter data structure.

This data structure is used to pass initialization parameters to the Mass Storage class function driver's init function.

Field Documentation

◆ mem_base

uint32_t USBD_MSC_INIT_PARAM_T::mem_base

Base memory location from where the stack can allocate data and buffers.

Note
The memory address set in this field should be accessible by USB DMA controller. Also this value should be aligned on 4 byte boundary.

◆ mem_size

uint32_t USBD_MSC_INIT_PARAM_T::mem_size

The size of memory buffer which stack can use.

Note
The mem_size should be greater than the size returned by USBD_MSC_API::GetMemSize() routine.

◆ InquiryStr

uint8_t* USBD_MSC_INIT_PARAM_T::InquiryStr

Pointer to the 28 character string. This string is sent in response to the SCSI Inquiry command.

Note
The data pointed by the pointer should be of global scope.

◆ BlockCount

uint32_t USBD_MSC_INIT_PARAM_T::BlockCount

Number of blocks present in the mass storage device

◆ BlockSize

uint32_t USBD_MSC_INIT_PARAM_T::BlockSize

Block size in number of bytes

◆ MemorySize

uint32_t USBD_MSC_INIT_PARAM_T::MemorySize

Memory size in number of bytes

◆ intf_desc

uint8_t* USBD_MSC_INIT_PARAM_T::intf_desc

Pointer to the interface descriptor within the descriptor array (high_speed_desc) passed to Init() through USB_CORE_DESCS_T structure. The stack assumes both HS and FS use same BULK endpoints.

◆ MSC_Write

void(* USBD_MSC_INIT_PARAM_T::MSC_Write) (uint32_t offset, uint8_t **src, uint32_t length, uint32_t high_offset)

MSC Write callback function.

This function is provided by the application software. This function gets called when host sends a write command.

Parameters
[in]Lower32 bit offset of Destination start address.
[in,out]srcPointer to a pointer to the source of data. Pointer-to-pointer is used to implement zero-copy buffers. See Zero-Copy Data Transfer model for more details on zero-copy concept.
[in]lengthNumber of bytes to be written.
[in]Higher32 bit offset of start address.
Returns
Nothing.

◆ MSC_Read

void(* USBD_MSC_INIT_PARAM_T::MSC_Read) (uint32_t offset, uint8_t **dst, uint32_t length, uint32_t high_offset)

MSC Read callback function.

This function is provided by the application software. This function gets called when host sends a read command.

Parameters
[in]Lower32 bit offset of Source start address.
[in,out]dstPointer to a pointer to the source of data. The MSC function drivers implemented in stack are written with zero-copy model. Meaning the stack doesn't make an extra copy of buffer before writing/reading data from USB hardware FIFO. Hence the parameter is pointer to a pointer containing address buffer (uint8_t** dst). So that the user application can update the buffer pointer instead of copying data to address pointed by the parameter. /note The updated buffer address should be accessible by USB DMA master. If user doesn't want to use zero-copy model, then the user should copy data to the address pointed by the passed buffer pointer parameter and shouldn't change the address value. See Zero-Copy Data Transfer model for more details on zero-copy concept.
[in]lengthNumber of bytes to be read.
[in]Higher32 bit offset of start address.
Returns
Nothing.

◆ MSC_Verify

ErrorCode_t(* USBD_MSC_INIT_PARAM_T::MSC_Verify) (uint32_t offset, uint8_t buf[], uint32_t length, uint32_t high_offset)

MSC Verify callback function.

This function is provided by the application software. This function gets called when host sends a verify command. The callback function should compare the buffer with the destination memory at the requested offset and

Parameters
[in]Lower32 bit offset of Destination start address.
[in]bufBuffer containing the data sent by the host.
[in]lengthNumber of bytes to verify.
[in]Higher32 bit offset of start address.
Returns
Returns ErrorCode_t type to indicate success or error condition.
Return values
LPC_OKIf data in the buffer matches the data at destination
ERR_FAILEDAt least one byte is different.

◆ MSC_GetWriteBuf

void(* USBD_MSC_INIT_PARAM_T::MSC_GetWriteBuf) (uint32_t offset, uint8_t **buff_adr, uint32_t length, uint32_t high_offset)

Optional callback function to optimize MSC_Write buffer transfer.

This function is provided by the application software. This function gets called when host sends SCSI_WRITE10/SCSI_WRITE12 command. The callback function should update the buff_adr pointer so that the stack transfers the data directly to the target buffer. /note The updated buffer address should be accessible by USB DMA master. If user doesn't want to use zero-copy model, then the user should not update the buffer pointer. See Zero-Copy Data Transfer model for more details on zero-copy concept.

Parameters
[in]Lower32 bit offset of Destination start address.
[in,out]bufBuffer containing the data sent by the host.
[in]lengthNumber of bytes to write.
[in]Higher32 bit offset of start address.
Returns
Nothing.

◆ MSC_Ep0_Hdlr

ErrorCode_t(* USBD_MSC_INIT_PARAM_T::MSC_Ep0_Hdlr) (USBD_HANDLE_T hUsb, void *data, uint32_t event)

Optional user override-able function to replace the default MSC class handler.

The application software could override the default EP0 class handler with their own by providing the handler function address as this data member of the parameter structure. Application which like the default handler should set this data member to zero before calling the USBD_MSC_API::Init().

Note
Parameters
[in]hUsbHandle to the USB device stack.
[in]dataPointer to the data which will be passed when callback function is called by the stack.
[in]eventType of endpoint event. See USBD_EVENT_T for more details.
Returns
The call back should returns ErrorCode_t type to indicate success or error condition.
Return values
LPC_OKOn success.
ERR_USBD_UNHANDLEDEvent is not handled hence pass the event to next in line.
ERR_USBD_xxxFor other error conditions.

The documentation for this struct was generated from the following file: