Skip to content

Mazda Connect Diagnostic Menu and Hidden Button Shortcuts

The Gen 6 Mazda Connect CMU (Connectivity Master Unit, the Linux computer behind the dash) has a built-in factory diagnostic menu. It is a service screen with version information, vehicle signals, speaker and display checks, GPS status, DTC tools, and the firmware update entry point. It is stock Mazda behavior and works on an unmodified car.

This page covers how to open it, which codes are safe to read, and which ones to leave alone.

The short answer: the two shortcuts most people come for are below. Both are physical key chords, so they behave the same on touchscreen and commander-only cars.

You want toHoldFor
Open the diagnostic test screenVolume/Mute + Music + Favorites/Star2–5 seconds
Reboot a stuck CMUNav + Back + Volume/Mute10–20 seconds, ignition on

Hold Volume/Mute + Music + Favorites/Star together for about 2–5 seconds. The CMU opens the diagnostic test screen. This is the factory service shortcut documented in Mazda’s own service bulletin.

There is also a touch-only entry on v74-style systems: open Settings > Display, long-press the hidden clock/status area for about 5 seconds, then long-press Home within the next few seconds. The hard-key shortcut above is the normal path to use.

ShortcutWhat It DoesNotes
Hold Volume/Mute + Music + Favorites/Star for about 2–5 secondsOpens the Mazda diagnostic test screenStock service shortcut.
Hold Nav + Back + Volume/Mute for about 10–20 secondsReboots the CMUUse if the screen or audio stack is stuck. The ignition or ACC has to be on for the keys to register. It does not erase settings. Owners report it does not work on the newer Gen 7 (8.8/10.25-inch) systems.
Hold Music + Back + Volume/Mute for several secondsToggles the CPU/memory system-monitor overlayShows live CPU and memory use in the top-right corner. Touch-hold the overlay to open the fuller Linux performance monitor. Present on builds that include the benchmark capture service.

Other key chords turn up in extracted firmware source, including a screenshot/log-marker combo and a separate Back + Favorites/Star gauge toggle. They only appear on engineering or internal builds and are not confirmed on a production car, so treat them as curiosities rather than owner tools.

If your CMU is stuck rather than just confusing, the reboot shortcut above is the first thing to try. For a stuck screen that won’t recover, see /mazda-connect/reboot-reset/ and /mazda-connect/black-screen/.

After the shortcut opens, the CMU shows a number pad. Type a test number and press Enter. If the firmware does not support that number, the screen shows Invalid.

The normal diagnostic screen accepts two-digit IDs. Some patched or internal “JCI Test Mode” screens accept longer IDs and expose extra engineering scripts. Those are not owner-facing tools, so don’t go looking for them.

These areas are safe to browse because they only display information:

CodeFunctionWhy It Is Useful
3, 4, 5, 6Read AVC, CMU, TAU, and CD DTCsShows stored diagnostic trouble codes without clearing them.
9Software Version Display (CD)Shows CD/DVD module software version where fitted.
10Part Number Readout CD/DVDShows CD/DVD module part information where fitted.
53Software Version Display (CMU)Confirms the installed Mazda Connect firmware version.
57Software Version Display (VIP)Shows vehicle interface processor/version details.
58Vehicle InfoConfirms the CMU’s detected vehicle information.
59CMU Serial Number ReadoutShows the CMU serial number.
61Vehicle Signal (Unit Status)Shows live vehicle signal status.
65Commander and Switch CheckVerifies commander knob and switch inputs.
68Software Version Display (TFT Display)Shows display module version information.
69Software Version Display (Touch Panel)Shows touch panel version information.
70Display CheckRuns display test screens.
72GPS DataShows GPS receiver data, including satellite count.
73DR Unit DataShows dead-reckoning sensor data.
74NEO-M8L DataShows u-blox GPS/dead-reckoning diagnostic data.
84, 85, 93, 95TAU informationShows tuner/audio-unit maker, part, software, and vehicle information where fitted.
96XM Serial NumberShows satellite-radio receiver serial information where fitted.

