Texas Instruments CC2511 사용자 설명서
CC2511 Dongle
As shown in Figure 10 the USB library is divided into five modules:
The USB Framework (usbfw) contains all USB status information and functions for
initialization, device reset handling, and transfers on endpoint 0. It also contains basic macros
and functions for endpoint control and FIFO access. Vendor and class requests are passed
up to the application, and standard requests further down for internal processing.
The USB Standard Requests (usbsr) module contains automated processing functions for
almost all standard requests. The automated handling and endpoint configuration relies on
the USB descriptor set and two look-up tables. Requests that are not supported
(SYNCH_FRAME and SET_DESCRIPTOR) or that are class specific, are passed up to the
application. The application is also notified upon important events, such as change in
endpoint status or interface alternate settings.
The USB Descriptor Parser (usbdp) module provides a mechanism for locating standard-
formatted USB descriptors. The user must provide a USB descriptor set, and two simple
lookup tables - one for locating other descriptor formats, and another for setting up endpoint
double-buffering. The necessary constant and structure definitions, and guidelines for writing
compatible descriptor sets, are found in the USB Descriptor module.
The USB Suspend (usbsusp) module provides easy to use, fully automated support for USB
suspend, USB resume and USB remote wakeup functionality.
To implement USB suspend and USB resume the user only need to add a short piece of code
to the main loop.
USB remote wakeup is performed by a single function call.
The complete documentation of the CC2511 USB embedded firmware framework is available
in a compressed HTML file, cc2511_USB_library.chm found in
“CC2511DK\embedded_sw\Library\cc2511\CC2511UsbLibrary\doc”.
The USB Framework (usbfw) contains all USB status information and functions for
initialization, device reset handling, and transfers on endpoint 0. It also contains basic macros
and functions for endpoint control and FIFO access. Vendor and class requests are passed
up to the application, and standard requests further down for internal processing.
The USB Standard Requests (usbsr) module contains automated processing functions for
almost all standard requests. The automated handling and endpoint configuration relies on
the USB descriptor set and two look-up tables. Requests that are not supported
(SYNCH_FRAME and SET_DESCRIPTOR) or that are class specific, are passed up to the
application. The application is also notified upon important events, such as change in
endpoint status or interface alternate settings.
The USB Descriptor Parser (usbdp) module provides a mechanism for locating standard-
formatted USB descriptors. The user must provide a USB descriptor set, and two simple
lookup tables - one for locating other descriptor formats, and another for setting up endpoint
double-buffering. The necessary constant and structure definitions, and guidelines for writing
compatible descriptor sets, are found in the USB Descriptor module.
The USB Suspend (usbsusp) module provides easy to use, fully automated support for USB
suspend, USB resume and USB remote wakeup functionality.
To implement USB suspend and USB resume the user only need to add a short piece of code
to the main loop.
USB remote wakeup is performed by a single function call.
The complete documentation of the CC2511 USB embedded firmware framework is available
in a compressed HTML file, cc2511_USB_library.chm found in
“CC2511DK\embedded_sw\Library\cc2511\CC2511UsbLibrary\doc”.
7.2
Windows USB driver framework
CUDAL (Chipcon USB Dongle Access Library) provides an easy-to-use C++ interface to the
CC2511 USB Dongle, making development of PC software easy. This framework is used to
create the USB driver in the WinAmp remote control application example. (The other
application examples use standard Windows drivers).
The following features are supported in CUDAL:
CC2511 USB Dongle, making development of PC software easy. This framework is used to
create the USB driver in the WinAmp remote control application example. (The other
application examples use standard Windows drivers).
The following features are supported in CUDAL:
• The standard requests:
o
GET_DESCRIPTOR
o
GET_STATUS
o
SET_CONFIGURATION
o
GET_CONFIGURATION
o
SET_INTERFACE
o
GET_INTERFACE
• All vendor requests
• All class requests
• BULK and INTERRUPT transfers, with asynchronous and synchronous read and
write functions
The following features are not supported in CUDAL:
• The following standard requests:
o
SET_DESCRIPTOR
o
SET_FEATURE
o
CLEAR_FEATURE
• Isochronous
transfers
SWRU082 Page 16 of 24