Hardware

M.2 E Key vs B Key vs M Key: Interfaces, Buses, and Power-On Checks

Determine M.2 E Key, B Key, and M Key compatibility from the notch, socket type, PCIe/USB/SATA buses, and power requirements, with pre-power documentation and multimeter checks.

Being able to insert an M.2 card does not mean the motherboard exposes the signals it needs. A matching notch also does not guarantee compatible power rails, reset, clocks, or configuration pins. Check the mechanical key, socket purpose, host wiring, and module datasheet together.

This guide focuses on the practical questions: what normally connects to E Key, B Key, and M Key, why a module may fit but remain undetected, and what to verify before wiring a custom carrier board.

How the three interfaces differ

Key / Socket Common equipment Possible bus from the host Common error zone
Key E / Socket 1 Wi-Fi, Bluetooth, partially wireless module PCIe, USB, I2S/PCM, etc. Think Wi-Fi and Bluetooth go, PCIe.
Key B / Socket 2 WWAN, Humming Room Module, Part SATA/PCIE SSD USB, PCIe, SATA, SIM/UIM etc. depending on host B+M SSD will support the SATA if you can.
Key M / Socket 3 NVME SSD, Partial Accelerator Card Usually PCIe x4, there may be other normative extensions. Match M Key with any NVMe device

Mechanical Key limits only partial insertions and does not describe exactly what signals the main panel is receiving.

Key E: Wi-Fi works but Bluetooth is missing

Many Wi-Fi cards put Wi-Fi in PCIe, Bluetooth in USB. If the host only connects to PCIe, the system may recognize wireless web cards without seeing the Bluetooth controller at all.

Check two main lines during the checkout:

Linux:

1
2
3
4

lspci -nn
lsusb
rfkill list
dmesg | grep -Ei 'wifi|wlan|bluetooth|usb|pci'

Windows: Expand “Network Adapter” and “Bluetooth” in the device manager to check for unknown USB devices. Don’t judge the slot to be fully compatible just because Wi-Fi is normal.

Key B: WWAN, SATA, and PCIe are easy to confuse

Key B slots are often used in cellular modules and may require USB, SIM/UIM, control and wake-up signals. B+M Key SSD can be mechanically compatible part B or M slots, but it actually uses SATA or PCIe and must look at modules and host descriptions.

Typical failures include:

  • The slot only goes to WWAN USB, no SATA or PCIE.
  • The motherboard firmware allows only specific device types.
  • SIM signal or power control was not taken out.
  • The module’s peak power exceeds the carrier board’s capacity.
  • The host understands the configuration foot state differently from the module.

PCI-SIG has published a change note for Key B that also provides PCIe and USB 3.1 Gen1, which also indicates that “Key B fixes only one bus”.

Key M: NVMe compatibility is more than the notch

Key M is usually used for PCIe x4 NVME SSD. The compatibility of judgement also depends on:

  • The main panel slot actually provides x1, x2 or x4.
  • Supported PCIe intergenerational and solid unit start-up capability.
  • Length of modules, e.g. 2230, 2242, 2260, 2280, 22110.
  • Whether single- or double-sided components interfere with the motherboard or heat spreader.
  • The ability of electricity and heat to sustain loads.

The old platform may be able to identify NVME data discs, but it cannot be activated from them; this is a problem with solids and start paths, not simply a foot failure.

Why can’t we just check one Pinout diagram?

The same foot position may be reserved, optional or reused under different Socket, code version and configuration. The third-party master board may also not be able to access all the buses allowed by the code.

Prepare at least:

  1. Current PCI-SIG M.2 specification or corresponding version of information.
  2. A board design guide for the main board/COM module.
  3. M.2 Module data manual.
  4. Mechanical dimensions and direction maps of the plugins.
  5. The main board rationale or a clear description of the interface function.

Do not determine Pin 1 from a web image alone. Connector orientation, top/bottom drawing views, and module-side numbering can differ.

Documentation checklist before power-on

Axle meters are suitable for checking short circuits, groundings and static power sources and for verifying the quality of high-speed PCIe differential signals.

After the blackout:

  1. Confirmed module unplugged.
  2. Check whether the 3.3V power source is close to short circuits.
  3. Check continuity between every GND pin and motherboard ground.
  4. Check whether the source foot was erroneously received by the retention or signal foot according to the rationale map.
  5. Check the plug welding short circuits and mispositions.

The first call recommended the use of a limited current power source and the measurement of slot voltage without modules. The installation module is then cut off when the voltage is correct.

Never use continuity or resistance mode on a powered board. Avoid touching adjacent high-speed pins with a broad probe tip, which can cause a short circuit.

Confirm the bus enumeration on Linux

Following the installation of the module, record the difference between the power up and down:

1
2

lspci -nnk > before-pci.txt
lsusb > before-usb.txt

Install and restart:

1
2
3
4
5

lspci -nnk > after-pci.txt
lsusb > after-usb.txt
diff -u before-pci.txt after-pci.txt
diff -u before-usb.txt after-usb.txt
dmesg | grep -Ei 'pcie|nvme|usb|firmware|timeout|link'

There is no new equipment at all, and priority is given to checking whether the power supply, repositioning, clock and bus are out; the equipment has failed but the drive is then checked for driver, solidware and equipment ID.

Order of judgement on common compatibility issues

It can be inserted, but the system has no equipment.

Confirm the use of the slot and the bus instead of replacing the driver. WWAN slots, storage slots and WLAN slots may be completely different even if they are close in size.

Wi-Fi works, but Bluetooth is missing

Checks the USB connection, the BIOS switch and the USB device count for Key E.

B+M SATA SSD not recognised after inserting M Key

Confirms whether the MKey slot is only PCIE/NVMe. Mechanical compatibility cannot convert SATA to PCIe.

Check the main board sharing channel, CPU/chip group expansion, slot actual lanes, BIOS settings and chain errors. Don’t blame SSD for all the downs.

The module overheats on the motherboard

The power is cut immediately and the direction, source foot, voltage and flow limit records are checked. Anomalous fever is not a normal “drive unloaded” phenomenon.

Checks for custom carrier-board designs

  • PCIe differentials are resistant, length matching and perforation.
  • REFCLK, PERST#, CLKREQ# is the timescale.
  • USB differential pair and ESD protection.
  • 3.3V Power peak, capacitation and pressure reduction.
  • Module configuration foot and host pull/down.
  • Fixed column position, module length, heat dispersion and antenna cleanness.

High-speed interfaces are occasionally identified at low loads and do not represent design pass. Official products still require oscilloscopes, protocol analysis or compliance testing, rather than only universal-use continuous checks.

References: