zudo-led-lamp
GitHub repository

Type to search...

to open search from anywhere

STUSB4500QTR

USB-PD sink controller — STMicroelectronics — C2678061 — board-p U1 — rec-stusb4500qtr

Everything below is projected from this project's stored component evidence. Values keep the exact wording, conditions, units and verdicts they were recorded with — nothing here is re-typed, corrected, or combined into an overall judgement about the part.

This record in the catalog: STUSB4500QTR

Identity

  • Record ID: rec-stusb4500qtr

  • Record kind: standalone

  • Manufacturer part number: STUSB4500QTR

  • Manufacturer: STMicroelectronics

  • Function: USB-PD sink controller

  • LCSC ID: C2678061

  • Package: QFN-24_L4.0-W4.0-P0.50-BL-EP2.8

  • Inventory line: line-c2678061

  • Also known as: USB PD sink controller, NVM controller

  • Owner skill: component-stusb4500qtr

  • Fit: Fitted

  • Identity state: UNRESOLVED

  • Source state: SOURCE UNAVAILABLE

  • Coverage: 6 open of 6 published

Component references

Footprint preview

Footprint preview for QFN-24_L4.0-W4.0-P0.50-BL-EP2.8
Shared footprint package: QFN-24_L4.0-W4.0-P0.50-BL-EP2.8. Open SVG

Footprint preview for QFN-24_L4.0-W4.0-P0.50-BL-EP2.8

Package model

Shared footprint package: QFN-24_L4.0-W4.0-P0.50-BL-EP2.8

Interactive inspection requires JavaScript and WebGL. The package identity remains available in this page.

This geometry represents a shared footprint package and may not exactly match the manufacturer part.

Interactive 3D view of shared footprint package QFN-24_L4.0-W4.0-P0.50-BL-EP2.8

Placements

Every position this exact line occupies in the as-built design. One line may be placed many times and across more than one board.

BoardReference designator
board-pU1

Coverage

Coverage is stated one domain at a time and is never rolled up. A domain marked open is a question that has not been answered; it is not a finding that the part is unsuitable. A record with no open domains has not thereby been declared safe.

identity/package/pinout

  • Coverage ID: cov-stusb-identity

  • Status: OPEN

Reason: Exact DS12499 Rev 8 bytes are reproducibly retained from a manufacturer-document mirror, but primary-only trust and project symbol/footprint/as-built evidence remain open for fact-stusb-manufacturer, fact-stusb-order-code, and fact-stusb-pin-states; dated 2026-08-02 and 2026-08-14 direct st.com retrievals (fact-stusb-ds12499-primary-attempt) found the primary source unavailable, so all remain UNSOURCED

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

unpowered/reset/startup/normal/fault/disconnect behavior

  • Coverage ID: cov-stusb-states

  • Status: OPEN

Reason: Exact DS12499 Rev 8 and UM2650 Rev 3 bytes are reproducibly retained from mirrors; primary-only trust in these mirror bytes has not been established, and state behavior still requires programmed/as-built bench confirmation for fact-stusb-ccdb, fact-stusb-disch, fact-stusb-vbus-vs-disch, fact-stusb-vben, fact-stusb-load-time, fact-stusb-state-sequence, fact-stusb-nvm-load, fact-stusb-volatile-pdo, fact-stusb-discharge-registers, and fact-stusb-fault-status; dated 2026-08-02 and 2026-08-14 direct st.com retrievals (fact-stusb-ds12499-primary-attempt, fact-stusb-um2650-primary-attempt) found both primary sources unavailable, so all remain UNSOURCED

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

project NVM image and factory-state capture

  • Coverage ID: cov-stusb-nvm

  • Status: OPEN

Reason: No as-built 40-byte dump or project-normalized image has been supplied for fact-stusb-artifact

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

NVM write endurance and production write budget

  • Coverage ID: cov-stusb-endurance

  • Status: OPEN

Reason: No manufacturer-primary endurance row is present in the retained reviewed extracts for fact-stusb-endurance

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

safe power/provisioning/bench discriminators

  • Coverage ID: cov-stusb-bringup

  • Status: OPEN

Reason: Operating/state mirror bytes are available, but primary-only trust for fact-stusb-supplies, fact-stusb-vdd-absolute-max, fact-stusb-cc-absolute-max, and fact-stusb-vbus-pin-absolute-max, plus project NVM/readback/power-cycle evidence and bench waveforms, remain open; dated 2026-08-02 and 2026-08-14 direct st.com retrievals (fact-stusb-ds12499-primary-attempt, fact-stusb-um2650-primary-attempt) found both primary sources unavailable, so all remain UNSOURCED

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

