UM10503
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2012. All rights reserved.
User manual
Rev. 1.3 — 6 July 2012
658 of 1269
NXP Semiconductors
UM10503
Chapter 25: LPC43xx USB API
25.5.32 USBD_HID_API
HID class API functions structure.This structure contains pointers to all the function
exposed by HID function driver module.
DFU_Done
void(*void(* USBD_DFU_INIT_PARAM::DFU_Done)(void))(void)
DFU done callback function.
This function is provided by the application software. This function gets called after download is
finished.
Nothing.
Returns:
Nothing.
DFU_Detach
void(*void(* USBD_DFU_INIT_PARAM::DFU_Detach)(USBD_HANDLE_T hUsb))(USBD_HANDLE_T hUsb)
DFU detach callback function.
This function is provided by the application software. This function gets called after
USB_REQ_DFU_DETACH is received. Applications which set USB_DFU_WILL_DETACH bit in DFU
descriptor should define this function. As part of this function application can call Connect() routine to
disconnect and then connect back with host. For application which rely on WinUSB based host
application should use this feature since USB reset can be invoked only by kernel drivers on Windows
host. By implementing this feature host doesn't have to issue reset instead the device has to do it
automatically by disconnect and connect procedure.
Parameters:
1. hUsb = Handle DFU control structure.
Returns:
Nothing.
DFU_Ep0_Hdlr
ErrorCode_t(*ErrorCode_t(* USBD_DFU_INIT_PARAM::DFU_Ep0_Hdlr)(USBD_HANDLE_T hUsb, void *data, uint32_t
event))(USBD_HANDLE_T hUsb, void *data, uint32_t event)
Optional user over ridable function to replace the default DFU 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_DFU_API::Init().
Remark:
Parameters:
1. hUsb = Handle to the USB device stack.
2. data = Pointer to the data which will be passed when callback function is called by the stack.
3. event = Type 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:
1. LPC_OK = On success.
2. ERR_USBD_UNHANDLED = Event is not handled hence pass the event to next in line.
3. ERR_USBD_xxx = For other error conditions.
Table 523. USBD_DFU_INIT_PARAM class structure
Member
Description