Mazda Connect Firmware Region Codes Explained

Every Gen 6 CMU firmware package is built for a specific region. The region code sets radio band configuration, language availability, navigation behavior, and which features are enabled. Flash a package from the wrong region and you can disable working hardware or leave the unit in an inconsistent state. This page covers what the codes mean, where to find yours, and how to recover if a wrong-region package has already been installed.

Your unit displays one code; the package filename uses another

The CMU shows a region code on the About screen. Firmware package filenames use a separate but related code. Both are listed below.

Display Code	Filename Code	Region	Primary Markets	Radio Bands
NA N	NA	North America	United States, Canada, Mexico	FM 87.5–108.0 MHz, AM 530–1710 kHz, SiriusXM
EU N	EU	Europe	UK, Germany, France, etc.	FM 87.5–108.0 MHz, DAB/DAB+ enabled
4A N	ADR	Asia-Pacific / Oceania	Australia, New Zealand, Middle East, Southeast Asia, South Africa, South America	FM 87.5–108.0 MHz, DAB enabled (Australia)
JP M	JP	Japan	Japan domestic market	FM 76.0–95.0 MHz (Wide FM band), different nav format

Additional codes appear in some markets:

Display Code	Filename Code	Region
MKH	MKH	Hong Kong

The ADR filename code stands for Australian Domestic Regulations. Australia and New Zealand are the primary markets, but the same package covers a much broader region: the Middle East, Southeast Asia, South Africa, and parts of South America.

Read your code on the About screen

Navigate to Settings → System → About. The screen shows:

OS Version:       74.00.324A
Region:           NA N
Failsafe Version: 59.00.504

The fields that matter:

• OS Version: the currently running firmware. See firmware versions for the full version history.
• Region: the display code that determines which firmware packages are compatible.
• Failsafe Version: the recovery partition firmware. The unit can fall back to this if an update fails.

Some versions of the About screen also list the serial number and the Bluetooth and WiFi MAC addresses. For step-by-step access to this screen, see check firmware.

The code sets radio bands, languages, and navigation behavior

Radio

• NA N enables SiriusXM satellite radio support.
• EU N and ADR/4A N (in Australia) enable DAB/DAB+ digital radio.
• JP uses the extended FM band (76.0–95.0 MHz) used in Japan.
• Installing NA N firmware on a EU unit disables DAB and can misconfigure FM.

Language and Localization

• Available language packs differ by region.
• Text-to-speech voice options are region-specific.
• Date and time format defaults change with region.

Navigation

• Map data format expectations differ by region.
• GPS datum and coordinate display preferences are region-set.
• Some navigation features are region-locked.

CarPlay / Android Auto

• All regions support wired CarPlay and Android Auto on v70+ with the correct USB hub hardware.
• Wireless CarPlay requires wireless-capable hardware: a native wireless-capable CMU, a wireless replacement hub, or an external adapter. It is not enabled by region code or firmware alone.

A wrong-region flash can take out radio, navigation, or recovery

Scenario	Risk Level	Symptoms
NA firmware on EU hardware	High	DAB disabled, radio misconfigured, possible boot issues
EU firmware on NA hardware	High	SiriusXM disabled, FM band configuration wrong
ADR firmware on NA hardware	Medium	Feature differences, DAB/SiriusXM mismatch
Same-region firmware, different version	Normal update risk	Standard update procedure applies

How a mismatch shows up

• Radio stops working: wrong band configuration means the tuner hardware cannot receive local stations.
• Features disappear: region-locked features (DAB, SiriusXM) are disabled when the region does not match.
• Boot loop: in rare cases, hardware initialization fails when firmware expects hardware not present for that region.
• Navigation failure: map data incompatibility can crash the navigation app.
• Recovery complications: if the failsafe partition is also wrong-region, recovery options narrow.

Recover by reinstalling the correct-region package

1. If the unit still boots, reinstall the correct-region firmware via USB. See firmware update procedure.
2. If the unit does not boot, the failsafe partition may recover it on the next power cycle.
3. If both the main and failsafe partitions are wrong-region, dealer intervention is likely required. See troubleshooting for further recovery guidance.

Prevention is far easier than recovery. Verify the region code in the firmware filename matches your unit before installing.

Match the filename code to your displayed code before installing

Firmware packages follow this naming pattern:

cmu150_NA_74.00.324A_update.up
       ^^
       Region (filename code)

Examples by region:

Filename	Target Region
cmu150_NA_74.00.324A_update.up	North America (displays as NA N)
cmu150_EU_74.00.324A_update.up	Europe (displays as EU N)
cmu150_ADR_74.00.324A_update.up	Asia-Pacific / Oceania (displays as 4A N)
cmu150_JP_74.00.324A_update.up	Japan (displays as JP M)

Match the filename region code to your unit’s displayed region code before installing. A cmu150_ADR_ package is correct for a unit displaying 4A N. Every region shares the same 74.00.324A version token, so a matching version number is not evidence that a package is region-correct. Confirm the region code before flashing.

The region locks the package, not the tweaks you run after

Region matching applies to the firmware package. Modifications you install afterward, like the touch-while-driving fix or community tweaks, gate on the OS version instead. All four regional 74.00.324A packages carry the same OS version; the region code is separate metadata that sets radio, language, and navigation. So a tweak validated on 74.00.324A behaves the same on an NA, EU, or ADR unit running that version: the touchscreen speed-lockout is stored in the same files with the same flags across the regional builds. The regional packages differ in size (the EU package is 2.4 GB against 1003 MB for NA because Europe carries more language and map data), but that difference is in the resources, not the part a touch-while-driving tweak edits.

TouchTune, for instance, checks for 74.00.324A and refuses any other version, but does not check the region. That does not loosen the rule above: the .up package itself is still region-locked, and cross-flashing regions still breaks radio and navigation. Match the package region when you flash firmware; the post-install tweak layer is region-independent.

Verify the region on any replacement CMU before you buy it

If buying a replacement CMU or receiving a dealer swap, verify the region code matches your vehicle’s market. Units sourced from another market may arrive with mismatched region firmware pre-installed.

The region is not reliably derivable from the VIN. The safest confirmation is to power on the unit and check the About screen, or to verify the filename of whatever firmware the dealer last installed.

For a full pre-purchase compatibility walkthrough, see before you buy. For which model years and CMU generations are covered at all, see supported vehicles.