USB EMBEDDED HOST CONTROLLER （3）

Published:2011/8/5 1:21:00 Author:Phyllis From:SeekIC

By Mark Schultz

Framework Flow

The framework code will execute as follows. On power on reset, the EZ-Host microprocessor will initialize all registers and counters as well as all device structures. It will then enter a loop:
-Check the host USB ports for any changes in status (devices inserted or removed).
-Check the TD processor and get status of all TDs running on the two SIEs.
-Go through the list of active device drivers and execute the run function for each.

Checking the host USB port for status changes requires inspection of a change variable. The port change interrupt handler v/ill set this variable if a change occurs. If the port shows a change, enumeration code will be executed to service this change.

If a device is found, frameworks code will attempt to match the device to a registered driver. Driver matching can be accomplished in a number of ways. If there is only one specific device to be supported, the device’s VID and PID can be added to a ’Targeted Peripheral List’. The device’s VID and PID are then checked against this list. A more common method of device/driver matching is via device class and interface class. In the case of mass storage devices, both the device class and interface class have a value of ’8’ and their respective subclasses have a value of ’6.’ So, when the driver is created, these values will be entered into the appropriate fields (see Figure 3).





Building an application

In this section we’ll show how to build a simple embedded USB design that controls a USB Flash drive. First, we will need to create a driver for the mass storage device. We can call the driver the mass_storage_driver or some name indicative of the capabilities of the device. The most important fields in this data structure are the class and subclass fields. The framework will use these values to match this driver up with any Flash device with the same class and subclass values. One other possibility here is to enter a specific Vendor ID and Product ID in the driver template. In this case, only the device containing those Vendor and Product IDs will be started when plugged in.

Once the driver is created, the next steps are to add the start, stop and run functions plus the class codes for the device so the driver can be found. A driver structure is shown in Figure 4.





The name of the driver function has to be added to the file drvrlist.h:
#define FWX_DRIVER_LIST { &mass_storage_driver}

The mass_storage_driver’s ’start’ function will use the CBW/CSW protocol to interrogate the device to determine its characteristics. Code inside of these functions will get the data and pass it on to the application layer of the design. This will enable the higher-level layers of the application to handle the specifics of file management. The stop function will clean up any pending operations or transfers and notify the application layer that a device has been removed. The run function, finally, will be used to check for any incoming commands from the application code.

Reprinted Url Of This Article: http://www.seekic.com/blog/project_solutions/2011/08/05/USB_EMBEDDED_HOST_CONTROLLER__（3）.html

Print this Page | Comments | Reading(340)