How to Format a USB Drive for Mazda Connect

The Gen 6 Mazda Connect CMU reads USB drives for firmware updates, navigation data, music, and recovery. It is also picky: the same drive that mounts fine on your laptop will be invisible to the head unit if the filesystem or partition table is wrong. Drive prep is the single most common reason an update or install fails to start.

Get one detail wrong and the symptom is silent — the CMU just doesn’t see the drive, with no error. So the requirements below are non-negotiable, not suggestions.

Requirements

Parameter	Requirement
Filesystem	FAT32 (mandatory — exFAT and NTFS are ignored)
Partition scheme	MBR (Master Boot Record), not GPT
Capacity	2 GB minimum; 32 GB or smaller is easiest. Larger drives work but Windows won’t format them FAT32 from the GUI (see below)
USB standard	USB 2.0 or 3.0 both work; the CMU port runs at USB 2.0 speed
Connector	USB-A, plugged directly into the port — no hub, no extension cable

Two of these trip people up the most: exFAT looks and behaves like FAT32 in everyday use but the CMU will not mount it, and modern OSes increasingly default to GPT partition tables that the head unit’s kernel can’t read.

Formatting Instructions

macOS

diskutil list                          # find your USB drive's identifier
diskutil eraseDisk FAT32 MFY MBRFormat /dev/diskN

Replace /dev/diskN with the device for your drive. The MBRFormat argument is what forces an MBR partition table instead of GPT — don’t omit it.

Windows

Open Disk Management (Win+X → Disk Management).
Right-click the USB drive → Delete Volume.
Right-click the unallocated space → New Simple Volume.
Choose FAT32, allocation unit size 32 KB.
Finish the wizard.

If the drive is larger than 32 GB, the GUI won’t offer FAT32. Use the command line (format X: /FS:FAT32 on Windows 11 24H2 and later) or a tool like Rufus set to “Non bootable,” FAT32, MBR.

Linux

sudo fdisk /dev/sdX    # create an MBR (DOS) partition table, one primary FAT32 partition
sudo mkfs.vfat -F 32 /dev/sdX1

Verifying You Have MBR, Not GPT

The CMU’s Linux 3.0.35 kernel and update scanner expect an MBR partition table. Confirm before you blame the drive:

macOS: diskutil info /dev/diskN | grep "Partition Map Type" → should read MBR.
Windows: Disk Management → right-click the disk → Properties → Volumes tab shows the partition style.
Linux: fdisk -l /dev/sdX → should say Disklabel type: dos, not gpt.

Most formatting tools let you pick MBR during the format. On macOS the MBRFormat flag handles it automatically.

The 4 GB File Size Limit

FAT32 caps individual files at 4 GB (4,294,967,295 bytes). The v74.00.324A firmware package is roughly 1 GB, so a normal update is well inside the limit. The cap only matters if you’re moving large log files or multiple packages onto one drive.

Common Failures

Symptom	Likely cause	Fix
CMU never detects the drive	exFAT or NTFS filesystem	Reformat as FAT32
Update scanner ignores the `.up` file	File isn’t at the root, or the table is GPT	Put the file at the root of a FAT32/MBR drive
Files copy fine but read back corrupted	Low-quality flash controller	Use a different, known-good drive
Detection comes and goes	Poor contact or power draw, hub, or extension cable	Plug directly into the port; try a different one
Drive mounts on your PC but not the car	GPT partition table	Reformat with MBR

Known-Good Drives

These mount reliably with the CMU:

SanDisk Cruzer Blade (any capacity)
SanDisk Ultra Fit (USB 3.0, backward compatible)
Kingston DataTraveler (SE9, 100 G3)
Samsung BAR Plus

Known-Problematic Configurations

Configuration	Issue
Drives larger than 32 GB	Windows GUI refuses FAT32; use the command line or a third-party tool
USB 3.0 drives with aggressive power management	Can disconnect mid-operation during long writes
USB hubs or extension cables	The CMU often won’t see a drive behind them
Hardware-encrypted drives	The encryption partition confuses the mount process
SD cards in USB adapters	Usually work, but the adapter is one more thing that can fail

Using a Drive for a Firmware Update

Format the drive fresh — don’t reuse one with other files on it.
Copy only the .up file to the root directory.
Eject the drive properly from your computer before pulling it out.
Insert it into the CMU while the unit is powered on.
Leave it in place until the update finishes and the unit reboots on its own.

For the full update walkthrough, see /firmware/update-procedure/. If an update is interrupted or the unit won’t boot afterward, go to /firmware/recovery/.

Removing a Drive Safely

Don’t pull a drive while the CMU is actively reading or writing — mid-update is the one time a bad removal can leave the unit in a bad state. Use the “Eject USB” option in the media menu, or power the vehicle off and wait about 30 seconds before removing.

ScreenTune products ship on drives already formatted to this spec. If yours still won’t read after a clean reformat following the steps above, the drive itself is likely the problem before the CMU is — swap to a known-good one. Related: /support/usb-not-working/.