Presented by: Heath Fortenberry Lee Ooi Khoo Fuh Taur Chin

1
Presented byHeath FortenberryLee Ooi KhooFuh
Taur Chin
2
Background of USB

• Universal Serial Bus (USB) was first introduced
  in 1995 by several leading manufacturers.
• The goal of USB development was to define an
  external expansion bus which makes adding new
  peripherals easy.

3
Objective of X-Teams USB Project

• Providing a cheap and easy upgrade of a low
  speed (1.5Mbps) USB device.
• Providing alternative solutions to USB
  development using standard cell, creating
  behavioral models for future upgrade and
  reusability using VHDL.

4
Overview

• Current USB devices are mostly designed using
  standard cell technology.
• Upgrade of product in a small time frame is not
  possible
• New designs have high overhead

5
More Overview

• Risk on stocking of new chip for new USB device.
• High engineering cost on a new design of USB
  device

6
Solution

• Using VHDL coding provides reusability option
• Using VHDL coding provides easy upgrade
• Using FPGA chip reduces risk on stocking new chip
  for new USB Device

7
Impact of This Megafunction

• The sole purpose of this megafunction project is
  to provide a guideline and serve as a building
  block for USB manufacturers or PC manufacturers
  that are interested in efficient, low cost,
  reusability and alternative to current USB device
  technology.

8
Impact of This Megafunction cont...

• Reduce design time significantly thus reducing
  time for new design to reach the market.
• Reduce engineering cost since this megafunction
  can be upgraded to suite the purpose of a new USB
  design.

9
Impact on User

• From a users perspective, USB devices created
  using the FPGA approach will be the same as any
  other USB device.
• Devices created will work and will do the same
  function as any device in its class.

10
Impact on PC Manufacturer

• The same ability of any USB device on the
  market.
• Upgrading hardware functionality by software
  means would be possible. This will not lead to
  keeping out-dated USB devices.

11
Impact on USBDevice Manufacturer

• With the use of FPGA technology on USB devices,
  production cost will be reduced since the
  manufacturer can store one type of chip and
  purchase large quantities at a lower price.
• Time to reach the market for a new USB device
  will also be reduce since design time will be
  reduce significantly

12
System requirementto run USB device

• Pentium Processor (or any processor operate
  using Window 98 and Window 2000 operating system)
• 64Mb Memory or higher
• USB interface card (or motherboard with USB
  support/interface)
• USB cable

13
Additional informationon System Requirement

• A user could check if he/she has a compatible
  system by downloading a software program from
  http//www.usb.org/data/usbready.exe This
  software will only work with Window 98 or Window
  98 SE.
• Window 98 or Window 98 SE and Windows 2000
  (formerly known as NT 5.0) does have USB support.

14
Design
15
Low Speed USB Interface
16
Serial Interface Engine
Contains intelligence to manage the bus bit-level
protocol
17
End Points

• Control Endpoint
• Responds to endpoint address 0 and is always
  configured
• Used during the enumeration process to provide
  the host with information about the device
• Complicated and requires a lot of system protocol
• Interrupt Endpoint
• Provides the device function a communication pipe
  to the host
• Root hub polls the device
• Only other type of endpoint a low speed device
  can provide

18
Configuration

• Configuration parameters can be provided to
  megafunction
• Identification data
• Serial Number
• Vendor ID
• etc.
• Max data payload size
• Device Class

19
Protocol - Packets
Data is transferred on the USB in packets
Sync Field
Packet ID
Optional Data
End of Packet
20
Protocol - Packets

• The synch field is used for data synchronization
  between the root hub and the device
• The PID identifies what type of packet is being
  transmitted
• Token
• Data
• Handshake
• Optional data is not required but usually
  contains the data payload
• End of packet signaled when both signals on USB
  are low

21
Protocol - Transactions

• Packets are used to build transactions

Typical Transaction
22
Design Constraints

• Conforms to USB 1.1 specifications
• Supports bandwidth needs of 10 - 100Kbps
• Conserves energy by switching to low power state
• Intellectual Property in the form of an Altera
  Megafunction
• Targeted for Altera Flex10K devices

23
Testing
24
Testing

• Testing on the USB Interface was divided into
  three phases.
• 1) Component Testing
• 2) Integration Testing
• 3) System/Device Testing

25
Test Plan
Unit Testing
Module Testing
Subsystem Testing
System Integration Testing
System Testing
Component Testing
Integration Testing
System/Device Testing
Both teams will take part
Testing done by Design Team
Testing done by Testing Team
26
Test Method

• USB device was broken down into several
  components. Each component was then implemented
  and tested independently.
• Output from each component was checked against
  the correct output of a given input.

27
Test Method cont

• After passing through component testing, the
  components were integrated and further testing
  was carried out.
• Final phase for testing is putting each
  sub-system of the USB device together and test it
  with software to determine the correctness of the
  functionality of the device.

28
Current Testing Progress

• Testing Phase

We are here
Requirements Specification
System Specification
System Design
Detailed Design
Acceptance Test Plan
System Integration Test Plan
Subsystem Integration Test Plan
Module/Unit Code and Test
System Or Device Test
System Integration Test
Subsystem Integration Test
USB Device
Testing Team
Design Team
29
Implementation
30
Implementation

• Implemented as a Megafunction
• Why?
• Economically feasible?
• Manufacturability?

31
Megafunction Benefits

• High Sustainability
• Easy to modify
• Low Maintenance
• Provide Time and Flexibility
• Large Market for Megafunctions
• FPGA designs widely used

32
(No Transcript)
33
Benefits for using our Megafunctions vs Making

• Save on Costs
• Assume
• Engineers pay of 120K a year
• Takes 6 weeks to design a megafunction
• Our Megafunction license cost 10K
• Conclusion
• Saves company 5K by purchasing our
• megafunction license

34
Costs
35
Cont.

• Saves Time
• Saves 6-8 weeks of production time
• Faster Time-to-Market
• - Gets the lion share of the market

36
Time
37
Manufacturability

• Manufacturing cost minimal
• CDROM with the Megafunction
• Megafunction available Online

38
Intellectual Property Concerns

• Piracy
• Use of encryption in the CDROM for
• security
• Use secure online server

39
Conclusions
40
Conclusions

• Design meets and complies with standards
• Provides a low speed interface to the USB
• Provides developers with a cost effective
  alternative

41
Conclusions

• Licensing of intellectual property megafunctions

Reduces cost
Reduces time to market
42
Questions?

• Questions?