Introduction to PCI Express M.2 Specification

The PCI Express (PCIe) M.2 specification defines a compact, modular form factor for add-in cards, primarily intended for mobile and embedded applications such as laptops, tablets, and small-form-factor desktops. It serves as a successor to earlier standards like the Mini Card and Half-Mini Card, offering reduced size, lower volume, and greater flexibility for integrating multiple functions (e.g., storage, wireless connectivity) into a single module. The M.2 form factor supports a variety of interfaces, including PCI Express, Serial ATA (SATA), USB, and others, allowing for high-speed data transfer and expandability. The specification is developed and maintained by the PCI Special Interest Group (PCI-SIG), ensuring interoperability across devices.

The M.2 connector uses a 75-position edge card design (with up to 67 active pins depending on keying), featuring a 0.5 mm pitch for compact integration. Modules can be connectorized (pluggable) or soldered-down, with mechanical keying to prevent incompatible insertions. This design enables backward compatibility with various PCIe revisions while supporting evolving performance needs, such as higher data rates and power efficiency.

History and Versions

The PCI Express M.2 specification has evolved through several revisions to accommodate advancements in PCIe technology, power management, and form factor requirements:

• Revision 1.0 (November 1, 2013): Initial release, focusing on basic electro-mechanical definitions, support for PCIe 3.0 (up to four lanes), SATA 3.0, USB 3.0, and other interfaces like SDIO, UART, and PCM/I2S. It introduced socket types, keying systems, and thermal guidelines for mobile platforms.
• Revision 1.1 (December 15, 2016): Minor updates for improved compatibility and integration.
• Revision 3.0, Version 1.0 (initial release in 2019): Aligned with PCIe 3.0 enhancements, emphasizing mobile adapters with better power and thermal handling.
• Revision 3.0, Version 1.2 (June 26, 2019): Incorporates Engineering Change Notices (ECNs) for refined features, available with change bars to highlight modifications from prior versions.
• Later revisions (e.g., Revision 4.0 in 2020, Revision 5.0 in 2023): Extended support for higher PCIe generations (e.g., PCIe 4.0 and 5.0), but Revision 3.0 remains relevant for legacy PCIe 3.0 implementations.

Revision 3.0, Version 1.2 represents a mature iteration tailored for PCIe 3.0, focusing on optimizations for solid-state drives (SSDs), wireless wide area network (WWAN) modules, and other peripherals. It differs from earlier versions (e.g., Revision 1.x) by incorporating targeted ECNs for increased capacitance, additional voltage options, socket enhancements, and thermal management, enabling higher integration and performance in constrained mobile environments.

Key Features and Updates in Revision 3.0, Version 1.2

This version builds on the core M.2 framework by addressing specific needs in mobile computing, particularly for SSDs and high-power applications. Key features include:

• Support for Multiple Interfaces: PCIe (up to x4 lanes at 3.0 speeds, offering up to 4 GB/s aggregate bandwidth), SATA 3.0 (up to 6 Gb/s), USB 3.0/2.0, and sideband signals for control (e.g., clock requests, resets). Manufacturers select supported interfaces based on device type and host capabilities.
• Form Factor Flexibility: Modules can expand or contract functions, supporting higher integration (e.g., combining storage and wireless on one card).
• Power Management: Single 3.3V rail (with optional VBAT for battery-powered devices), current limits per pin (e.g., 500 mA), and features like FULL_CARD_POWER_OFF# for low-power states.
• Thermal Enhancements: Guidelines for dissipation in fanless (e.g., tablets) and fan-based systems (e.g., notebooks), with skin temperature limits (e.g., 37-58°C) to ensure user comfort.
• Signal Integrity: Specifications for differential insertion loss (≤ -0.5 dB up to 2.5 GHz), return loss (≤ -15 dB up to 3 GHz), and crosstalk (≤ -32 dB up to 2.5 GHz) to maintain high-speed performance.

Updates specific to Version 1.2 via ECNs:

• Cin Maximum Increase: Increases maximum input capacitance for better compatibility with PCIe CEM Spec 4.0 and M.2 Spec 3.0 (effective June 18, 2020).
• Add Core Voltage 0.8 V in PWR_3 for BGA SSD: Introduces 0.8V support on the PWR_3 rail for Ball Grid Array (BGA) SSDs, linked to a Voltage ID ECN (July 7, 2020), improving power efficiency for compact storage.
• M.2 Socket-1 Enhancements: Improves functionality for connectivity-focused sockets (July 7, 2020).
• High Power M.2 Heat Spreader: Adds support for heat spreaders to handle higher thermal design power (TDP) in demanding applications (July 7, 2020).

These updates enhance reliability, power optimization, and thermal performance compared to prior revisions, making Version 1.2 suitable for advanced mobile SSDs and WWAN modules.

Form Factors, Sizes, and Keys

M.2 modules come in standardized sizes and keying configurations to ensure compatibility:

• Sizes: Denoted as WWLL (width x length in mm), with fixed widths (12, 16, 22, or 30 mm) and variable lengths (16, 26, 30, 42, 60, 80, or 110 mm). Common examples:
  • 2230 (22×30 mm): Compact for WiFi/Bluetooth.
  • 2242 (22×42 mm): Balanced for SSDs.
  • 2260 (22×60 mm): Mid-size.
  • 2280 (22×80 mm): Standard for high-capacity SSDs.
  • 22110 (22×110 mm): Extended for larger storage.
• Heights: Single-sided (S1-S3: 1.2-1.5 mm component height) or double-sided (D1-D5: varying top/bottom heights). Connector heights range from H2.3 to H4.2 mm (top-side) or M1.8 mm (mid-line).
• Keying System: Notches (keys A-M) define socket compatibility and supported lanes/interfaces:
  • Key A/E: For Socket 1 (PCIe x2 + USB, WiFi/BT/GNSS).
  • Key B: For Socket 2 (PCIe x2 + SATA/USB, WWAN/SSD).
  • Key M: For Socket 3 (PCIe x4 + SATA, high-performance SSDs).
  • Dual keys (e.g., B+M): Allow insertion into multiple socket types (e.g., PCIe x2 in M-key slots).

Keying prevents mismatches, with dual-key modules offering flexibility (e.g., a B+M SSD works in B or M sockets but limits to x2 lanes in M).

Socket Types and Pinouts

