Amazon. com Seagate Backup Plus Slim 2. TB Portable External Hard Drive USB 3. Silver STDR2. 00. Computers Accessories. Capacity 2. TB. Style Hard Drive. Are you getting a USB device not recognized error whenever you plug in a USB mouse, keyboard, camera, or other device I cant live without USB ports and. Free Driver Download. Worlds most popular driver download site. If you have replaced your dvddrive with an HDD Caddy, you can still use your dvddrive as an external USB dvddrive. You will need a USB enclosure that. Color Silver. Seagate Backup Plus Slim is an easy way to protect and share your digital life. Ready to go with up to 5. TB of storage space for your most important files, the sleek and protective metal finish is available in classic black, silver, red or blue. Choose your flavor and join the millions of satisfied customers with one of Seagates most popular and trusted portable drive. External Usb Device Driver' title='External Usb Device Driver' />Create an USB Device Application. This chapter describes the software structure of the USB Device Component and its use for creating applications. The USB Device Component simplifies the software development of microcontroller systems that interface to a USB Host. Attributes of the USB Device Component Supports Low Speed, Full Speed and High Speed. Supports standard USB Classes with multiple device class instances. Supports composite devices. Combine USB Device Classes to create a composite device. Supports multiple USB Devices on a single microcontroller with more than one USB Device controller. Provides for implementing the USB Device functionality. Provides an user friendly configuration file for each device class to generate USB Descriptors. Flexibly assigns USB Endpoints to the microcontroller USB Device peripheral. Provides USB Device Examples to show the use of the software stack. For interfacing to an USB Host Computer, additional software may be required. Page Interface to an USB Host Computer shows an example for such a software running on Windows PCs. RTE Components The picture shows the relationship between RTE Components and the microcontrollers USB Device peripheral USB Controller. RTE Components provide configuration files and user code templates. Configuration files configure the RTE Components, hardware interfaces, memory resources and USB Device driver parameters. They can have an impact on multiple RTE Components for example RTEDevice. USB Controller 0 and DriverUSBD0. User code templates provide the skeleton for implementing the USB Device functionality. The grey area around the RTE Components USB Device 1 and DriverUSBD1, as well as USB Controller 1 means that these components are optional and can only be used if a microcontroller device has multiple USB controllers present. If this is the case, an USB Device Class can be connected to any of the USB Device Instances. USB Device Structure USB Device peripherals can have one or more of the following USB Device Classes Audio Device Class ADC is used to exchange streaming audio data between the USB Host and the USB Device. Communication Device Class CDC provides virtual communication port functionality to the USB Host. Human Interface Device HID is typically used to implement a keyboard, joystick, or mouse. The HID Class can be also used for low bandwidth data exchange. Mass Storage Class MSC is used to connect various storage devices to an USB Host. Mass Storage Class media can be an SD card, internal or external Flash memory, or RAM. Custom Class is used to implement either a standard or a vendor specific USB Device Class. Generic information about USB Device Classes can be found on the USB IFs Approved Class Specification Documents page. Multiple RTE Component instances can interface with more than one USB Controller or can implement multiple USB Device Classes. RTE Component instances are numbered. The number is appended to the RTE Component name, related configuration files, and user code templates. Each RTE Component has a separate configuration file. For example, for HID 0 and HID 1 the configuration files have the name USBConfigHID0. USBConfigHID1. Note. The default configuration settings are pre configured for one instance of an USB Device or USB Device Class in a non composite device peripheral. For other combinations the settings need to be edited to ensure proper operation. The USB Composite Device example shows how to implement and configure a composite devices. The steps to create a microcontroller application that uses USB communication with an USB Device controller are Select RTE Components along with the USB Device Classes that are required for your application. Enable and configure the USB Device Driver. Configure the USB Device that connects the USB Middleware to the microcontroller USB peripheral. Configure USB Device Class Configuration and USB Endpoint Settings for each selected USB Device Class and instance. Configure the System Resources according to the USB Device components Resource Requirements. Tennis Elbow 2009 Patch. Implement the Application Code using code templates that are provided for the USB Device Classes. If required by your application, you can change the default USB Device descriptors. For interfacing to an USB Host computer, standard USB Device Classes drivers can be used. This may require additional software development for the USB Host application. An exemplary application for interfacing to an USB HID Device is explained here. RTE Component Selection. Only a few steps are necessary to complete the RTE Component selection From the USB Component Select USB CORE that provides the basic functionality required for USB communication. Set USB Device to 1. This creates one USB Device for communication with the USB Host. Select the desired USB Classes HID, MSC, CDC, ADC, or Custom Class. For example, set USB Device HID to 1 to create a single HID Class Device. If you select more than one class or multiple instances of the same class on the same device, you will create a Composite USB Device. From the Drivers Component Select an appropriate USB Device driver suitable for your application. From the Device Component Additional device specific drivers may be required according to the validation output. From the CMSIS Component Select the CMSIS CORE to provide the core interface to the processor. Select a suitable CMSIS RTOS that is a required for the USB Component. RTE Component Selection. Note. Most microcontrollers have only one USB Controller implemented in hardware and only one driver DriverUSBD0 is available. In this case, only one USB Device can be selected to generate USB Device 0. On a single USB Device 0 an USB Composite Device may be implemented that combines multiple USB Device Classes. When a microcontroller implements multiple USB Controllers an additional USB Device 1 can be generated by setting USB Device to 2. USB Driver and Controller. The USB Device Driver and the USB Controller of the microcontroller need to be correctly configured. In particular this means The USB Device Driver selected under the Drivers Component is typically configured with the RTEDevice. While this file provides multiple options, it is typically sufficient to enable the USB Device peripheral related to this driver. Some microcontrollers may require settings that are related to a physical layer interface PHY. The picture below shows two possible variants. Either, the USB PHY is integrated into the controller, or an external chip is used for providing the USB signal lines. USB Controller and PHY Setups. The USB Controller of the microcontroller typically needs specific clock settings. Consult the users guide of the microcontroller to understand the requirements. Alternatively, you may copy the setup of an USB Device example in case your hardware setup is similar to that of the chosen evaluation boards. USB Device Configuration. The configuration file USBDConfign. Project Windows under the Component USB and contains a number of important settings for the specific USB Device. The DriverUSBD number is set according to the selected USB Controller. This specifies which driver will be used for the USB Device determining the pin out as well. For single USB Device Controllers it will be 0. High Speed may be selected if supported by the USB Controller. The Vendor. ID VID needs to be set to a private VID. The default Vendor ID is owned by Keil and must not be used for actual products.