M61 DualSense Dongle

简体中文

An open-source, single-chip DualSense-to-USB bridge for the Ai-M61-32s-Kit (BL616/BL618 family). The M61 connects to a real DualSense over Bluetooth Classic HIDP and exposes a native USB 054C:0CE6 DualSense composite device to the host PC.

DualSense -- Bluetooth Classic HIDP --> M61 -- native USB --> PC

This is an independent community project. It is not affiliated with or endorsed by Sony Interactive Entertainment. “DualSense” is a trademark of its respective owner.

New users should begin with Quick start: download the graphical flasher, enter BOOT+RESET, wire the board's dedicated USB_DP/USB_DM headers, pair the controller, and save the WebUI settings.

Current capabilities

Area	Implemented
Bluetooth	BR/EDR discovery, pairing/security, SDP, HID control/interrupt L2CAP, saved-device reconnect
USB HID	DualSense descriptors and input reports, output reports, complete Feature GET/SET proxy
Controller output	Light bar/player LEDs, mute LED, standard rumble, adaptive triggers
Audio and haptics	48 kHz/16-bit four-channel USB OUT, speaker/headset routing, HD haptics, Opus transport
Microphone	DualSense Opus decode to 48 kHz/16-bit stereo USB IN (duplicated controller mono)
Runtime controls	Persistent audio routing/buffer hint, hardware-PWM LED brightness, 320/384/400 MHz DVFS, stick deadzones, idle power-off, and 250/500 Hz USB report modes
WebUI	Versioned WebHID configuration, Flash persistence, controller management, and bounded telemetry
Diagnostics	Serial status/bring-up commands, compile-gated HPM/pipeline/runtime profiling, host validation tools

The production defaults are conservative and deterministic: 320 MHz manual CPU mode, microphone disabled, automatic speaker route, no overclock, no stick deadzone, 12% status-LED brightness, audio buffer length 48, no inactivity power-off, and realtime Bluetooth report forwarding. See Features and limitations for validation status and known constraints.

Configure these persistent settings from the M61-specific WebHID application: https://ds5.766677.xyz/. Use a Chromium-based browser over HTTPS, connect the M61, read the current configuration, then save the complete configuration to Flash. The USB report choices are realtime fresh-report forwarding and hardware-validated fixed 250 Hz or 500 Hz modes; fixed modes may repeat the latest Bluetooth sample and do not raise the controller's native sampling rate.

The supported controller target is the standard DualSense. DualSense Edge is not supported or hardware-qualified. During long wireless speaker playback, the sound can occasionally become temporarily muffled and later recover; this known limitation does not affect USB enumeration or controller input.

Using a prebuilt Release

Normal Windows users only need M61-Flasher-Windows.exe from the project Releases. Double-click it to open the graphical interface, select a firmware version from the complete verified Release list, and follow the BOOT+RESET instructions. It detects the M61 CH340 port, downloads and checks the selected complete firmware ZIP, and can download the signed official WCH driver when the connected CH340 has no usable COM port.

No repository clone, Python, Rust, SDK, or compiler is required. The community EXE is not Authenticode code-signed, so Windows SmartScreen may ask for confirmation. Download it only from this repository and verify the SHA256 published beside it. The manual three-BIN developer path remains documented in Building and flashing.

The flasher GUI supports Simplified Chinese and English, defaults from the Windows user locale, and provides an in-app language selector. For offline or custom flashing, select a downloaded M61-Firmware-<version>.zip directly; an advanced three-file directory option is also available. The log supports mouse selection and a Copy all button.

Performance-reproducible build

The default build is the measured release profile, not an SDK fallback:

• Bouffalo SDK 2.3.24 at commit d9306a4a221db414131337ec95113e3adaf7072b;
• Xuantie/T-Head GCC 10.2.0 V2.6.1 at a pinned platform commit;
• Opus 1.2.1 downloaded by SHA256 and rebuilt with the tracked 11-patch E907 optimization stack;
• m61_usb_gamepad.c at -O2, Opus at -O2 -flto, 160 KiB WRAM, 1 ms codec window, Flash-resident nibble CRC, and decode-MDCT SRAM placement;
• HPM, pipeline, task-runtime, and Opus-stage instrumentation disabled.

build_windows.ps1 and build.sh reject an unpinned SDK/toolchain by default. Every successful build emits a JSON provenance manifest beside the firmware. The complete lock is reproducible-build.lock.json.

Developer build (Windows)

Clone the three repositories at their locked commits:

git clone https://github.com/ccc007ccc/DS5Dongle.git
git clone https://github.com/bouffalolab/bl_mcu_sdk.git
git -C bl_mcu_sdk checkout d9306a4a221db414131337ec95113e3adaf7072b
git clone https://github.com/bouffalolab/toolchain_gcc_t-head_windows.git
git -C toolchain_gcc_t-head_windows checkout 072fc29d765774d66366c57a4d962e90c366ef1b

cd DS5Dongle\m61\dualsense_hidp_probe
.\build_windows.ps1 -Command All `
  -SdkPath C:\path\to\bl_mcu_sdk `
  -ToolchainBin C:\path\to\toolchain_gcc_t-head_windows\bin

The script downloads and verifies Opus automatically. Release artifacts are written to:

m61/dualsense_hidp_probe/build-win/build_out/
  m61_dualsense_hidp_probe_bl616.bin
  m61_dualsense_hidp_probe_bl616.elf
  m61_dualsense_hidp_probe_bl616.map
  m61_dualsense_hidp_probe_bl616.manifest.json

Read Building and flashing before overriding any release option. An override intentionally produces a custom manifest and is not a performance-equivalent release build.

Hardware

The Ai-M61-32s-Kit header directly exposes USB_DP, USB_DM, 5V, and GND; GPIO numbers are not needed. Its onboard Type-C connector is attached to CH340 and is used for UART flashing, logs, and power, not game-controller enumeration.

For normal use, connect only native USB so 5V, GND, USB_DP, and USB_DM provide both power and controller data. For flashing, unplug native USB and connect only Type-C/CH340. Never let both USB paths supply 5 V at the same time. See Quick start and Hardware and wiring for the diagram and safety details.

Flash and verify

Normal users run M61-Flasher-Windows.exe, select a firmware Release, and follow its on-screen instructions. Disconnect native USB while flashing and connect only Type-C/CH340. After flashing succeeds, unplug Type-C before connecting the four-wire native USB cable for normal use.

Source development and hardware diagnostics use the repository commands below:

python tools\flash_m61_firmware.py -p COM5 --windows-build
python tools\check_m61_usb_windows.py
python tools\validate_m61_usb_hardware.py -p COM5

The normal flasher default is 460800 baud. Select the board's CH340 UART (1A86:7523, typically COM5), not another transient USB serial port. Add -b 115200 only as a conservative fallback for an unstable cable or hub.

--reboot-isp is a best-effort development convenience: some BL616 boards warm-reset into BootROM but then fail its eFuse read. Holding BOOT, tapping RESET, and releasing BOOT is the reliable recovery and flashing procedure.

Documentation

• Quick start
• Features and limitations
• Architecture
• Building and flashing
• Hardware and wiring
• Protocol and audio formats
• Performance and benchmark policy
• Development and validation
• Dependencies, licensing, and redistribution

License

Project-owned source and documentation are released under the MIT License. External SDKs and Opus retain their own licenses; see Third-party notices.