Debug Store

Acute Technologies MIPI D-PHY Option

Acute Technologies MIPI D-PHY Option

Add MIPI D-PHY decode, image restore, and error analysis to BusFinder.

SKU: BFO-PHY

Regular price
£14,830.00 exc VAT
£17,796.00 inc VAT
Regular price Sale price
£14,830.00 exc VAT
£17,796.00 inc VAT
Sale Sold out
Shipping calculated at checkout.

Payment methods

  • American Express
  • Visa
  • Mastercard
  • Maestro
  • PayPal
  • Apple Pay
  • Google Pay
  • Bank transfer
View full details

Overview

The Acute MIPI D-PHY Option (BFO-PHY) equips BusFinder analysers with full-speed capture and decode for CSI-2 1.3 and DSI 1.3 across 1+4 lanes up to 2.0 Gbps per lane, including LP-to-HS transition coverage for reliable bring-up and debug.

It displays reconstructed images (RGB, YCbCr, RAW, DSC), counts porches for timing verification, and tallies ECC/CRC errors while exposing packet tables, search and filter tools to pinpoint protocol faults and data integrity issues quickly.

Engineers typically pair this option with the BusFinder BF7264B/BF7264B+/Pro platforms, adding Way Stations, SMPM coax, and differential end-tips for safe access to CLK and D0–D3; see Acute BusFinder BF7264B for the host instrument on The Debug Store.

Related product: Acute BusFinder BF7264B Protocol Analyser — https://thedebugstore.com/products/acute-technology-busfinder-bf7264b-protocol-analyser-uk

Professional MIPI D-PHY Decode for CSI-2 and DSI

Add-on option for Acute BusFinder protocol analysers to capture, decode and visualise MIPI D-PHY traffic from Low-Power to High-Speed transitions.

Interface Standard Lanes Data Rate Display Formats Error Checks
MIPI D-PHY V1.2 1 + 4 (CLK, D0–D3) Up to 2.0 Gbps per lane RGB, YCbCr, RAW, DSC ECC/CRC count & report

What it does

  • Decodes CSI-2 1.3 and DSI 1.3 packets with DCS 1.3 command analysis.
  • Captures from LP init through HS data, with filters to ignore image payloads and extend capture depth.
  • Restores and displays image frames; provides porch statistics for timing analysis.
  • Searches by packet type, virtual channel, data ID or error; compiles command statistics.
  • Detects TE (Tearing Effect) signalling; exports logs to TXT/CSV for post-processing.

Way Station Pinout

Pair Signals Notes
CLK (Diff) CLK+ / CLK− Differential clock input
D0 (Diff) D0+ / D0− Data lane 0
D1 (Diff) D1+ / D1− Data lane 1
D2 (Diff) D2+ / D2− Data lane 2
D3 (Diff) D3+ / D3− Data lane 3
TE (Optional) TE Tearing Effect detection channel

Signal access: keep solder pigtails under 5 mm; on the DUT, place a 100 Ω termination and connect to the end-tip with ~3 cm coax to minimise loading.

Wiring Quick-Start

  1. Power and connect the BusFinder; fit the D-PHY Way Station to Slot-B and SMPM coax leads to the end-tips.
  2. Solder ultra-short pigtails to CLK and D0–D3 differential pairs at the DUT test pads; add optional TE lead if required.
  3. Launch BusFinder software, select MIPI D-PHY DSI/CSI mode, verify Way Station LEDs, then arm capture in LP mode.
  4. Use Data Filter to suppress image payloads, enable ECC/CRC counters, and configure triggers on specific packet types.

Ready-to-Run CSV Post-Processing

# Parse BusFinder MIPI CSV and summarise ECC/CRC errors per virtual channel import csv, collections errors = collections.defaultdict(lambda: {"ECC":0, "CRC":0}) with open("mipi_dphy_log.csv", newline="") as f: rd = csv.DictReader(f) for r in rd: vc = r.get("VC","NA") if r.get("ECC_Error") == "1": errors[vc]["ECC"] += 1 if r.get("CRC_Error") == "1": errors[vc]["CRC"] += 1
print("VC, ECC_Errors, CRC_Errors")
for vc, d in errors.items():
print(f"{vc}, {d['ECC']}, {d['CRC']}")
[Hero image placeholder]
[Probe connection diagram placeholder]
[Decoded frame/table view placeholder]
Ordering information
Part number (SKU)BFO-PHY
ManufacturerDebug Store
EAN5055383600144
Shipping weight0.5 kg
  • 1 ×Acute Technologies MIPI D-PHY Option

Contact us to confirm the full contents of the box.

Engineer Q&A

Questions and Answers

No questions have been asked about this product yet. Ask our engineers below and we'll reply by email.

Can't find your answer? Ask our engineers.

Ask a Question

Ask Our Engineers About This Product

Your question goes to the Debug Store technical team. We answer by email, and useful questions may be added to this page without your name or email address.

We reply within 24 hours.