Code 53 is the granular version readout, with more detail than Settings > About. It’s the fastest way to confirm exactly which firmware build is installed. To interpret what it tells you, see /mazda-connect/check-firmware/ and /firmware/versions/.

These entries can clear data, reset modules, or start service routines. Do not run them unless you know why or support asks you to.

CodeFunctionWhy To Be Careful
2Clear DTCClears diagnostic trouble codes. Used during firmware update workflows, but it erases evidence.
8Software Reset AVCRestarts the audio/video controller path.
30Copy Data To USBMay export diagnostic data on builds that expose it.
31Clear All DataClears stored data. Treat as service-only.
32, 33, 34Clear heater/brake/battery dataVehicle/module-specific clear operations. Hidden on some vehicle variants.
75Clear NEO-M8L Backup DataClears GPS/dead-reckoning backup data.
81Clear iAP ID Data & CMU ResetClears Apple accessory pairing identity data and resets the CMU.
82XM Clear DataClears satellite-radio data where fitted.
99System UpdateSearches for firmware update packages. Use only with the correct update files and the documented procedure.

Codes 1, 25, 28, 83, 86–92, 94, 97, and 98 are active CD/audio/radio/XM/HD/DAB tests. They are useful for service diagnosis, but they can make unexpected sound or change tuner/test state while running.

If you triggered a clear by accident and the car is now misbehaving, the recovery paths are documented in /firmware/recovery/ and /support/factory-reset-vs-firmware-reinstall/.

Some firmware images include native engineering overlays:

ToolWhat It ShowsHow It Is Exposed
CPU/memory gaugeCPU load, memory use, thread count, and Linux/system version dataOn builds with the benchmark capture service, hold Music + Back + Volume/Mute for several seconds to toggle the overlay. Touch-hold it to open the fuller Linux performance monitor. Internal service menus can also toggle it.
FPS counterBrowser/UI frame-rate counterPresent in Mazda’s Opera user-script path on some builds.
Boot profilerBoot timing, CPU, and memory logsWrites logs to disk; it is not an on-screen owner control.

If a profiler shortcut does not visibly do anything, the build is usually running the tool in background mode or the capture service is not enabled.

The Shortcut Is Consistent; the Code List Varies by Firmware

Section titled “The Shortcut Is Consistent; the Code List Varies by Firmware”

The diagnostic shortcut is broadly consistent across Gen 6 Mazda Connect firmware, but the exact menu contents are reported by the firmware at runtime and vary by version, vehicle, and installed modules. Always trust what the CMU shows as valid over any printed list.

Version / BuildDifference
v74 reference firmwareSupports the v74 diagnostic behavior described above. Some extracted builds include the CPU/memory gauge and benchmark capture shortcuts.
J03G-style vehicle variantsThe firmware hides the data clear/export IDs 30–34.
Internal/JCI Test ModeAdds JCI engineering test IDs and script launch paths. Normal owners should not use this mode.
AIO-patched diagnostic appSome AIO versions add or restore a visible T/M button and shorten the touch-entry hold timing. That is not stock Mazda behavior.
Older 55/59/70 firmwareThe diagnostic entry and update code 99 are familiar, but the exact test list can differ.
  • Verifying GPS reception: code 72 shows satellite count without needing a navigation destination.
  • Identifying speaker channels: useful when troubleshooting audio or verifying Bose wiring. See /mazda-connect/bose-audio/.
  • Reading detailed version info: code 53 is more granular than Settings > About.
  • Touchscreen issues: display and touch-panel checks help confirm a genuine ghost touch or touch-offset problem versus a software glitch.
  • Confirming hardware capabilities: checking what hardware the CMU detects as present.

The diagnostic menu is a factory tool that runs through the CMU’s own UI framework. It reads and resets modules; it does not install or remove any aftermarket software.