The specification defines three primary sockets based on use cases. Pinouts are based on Revision 3.0, Version 1.2, with signals including differential pairs for PCIe/SATA, control lines (e.g., PERST#, CLKREQ#), and vendor-defined pins. Directions: I (input), O (output), I/O (bidirectional); voltages are typical (e.g., 0/1.8V for logic, 0/3.3V for power-related).

Socket 1 – Key E (Connectivity: WiFi, BT, NFC, GNSS)

• Supports PCIe x2, USB 2.0, SDIO, UART, PCM/I2S, I2C. No configuration pins; CLKREQ# requires pull-up on host.
• Reference design: Typically includes pull-ups for open-drain signals like CLKREQ#.

Socket 2 – Key B (WWAN/SSD/Other: PCIe x2, SATA, USB, SSIC)

• Configuration pins (CONFIG_0-3) select interface (e.g., low for SATA, high for PCIe). Pull-ups required on host for unpowered detection.

Socket 3 – Key M (SSD: PCIe x4, SATA)

• Focused on high-performance storage; similar to Socket 2 but with x4 PCIe lanes.
• Reference design: Emphasizes SMBus for management, DEVSLP for SATA power saving.

Electrical Specifications

• Power: 3.3V primary (module derives 1.8V); optional 0.8V for BGA SSDs in Version 1.2. Power sequencing includes handshakes for safe on/off.
• PCIe Signals: Differential pairs (PER/PET for Rx/Tx), REFCLK (100 MHz reference), control (PERST# for reset, CLKREQ# for clock request, PEWAKE# for wake).
• Other Interfaces: USB D+/D-, SATA A+/A-/B+/B-, UIM for SIM, ANTCTL for antenna tuning.
• Contact Resistance: ≤20 mΩ initial, with test methods for reliability.
• Insertion: 20° angle to minimize force; retention via stand-offs/screws (M2/M3).

Thermal and Power Guidelines

• TDP: Varies by use (e.g., WiFi at 0.9-3W, WWAN up to 3.1W); Version 1.2 adds heat spreader support for high-power scenarios.
• Temperature Limits: Ambient 25-35°C; module skin ≤85°C with fans, lower in fanless designs. Placement away from CPU/GPU heat sources.
• Assumptions: For thin platforms; includes dissipation estimates and sensitivity (e.g., 3°C/W increase in fanless systems).

Relation to PCIe Revisions

M.2 Revision 3.0 aligns with PCIe 3.0 (8 GT/s per lane, up to x4 for 4 GB/s), but is backward-compatible with earlier PCIe (e.g., 2.0 at 5 GT/s). Higher M.2 revisions support PCIe 4.0/5.0 for doubled bandwidth (e.g., 8-16 GB/s per lane), but devices negotiate to available speeds. M-key slots maximize lanes; B-key limits to x2.

---

1) PCI Express (PCIe) M.2 Revision 3.0: Support for Multiple Interfaces

The PCI Express M.2 Specification Revision 3.0 defines a highly flexible form factor that supports multiple interfaces over a single compact 75-position edge connector. This multi-protocol capability is one of the key strengths of M.2, allowing the same physical module and socket to serve diverse functions—such as high-speed storage (NVMe SSDs), legacy storage (SATA SSDs), wireless connectivity (Wi-Fi/Bluetooth/GNSS), WWAN (cellular modems), and more—depending on the socket type, keying, and module implementation.

The specification does not mandate that every M.2 implementation support all interfaces simultaneously. Instead, it provides a framework where:

• The host (e.g., motherboard or platform) selects which interfaces to wire and expose.
• The module (e.g., SSD, Wi-Fi card) indicates its supported interfaces via keying, configuration pins (where applicable), and pin usage.
• Shared differential pairs and sideband signals enable multiplexing of protocols, with the active interface determined at enumeration or via static configuration.

This approach ensures backward compatibility, reduces platform complexity, and optimizes for mobile/embedded constraints (power, thermal, space).

Core Supported Interfaces in Revision 3.0

Revision 3.0 aligns with PCIe 3.0 (8 GT/s per lane) and defines support for the following primary high-speed interfaces, plus numerous sideband/control signals:

1. PCI Express (PCIe)
   • Primary high-performance interface for NVMe SSDs, wireless controllers, and other peripherals.
   • Lane counts:
     • Up to x4 lanes in Socket 3 (Key M) — ideal for premium SSDs (theoretical ~4 GB/s aggregate at PCIe 3.0).
     • Up to x2 lanes in Socket 1 (Key E) and Socket 2 (Key B) — common for Wi-Fi/BT combos or entry-level SSDs/WWAN.
   • Backward compatible with earlier PCIe generations (e.g., 2.0 at 5 GT/s, 1.1 at 2.5 GT/s).
   • Uses differential pairs (PETp/n for Tx, PERp/n for Rx) and reference clock (REFCLKp/n at 100 MHz).
   • Power management via CLKREQ#, PEWAKE#, PERST#, and L1/L0s ASPM states.
2. Serial ATA (SATA)
   • SATA 3.0 (6 Gb/s) for legacy SSD/HDD compatibility.
   • Supported primarily in Socket 2 (Key B) and Socket 3 (Key M).
   • Shares differential pairs with PCIe lane 0:
     • PETp0/n0 → SATA-A+/A- (host Tx → device Rx).
     • PERp0/n0 → SATA-B+/B- (host Rx → device Tx).
   • Detection mechanism: In Socket 3, PEDET pin (grounded by module for SATA, open for PCIe).
   • Additional SATA-specific signals: DEVSLP (device sleep for power saving).
   • Fallback mode for hybrid SSDs that support both NVMe (PCIe) and AHCI (SATA).
3. USB
   • USB 2.0 (high-speed 480 Mb/s) — widely supported across all sockets for Bluetooth, debug, or legacy functions.
     • Pins: USB_D+ and USB_D- (shared in Socket 1 and Socket 2).
   • USB 3.0/3.1 Gen1 (5 Gb/s) — optional in some Socket 2 implementations.
     • Uses secondary PCIe lane pairs (e.g., PETp1/n1 and PERp1/n1 repurposed as USB Tx/Rx).
     • Enabled via configuration pins or host wiring (e.g., ECN for USB 3.1 Gen1 on Key B).
   • Sideband support for USB-related wake/resume.
4. Other Interfaces and Sidebands
   • SDIO — For SDIO-based Wi-Fi modules (Socket 1).
   • I2S/PCM — Audio interfaces for Bluetooth (Socket 1).
   • UART — Serial debug/console (Socket 1 and Socket 2).
   • I2C/SMBus — Configuration, management, alerts (e.g., ALERT# pin).
   • UIM/SIM — For WWAN cellular modems (Socket 2).
   • Coexistence (COEX) — Wi-Fi/Bluetooth interference mitigation signals.
   • Antenna Control (ANTCTL) — RF tuning/switching for multi-radio modules.
   • Vendor-Defined Pins — Flexible for proprietary features (e.g., wake handshakes).
   • General-Purpose I/O (GPIO) — Multiple pins for custom control (e.g., W_DISABLE#, LED#, DPR).

How Multiple Interfaces Are Supported per Socket Type

The specification assigns interfaces based on socket type and keying to avoid conflicts:

• Socket 1 – Key E (Connectivity: Wi-Fi/BT/GNSS/NFC)
  • Primary: PCIe x2 + USB 2.0.
  • Additional: SDIO, I2S/PCM, UART, I2C, COEX, vendor pins.
  • No SATA support.
  • Focus: Low-power wireless; no high-bandwidth storage.
• Socket 2 – Key B (WWAN/SSD/Other)
  • Primary: PCIe x2, SATA 3.0, USB 2.0 (optional USB 3.x on lane 1).
  • Additional: UIM/SIM, ANTCTL, COEX, multiple GPIOs, SMBus.
  • Configuration pins (CONFIG_0–3): Module pulls low/high to select PCIe vs. SATA vs. WWAN mode.
  • Versatile: Supports WWAN modems (with SIM and antenna controls) or SATA/PCIe SSDs.
• Socket 3 – Key M (SSD Drive)
  • Primary: PCIe x4 (preferred for NVMe), SATA fallback on lane 0.
  • Additional: SMBus, DEVSLP, ALERT#, PEDET for detection.
  • Focus: Maximum storage performance; minimal sidebands for wireless.

Implementation and Compatibility Details

• Shared Pins and Multiplexing — Differential pairs are protocol-multiplexed (e.g., PCIe lane 0 = SATA in fallback). The host routes signals based on detected module type (via keying, PEDET, CONFIG pins, or enumeration).
• Power Rail — Single 3.3 V primary; optional VBAT (always-on) in Socket 2 for WWAN RTC/SIM.
• Power Management — Unified across interfaces: FULL_CARD_POWER_OFF#, CLKREQ#, PEWAKE#, PERST#, SUSCLK (32 kHz).
• Backward Compatibility — Revision 3.0 modules work in later M.2 revisions (e.g., 4.0/5.0) at reduced speeds/lanes if needed.
• ECNs in Version 1.2 — Minor refinements (e.g., Cin increase for better signal integrity, 0.8 V core voltage option for BGA SSDs) do not alter core multi-interface support.
• Manufacturer Choice — Not all hosts implement every interface (e.g., many consumer laptops wire only PCIe x4 for M-key SSDs, no SATA fallback). Modules declare supported interfaces in datasheets.

This multi-interface design makes M.2 extremely adaptable, replacing older standards like mSATA and Mini PCIe while enabling unified platforms for storage and connectivity in thin devices. For exact pin mappings and configuration tables, refer to the full PCI-SIG M.2 Specification Revision 3.0 document (member access required).

---

2) PCIe M.2 Revision 3.0: Form Factors, Sizes, and Keys

The PCI Express M.2 Specification Revision 3.0 (including Version 1.2 from June 2019) defines the electro-mechanical characteristics of the M.2 form factor, building on earlier revisions to support mobile and embedded platforms. It maintains the core family of module sizes, mechanical keying, socket types, and compatibility rules established in prior versions, while incorporating refinements for power, thermal, and signal integrity suitable for PCIe 3.0 implementations (up to 8 GT/s per lane).

The M.2 form factor is a compact, flat module with a 75-position edge connector (typically 67 active pins), designed for high integration in space-constrained devices like laptops, tablets, ultrabooks, and small desktops. It supports multiple interfaces (PCIe, SATA, USB, and sideband signals) and allows for both pluggable (connectorized) and soldered-down modules.

M.2 Form Factor Naming Convention

M.2 modules follow a standardized naming scheme that encodes width, length, component height (single- or double-sided), and keying. The format is typically:

WWLL – [S/D][number] – [Key1][+Key2]

• WW — Width in mm (most common is 22 mm; others include 12, 16, 30 mm for specific uses).
• LL — Length in mm (e.g., 30, 42, 60, 80, 110).
• S = Single-sided module; D = Double-sided module.
• [number] after S/D indicates maximum component height limits (top and bottom sides), e.g.:
  • S1/S2/S3: Single-sided with varying top heights (typically 1.2–1.5 mm).
  • D1–D5: Double-sided with combinations (e.g., D2 often 1.35 mm top/bottom).
• Key1/Key2 — Mechanical key(s) (letter A–M), with + for dual-key modules.

Examples:

• 2280-D2-M: 22 mm wide × 80 mm long, double-sided (D2 height), M-keyed.
• 2230-S1-E: 22 mm × 30 mm, single-sided, E-keyed (common for Wi-Fi/Bluetooth).
• 2242-B+M: 22 mm × 42 mm, B+M dual-keyed (versatile for SATA or PCIe x2).

All consumer and most enterprise SSDs use 22 mm width, as it balances size, capacity, and compatibility. Narrower widths (e.g., 16 mm or 12 mm) appear in soldered-down or specialized connectivity modules.

Supported Sizes in Revision 3.0

Revision 3.0 defines a range of connectorized sizes, with preferred and optional configurations tied to socket types. The most common commercially available sizes remain consistent across revisions:

• 2230 (22 × 30 mm) — Compact; ideal for Wi-Fi, Bluetooth, or small SSDs/WWAN.
• 2242 (22 × 42 mm) — Balanced; used for entry-level SSDs or storage in thin devices.
• 2260 (22 × 60 mm) — Mid-length; common for moderate-capacity SSDs.
• 2280 (22 × 80 mm) — Standard and most prevalent for high-capacity consumer NVMe SSDs (e.g., 1–8 TB drives).
• 22110 (22 × 110 mm) — Extended length; allows maximum NAND flash for highest-capacity SSDs (enterprise or high-end consumer).

Other sizes (e.g., 1630, 3030, 3042) are defined for connectivity (Socket 1) or WWAN (Socket 2), but less common in storage. Soldered-down variants (e.g., 2226, 1216) exist without keys for embedded use.

Motherboard M.2 slots are almost always 22 mm wide, even if they support wider modules in rare cases. Slots include adjustable standoffs/screws to accommodate different lengths (e.g., one slot supporting 2242/2260/2280 via multiple mounting holes).

Component Height (Thickness) Options

Modules can be single-sided (components on one face) or double-sided (both faces), with strict Z-height limits to fit thin chassis:

• Single-sided (S): S1 (top max ~1.5 mm), S2, S3 — Used where space is extremely tight (e.g., ultrabooks).
• Double-sided (D): D1–D5 (e.g., D2: ~1.35 mm top + bottom) — Common for higher-capacity SSDs needing more NAND chips.

The specification ensures modules fit within platform thermal and mechanical envelopes, with guidelines for fanless vs. fan-cooled systems.

Keys and Socket Types

Keying uses physical notches on the module edge connector to prevent incompatible insertions. The socket on the host has a corresponding key protrusion. Revision 3.0 defines three primary socket types, each with associated keys and pin assignments:

1. Socket 1 (Connectivity — e.g., Wi-Fi, Bluetooth, GNSS, NFC)
   • Keys: A, E, or A+E (dual).
   • Interfaces: PCIe x2 + USB 2.0, plus sidebands (I2C, SDIO, UART, PCM/I2S).
   • Common sizes: 1630, 2230, 3030.
   • Notch positions: A (pins 8–15), E (pins 24–31).
   • Purpose: Wireless modules; limited to x2 lanes.
2. Socket 2 (WWAN/SSD/Other — versatile)
   • Keys: B, or B+M (dual for compatibility).
   • Interfaces: PCIe x2, SATA 3.0, USB 2.0/3.0, plus UIM (SIM), SSIC, SMBus.
   • Common sizes: 2230–22110 (for SSDs), 3042 (WWAN).
   • Notch position: B (pins 12–19).
   • CONFIG pins select interface (e.g., SATA vs. PCIe).
   • Dual B+M allows insertion into B or M sockets (but limits to x2 lanes in M).
3. Socket 3 (SSD Drive — high-performance storage)
   • Key: M (or B+M for backward compatibility).
   • Interfaces: PCIe x4 (preferred for NVMe), SATA fallback, SMBus.
   • Common sizes: 2242, 2260, 2280, 22110.
   • Notch position: M (pins 59–66).
   • Purpose: Maximum bandwidth SSDs (up to ~4 GB/s theoretical with PCIe 3.0 x4).

Key Comparison Table:

Key Type	Notch Position	Primary Interfaces	Max PCIe Lanes	Common Uses	Compatibility Notes
A	Pins 8–15	PCIe x2 + USB + sidebands	x2	Wi-Fi/BT (Socket 1)	Limited; connectivity only
E	Pins 24–31	PCIe x2 + USB + sidebands	x2	Wi-Fi/BT/GNSS (Socket 1)	Most common wireless key
B	Pins 12–19	PCIe x2, SATA, USB	x2	WWAN, SATA SSDs (Socket 2)	Often dual-keyed as B+M
M	Pins 59–66	PCIe x4, SATA	x4	High-speed NVMe SSDs (Socket 3)	Preferred for performance; single notch right
B+M	Both B & M	PCIe x2 or SATA	x2 (in M slot)	Versatile SSDs (works in B or M)	Most flexible; limits to x2 lanes even in x4 slot

• Single-notch keys (B or M) are offset to one side.
• Dual-notch (B+M) fits both B-key and M-key sockets, maximizing interchangeability but capping at PCIe x2 bandwidth.
• Keys prevent damage: An M-key module cannot physically insert into a B-key socket, and vice versa.

Practical Implications in Revision 3.0

• Storage focus: Most PCIe 3.0 NVMe SSDs use M-key (Socket 3) for full x4 lanes (~3.94 GB/s max practical). B+M-key SSDs work broadly but are slower in M slots.
• Backward compatibility: Revision 3.0 modules work in later revisions (e.g., 4.0/5.0 slots) at reduced speeds if the host limits lanes or generation.
• Motherboard labeling: Slots specify supported sizes (e.g., “M.2 Socket 3, M Key, 2242/2260/2280”) and lanes (x4 for NVMe, x2 for some SATA/legacy).

This structure in Revision 3.0 ensures mechanical safety, electrical compatibility, and flexibility across diverse applications while optimizing for mobile power/thermal constraints.

---

3) PCI Express (PCIe) M.2 Revision 3.0: Form Factor Flexibility

The PCI Express M.2 Specification Revision 3.0 emphasizes form factor flexibility as a core design principle. This flexibility allows the M.2 standard to adapt to a wide range of devices, applications, and integration needs while maintaining a unified 75-position edge connector (with up to 67 active pins) and mechanical/electrical consistency. The specification describes M.2 as “a family of form factors that enables expansion, contraction, and higher integration of functions onto a single form factor module solution,” making it a natural evolution from earlier standards like Mini PCIe and mSATA.

This adaptability stems from several interconnected elements: variable module dimensions (width × length), single- or double-sided component population with defined height limits, mechanical keying for interface compatibility, support for pluggable (connectorized) or soldered-down implementations, and alignment with different socket types (Socket 1, 2, 3). These features allow manufacturers to scale modules for specific use cases—such as compact wireless cards in ultrathin laptops or high-capacity SSDs in desktops—without requiring entirely new connector designs or platform redesigns.

Key Aspects of Form Factor Flexibility in Revision 3.0

1. Variable Module Sizes (Width and Length Combinations) The specification defines a family of module sizes using a WWLL naming convention (width in mm × length in mm). This allows “expansion” (longer modules for more components/capacity) or “contraction” (shorter modules for space-constrained designs).
   • Widths (fixed options): 12 mm, 16 mm, 22 mm (most common for storage and connectivity), 30 mm (for extended WWAN or multi-function modules).
   • Lengths (scalable): 16 mm, 26 mm, 30 mm, 38 mm, 42 mm, 60 mm, 80 mm, 110 mm (and others in early drafts like 1216, 2226 for soldered-down). Common examples in Revision 3.0:
   • 2230 (22 × 30 mm): Compact for Wi-Fi/Bluetooth/GNSS modules (Socket 1, Key E).
   • 2242 (22 × 42 mm): Balanced for entry-level SSDs or WWAN (Socket 2/3).
   • 2260 (22 × 60 mm): Mid-size for moderate-capacity storage.
   • 2280 (22 × 80 mm): Dominant for high-capacity consumer NVMe SSDs (Socket 3, Key M).
   • 22110 (22 × 110 mm): Extended for maximum NAND flash density in enterprise SSDs.
   • Wider variants like 3042 (30 × 42 mm): For WWAN modules needing more RF connectors (Socket 2, Key B).
   Many host platforms (e.g., motherboards) include multiple mounting holes/standoffs in a single M.2 slot, supporting several lengths (e.g., 2242/2260/2280) for user upgrade flexibility.
2. Single-Sided vs. Double-Sided Modules and Component Height Limits Flexibility in component population allows optimization for thin devices or higher capacity:
   • Single-sided (S): Components on one face only (e.g., S1, S2, S3 with top heights ~1.2–1.5 mm). Ideal for ultra-thin platforms where bottom clearance is minimal.
   • Double-sided (D): Components on both faces (e.g., D1–D5 with combinations like 1.35 mm top/bottom). Enables more NAND chips or RF circuitry for higher capacity/functionality. The specification sets strict Z-height limits to fit within mobile thermal/mechanical envelopes (e.g., fanless tablets or thin notebooks), ensuring modules remain compatible across platforms.
3. Mechanical Keying and Socket Compatibility Keying uses physical notches to prevent mismatches while allowing intentional cross-compatibility:
   • Single keys (A, E, B, M) for specific socket types.
   • Dual keys (e.g., B+M) for broad compatibility — a B+M module inserts into either B-key (Socket 2) or M-key (Socket 3) sockets, though limited to x2 PCIe lanes in M sockets. This enables versatile modules (e.g., SATA/PCIe x2 SSDs) that work across different host designs without redesign.
4. Connectorized vs. Soldered-Down Options
   • Connectorized (pluggable): Standard 75-position edge card with keys; user-replaceable in most laptops/desktops.
   • Soldered-down: No keys; direct PCB attachment for embedded/IoT (e.g., types 1216, 2226, 3026). Reduces cost/height but sacrifices upgradability. Revision 3.0 retains both, providing flexibility for OEMs choosing serviceability vs. integration density.
5. Alignment with Socket Types and Use Cases The form factor family ties directly to socket types:
   • Socket 1 (Key E/A): Compact connectivity (2230 common).
   • Socket 2 (Key B): Versatile WWAN/SSD (2242–22110, 3042).
   • Socket 3 (Key M): High-performance storage (2242–22110). This mapping ensures the right size/key combination for the application while allowing host platforms to support multiple functions via different sockets/slots.

Benefits of This Flexibility in Revision 3.0

• Scalability Across Devices: From tiny tablets (short/narrow modules) to high-capacity laptops/desktops (longer modules).
• Higher Integration: Combine functions (e.g., storage + wireless) or add more components (double-sided, longer boards).
• Backward/Forward Compatibility: Same connector family works across revisions; modules fit later specs at reduced performance if needed.
• Platform Design Efficiency: OEMs use one connector type for diverse needs, reducing inventory and qualification effort.
• Thermal/Power Optimization: Height limits and size options suit fanless or high-TDP scenarios (with ECNs in Version 1.2 adding heat spreader support for high-power modules).

In summary, Revision 3.0’s form factor flexibility makes M.2 a highly adaptable standard, supporting everything from low-power wireless to high-bandwidth NVMe storage in constrained mobile environments. This modularity has driven its dominance in modern computing, with the 22 mm width family (especially 2280) becoming the de facto standard for consumer SSDs due to its balance of size, capacity, and compatibility. For precise mechanical drawings and tolerances, refer to the full PCI-SIG M.2 Specification Revision 3.0 document.

---

4) PCI Express (PCIe) M.2 Revision 3.0: Socket Types and Pinouts – Socket 1 – Key E