VREG_2V7 external DC loading and NVM-jig voltage matching

  • Coverage ID: cov-stusb-vreg2v7-load

  • Status: OPEN

Reason: Pin 23 (VREG_2V7) is documented decoupling-only in DS12499, yet Board P loads it with R15/R16 4.7k I2C pull-ups and exposes it on debug pogo pad J3.3 (net U1.23 C30.2 R15.2 R16.2 J3.3); closure requires a manufacturer-primary locator authorizing this external DC load (or a re-route decision, out of this plan's scope) plus confirmation that the NVM-programming jig's logic levels match 2.7 V before issue #34's programming artifact executes

Facts in this domain:

Blocked by: these facts must be resolved before the domain can close. Each is listed in full under Facts.

Facts

Each fact keeps its value, its unit, the conditions it holds under, where it came from and how far it has been confirmed as separate fields, because they are separate claims. A value without its conditions is not the same fact, and a verdict is about the evidence for the value, not about the part.

ABSOLUTE_MAXIMUM

A never-exceed limit. Reaching it may damage the part; it is not an operating target and there is no margin implied by it.

FactValueUnitConditionsVerdictProvenanceEvidence
fact-stusb-vdd-absolute-max28VVDD pin absolute maximum; not an operating target; manufacturer-authored Rev 8 bytes are retained only through a mirrorUNSOURCEDUNVERIFIEDsrc-stusb-ds12499-ratings — src-stusb-ds12499: Section 7.1, Table 20, row VDD Supply voltage on VDD pin
fact-stusb-cc-absolute-max22VCC1, CC2, CC1DB and CC2DB high-voltage absolute maximum; not an operating target; mirror evidenceUNSOURCEDUNVERIFIEDsrc-stusb-ds12499-ratings — src-stusb-ds12499: Section 7.1, Table 20, grouped rows VCC1/VCC2/VCC1DB/VCC2DB
fact-stusb-vbus-pin-absolute-max28VVBUS_EN_SNK, VBUS_VS_DISCH, DISCH and POWER_OK2 high-voltage absolute maximum; not an operating target; mirror evidenceUNSOURCEDUNVERIFIEDsrc-stusb-ds12499-ratings — src-stusb-ds12499: Section 7.1, Table 20, grouped high-voltage VBUS-pin rows
fact-stusb-endurancenot established by retained extractNONENVM write-cycle budget; do not authorize production cyclingUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 5 start-up configuration; no retained endurance row

The range the manufacturer intends the part to be used in. Always narrower than the absolute maximum.

FactValueUnitConditionsVerdictProvenanceEvidence
fact-stusb-suppliesVDD 4.1..22; VSYS 3.0..5.5VTable 21 operating range; never infer absolute-max as operating permissionUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 7.2, Table 21 rows VDD and VSYS

GUARANTEED_ELECTRICAL

A parameter the manufacturer guarantees over the stated conditions, usually with minimum, typical and maximum values.

FactValueUnitConditionsVerdictProvenanceEvidence
fact-stusb-load-time30msI2C registers loading at power-up or after resetUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 7.3, Table 22 row TLOAD

TRANSIENT

Behaviour during a short event — startup, a switching edge, a fault or a surge.

FactValueUnitConditionsVerdictProvenanceEvidence
fact-stusb-disch500mAmaximum current when DISCH pin is used as internal discharge input through series resistor; alternatively active-low open-drain external switch controlUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 2.2.5 DISCH, maximum discharge-current sentence
fact-stusb-vbus-vs-disch50mAmaximum VBUS_VS_DISCH discharge current through mandatory series resistor; pin also senses and monitors receptacle-side VBUSUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 2.2.12 VBUS_VS_DISCH, current-limit row

PROJECT_STATE

A value this project recorded about how the part is used here — a chosen operating point, a net assignment, or a derived figure. Not a manufacturer specification.

FactValueUnitConditionsVerdictProvenanceEvidence
fact-stusb-manufacturerSTMicroelectronicsNONEexact order code STUSB4500QTRUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: title block and device summary row STUSB4500QTR
fact-stusb-order-codeQFN-24 EP 4x4, marking 4500NONESTUSB4500QTR order codeUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: title block, Device summary row STUSB4500QTR
fact-stusb-pin-statesCC1/CC2 Hi-Z during reset; SCL/SDA pulled down with neither VDD nor VSYS; open-drain status outputs require pull-upsNONEreset or unpowered state as statedUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Sections 2.2.1 and 2.2.4, Table 1 pin rows
fact-stusb-ccdbConnect CC1DB to CC1 and CC2DB to CC2 for passive dead-battery Rd; ground CCDB pins when mode is unusedNONEdevice unpowered/dead-battery support selectionUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 2.2.2, CC1DB/CC2DB warning; Section 3.5
fact-stusb-vbenHi-Z detached; 0 asserted attached by default; configurable to assert only for PDO2/PDO3NONEVBUS_EN_SNK active-low high-voltage open-drain outputUNSOURCEDUNVERIFIEDsrc-stusb-ds12499: Section 2.2.10, Table 6 VBUS_EN_SNK configuration rows
fact-stusb-state-sequencePE_INIT -> SNK_STARTUP/DISCOVERY/WAIT/EVALUATE/SELECT/TRANSITION -> SNK_READY; hard-reset shutdown/recovery and error-recovery are distinct statesNONEpolicy-engine state register 0x29 during attach/negotiation/faultUNSOURCEDUNVERIFIEDsrc-stusb-um2650: Section 3.25, Table PE_FSM register values
fact-stusb-nvm-loadstartup register reset values marked initialized by NVMNONEafter power-up or reset load completesUNSOURCEDUNVERIFIEDsrc-stusb-um2650: Sections 3.22 and 3.60-3.72, register reset rows
fact-stusb-volatile-pdoPDO registers 0x85..0x90 are R/W volatile views initialized from NVMNONEruntime register writes do not by themselves prove persistent NVM programmingUNSOURCEDUNVERIFIEDsrc-stusb-um2650: Sections 3.61 through 3.72, PDO register Type/Reset rows
fact-stusb-discharge-registers0x25 defaults 800 ms to 0 V and 270 ms transition; 0x26 bit7 can force dischargeNONEstandard NVM defaults; project image may differUNSOURCEDUNVERIFIEDsrc-stusb-um2650: Sections 3.22-3.23, register tables 0x25 and 0x26
fact-stusb-fault-status0x13 reports CC pull-up OVP/validity and VBUS discharge faultNONEfault and recovery diagnosisUNSOURCEDUNVERIFIEDsrc-stusb-um2650: Section 3.14, CC_HW_FAULT_STATUS_1 register bit rows
fact-stusb-reference-designSTEVAL-ISC005V1 demonstrates autonomous dead-battery negotiation, switched paths, discharge, and programming/debug interfaceNONEreference topology only; not proof of Board P behaviorNEEDS BENCHREFERENCE-DESIGNsrc-stusb-um2398: Section 1.1 board overview and schematic figures
fact-stusb-artifactnormalized 40-byte NVM image, SHA-256, decoded fields, tool/library version, pre-write dump, post-write readback, reset readback, power-cycle readbackNONEproject acceptance artifact; no image currently retained in this skillNEEDS BENCHPROJECT-CHOICEsrc-stusb-stsw004: Product overview, STUSB-NVM.h export/load workflow section
fact-stusb-ds12499-primary-attemptdirect manufacturer-primary retrieval of DS12499 from st.com is not established; retained bytes remain a reproducible mirror onlyNONEattempted 2026-08-02 (every st.com path timed out and a community.st.com mirror redirected to its forum homepage) and 2026-08-14 (HTTP/2 stream error then HTTP/1.1 timeouts on every st.com path while control fetches succeeded)UNSOURCEDUNVERIFIEDsrc-stusb-ds12499-primary-attempt: cover title block, inaccessible retrieval response
fact-stusb-um2650-primary-attemptdirect manufacturer-primary retrieval of UM2650 from st.com is not established; retained bytes remain a reproducible mirror onlyNONEattempted 2026-08-02 (canonical and legacy st.com paths both timed out) and 2026-08-14 (canonical path timed out again while control fetches succeeded)UNSOURCEDUNVERIFIEDsrc-stusb-um2650-primary-attempt: cover title block, inaccessible retrieval response
fact-stusb-vreg2v7-loadVREG_2V7 (pin 23) bridges to C30.2, R15.2, R16.2 and debug pogo pad J3.3; R15/R16 are 4.7k I2C pull-ups fed from this pin rather than VDD/VSYSNONEcurrent Board P generator connectivity; DS12499 documents pin 23 as 2.7 V regulator decoupling only and does not authorize external DC loadingNEEDS BENCHPROJECT-CHOICEsrc-stusb-board-p-generator: NETS table row VREG_2V7 and rows SCL/SDA

Pin maps

The mapping between schematic pins and PCB pads, or physical terminals for an external part, as recorded. A record may carry more than one map when the same part is documented in more than one context.

pinmap-stusb4500qtr

  • Symbol: STUSB4500QTR

  • Footprint: QFN-24_L4.0-W4.0-P0.50-BL-EP2.8

  • Pins: 25

Pin assignments
Symbol pinNameFootprint padFunction
1CC1DB1dead-battery enable CC1
2CC12configuration channel 1
3NC3no connect
4CC24configuration channel 2
5CC2DB5dead-battery enable CC2
6RESET6active-high reset
7SCL7I2C clock
8SDA8I2C data open drain
9DISCH9internal discharge input or external discharge active-low OD
10GND10ground
11ATTACH11active-low open-drain attach
12ADDR012I2C address
13ADDR113I2C address
14POWER_OK314active-low open-drain contract flag
15GPIO15configurable active-low open-drain
16VBUS_EN_SNK16active-low HV open-drain sink-path enable
17A_B_SIDE17active-low open-drain orientation
18VBUS_VS_DISCH18VBUS sense/monitor/internal discharge
19ALERT19I2C interrupt active-low OD
20POWER_OK220HV active-low OD contract flag
21VREG_1V2211.2 V regulator decoupling
22VSYS22system supply or ground if unused
23VREG_2V7232.7 V regulator decoupling
24VDD24VBUS-side supply
25EP25exposed-pad ground

Interactions

Behaviour that is not a property of this part alone. Each interaction names the records it spans, the conditions it holds under, and how far it has been confirmed. An interaction that spans several parts appears on every one of their pages, under the same identifier, because it is equally a fact about each.

int-stusb-netlist

  • Records involved: rec-stusb4500qtr (this record)

  • Conditions: Assert U1.24=VBUS_IN; U1.18 reaches VBUS_IN only through R14; U1.9 reaches VBUS_OUT only through R13; U1.16=VBEN drives the PMOS gate network; U1.1/5 bridge through R19/R20 to CC1/CC2; U1.22 and EP are GND; NC pins remain NC; U1.23=VREG_2V7 also bridges to R15.2/R16.2 (I2C pull-ups) and pogo pad J3.3, an external DC load beyond decoupling that DS12499 does not yet authorize

  • Verdict: UNSOURCED

Facts this rests on:

int-stusb-safe-power

  • Records involved: rec-stusb4500qtr (this record)

  • Conditions: First power with load disconnected and current limit; use VDD 4.1..22 V or VSYS 3.0..5.5 V, common-ground I2C, wait beyond TLOAD, confirm gate remains deasserted detached before attaching a compliant source

  • Verdict: NEEDS BENCH

Facts this rests on:

int-stusb-nvm-verification

  • Records involved: rec-stusb4500qtr (this record)

  • Conditions: Capture factory 40 bytes; diff intended normalized 40-byte image; write once within verified endurance; read all 40 bytes; reset and read; remove all power long enough for rails to collapse and read again; decode PDO/polarity/discharge fields and negotiate each intended profile

  • Verdict: NEEDS BENCH

Facts this rests on:

int-stusb-state-bench

  • Records involved: rec-stusb4500qtr (this record)

  • Conditions: Observe unpowered Rd, reset Hi-Z, startup load, attach/negotiation, SNK_READY, detach, hard reset, lower-PDO transition, forced fault, VBUS discharge, VBUS_EN_SNK and POWER_OK/ATTACH polarity with scope and register snapshots

  • Verdict: NEEDS BENCH

Facts this rests on:

int-stusb-cc-protection

  • Records involved: rec-stusb4500qtr (this record), rec-pesd24vs1ub

  • Conditions: D6/D7 are DNP from CC1/CC2 to GND; if fitted, pin 1 must face CC and pin 2 GND; confirm capacitance and clamp behavior do not invalidate PD signaling or ST CC protection limits

  • Verdict: NEEDS BENCH

Facts this rests on:

int-stusb-external-rd

  • Records involved: rec-stusb4500qtr (this record), rec-rd-0603waf5101t5e

  • Conditions: R17/R18 are DNP CC-to-GND external Rd options while R19/R20 fit CCDB bridges; fitting both may parallel Rd and is prohibited until the exact intended topology and resistance tolerance are re-audited

  • Verdict: NEEDS BENCH

Facts this rests on:

Cross-component rules

Rules that span several parts at once and are published in full on the integration page. Each rule's verdict below is that rule's own — it is a statement about the cross-component question, not about this part — and the exact wording of what the rule refuses to conclude is published with the rule itself.

  • rule-rail-envelope — rail-envelope — rule verdict: UNSOURCED — Whether every part on the input rail stays inside its own recorded limits across a legal power contract, a mis-contract, and a transient clamp event.

  • rule-usb-pd-nvm-load-switch — usb-pd-nvm-load-switch — rule verdict: UNSOURCED — How the power-delivery controller's stored configuration and its enable output drive the load switch, through every state from detached to fault.

  • rule-evidence-chain — source-to-bench-chain — rule verdict: NEEDS BENCH — How far each claim has travelled from a manufacturer document towards a measurement on real hardware, stage by stage.

All cross-component rules

Sources

Every document cited above, with its identification, when it was retrieved, and what kind of authority it carries. Sources that could not be retrieved are listed too, with their unavailability stated, so a gap in the evidence is visible rather than absent.

STUSB4500 standalone USB PD sink controller with short-to-VBUS protections

STUSB4500 standalone USB PD sink controller with short-to-VBUS protections

The STUSB4500 software programming guide

Getting started with the STEVAL-ISC005V1 evaluation board for STUSB4500

STSW-STUSB004 NVM customization tool

  • Source ID: src-stusb-stsw004

  • Document number: DB3902

  • Revision: Rev 2

  • Document date: 2020-12

  • Retrieved: 2026-08-02

  • Authority: MANUFACTURER_PRIMARY

  • Locator: Cover Description section, lines describing STUSB-NVM.h export and automatic NVM load

  • Printed page: 1

  • Availability: SOURCE UNAVAILABLE

  • Document URL: https://www.st.com/resource/en/data\_brief/stsw-stusb004.pdf

STUSB4500 standalone USB PD sink controller with short-to-VBUS protections

  • Source ID: src-stusb-ds12499-primary-attempt

  • Document number: DS12499

  • Revision: Rev 8

  • Document date: 2022-11

  • Retrieved: 2026-08-14

  • Authority: MANUFACTURER_PRIMARY

  • Locator: Cover title block and Section 7.1 Table 20 rows; direct st.com retrieval attempted for primary-only trust recovery per issue #43

  • Printed page: 1

  • Availability: SOURCE UNAVAILABLE

  • Document URL: https://www.st.com/resource/en/datasheet/stusb4500.pdf

The STUSB4500 software programming guide

Board P generated schematic specification

Legend

What the recorded terms on this page mean, in ordinary words. The exact terms above are the ones that count; these descriptions explain them and never replace them.

Verdict

Recorded termWhat it means
NEEDS BENCHCannot be settled from documents. It needs measurement on real hardware before it can be relied on.
UNSOURCEDNo accepted source backs this value yet. Treat it as a claim, not a fact.

Provenance

Recorded termWhat it means
PROJECT-CHOICEA decision made by this project. No vendor asserts it.
REFERENCE-DESIGNTaken from a vendor reference design or application note rather than the device specification.
UNVERIFIEDRecorded, but not yet backed by an accepted source.

Fact class

Recorded termWhat it means
ABSOLUTE_MAXIMUMA never-exceed limit. Reaching it may damage the part; it is not an operating target and there is no margin implied by it.
GUARANTEED_ELECTRICALA parameter the manufacturer guarantees over the stated conditions, usually with minimum, typical and maximum values.
PROJECT_STATEA value this project recorded about how the part is used here — a chosen operating point, a net assignment, or a derived figure. Not a manufacturer specification.
RECOMMENDED_OPERATIONThe range the manufacturer intends the part to be used in. Always narrower than the absolute maximum.
TRANSIENTBehaviour during a short event — startup, a switching edge, a fault or a surge.

Coverage status

Recorded termWhat it means
OPENUnresolved. Open means the question has not been answered, not that the part is unsafe — the reason states what is missing.

Source availability

Recorded termWhat it means
AVAILABLEThe document was retrieved and is on record.
SOURCE UNAVAILABLEThe document could not be retrieved. It stays listed so the gap is visible; anything resting on it remains unsourced.

Source authority

Recorded termWhat it means
MANUFACTURER_MIRRORA copy of a manufacturer document hosted elsewhere. Usable, but weaker than the manufacturer's own copy.
MANUFACTURER_PRIMARYThe manufacturer's own document for this exact part.
PROJECT_GENERATORA document this project generated, such as a schematic or netlist export.
REFERENCE_DESIGNA reference design or application note rather than a device specification.

Identity state

Recorded termWhat it means
UNRESOLVEDThe exact orderable part is not yet confirmed. Substituting a same-name part from another vendor is not permitted on that basis.

Source state

Recorded termWhat it means
SOURCE UNAVAILABLENo document backing this line could be retrieved.

Unit

Recorded termWhat it means
NONEThe value is not a physical quantity, so it carries no unit. Recorded as `NONE`.

Raw agent resource

This page is generated from a stored evidence bundle and does not restate it. The bundle is the source of truth: where the two ever disagree, the bundle is right and this page is stale.

Open the owning bundle component-stusb4500qtr