I can’t apply terminal-level controlled-impedance properties directly with my current edit tools.
This is the most relevant entry I found related to the topic:
Defined at terminal level
Bus Group: this property defines the different differential pairs. Some interfaces might require many different bus groups (like ethernet), while others only require one (like USB2.0). For example, if a microcontroller contains two USB buses, terminals for one bus should contain “Bus Group” = USB_1 and terminals in the second bus should contain “Bus Group” = USB_ 2
Pair Role: defines what type of role the terminal has. For example CLK, D1, D2, D3, D4, TX, TX1, TX2, TX3, RX, RX1, RX2, RX3, etc.
Controlled Impedance Pair: this should be a unique name that identifies the pair. This is particularly important for parts that contain more than one bus. For example in a part with two USB buses, you will have two Data 1 pairs. In that case one pair could be named “Data1_Bus1” and the other pair “Data1_Bus2”. You can follow any naming convention you prefer, the only requirement is that each pair has a unique “Controlled Impedance Pair” string.
This board is a compact USB-C to TC2030 programming and debug adapter for ESP32-S3 targets using native USB-Serial/JTAG. Revision A1 focuses on a simple, non-powered adapter that protects the USB data pair while keeping the target-supplied 3.3 V rail isolated from USB VBUS.
In scope
USB-C receptacle interface with USB2 D+ and D- routing
CC1 and CC2 5.1 kOhm pull-down resistors for USB-C device role
USBLC6-2SC6 ESD protection on USB D+ and D-
VBUS indicator LED and local 100 nF VBUS decoupling
Manual reset button with 10 kOhm pull-up to target 3.3 V and 100 nF capacitor across switch
Target header J2 and debug header J3 pinout implementation
2-layer PCB with JLCPCB-compatible constraints and required silkscreen markings
Out of scope
Onboard 3.3 V regulation from USB VBUS
USB-UART bridge or any active protocol conversion
Automatic boot/reset sequencing circuitry
Enclosure-specific mounting features
System context
This adapter sits between a USB host and an ESP32-S3 target board. The host connects through USB-C. Protected USB D+ and D- and target power reference are delivered to a compact TC2030-compatible target header, while a separate debug header exposes unprotected USB data, VBUS, reset, 3.3 V reference, and ground.
Key interfaces
USB-C host connection through J1
Protected target programming/debug connection through J2
Auxiliary debug breakout through J3
Manual reset through SW1 on the shared RST net
Attach: simple block diagram
Diagram
Requirements
Functional
The board shall provide a USB-C receptacle for connection to a host computer.
The board shall support ESP32-S3 flashing and debugging over native USB-Serial/JTAG.
The board shall route USB D+ and D- through an ESD protection device before reaching target header J2.
The board shall expose unprotected D+ and D- on debug header J3.
The board shall include a manual reset button on the RST net.
The board shall include a visible green LED that indicates presence of VBUS.
Electrical
USB-C CC1 and CC2 shall each use 5.1 kOhm pull-downs to GND.
VBUS shall connect only to the ESD device VBUS pin, the VBUS LED path through 1 kOhm, the 100 nF decoupling capacitor, and J3 pin 1.
+3V3 shall enter only from J2 pin 1 and shall not be tied to VBUS.
Reset network shall use a 10 kOhm pull-up from RST to +3V3.
Reset switch bypass capacitor shall be 100 nF connected across SW1.
Compact 30 mm x 20 mm 2-layer USB-C to TC2030 programming/debug adapter for ESP32-S3 native USB-Serial/JTAG with CC pull-downs, USB ESD protection, VBUS activity LED, manual reset, and JLCPCB-compatible manufacturing constraints.
Properties
Properties describe core aspects of the project.
Pricing & Availability
Distributor
Qty 1
Arrow
$0.26–$0.56
Digi-Key
$0.77–$1.35
LCSC
$0.59–$0.72
Mouser
$1.15
TME
$0.32
Verical
$0.16–$0.65
Controls
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.