Skip to content

MiraLink 0.37 - Single-controller test candidate

Choose a tag to compare

View all tags
@LeParfait271 LeParfait271 released this 14 Aug 04:36
v0.37
c649780

MiraLink 0.37 — manual hardware-test candidate

This release supersedes 0.36, whose first Windows test exposed two Pico-owned DualSense children and did not establish a validated Bluetooth link.

Corrections

  • exactly one top-level Gamepad Application collection; MiraLink Feature reports 0x70/0x71 are nested below it;
  • compile-time HID topology checks prevent the duplicate Windows controller layout from returning;
  • CYW43/BTstack now runs by explicit main-loop polling instead of competing background IRQ callbacks;
  • a new Bluetooth address is trusted only after a valid DualSense input report;
  • failed new keys are removed without deleting keys that existed before the attempt;
  • stale HID-CID events are filtered and teardown retries are bounded outside BTstack callbacks.

Validation before publication

  • application syntax/build and tests: 68/68 passed;
  • native core test: 1/1 passed;
  • Pico 2 W Release build: passed;
  • picotool: MiraLink 0.37, pico2_w, RP2350 ARM Secure, SDK 2.3.0;
  • UF2 SHA-256: 3FC7119F4513B2AE75CA4D57286C6C36F729C63D8C1ADF94DA3F2ABE1E5B9E30.

No board was flashed automatically. After manually copying the UF2 in BOOTSEL mode, first verify that joy.cpl shows exactly one controller before attempting pairing. Version 0.37 is not considered hardware-validated until that test, WebHID and real Bluetooth pairing succeed.

DS5Dongle v0.7.2-hotfix stays fixed at 100%. MiraLink 0.37 remains 76% raw coverage and 43% weighted proven coverage pending the physical retest (0.36 observed: 39%).

Assets 8
Loading