In the PCI Express M.2 Specification Revision 3.0 (including Version 1.2, dated June 26, 2019), Socket 1 is specifically designed for connectivity applications, most commonly wireless modules such as Wi-Fi, Bluetooth, GNSS (Global Navigation Satellite System), NFC, or combinations thereof. It is the socket type associated with Key E (and sometimes dual A+E for broader compatibility with Key A modules).

Socket 1 – Key E provides a standardized interface for these wireless adapters in mobile and embedded platforms, emphasizing low power, compact size, and support for multiple control and data buses. The keying notch for Key E removes substrate material between pins 24–31 on the module edge connector, ensuring physical incompatibility with other socket types (e.g., B or M keys used for storage).

Purpose and Supported Interfaces

Socket 1 – Key E is optimized for wireless connectivity modules and supports the following primary interfaces:

• PCI Express — Up to x2 lanes (typically x1 or x2 used in practice for Wi-Fi/BT combos), enabling high-speed data transfer at PCIe 3.0 rates (up to 8 GT/s per lane).
• USB — USB 2.0 (high-speed/full-speed/low-speed) for Bluetooth or legacy functions.
• Sideband and Control Signals — Including PERST# (reset), CLKREQ# (clock request for power management), PEWAKE# (wake signaling), SUSCLK (32 kHz suspend clock), and LED indicators.
• Additional Buses (optional or vendor-specific implementations):
  • SDIO (for SDIO-based Wi-Fi modules).
  • I2S/PCM (for audio interfaces, e.g., Bluetooth audio).
  • UART (serial console or debug).
  • I2C (for configuration or sensor control).
  • Coexistence (COEX) signals for Wi-Fi/Bluetooth interference mitigation.
  • Vendor-defined pins (often for RF control, antenna switching, or proprietary features).

No configuration pins (like those in Socket 2) are present — the host assumes connectivity usage. The socket supports PCIe reference clock (REFCLK) output from the host, with CLKREQ# allowing dynamic clock gating for power savings.

Common module sizes for Key E: 1630, 2230, or 3030 mm (compact to fit in thin laptops/tablets). Most modern Wi-Fi 6/6E/7 or Bluetooth 5.x cards use this socket.

Pinout for Socket 1 – Key E (Revision 3.0)

The M.2 connector has 75 positions (pins numbered 1 to 75, odd on one side, even on the other). Pinout is defined from the host (socket) perspective, with directions relative to the host:

• I = Input to host (output from module).
• O = Output from host (input to module).
• I/O = Bidirectional.
• OD = Open-drain (requires pull-up on host).
• Voltages: Logic typically 0/1.8 V or 0/3.3 V; power is 3.3 V.

The table below lists all pins, signals, directions, and typical voltages (based on Revision 3.0 definitions, consistent across implementations like congatec AN43 and PCI-SIG-aligned references):

Pin	Signal Name	Direction	Typical Voltage	Description / Notes
1	GND	–	–	Ground
2	3.3V	–	3.3 V	Power supply
3	USB_D+	I/O	–	USB 2.0 data positive
4	3.3V	–	3.3 V	Power supply
5	USB_D-	I/O	–	USB 2.0 data negative
6	LED_1#	I	OD	Activity LED 1 (open-drain)
7	GND	–	–	Ground
8	PCM_CLK / I2S_SCK	I/O	0/1.8 V	PCM/I2S clock
9	SDIO_CLK / SYSCLK	O	0/1.8 V	SDIO clock or system clock output
10	PCM_SYNC / I2S_WS	I/O	0/1.8 V	PCM/I2S word select/frame sync
11	SDIO_CMD	I/O	0/1.8 V	SDIO command
12	PCM_IN / I2S_SD_IN	I	0/1.8 V	PCM/I2S data input
13	SDIO_DATA0	I/O	0/1.8 V	SDIO data bit 0
14	PCM_OUT / I2S_SD_OUT	O	0/1.8 V	PCM/I2S data output
15	SDIO_DATA1	I/O	0/1.8 V	SDIO data bit 1
16	LED_2#	I	OD	Activity LED 2 (open-drain)
17	SDIO_DATA2	I/O	0/1.8 V	SDIO data bit 2
18	GND	–	–	Ground
19	SDIO_DATA3	I/O	0/1.8 V	SDIO data bit 3
20	UART_WAKE#	I	0/3.3 V	UART wake (often BT_WAKE_OUT)
21	SDIO_WAKE#	I	0/1.8 V	SDIO wake (often WL_WAKE_OUT)
22	UART_RXD	I	0/1.8 V	UART receive data
23	SDIO_RESET# / TX_BLANKING	O	0/1.8 V	SDIO reset or TX blanking
24–31	Key E (notched)	–	–	Physical key notch (no pins)
32	UART_TXD	O	0/1.8 V	UART transmit data
33	GND	–	–	Ground
34	UART_CTS	I	0/1.8 V	UART clear-to-send
35	PETp0	O	–	PCIe Tx positive lane 0
36	UART_RTS	O	0/1.8 V	UART request-to-send
37	PETn0	O	–	PCIe Tx negative lane 0
38	VENDOR DEFINED	I/O	0/1.8 V	Vendor-specific (often wake or SPI)
39	GND	–	–	Ground
40	VENDOR DEFINED	I/O	0/1.8 V	Vendor-specific
41	PERp0	I	–	PCIe Rx positive lane 0
42	VENDOR DEFINED	I/O	0/1.8 V	Vendor-specific
43	PERn0	I	–	PCIe Rx negative lane 0
44	COEX3	I/O	0/1.8 V	Coexistence signal 3
45	GND	–	–	Ground
46	COEX_RXD	I	0/1.8 V	Coexistence UART RX
47	REFCLKp0	O	–	PCIe reference clock positive lane 0
48	COEX_TXD	O	0/1.8 V	Coexistence UART TX
49	REFCLKn0	O	–	PCIe reference clock negative lane 0
50	SUSCLK (32kHz)	O	0/3.3 V	Suspend clock output
51	GND	–	–	Ground
52	PERST0#	O	0/3.3 V	PCIe reset (active low)
53	CLKREQ0#	I/O	0/3.3 V	Clock request (open-drain, pull-up required on host)
54	W_DISABLE2#	O	0/3.3 V	Wireless disable 2 (e.g., BT reset)
55	PEWAKE0#	I/O	0/3.3 V	PCIe wake
56	W_DISABLE1#	O	0/3.3 V	Wireless disable 1 (e.g., main RF kill)
57	GND	–	–	Ground
58	I2C_DATA	I/O	0/1.8 V	I2C data
59	PETp1	O	–	PCIe Tx positive lane 1 (optional)
60	I2C_CLK	O	0/1.8 V	I2C clock
61	PETn1	O	–	PCIe Tx negative lane 1 (optional)
62	ALERT#	I	0/1.8 V	Alert or interrupt
63	GND	–	–	Ground
64	RESERVED	–	–	Reserved
65	PERp1	I	–	PCIe Rx positive lane 1 (optional)
66	UIM_SWP / PERST1#	–	–	UIM SIM swap or secondary reset
67	PERn1	I	–	PCIe Rx negative lane 1 (optional)
68	UIM_POWER_SNK / CLKREQ1#	–	–	UIM power sink or secondary clock request
69	GND	–	–	Ground
70	UIM_POWER_SRC / GPIO_1 / PEWAKE1#	–	–	UIM power source or GPIO or secondary wake
71	REFCLKp1	O	–	Secondary REFCLK positive (optional)
72	RESERVED / REFCLKn1	–	–	Reserved or secondary REFCLK negative
73	3.3V	–	3.3 V	Power supply
74	3.3V	–	3.3 V	Power supply
75	GND	–	–	Ground

Key Design Notes for Revision 3.0

• PCIe Lanes: Lane 0 (pins 35/37 Tx, 41/43 Rx) is primary; Lane 1 (59/61 Tx, 65/67 Rx) is optional and often reserved or not connected.
• Power: Single 3.3 V rail; modules derive lower voltages (e.g., 1.8 V) internally.
• Open-Drain Signals: CLKREQ#, LED#, W_DISABLE# require host pull-ups (typically 10–100 kΩ to 3.3 V).
• Reference Clock: 100 MHz differential REFCLK from host; AC-coupled on some implementations.
• Wake and Reset: PERST# initializes PCIe link; PEWAKE# supports wake-from-sleep events.
• Vendor Pins (38, 40, 42): Frequently repurposed for wake/handshake (e.g., WL_WAKE_IN, BT_WAKE_IN) or coexistence.
• Compatibility: Key E modules fit only Key E (or A+E) sockets; backward-compatible with earlier M.2 revisions for basic connectivity.

This pinout ensures reliable, low-latency wireless performance in constrained mobile environments while allowing flexibility for different radio technologies. For exact implementation in a specific platform or module, always cross-reference the device datasheet, as some pins may be NC (no connect) or reassigned by vendors. The full authoritative details are in the PCI-SIG M.2 Specification Revision 3.0 document.

---

5) PCI Express (PCIe) M.2 Revision 3.0: Socket Types and Pinouts – Socket 2 – Key B

In the PCI Express M.2 Specification Revision 3.0, Socket 2 is a versatile socket type primarily associated with Key B (mechanical key notch located between pins 12–19 on the module edge connector). This socket supports a wide range of applications, including Wireless Wide Area Network (WWAN) modules (e.g., 3G/4G/5G cellular modems with GNSS), SATA-based or PCIe x2 SSDs, SSD caches, and other connectivity or storage peripherals in mobile and embedded platforms.

Socket 2 – Key B is designed for flexibility: it can provide PCIe x2 lanes (for NVMe or other PCIe devices), SATA 3.0 (6 Gb/s), USB 2.0/3.0, and various sideband/control signals (e.g., UIM/SIM for cellular, antenna controls, coexistence signals for multi-radio interference mitigation). The socket uses configuration pins (CONFIG_0 to CONFIG_3) to allow the module to signal its desired interface mode to the host, enabling dynamic selection between SATA, PCIe, or WWAN-specific configurations.

Key B modules are single-notched (left side when viewed with the label facing up), preventing insertion into Key M sockets (unless dual-keyed as B+M). B+M dual-key modules are common for SSDs to maximize compatibility across hosts with either B or M sockets, though they are limited to x2 PCIe lanes even in x4-capable slots.

Common module sizes for Key B: 2230, 2242, 2260, 2280 (for SSDs), and 3042 (extended width for WWAN with more RF connectors). The socket supports both single-sided and double-sided modules with appropriate height limits.

Purpose and Supported Interfaces

Socket 2 – Key B targets WWAN/SSD/Other use cases, with these primary interfaces:

• PCI Express — Up to x2 lanes (PCIe 3.0 at 8 GT/s per lane, ~2 GB/s aggregate theoretical bandwidth).
• SATA — SATA 3.0 (6 Gb/s) for legacy storage compatibility.
• USB — USB 2.0 (high-speed) and optional USB 3.0/3.1 Gen1 signals (via shared differential pairs).
• Sideband and Control Signals — Including PERST# (reset), CLKREQ# (clock request), PEWAKE# (wake), SUSCLK (32 kHz suspend clock), FULL_CARD_POWER_OFF# (power gating), W_DISABLE# (RF disable), DEVSLP (device sleep for SATA), DAS/DSS# (device activity/LED), UIM (SIM card interface for WWAN), antenna control (ANTCTL), coexistence (COEX), I2C/SMBus, GPIO, and vendor-defined pins.

Configuration pins (pulled high/low by the module) determine the active interface:

• CONFIG_1 typically high → PCIe mode.
• CONFIG_1 low → SATA mode.
• Other combinations support WWAN or specialized configs (detailed in the spec’s configuration table).

No fixed lane assignment exists without configuration detection; the host must support the selected mode via pull-ups on CONFIG pins for unpowered detection.

Pinout for Socket 2 – Key B (Revision 3.0)

The 75-position connector uses the standard M.2 numbering (odd pins on one side, even on the other). Directions are from the host perspective:

• I = Input to host.
• O = Output from host.
• I/O = Bidirectional.
• OD = Open-drain (host pull-up required).
• Voltages: Logic typically 0/1.8 V or 0/3.3 V; power is 3.3 V (some pins support VBAT alternative).

The table below provides the complete pinout based on Revision 3.0 definitions (aligned with PCI-SIG and implementations like congatec AN43, which explicitly references this revision):

Pin	Signal Name	Direction	Typical Voltage	Description / Notes
1	CONFIG_3	–	–	Configuration pin (defines module type/interface)
2	3.3V	–	3.3 V	Power supply
3	GND	–	–	Ground
4	3.3V	–	3.3 V	Power supply
5	GND	–	–	Ground
6	FULL_CARD_POWER_OFF#	O	0/1.8 V or 3.3 V	Full card power off control (active low)
7	USB_D+	I/O	–	USB 2.0 data positive
8	W_DISABLE1#	O	0/3.3 V	Wireless disable 1 (RF kill, active low)
9	USB_D-	I/O	–	USB 2.0 data negative
10	GPIO_9 / DAS# / DSS# / LED_1#	I/O	0/3.3 V	Device activity signal, disable staggered spinup, or LED (multi-function)
11	GND	–	–	Ground
12–19	Key B (notched)	–	–	Physical key notch (no pins)
20	GPIO_5	I/O	0/1.8 V	General purpose I/O
21	CONFIG_0	–	–	Configuration pin
22	GPIO_6	I/O	0/1.8 V	General purpose I/O
23	GPIO_11	I/O	0/1.8 V	General purpose I/O
24	GPIO_7	I/O	0/1.8 V	General purpose I/O
25	DPR	O	0/1.8 V	Data plane ready (WWAN-specific)
26	GPIO_10	I/O	0/1.8 V	General purpose I/O
27	GND	–	–	Ground
28	GPIO_8	I/O	0/1.8 V	General purpose I/O
29	PERn1 / USB3.1-Rx- / SSIC-RxN	I	–	PCIe Rx negative lane 1 or USB 3.x Rx- or SSIC
30	UIM_RESET	I	–	SIM reset
31	PERp1 / USB3.1-Rx+ / SSIC-RxP	I	–	PCIe Rx positive lane 1 or USB 3.x Rx+ or SSIC
32	UIM_CLK	I	–	SIM clock
33	GND	–	–	Ground
34	UIM_DATA	I/O	–	SIM data
35	PETn1 / USB3.1-Tx- / SSIC-TxN	O	–	PCIe Tx negative lane 1 or USB 3.x Tx- or SSIC
36	UIM_PWR	I	–	SIM power
37	PETp1 / USB3.1-Tx+ / SSIC-TxP	O	–	PCIe Tx positive lane 1 or USB 3.x Tx+ or SSIC
38	DEVSLP	O	–	Device sleep (SATA power management)
39	GND	–	–	Ground
40	GPIO_0 / SMB_CLK	I/O	0/1.8 V	SMBus clock or GPIO
41	PERn0 / SATA-B+	I	–	PCIe Rx negative lane 0 or SATA B+
42	GPIO_1 / SMB_DATA	I/O	0/1.8 V	SMBus data or GPIO
43	PERp0 / SATA-B-	I	–	PCIe Rx positive lane 0 or SATA B-
44	GPIO_2 / ALERT#	I	0/1.8 V	Alert/interrupt or GPIO
45	GND	–	–	Ground
46	GPIO_3	I/O	0/1.8 V	General purpose I/O
47	PETn0 / SATA-A-	O	–	PCIe Tx negative lane 0 or SATA A-
48	GPIO_4	I/O	0/1.8 V	General purpose I/O
49	PETp0 / SATA-A+	O	–	PCIe Tx positive lane 0 or SATA A+
50	PERST#	O	0/3.3 V	PCIe reset (active low)
51	GND	–	–	Ground
52	CLKREQ#	I/O	0/3.3 V	Clock request (OD, host pull-up)
53	REFCLKn	O	–	PCIe reference clock negative
54	PEWAKE#	I/O	0/3.3 V	PCIe wake (OD)
55	REFCLKp	O	–	PCIe reference clock positive (100 MHz)
56	NC	–	–	No connect
57	GND	–	–	Ground
58	NC	–	–	No connect
59	ANTCTL0	I	0/1.8 V	Antenna control 0
60	COEX3	I/O	0/1.8 V	Coexistence signal 3
61	ANTCTL1	I	0/1.8 V	Antenna control 1
62	COEX_TXD	O	0/1.8 V	Coexistence UART TX
63	ANTCTL2	I	0/1.8 V	Antenna control 2
64	COEX_RXD	I	0/1.8 V	Coexistence UART RX
65	ANTCTL3	I	0/1.8 V	Antenna control 3
66	SIM_DETECT	O	–	SIM card detect
67	RESET#	O	0/1.8 V	General reset
68	SUSCLK (32kHz)	O	0/3.3 V	Suspend clock output
69	CONFIG_1	–	–	Configuration pin (often enables PCIe when high)
70	3.3V / VBAT	–	3.3 V or VBAT	Power (3.3 V or optional battery voltage)
71	GND	–	–	Ground
72	3.3V / VBAT	–	3.3 V or VBAT	Power
73	GND	–	–	Ground
74	3.3V / VBAT	–	3.3 V or VBAT	Power
75	CONFIG_2	–	–	Configuration pin

Key Design Notes for Revision 3.0

• PCIe Lanes — Lane 0 (pins 41/43 Rx, 47/49 Tx) is primary; Lane 1 (29/31 Rx, 35/37 Tx) is secondary/optional (often for USB 3.x fallback or SSIC).
• Power — Primarily 3.3 V rail; optional VBAT on pins 70/72/74 for always-on features (e.g., WWAN RTC).
• Open-Drain Signals — CLKREQ#, PEWAKE#, W_DISABLE#, etc., require host pull-ups (typically 10–100 kΩ to 3.3 V).
• Reference Clock — 100 MHz differential REFCLK from host; AC-coupled in many designs.
• UIM/SIM Interface — Pins 30/32/34/36 for cellular SIM card support in WWAN modules.
• Antenna Controls — Pins 59–65 for RF antenna switching/tuning in multi-radio setups.
• Configuration Detection — Host applies pull-ups to CONFIG pins; module grounds or leaves open to select mode (e.g., SATA vs. PCIe).
• Compatibility — Key B modules fit Key B sockets; B+M modules fit both B and M sockets (but limited to x2 lanes in M). Backward-compatible with earlier M.2 revisions.

This pinout enables robust support for mixed storage and connectivity in power/thermal-constrained mobile platforms. Vendor implementations may leave some pins NC or repurpose them (e.g., additional GPIOs), so always consult the specific module or platform datasheet alongside the PCI-SIG M.2 Specification Revision 3.0 for precise details.

---

6) PCI Express (PCIe) M.2 Revision 3.0: Socket Types and Pinouts – Socket 3 – Key M

In the PCI Express M.2 Specification Revision 3.0 (including Version 1.2 from June 26, 2019), Socket 3 is the dedicated socket type for high-performance storage devices, specifically associated with Key M (mechanical key notch located between pins 59–66 on the module edge connector). This socket is optimized for solid-state drives (SSDs), supporting PCIe x4 lanes (preferred for NVMe protocol) or SATA 3.0 fallback, along with essential sideband signals for power management, reset, clocking, and status indication.

Socket 3 – Key M targets maximum bandwidth applications, such as consumer and enterprise NVMe SSDs, where PCIe 3.0 x4 provides up to ~4 GB/s theoretical aggregate bandwidth (8 GT/s per lane × 4 lanes, minus encoding overhead). The key notch on the right side (when viewing the module label up) prevents insertion into Key B sockets unless the module is dual-keyed (B+M for compatibility, but limited to x2 lanes in such cases).

Common module sizes for Key M: 2242, 2260, 2280 (most prevalent for consumer NVMe drives), and 22110 (extended for highest-capacity enterprise SSDs). The socket supports single-sided and double-sided modules with defined height limits (S2/D2 typical for storage to balance capacity and thermal constraints in laptops/desktops).

Purpose and Supported Interfaces

Socket 3 – Key M focuses exclusively on SSD Drive use cases, with these primary interfaces:

• PCI Express — Up to x4 lanes (PCIe 3.0 at 8 GT/s per lane), enabling full NVMe performance. Lanes are prioritized for maximum throughput.
• SATA — SATA 3.0 (6 Gb/s) as a fallback or for legacy compatibility (shared differential pairs with PCIe lane 0).
• Sideband and Control Signals — Including PERST# (reset), CLKREQ# (clock request for dynamic power/clock gating), PEWAKE# (wake from low-power states), SUSCLK (32 kHz suspend clock input), DEVSLP (device sleep for SATA power saving), DAS/DSS#/LED_1# (device activity/LED indicator), ALERT# (SMBus alert), SMBus (for management and configuration), PEDET (PCIe/SATA detection), and vendor/manufacturing reserved pins.

No configuration pins like those in Socket 2 are used; interface selection relies on PEDET (pulled low by module for SATA, left open/NC for PCIe) and host detection of connected lanes. SMBus provides optional out-of-band management.

Pinout for Socket 3 – Key M (Revision 3.0)

The 75-position connector follows standard M.2 numbering. Directions are from the host (socket) perspective:

• I = Input to host.
• O = Output from host.
• I/O = Bidirectional.
• OD = Open-drain (host pull-up required).
• Voltages: Logic 0/1.8 V or 0/3.3 V; power 3.3 V.

