DLPU110B April   2021  – August 2022 DLPC6540

 

  1.   Programmer's Guide
  2.   Trademarks
  3. 1 Scope
  4. 2 References
  5. 3 Acronyms
  6. 4 System Boot
    1. 4.1 Data In flash
    2. 4.2 Bootloader Application
    3. 4.3 Main Application
    4. 4.4 Commands supported by Bootloader and Main Applications
    5. 4.5 Debug Terminal
    6. 4.6 HOST_IRQ/SYSTEM_BUSY
    7. 4.7 Heartbeat
    8. 4.8 Low-level Fault
  7. 5 System Status
  8. 6 Version
  9. 7 Power Modes
  10. 8 Display Modes
  11. 9 Source Detection and Configuration
  12. 10Internal sources
    1. 10.1 Test Patterns (TPG)
    2. 10.2 Solid Field (SFG) Color
    3. 10.3 Curtain
  13. 11Display Formatting
  14. 12Image Processing
  15. 13Illumination Control
  16. 14Peripherals
    1. 14.1 GPIO
  17. 15Interface Protocol
    1. 15.1 Supported Interfaces
    2. 15.2 I2C Target
    3. 15.3 USB
  18. 16Command Protocol
    1. 16.1 Command Packet
    2. 16.2 Response Packet
    3. 16.3 Destination Details
    4. 16.4 Error Handling and Recovery
    5. 16.5 System Busy - I2C scenarios
      1. 16.5.1 GPIO implementation
      2. 16.5.2 Short Status response
    6. 16.6 Support for Variable Data Size
  19. 17Auto-Initilization Batch File
  20. 18Command Descriptions
  21. 19 System Commands
    1. 19.1  3D
    2. 19.2  Administrative
    3. 19.3  Autolock
    4. 19.4  Blending
    5. 19.5  Bootloader
    6. 19.6  Calibration
    7. 19.7  Debug Internal
    8. 19.8  Debug
    9. 19.9  General Operation
    10. 19.10 Illumination
    11. 19.11 Image Processing
    12. 19.12 Peripherals
    13. 19.13 Warping
    14. 19.14 Manual WPC
  22. 20Revision History

15.3 USB

The DLPC6540 controller has USB OTG 2.0 compliant hardware. When connected to a USB host, the controller configures as USB device (target) mode operating at high speed (480 Mbit/s).The controller enumerates one of the interfaces as a generic WinUSB device with two bulk endpoints. A USB bulk transfer sends the command and response packets through these endpoints. The OUT endpoint is used for command packet and the IN endpoint is used for response packet. The USB transfer size can vary from 1 byte to 512 bytes. When the host sends the USB IN request, the controller responds with NAK until there is a response packet ready from the software.

GUID-C3C859AF-9A84-4AC6-A961-C89728C01FFC-low.gifFigure 15-1 USB Core