Commit b3a4d851 authored by Dean Camera's avatar Dean Camera
Browse files

Fixed incorrect PID value being used in the USBtoSerial project (thanks to Phill).

parent 59becad8
...@@ -54,7 +54,7 @@ USB_Descriptor_Device_t PROGMEM DeviceDescriptor = ...@@ -54,7 +54,7 @@ USB_Descriptor_Device_t PROGMEM DeviceDescriptor =
.Endpoint0Size = FIXED_CONTROL_ENDPOINT_SIZE, .Endpoint0Size = FIXED_CONTROL_ENDPOINT_SIZE,
.VendorID = 0x03EB, .VendorID = 0x03EB,
.ProductID = 0x2044, .ProductID = 0x204B,
.ReleaseNumber = 0x0000, .ReleaseNumber = 0x0000,
.ManufacturerStrIndex = 0x01, .ManufacturerStrIndex = 0x01,
......
...@@ -25,6 +25,7 @@ ...@@ -25,6 +25,7 @@
* - Removed STREAM_CALLBACK() macro - callbacks now use regular function definitions to clarify user code * - Removed STREAM_CALLBACK() macro - callbacks now use regular function definitions to clarify user code
* - Removed DESCRIPTOR_COMPARATOR() macro - comparators should now use regular function definitions to clarify user code * - Removed DESCRIPTOR_COMPARATOR() macro - comparators should now use regular function definitions to clarify user code
* - USB_IsConnected is now cleared before the USB_Disconnect() event is fired in response to VBUS being removed * - USB_IsConnected is now cleared before the USB_Disconnect() event is fired in response to VBUS being removed
* - Fixed incorrect PID value being used in the USBtoSerial project (thanks to Phill)
* *
* *
* \section Sec_ChangeLog090510 Version 090510 * \section Sec_ChangeLog090510 Version 090510
......
...@@ -128,14 +128,15 @@ ...@@ -128,14 +128,15 @@
* in device mode) in order to manage USB communications. This task may be executed inside an RTOS, * in device mode) in order to manage USB communications. This task may be executed inside an RTOS,
* scheduler (e.g. the simple LUFA Scheduler), fast timer ISR or the main user application loop. * scheduler (e.g. the simple LUFA Scheduler), fast timer ISR or the main user application loop.
* *
* The USB task must be serviced within 50mS in all modes, when needed. The task may be serviced * The USB task must be serviced within 30ms while in device mode, or within 1ms while in host mode.
* at all times, or (for minimum CPU consumption): * The task may be serviced at all times, or (for minimum CPU consumption):
* *
* - In device mode, it may be disabled at start-up, enabled on the firing of the \ref EVENT_USB_Connect() event * - In device mode, it may be disabled at start-up, enabled on the firing of the \ref EVENT_USB_Connect() event
* and disabled again on the firing of the \ref EVENT_USB_Disconnect() event. * and disabled again on the firing of the \ref EVENT_USB_Disconnect() event.
* *
* - In host mode, it may be disabled at start-up, enabled on the firing of the \ref EVENT_USB_DeviceAttached() * - In host mode, it may be disabled at start-up, enabled on the firing of the \ref EVENT_USB_DeviceAttached()
* event and disabled again on the firing of the \ref EVENT_USB_DeviceUnattached() event. * event and disabled again on the firing of the \ref EVENT_USB_DeviceEnumerationComplete() or
* \ref EVENT_USB_DeviceEnumerationFailed() events.
* *
* If in device mode (only), the control endpoint can instead be managed via interrupts entirely by the library * If in device mode (only), the control endpoint can instead be managed via interrupts entirely by the library
* by defining the INTERRUPT_CONTROL_ENDPOINT token and passing it to the compiler via the -D switch. * by defining the INTERRUPT_CONTROL_ENDPOINT token and passing it to the compiler via the -D switch.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment