Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Paths
  • Concept Map
  • How to Read the Diagrams
  • Part 0: What Is a Protocol?10
  • Part 1: Timing and Clocking11
  • Part 2: Encoding and Framing12
  • Part 3: Handshakes13
  • Part 4: Flow Control17
  • Part 5: Transactions19
  • Part 6: Concurrency and Performance17
  • Part 7: Ordering13
  • Part 8: Sharing and Arbitration12
  • Part 9: Deadlock and Liveness13
  • Part 10: Reliability and Recovery20
  • Part 11: Bring-Up and Link Management10
    • Reset Semantics
    • Reset Sequencing Across Interfaces
    • Presence and Hot-Plug
    • Link Training
    • Capability Negotiation
    • Enumeration and Discovery
    • Link State Machines
    • Versioning and Compatibility
    • Protocols Compared: Bring-Up and Link Management
    • Drills: Bring-Up and Link Management
  • Part 12: Power8
  • Part 13: Shared State and Coherence9
  • Part 14: Security and Isolation7
  • Part 15: Specifying and Verifying11
  • Part 16: Protocols Dissected17
  • Part 17: Capstones5
  • Part 18: Interview Preparation6
Loading lesson

‹Part 11: Bring-Up and Link Management
  1. Topics
  2. First Principles of Hardware Protocols
  3. Part 11: Bring-Up and Link Management
  4. Protocols Compared: Bring-Up and Link Management

Part 11 · Bring-Up and Link Management · All levels

Protocols Compared: Bring-Up and Link Management

How PCI Express, USB, Ethernet, AXI and DCLink reset, detect partners, train, negotiate, enumerate and evolve.

On this page

    Read across for one protocol; read down to see how differently each one gets from power-up to its first transaction.

    Bring-up, side by side

    PCI Express

    USB

    Ethernet

    AXI

    DCLink

    Reset rule

    Link reset retrains and re-initialises flow control

    Port reset before enumeration

    Link restarts auto-negotiation

    Valids low in reset; start on a clock edge after ARESETn is high

    Training and credits before any packet

    Partner detection

    Receiver detection; slot presence detect

    Attach detected per port

    Link pulses / signal detect

    None (fixed wiring)

    First training word

    Training

    LTSSM: Detect, Polling, Configuration, L0; Recovery with equalisation

    Speed detection and handshake

    Auto-negotiation; link training on backplanes

    None

    Lesson 2.8 lock, then step 10

    Negotiation

    Rates in TS1/TS2; width in Configuration

    Highest common speed and version

    Highest common mode

    Optional signals with defaults

    Minimum speed and lanes, confirmed twice

    Enumeration

    Config space scan, bus numbers, BAR sizing

    Default address 0, descriptors, SET_ADDRESS

    — (addresses at higher layers)

    Fixed address map

    —

    Hot-plug

    Slot hot-plug, optional surprise removal

    Native

    Native (cable)

    Power domains with isolation

    —

    Evolution

    Capability lists, fallback to older rates

    Version in descriptors

    Negotiated modes

    Optional signals, defaults

    Room for version and feature bits

    What the table shows

    • Off-chip links must discover, train and negotiate, because neither side knows what it will meet.

    • On-chip buses mostly skip it: the wiring and address map are fixed at design time, so reset rules carry the burden.

    • Enumeration appears wherever devices can be added, and always needs a default way to reach a new one.

    • Compatibility rules are the oldest part of each protocol, set in its first version.

    Where each idea is explained

    • 11.1 Reset Semantics

    • 11.3 Presence and Hot-Plug

    • 11.4 Link Training

    • 11.5 Capability Negotiation

    • 11.6 Enumeration and Discovery

    • 11.7 Link State Machines

    • 11.8 Versioning and Compatibility

    Tip

    For any interface, trace the path from power-up to the first transaction and name what each side must know, and how it learns it, at every step.

    Keep going

    Next: Drills: Bring-Up and Link Management. Interview questions, a whiteboard exercise and a ten-question checkpoint for Part 11.

    Related topics

    • Part 11 overview: Bring-Up and Link Management

    • Course hub

    Previous

    170 / 234

    Next: Drills: Bring-Up and Link Management

    Up next

    Up nextDrills: Bring-Up and Link Management

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Reset Semantics
    • Reset Sequencing Across Interfaces
    • Presence and Hot-Plug