Jump to main content

##

# 3.7.4.3 USB_HOST_MSD_RESULT Enumeration

## C

    typedef enum {
      USB_HOST_MSD_RESULT_COMMAND_PASSED = 0,
      USB_HOST_MSD_RESULT_COMMAND_FAILED = 1,
      USB_HOST_MSD_RESULT_COMMAND_PHASE_ERROR = 2,
      USB_HOST_MSD_RESULT_SUCCESS,
      USB_HOST_MSD_RESULT_FAILURE,
      USB_HOST_MSD_RESULT_BUSY,
      USB_HOST_MSD_RESULT_LUN_HANDLE_INVALID,
      USB_HOST_MSD_RESULT_COMMAND_STALLED
    } USB_HOST_MSD_RESULT;

## Summary

USB HOST MSD Result

This enumeration defines the possible return values of different USB HOST MSD Client driver function call. Refer to the specific function documentation for details on the return values.

## Members

Members | Description
USB_HOST_MSD_RESULT_COMMAND_PASSED = 0 | MSD Command result was success. The command issued to the MSD device passed.
USB_HOST_MSD_RESULT_COMMAND_FAILED = 1 | MSD Command failed. The command issued to the MSD device failed. The device BOT state machine is in sync with the host. The data residue length is valid.
USB_HOST_MSD_RESULT_COMMAND_PHASE_ERROR = 2 | MSD Command failed with phase error. The command issued to the MSD device has failed. The failure reason is unknown. The MSD Host Client driver has reset the device BOT state machine.
USB_HOST_MSD_RESULT_SUCCESS | The operation was successful
USB_HOST_MSD_RESULT_FAILURE | An unknown failure has occurred.
USB_HOST_MSD_RESULT_BUSY | The request cannot be accepted at this time
USB_HOST_MSD_RESULT_LUN_HANDLE_INVALID | The specified LUN is not valid
USB_HOST_MSD_RESULT_COMMAND_STALLED | The MSD request was stalled

## Remarks

None.