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

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
    • USB Link & Packet Model
    • Ethernet MAC / PHY Basics
      • Ethernet MAC / PHY Basics: Concepts
      • Ethernet MAC / PHY Basics: Integration
      • Ethernet MAC / PHY Basics: Debug
      • Ethernet MAC / PHY Basics: Interview
    • MIPI CSI / DSI Overview
    • High-Speed I/O Debug
    • High-Speed I/O (USB / Ethernet / MIPI): Tricky Q&A
  • Protocol Verification & Compliance21
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Ethernet MAC / PHY Basics
  1. Topics
  2. Bus Protocols
  3. High-Speed I/O (USB / Ethernet / MIPI)
  4. Ethernet MAC / PHY Basics
  5. Ethernet MAC / PHY Basics: Interview
On this page

    Interface ProtocolsAll levels

    Ethernet MAC / PHY Basics: Interview

    Interview for Ethernet MAC / PHY Basics.

    Interview drills

    Do 980 consumed frames prove that the physical link corrupted 20 of the 1,000 frames?

    Check yourself Do 980 consumed frames prove that the physical link corrupted 20 of the 1,000 frames?

    No. The MAC counted valid arrivals. Reconcile the DMA and software boundaries, including pending buffers and the drain point, before calling any gap loss.

    Common trap: Giving a generic fix without identifying the boundary and unmet obligation in this example.

    Link up but high CRC — where to look?

    Check yourself Link up but high CRC — where to look?

    Correlate the failing receive frames with MAC FCS counts, PCS errors, PHY diagnostics and configuration. A channel fault is one candidate, but CRC alone does not locate the corruption. Compare known-good traffic, interface timing and mode settings, then vary one physical or configuration factor at a time.

    Common trap: Rewriting the driver first.

    Previous

    122 / 158

    Next: MIPI CSI / DSI Overview

    Up next

    Up nextMIPI CSI / DSI Overview

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Ethernet MAC / PHY Basics: Concepts
    • Ethernet MAC / PHY Basics: Integration