Access Official Technical PDF

Share Summary:LinkedInEmail

Evaluating USB Type-C behavior involves more than checking whether a connector is attached. Engineers also need to examine cable orientation, source and sink roles, current advertisements, and USB Power Delivery (PD) exchanges. The FUSB302 evaluation board provides a laboratory platform for exploring these functions, with a graphical interface for configuration and monitoring as well as access for external I2C control.

The board is designed to help system developers assess the FUSB302 Type-C interface detection solution. It can operate as a source, sink, or dual-role port, allowing teams to investigate connection behavior and PD interactions before integrating the controller into a larger design.

What the FUSB302 evaluation board is designed to test

The FUSB302 handles key USB Type-C configuration-channel (CC) functions, including attach and detach detection, cable orientation detection, and current capability signaling and detection. It also supports accessory detection, including audio adapter and debug accessory modes, and active cable detection. These functions make the device relevant to designs that need a Type-C receptacle or plug with limited programmability.

The controller also integrates the physical layer for the USB BMC Power Delivery protocol. Its listed PD functions include automatic GoodCRC responses, packet retries, soft and hard reset handling, and support for extended and chunked messages. The device also supports Programmable Power Supply (PPS) and basic source-side collision avoidance. The manual identifies support for USB Type-C 1.3 and USB PD 3.0.

For system designers, these capabilities provide a way to examine the detection and communication layer of a Type-C interface. The evaluation board is not, by itself, a complete application implementation: engineers should assess its configuration and connections against their own system requirements.

Power, I2C, and Type-C connections

The board can receive power through its micro-B USB connector, J2. An onboard regulator generates the 3.3 V supply for the FUSB302, and the corresponding LED indicates when VDD is supplied. When connected to a PC, the board’s PIC32 microcontroller acts as the I2C master used by the GUI. The board also generates a regulated 1.8 V supply for an external I2C translator.

For setups that use a separate controller, engineers can connect an I2C master to the SCL, SDA, and INT_N test points. This provides an alternative to PC-based control for bench testing and integration work.

On the Type-C side, CC1 and CC2 connect directly to the board’s receptacle, with test points available for external access. VBUS behavior depends on the configured port role:

  • As a sink: VBUS connects directly to the Type-C receptacle and its nearby test point.
  • As a source: the GUI can control VBUS supplied from the PC’s micro-B USB connection through an onboard load switch.

VCONN is normally supplied from the PC connection. The manual describes how to supply it externally by removing resistor R6 and applying power at the VCON test point. USB 2.0 and SBU signals are left unconnected on this evaluation board, an important limitation when planning test coverage.

Configuring port roles and Power Delivery

The FUSB302 GUI offers autonomous and manual operating modes. In autonomous operation, the Type-C state machine manages connection behavior. In manual operation, that state machine is disabled and engineers configure the device through the GUI controls. The modes should not be used simultaneously, because manual configuration can interfere with autonomous state-machine operation.

On the General USB tab, users select DRP, sink, or source mode and apply the choice with the Write Config control. When the Type-C state machine is enabled, the PD state machines are enabled by default. They can be controlled separately, and the PD behavior depends on the source and sink capabilities configured in the Capabilities tab. The automatic negotiation process uses those settings after attachment.

The PD Control tab displays message history, state-machine status, and the negotiated contract. When the board operates as a sink, it can show the connected source’s advertised capabilities, from which users can select and request a capability. The interface also supports sending PD messages manually, giving engineers a way to investigate specific exchanges.

Using logs, registers, and scripts for debugging

For troubleshooting, the State Logs tab records events when Auto Poll is enabled in the Preferences menu. Log entries include timestamps with 100-microsecond resolution, which can help teams review the sequence and timing of Type-C and PD activity. The interface also provides controls to clear the state and PD logs, and a Set State function to force a selected state-machine state during debugging.

The Register Map tab allows users to read and write FUSB302 registers over I2C. A write operation is followed by a readback to confirm the register value. Register polling should be used cautiously: the manual warns that frequent polling can disrupt firmware timing, and reading the interrupt registers clears them. This matters when investigating transient events or trying to reproduce a timing-sensitive issue.

For repeatable sequences, the Script tab accepts line-by-line read and write commands, with options to execute a script, step through it, or run it in a loop. Results appear in the GUI and can be copied for later review. The VDM tab provides controls for configuring and requesting Vendor Defined Message information, including identity, SVID, and mode discovery.

Practical implications for engineering teams

The FUSB302 evaluation board brings Type-C detection, role selection, PD monitoring, register access, and scripted operations into one development setup. That combination can help engineers validate configuration choices, inspect message flows, and isolate issues before applying what they learn to a product design.

Use the board as a research and development tool, not as a finished product. Its documentation specifies laboratory and evaluation use by technically trained personnel, and the board may not meet regulatory requirements applicable to finished equipment. Confirm the design’s behavior in the intended application and validate the completed system independently before deployment.

Access Official Technical PDF

About The Author