The table below compiles the pinout based on Revision 3.0 definitions (consistent with PCI-SIG, congatec AN43 referencing this revision, and aligned implementations for NVMe SSDs):

Pin	Signal Name	Direction	Typical Voltage	Description / Notes
1	GND	–	–	Ground
2	3.3V	–	3.3 V	Power supply
3	GND	–	–	Ground
4	3.3V	–	3.3 V	Power supply
5	PERn3	I	–	PCIe Rx negative lane 3
6	NC	–	–	No connect
7	PERp3	I	–	PCIe Rx positive lane 3
8	NC	–	–	No connect
9	GND	–	–	Ground
10	DAS#/DSS#/LED_1#	I/O	0/3.3 V	Device activity / disable staggered spin-up / LED (multi-function, OD)
11	PETn3	O	–	PCIe Tx negative lane 3
12	3.3V	–	3.3 V	Power supply
13	PETp3	O	–	PCIe Tx positive lane 3
14	3.3V	–	3.3 V	Power supply
15	GND	–	–	Ground
16	3.3V	–	3.3 V	Power supply
17	PERn2	I	–	PCIe Rx negative lane 2
18	3.3V	–	3.3 V	Power supply
19	PERp2	I	–	PCIe Rx positive lane 2
20	NC	–	–	No connect
21	GND	–	–	Ground
22	NC	–	–	No connect
23	PETn2	O	–	PCIe Tx negative lane 2
24	NC	–	–	No connect
25	PETp2	O	–	PCIe Tx positive lane 2
26	NC	–	–	No connect
27	GND	–	–	Ground
28	NC	–	–	No connect
29	PERn1	I	–	PCIe Rx negative lane 1
30	NC	–	–	No connect
31	PERp1	I	–	PCIe Rx positive lane 1
32	NC	–	–	No connect
33	GND	–	–	Ground
34	NC	–	–	No connect
35	PETn1	O	–	PCIe Tx negative lane 1
36	NC	–	–	No connect
37	PETp1	O	–	PCIe Tx positive lane 1
38	DEVSLP	O	–	Device sleep (SATA low-power mode)
39	GND	–	–	Ground
40	SMB_CLK	I/O	0/1.8 V	SMBus clock (OD, host pull-up)
41	PERn0 / SATA-B+	I	–	PCIe Rx negative lane 0 or SATA B+
42	SMB_DATA	I/O	0/1.8 V	SMBus data (OD, host pull-up)
43	PERp0 / SATA-B-	I	–	PCIe Rx positive lane 0 or SATA B-
44	ALERT#	I	0/1.8 V	SMBus alert (OD)
45	GND	–	–	Ground
46	NC	–	–	No connect
47	PETn0 / SATA-A-	O	–	PCIe Tx negative lane 0 or SATA A-
48	NC	–	–	No connect
49	PETp0 / SATA-A+	O	–	PCIe Tx positive lane 0 or SATA A+
50	PERST#	O	0/3.3 V	PCIe reset (active low)
51	GND	–	–	Ground
52	CLKREQ#	I/O	0/3.3 V	Clock request (OD, host pull-up)
53	REFCLKn	O	–	PCIe reference clock negative (100 MHz)
54	PEWAKE#	I/O	0/3.3 V	PCIe wake (OD, host pull-up)
55	REFCLKp	O	–	PCIe reference clock positive (100 MHz)
56	NC (MFG_DATA)	–	–	Reserved for manufacturing data (leave NC on host)
57	GND	–	–	Ground
58	NC (MFG_CLK)	–	–	Reserved for manufacturing clock (leave NC on host)
59–66	Key M (notched)	–	–	Physical key notch (no pins)
67	NC	–	–	No connect
68	SUSCLK (32kHz)	I	0/3.3 V	Suspend clock input from host
69	PEDET	–	–	PCIe/SATA detect (module grounds for SATA, NC for PCIe)
70	3.3V	–	3.3 V	Power supply
71	GND	–	–	Ground
72	3.3V	–	3.3 V	Power supply
73	GND	–	–	Ground
74	3.3V	–	3.3 V	Power supply
75	GND	–	–	Ground

Key Design Notes for Revision 3.0

• PCIe Lanes — Full x4 support: Lane 0 (pins 41/43 Rx, 47/49 Tx), Lane 1 (29/31 Rx, 35/37 Tx), Lane 2 (17/19 Rx, 23/25 Tx), Lane 3 (5/7 Rx, 11/13 Tx). NVMe SSDs typically use all four for maximum performance.
• SATA Fallback — Shared on lane 0 pairs; host must route appropriately based on PEDET.
• Power — Single 3.3 V rail; high-power SSDs may draw significant current (up to limits defined in spec).
• Open-Drain Signals — CLKREQ#, PEWAKE#, ALERT#, etc., require host pull-ups (typically 10–100 kΩ to 3.3 V).
• Reference Clock — 100 MHz differential REFCLK from host; must be low-jitter for PCIe integrity.
• PEDET Detection — Critical for host to select PCIe or SATA routing (module behavior: grounded = SATA, open = PCIe).
• SMBus — Pins 40/42 for optional management (e.g., temperature monitoring, firmware updates).
• Manufacturing Pins — Pins 56/58 reserved; host leaves NC to avoid interference.
• Compatibility — Pure M-key modules fit only M-key sockets; B+M modules fit both B and M but cap at x2 lanes/SATA in M slots. Backward-compatible with earlier revisions for basic storage.

This pinout prioritizes high-speed storage in Revision 3.0, making Socket 3 – Key M the standard for modern NVMe SSDs in desktops, laptops, and servers. For platform-specific wiring (e.g., lane multiplexing or optional SATA support), consult the motherboard datasheet alongside the PCI-SIG M.2 Specification Revision 3.0.

---

7) PCI Express (PCIe) M.2 Revision 3.0: Power Management

The PCI Express M.2 Specification Revision 3.0 incorporates comprehensive power management features tailored for mobile and embedded platforms, where battery life, thermal constraints, and energy efficiency are critical. Power management in M.2 is multi-layered: it combines PCI Express link-level power states (from the PCIe Base Specification Revision 3.0), card-level power controls (M.2-specific signals), device-level states (via PCI Configuration Space and NVMe for SSDs), and platform-level coordination (e.g., suspend/resume handling). This ensures low idle power, dynamic scaling, and safe power transitions while supporting multiple interfaces (PCIe, SATA, USB, etc.).

The design prioritizes flexibility: modules derive internal voltages from the single 3.3 V rail (with optional VBAT in Socket 2 for always-on features like WWAN RTC), and power states are coordinated via dedicated sideband signals present across Socket 1 (Key E), Socket 2 (Key B), and Socket 3 (Key M).

1. Power Supply and Rail Characteristics

• Primary Power Rail: All M.2 modules use a single 3.3 V supply (pins like 2, 4, 70, 72, 74 depending on socket).
  • Voltage tolerance: Typically ±5% (3.135 V to 3.465 V).
  • Current capability: Defined per pin (e.g., up to 500 mA continuous per power pin in many implementations), with total module draw varying by type (e.g., Wi-Fi ~1–3 W, high-end NVMe SSDs up to several watts under load).
• Optional VBAT: In Socket 2 (Key B), pins 70/72/74 can support VBAT (battery voltage) for always-on functions like RTC or SIM card retention in WWAN modules.
• Internal Regulation: Modules internally generate lower voltages (e.g., 1.8 V, 1.2 V, or 0.8 V for core in BGA SSDs per ECN in Version 1.2).
• Power Sequencing: The specification requires safe ramp-up/ramp-down. PERST# (reset) is asserted during power-up until rails stabilize, preventing damage or undefined states.

2. Key Power Management Signals

These open-drain or active-low signals (pulled up on the host, typically to 3.3 V) enable coordinated power control:

• PERST# (PCIe Reset, active low)
  • Primary reset signal from host.
  • Asserted during power-up, system reset, or to force link retraining/power-down.
  • Deasserted only after power rails and REFCLK are stable.
  • Used across all sockets; critical for PCIe link initialization.
• CLKREQ# (Clock Request, bidirectional, open-drain)
  • Enables/disables the 100 MHz PCIe reference clock (REFCLK) for power savings.
  • Module asserts (pulls low) when it needs REFCLK (e.g., during link training or active operation).
  • Host deasserts REFCLK when idle (after timeout) if CLKREQ# is high.
  • Supports Clock Power Management (enabled via PCIe Configuration Space bit).
  • Required pull-up on host; used in all sockets.
• PEWAKE# (PCIe Wake, bidirectional, open-drain)
  • Allows module to wake the host from low-power system states (e.g., S3 sleep).
  • Module asserts (pulls low) for wake events (e.g., incoming data on WWAN, hotplug-like events).
  • Host asserts to wake module in some scenarios.
  • Supports PME (Power Management Event) signaling.
• FULL_CARD_POWER_OFF# (Socket 2 specific, active low)
  • Host-driven signal to completely power off the module (e.g., for WWAN radio disable).
  • When asserted, module must enter lowest power state or power down non-essential circuits.
• DEVSLP (Device Sleep, Socket 2/3, host output)
  • SATA-specific low-power command; puts SATA devices into deepest sleep (near-zero power).
  • Used when SATA fallback is active.
