Preliminary - Information Subject to Change - 9/24/98
EZ-USB Development Kit Overview
1 - 7
•
Your Loader Driver performs an Anchor download of the
embedded 8051 firmware into the EZ-USB chip.
•
The Loader Driver then releases the Reset of the EZ-USB
8051 processor and your firmware application code starts
running.
•
Your 8051 firmware electrically disconnects the EZ-USB
from the USB bus.
•
The host, seeing the original device disappear, discards the
Loader Driver from host memory.
•
Your 8051 firmware Reconnects the EZ-USB to the USB
bus.
•
The Host detects that your device is plugged in and asks the
device for it’s ID’s.
•
The 8051 firmware responds with ID’s that represent a your
fully downloaded and configured device: (Vendor=XYZ
Corp, Product=GIZMO).
•
The Host PC sees these ID’s and knows to load your
Custom Device Driver (based on the Generic Driver
example).
•
The Host Driver and EZ-USB firmware are now loaded and
running and perform the data transfers and control functions
necessary for your application. You may also have a
Windows application that calls your device driver that sends
and receives data.
EZ-USB
Development
System Block
Diagram
During system development, the EZ-USB system looks slightly
different than your final system. The development environment
provides debugging tools for the system under development. In
order to accomplish this, a monitor program is first downloaded
over a serial port and run in the EZ-USB 8051 processor. Then,
using the Keil Debugger, you can load programs and debug your
firmware application by single stepping and setting breakpoints.
Once your firmware is loaded, the Anchor Control panel (which
uses the Windows USB driver) allows you to generate USB traffic
to test your USB control firmware.
