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 640 of 1269NXP Semiconductors UM10503Chapter 25: LPC43xx USB API25.5.26 USBD_API_INIT_PARAMUSB device stack initilization parameter data structure.cdc const USBD_CDC_API_T *const USBD_CDC_API_T* USBD_API::cdcPointer to function table which exposes functions provided by CDC-ACM function driver module.reserved6 const uint32_t *const uint32_t* USBD_API::reserved6Reserved for future function driver module.version const uint32_tconst uint32_t USBD_API::versionVersion identifier of USB ROM stack. The version is defined as 0x0CHDMhCC where each nibblerepresents version number of the corresponding component. CC - 7:0 - 8bit core version number h - 11:8- 4bit hardware interface version number M - 15:12 - 4bit MSC class module version number D - 19:16 -4bit DFU class module version number H - 23:20 - 4bit HID class module version number C - 27:24 - 4bitCDC class module version number H - 31:28 - 4bit reservedTable 517. USBD_API class structureMember DescriptionTable 518. USBD_API_INIT_PARAM class structureMember Descriptionusb_reg_base uint32_tuint32_t USBD_API_INIT_PARAM::usb_reg_baseUSB device controller's base register address.mem_base uint32_tuint32_t USBD_API_INIT_PARAM::mem_baseBase memory location from where the stack can allocate data and buffers.Remark: The memory address set in this field should be accessible by USB DMA controller. Alsothis value should be aligned on 2048 byte boundary.mem_size uint32_tuint32_t USBD_API_INIT_PARAM::mem_sizeThe size of memory buffer which stack can use.Remark: The mem_size should be greater than the size returned byUSBD_HW_API::GetMemSize() routine.max_num_ep uint8_tuint8_t USBD_API_INIT_PARAM::max_num_epmax number of endpoints supported by the USB device controller instance (specified bypad0 uint8_tuint8_t USBD_API_INIT_PARAM::pad0[3][3]USB_Reset_Event USB_CB_TUSB_CB_T USBD_API_INIT_PARAM::USB_Reset_EventEvent for USB interface reset. This event fires when the USB host requests that the device resetits interface. This event fires after the control endpoint has been automatically configured by thelibrary.Remark: This event is called from USB_ISR context and hence is time-critical. Having delays inthis callback will prevent the device from enumerating correctly or operate properly.USB_Suspend_Event USB_CB_TUSB_CB_T USBD_API_INIT_PARAM::USB_Suspend_EventEvent for USB suspend. This event fires when the USB host suspends the device by halting itstransmission of Start Of Frame pulses to the device. This is generally hooked in order to move thedevice over to a low power state until the host wakes up the device.Remark: This event is called from USB_ISR context and hence is time-critical. Having delays inthis callback will cause other system issues.