• W_DISABLE# (Wireless Disable, Socket 1/2)
  • Host RF-kill signals (W_DISABLE1#, W_DISABLE2#) to disable radios (e.g., airplane mode).
  • Forces module to low-power RF-off state.
• SUSCLK (32 kHz)
  • Host provides suspend clock for module RTC or low-power timers.

3. PCIe Link Power Management States

M.2 adheres to PCIe Base Spec Rev 3.0 Active State Power Management (ASPM):

• L0: Full active state (highest power).
• L0s: Shallow idle (quick exit, low latency; Tx side enters electrical idle).
• L1: Deeper idle (longer exit latency; clock gating, PLL power-down possible).
  • L1.1/L1.2 (substates): Even lower power via clock stop; optional in Rev 3.0 but supported in many M.2 SSDs.
• L2/L3: System sleep states (link powered down; wake via PEWAKE# or beacon).

ASPM is enabled via PCIe Configuration Space (Link Control Register). Modules advertise support (e.g., L0s/L1 exit latencies in Link Capabilities Register). NVMe SSDs often support Autonomous Power State Transition (APST) for device-initiated transitions.

4. Device-Level Power Management

• PCI Configuration Space:
  • Power Management Capability (offset ~40h): Supports D0 (active), D3hot (software-controlled low power), PME enable/status.
  • PCIe Capability: ASPM support, clock power management bit, L1 substates.
  • Latency Tolerance Reporting (LTR), Power Budgeting for platform awareness.
• NVMe-Specific (for SSDs in Socket 3/Key M):
  • Set Features (Power Management, Autonomous Power State Transition).
  • Non-Operational Power States (e.g., PS3/PS4 for deep idle).
  • Host Memory Buffer, Autonomous transitions reduce host polling.
• SATA Fallback: DEVSLP for ultra-low power.

5. Platform and Thermal Considerations

• Power-Up Sequence: Host asserts PERST# until 3.3 V stable; module holds CLKREQ# low initially.
• Wake/Suspend: PEWAKE# + PME for resume from S3/S4.
• Thermal/Power Limits: Guidelines for TDP (e.g., 3–5 W typical for SSDs); Version 1.2 adds high-power heat spreader ECN for better dissipation.
• Battery-Powered Systems: VBAT + low-power states minimize drain in sleep.

Revision 3.0’s power management ensures M.2 modules achieve low idle power (often <10 mW in deep states) while delivering high performance when needed, making it ideal for laptops, tablets, and embedded systems. These features are backward-compatible and build on PCIe 3.0 standards without major changes in later revisions for core signals. For exact timings, voltage thresholds, and ECN details (e.g., Cin increase for signal integrity aiding power states), the full PCI-SIG document provides authoritative reference.

---

8) PCI Express (PCIe) M.2 Revision 3.0: Electrical Specifications

The PCI Express M.2 Specification Revision 3.0 defines the electrical characteristics for the M.2 form factor to ensure reliable, high-speed operation in mobile and embedded platforms. These specifications cover power delivery, signaling integrity for PCIe (at 8 GT/s), SATA, USB, and sideband signals, connector contact requirements, insertion/extraction behavior, and signal quality parameters. The goal is to support multiple interfaces (PCIe up to x4, SATA 3.0, USB 2.0/3.0) over the 75-position (0.5 mm pitch) edge card connector while maintaining low power, electromagnetic compatibility (EMC), and compatibility with PCIe Base Specification Revision 3.0.

The electrical design assumes a single primary 3.3 V power rail, differential high-speed signaling, open-drain sidebands, and strict limits on capacitance, crosstalk, and loss to achieve robust performance in constrained environments (e.g., laptops with limited PCB routing space).

1. Power Supply Specifications

• Primary Voltage Rail: 3.3 V ±5% (nominal 3.3 V, range 3.135 V to 3.465 V).
  • All modules derive internal voltages (e.g., 1.8 V, 1.2 V, core logic) from this rail.
  • Power pins: Multiple redundant pins (e.g., pins 2, 4, 12, 14, 16, 18, 70, 72, 74 depending on socket) for current distribution and redundancy.
  • Current per pin: Up to 500 mA continuous (typical implementation limit; total module power varies by type, e.g., 1–3 W for wireless, higher for SSDs).
  • Optional VBAT: In Socket 2 (Key B), pins 70/72/74 support battery voltage (typically 3.0–4.2 V) for always-on features like RTC or SIM retention in WWAN modules. VBAT is not required and must not back-drive 3.3 V rail.
• Power Sequencing and Ramp-Up:
  • 3.3 V must rise monotonically.
  • PERST# asserted (low) until rails stabilize and REFCLK is valid.
  • Module must not draw excessive inrush current; soft-start circuits recommended.
• Power Consumption Guidelines: Vary by module class (e.g., Wi-Fi/BT ~0.9–3 W TDP, high-power SSDs higher with Version 1.2 heat spreader support). Platforms must provide sufficient current without excessive voltage drop.
• ECN Additions in Version 1.2:
  • Support for 0.8 V core voltage option on PWR_3 rail for BGA SSDs (improves efficiency in compact storage modules).

2. High-Speed Differential Signaling (PCIe and Shared Interfaces)

• PCIe Signaling: Compliant with PCIe Base Spec Rev 3.0 (8 GT/s, 128b/130b encoding).
  • Differential pairs: PETp/n (Tx from host), PERp/n (Rx to host).
  • Reference Clock (REFCLK): 100 MHz ±300 ppm differential (REFCLKp/n), low jitter (<3 ps RMS), AC-coupled on some implementations.
  • Insertion Loss: ≤ -0.5 dB up to 2.5 GHz (channel from host to module connector).
  • Return Loss: ≤ -15 dB up to 3 GHz.
  • Crosstalk: ≤ -32 dB up to 2.5 GHz (far-end and near-end).
  • Differential Voltage: Tx swing typically 800–1200 mV peak-to-peak (adjustable via de-emphasis/margining).
  • Receiver Sensitivity: Compliant with PCIe 3.0 eye diagram requirements.
• SATA (when active): SATA 3.0 (6 Gb/s), shared on lane 0 pairs (PETp0/n0 = SATA-A+/A-, PERp0/n0 = SATA-B+/B-). Electrical specs follow SATA-IO requirements.
• USB:
  • USB 2.0 (D+/D-): High-speed 480 Mb/s, full-speed/low-speed fallback.
  • Optional USB 3.0/3.1 Gen1 (5 Gb/s): On secondary lane pairs in some Socket 2 implementations.
• Input Capacitance (Cin):
  • Maximum increased via ECN in Version 1.2 for better compatibility with PCIe CEM Spec 4.0 and M.2 requirements (improves signal integrity margins).

3. Sideband and Control Signals

• Logic Levels:
  • Most sidebands (PERST#, CLKREQ#, PEWAKE#, W_DISABLE#, etc.): 0/3.3 V.
  • Some (e.g., I2C, UART, SDIO, PCM/I2S): 0/1.8 V.
  • Open-drain signals require host pull-ups (typically 10–100 kΩ to 3.3 V).
• Signal Integrity Requirements:
  • Rise/fall times, overshoot/undershoot limits per voltage domain.
  • ESD protection: Module and host must withstand system-level ESD (e.g., ±8 kV contact, ±15 kV air per IEC 61000-4-2).

4. Connector Electrical Characteristics

• Contact Resistance: ≤20 mΩ initial (after environmental testing).
• Insulation Resistance: ≥1000 MΩ at 500 V DC.
• Dielectric Withstanding Voltage: 500 V AC RMS for 1 minute (no breakdown).
• Insertion/Extraction Force:
  • Insertion: ≤ 45 N (20° angled insertion to reduce force).
  • Extraction: ≤ 20 N (with retention screw).
• Durability: 60 mating cycles minimum.
• Grounding: Multiple GND pins (e.g., 1, 3, 7, 11, etc.) for low impedance return path and EMC. Mechanical ground pads on module edge.

5. Additional Electrical Features and Constraints

• Hot-Plug / Surprise Removal: Not natively supported (PERST# used for controlled power-down); some platforms implement software hot-swap via NVMe.
• Electromagnetic Interference (EMI): Modules must comply with FCC Class B / CISPR 22 limits; shielding and filtering recommended.
• Thermal Electrical Interaction: Power pins sized for current without excessive heating; thermal guidelines tie into electrical limits.
• Configuration Detection: In Socket 2, CONFIG pins use pull-up/pull-down to select interface (e.g., high on CONFIG_1 for PCIe).

These electrical specifications ensure interoperability across hosts and modules while optimizing for mobile power/thermal budgets. Revision 3.0 aligns closely with PCIe Base 3.0 for signaling and adds mobile-specific refinements (e.g., capacitance adjustments in Version 1.2). For precise values (e.g., exact eye diagrams, timing parameters, or ECN details), the authoritative source is the PCI-SIG M.2 Specification Revision 3.0 document (member access required). Implementations may vary slightly per vendor, but all must meet or exceed these minimums for compliance.

---

9) PCI Express (PCIe) M.2 Revision 3.0: Thermal and Power Guidelines

The PCI Express M.2 Specification Revision 3.0 (including Version 1.2 dated June 26, 2019) includes dedicated thermal and power guidelines optimized for mobile and embedded platforms, such as ultrabooks, tablets, thin notebooks, and small-form-factor systems. These guidelines address the challenges of high integration in space-constrained, often fanless or low-airflow environments, where excessive heat can degrade performance, reduce component lifespan, or cause user discomfort (e.g., hot skin temperatures).

The guidelines focus on Thermal Design Power (TDP) definitions, module power dissipation estimates, skin temperature limits, placement recommendations, heat dissipation strategies, and assumptions for different platform types (fanless vs. fan-cooled). They are informed by the need to balance performance (e.g., PCIe 3.0 x4 bandwidth for SSDs) with thermal constraints, while incorporating refinements from prior revisions and ECNs (Engineering Change Notices) in Version 1.2, such as support for high-power heat spreaders.

1. Thermal Design Power (TDP) Definition and Module Classes

• TDP Definition: TDP is defined as the worst-case average power dissipation over a representative time duration under maximum sustained workload conditions. It represents the thermal load the platform must handle to prevent throttling or damage.
• Module-Specific TDP Estimates (typical ranges from the specification and aligned implementations):
  • Connectivity modules (Socket 1, Key E — Wi-Fi/Bluetooth/GNSS): 0.9 W to 3 W (idle ~0.5–1 W, peak during transmission).
  • WWAN modules (Socket 2, Key B — cellular modems): Up to 3.1 W sustained, with peaks higher during high-data-rate bursts (e.g., 4G/early 5G).
  • Storage modules (Socket 2/3, Key B/M — SSDs):
    • Entry-level/SATA: ~2–4 W.
    • PCIe 3.0 NVMe (x4): 3–7 W typical sustained, with peaks up to 8–10 W or more in high-performance drives under heavy sequential workloads.
  • Higher TDP modules (e.g., advanced accelerators or high-capacity SSDs) benefit from Version 1.2 ECN additions like the High Power M.2 Heat Spreader support, enabling better thermal dissipation for modules exceeding standard limits.

These values are not hard caps but guidelines; actual consumption depends on workload, firmware, and NVMe/SATA power states.

2. Temperature Limits and Skin Temperature Guidelines

• Module Operating Temperature:
  • Normal: Typically 0°C to 70°C (component junction or case).
  • Extended: Some implementations support -40°C to +85°C for industrial-grade modules.
• Skin Temperature Limits (critical for user-contact surfaces in mobile devices):
  • Fanless platforms (e.g., tablets): 37°C to 45°C maximum skin temperature to ensure comfort.
  • Fan-cooled notebooks: Up to 58°C allowable in some areas.
  • The specification provides sensitivity analysis: e.g., a 3°C/W increase in thermal resistance in fanless designs can significantly raise skin temperatures.
• Ambient Assumptions:
  • System ambient: 25°C to 35°C typical for mobile platforms.
  • Modules placed away from high-heat sources (CPU/GPU) to minimize compound heating.

Exceeding these can trigger thermal throttling (e.g., NVMe Autonomous Power State Transition or firmware downclocking).

3. Thermal Dissipation and Management Strategies

• Dissipation Paths:
  • Primary heat path: Through the module PCB and components to the top surface (for heat spreaders) or bottom (to chassis/thermal pads).
  • Double-sided modules (D1–D5) require careful component placement to avoid hot spots.
• Platform Recommendations:
  • Use thermal interface materials (TIM) or pads between module and chassis/heatsink.
  • Ensure airflow or conduction paths in fan-cooled systems.
  • Avoid placement near other high-TDP components.
  • For high-power scenarios: Version 1.2 introduces explicit support for heat spreaders (via ECN) to handle increased TDP without exceeding skin limits.
• Thermal Sensitivity:
  • Fanless systems: Higher thermal resistance (e.g., 10–20°C/W from module to ambient), leading to more aggressive power limiting.
  • Fan-based: Lower resistance, allowing sustained higher TDP.

4. Power-Related Thermal Interactions

Power guidelines tie directly into thermal management:

• Power Rail: Single 3.3 V (with optional VBAT in Socket 2 for always-on features). High current draw (e.g., >2 A in high-TDP SSDs) generates I²R heating in pins and traces.
• Power Management Features (cross-referenced with power section):
  • ASPM (L0s/L1/L1 substates), CLKREQ#, PEWAKE#, DEVSLP reduce average power and heat.
  • NVMe APST and Host Controlled Thermal Management (HCTM) allow dynamic throttling based on temperature sensors.
  • Idle power: Often <10–50 mW in deepest states (e.g., PS4 for NVMe).
• High-Power Considerations: Version 1.2 ECNs (e.g., High Power M.2 Heat Spreader) enable modules with higher sustained TDP by improving heat transfer to the platform.

5. Assumptions and Platform-Specific Notes

• Guidelines assume thin mobile platforms (e.g., <15 mm thick notebooks/tablets).
• Fanless designs require conservative TDP limits and placement to meet skin temperature goals.
• Testing assumes worst-case workloads (e.g., sustained sequential writes for SSDs, high TX power for WWAN).
• Manufacturers must validate thermal performance per module type; the specification provides reference models and sensitivity curves rather than rigid limits.

These thermal and power guidelines in Revision 3.0 ensure M.2 remains viable for power- and thermal-constrained mobile computing, supporting reliable operation across connectivity, storage, and emerging use cases. Later M.2 revisions (e.g., 4.0/5.0) build on these with higher TDP allowances for faster PCIe generations, but Revision 3.0 remains foundational for PCIe 3.0-era devices. For exact tables, figures (e.g., thermal resistance models), and ECN details, consult the full PCI-SIG M.2 Specification Revision 3.0 document.

---

10) PCI Express (PCIe) M.2 Revision 3.0: Signal Integrity

The PCI Express M.2 Specification Revision 3.0 (including Version 1.2 from June 26, 2019) places strong emphasis on signal integrity (SI) to ensure reliable high-speed data transmission in the compact, mobile-oriented M.2 form factor. At PCIe 3.0 speeds (8 GT/s per lane, Nyquist frequency of 4 GHz), the short interconnect paths between host and module—combined with the 0.5 mm pitch 75-position edge connector—still introduce challenges such as frequency-dependent loss, reflections, crosstalk, and impedance discontinuities. The specification defines electrical budgets, channel requirements, and test parameters to maintain eye opening, bit error rate (BER) targets, and overall link robustness across Socket 1 (Key E), Socket 2 (Key B), and Socket 3 (Key M).

Signal integrity in M.2 is governed by alignment with the PCI Express Base Specification Revision 3.0 for transmitter/receiver characteristics, equalization, and jitter budgets, while the M.2 document adds module-specific constraints for the edge connector, PCB routing, and differential pairs. The design assumes worst-case mobile platforms with limited PCB space, tight bends, vias, and proximity to other signals, necessitating conservative loss and noise margins.

1. Key Signal Integrity Parameters and Requirements

The M.2 specification outlines channel-level requirements for high-speed differential interfaces (primarily PCIe lanes, with shared pairs for SATA/USB in fallback modes). These parameters ensure the end-to-end channel (host PCB → connector → module PCB) delivers acceptable performance at 8 GT/s.

• Differential Insertion Loss (IL)
  • Maximum allowed: ≤ -0.5 dB up to 2.5 GHz (often extended to cover up to Nyquist at 4 GHz in practice).
  • This tight limit reflects the short but connector-dominated channel in M.2.
  • Objective: Minimize attenuation of high-frequency content to preserve eye height after equalization.
  • In mobile platforms, total channel loss (including host routing and module traces) is kept low compared to full-size add-in cards.
• Return Loss (RL)
  • Differential return loss: ≤ -15 dB up to 3 GHz (typically measured single-ended or differential).
  • Ensures minimal reflections from impedance mismatches at the connector, vias, or component pads.
  • Poor return loss causes deterministic jitter (DJ) from reflections, closing the eye at the receiver.
• Crosstalk
  • Far-end crosstalk (FEXT) and near-end crosstalk (NEXT): ≤ -32 dB up to 2.5 GHz.
  • Aggressive limit due to dense pinout (0.5 mm pitch) and proximity of Tx/Rx pairs in the connector.
  • Crosstalk is a major concern in Socket 3 (Key M) with x4 lanes, where adjacent differential pairs can couple noise.
  • Specification often references ccICN (component comprehensive integrated crosstalk noise) concepts in later interpretations, but Revision 3.0 uses simpler FEXT/NEXT masks.

These parameters are defined for the M.2 channel (from host breakout to module edge fingers), with test procedures involving vector network analyzer (VNA) measurements or simulation.

2. Additional Electrical Constraints Impacting Signal Integrity

• Input Capacitance (Cin)
  • Maximum receiver input capacitance increased via ECN in Version 1.2.
  • Allows better compatibility with PCIe CEM Spec 4.0 practices while maintaining margins for reflections and bandwidth.
  • Higher Cin can slightly degrade high-frequency response but improves robustness in real systems.
• Impedance Targets
  • Differential impedance: 85 Ω ±15% (nominal for PCIe).
  • Single-ended: ~50 Ω per trace.
  • Connector and edge finger design minimize discontinuities; plating and chamfer regions are optimized to reduce reflection coefficient.
• Reference Clock (REFCLK)
  • 100 MHz differential, low jitter (<3 ps RMS typical).
  • AC-coupled in some designs; spread-spectrum clocking (SSC) supported to reduce EMI while preserving integrity.
• Jitter Budget
  • Total jitter (TJ) at BER 10⁻¹² derived from PCIe Base 3.0: ~0.3–0.35 UI typical in stressed receiver tests.
  • Includes random jitter (RJ), deterministic jitter (DJ from ISI, crosstalk, reflections), and duty cycle distortion.

3. High-Speed Interfaces and Shared Pairs

• PCIe Lanes (PETp/n Tx, PERp/n Rx): Primary focus; full x4 in Socket 3, x2 in Socket 1/2.
• SATA Fallback (shared on lane 0 in Socket 2/3): Must meet both PCIe 8 GT/s and SATA 6 Gb/s integrity.
• USB (D+/D- in Socket 1/2): Lower speed but sensitive to crosstalk from adjacent high-speed pairs.

4. Design and Implementation Guidelines for Signal Integrity

• Routing Recommendations:
  • Keep differential pairs tightly coupled (minimal length mismatch <0.5 mm).
  • Avoid right-angle bends; use 45° or curved traces.
  • Minimize vias; use back-drilling if needed.
  • Reference to continuous ground planes; avoid splits under high-speed traces.
• Connector Considerations:
  • 75-position edge card with 0.5 mm pitch; ground pins surround differential pairs for shielding.
  • Insertion/removal force minimized while preserving contact integrity (durability ≥60 cycles).
• Equalization and Compensation:
  • PCIe 3.0 Tx de-emphasis (preset levels) and Rx continuous time linear equalizer (CTLE) + decision feedback equalizer (DFE) compensate for channel loss.
  • M.2 modules must support required presets for link training.
• Testing and Validation:
  • VNA for S-parameters (IL, RL, crosstalk).
  • Oscilloscope-based eye diagram analysis (post-CTLE/DFE).
  • Compliance channels and stressed receiver testing per PCIe Base 3.0.

5. Relation to Later Revisions and Practical Implications

Revision 3.0’s SI requirements are conservative compared to PCIe 4.0/5.0 (16/32 GT/s), where loss budgets reach 28–36 dB and Nyquist frequencies double. The tight limits in Rev 3.0 (e.g., low IL, strict crosstalk) enable reliable 8 GT/s operation in short mobile channels without excessive equalization complexity. In practice, most M.2 implementations (especially 2280 NVMe SSDs) achieve robust BER with margin when following these guidelines.

These signal integrity provisions in Revision 3.0 ensure M.2 supports high-performance PCIe 3.0 applications (e.g., NVMe SSDs at ~4 GB/s aggregate) in power- and space-constrained mobile platforms while maintaining interoperability and low error rates. For exact S-parameter masks, test fixtures, and ECN details (e.g., Cin increase), refer to the full PCI-SIG M.2 Specification Revision 3.0 document.

---