Skip to content

v1.4.1 - Pico firmware that stays awake on the PS3

Latest

Choose a tag to compare

@Gabarsolon Gabarsolon released this 07 Nov 23:32
· 1 commit to main since this release

🚀 Buzz! Bridge v1.4.1: Pico firmware that stays awake on the PS3

✨ What's new

  • Pico firmware 1.4.1 (buzz_bridge_modec2.uf2): on a real PS3, the console disabled the Pico's DualShock pad about 14 minutes into a session (the saved request log shows the PS3's disable command), and the pad then stayed dead until the Pico was reflashed. This firmware adds two changes:
    • small, bounded noise on the DualShock's motion-sensor bytes, like a real pad (jitter on|off over the debug port, on by default);
    • up to three delayed automatic PS-button presses after a PS3 disable, so a disable cannot leave the pad dead until a reboot.
  • Buttons, sticks, pressures, the buzzer-bit decoding and Modes A and B are unchanged. The PS2 patcher (buzz-bridge-ps2.exe, layout 14) is the same as in v1.4.0.

📦 Download Assets

File What
buzz-bridge-pico-v1.4.1.zip the pico/ folder: firmware (UF2), source, PC helpers, docs, README with wiring and steps
buzz_bridge_modec2.uf2 the Pico firmware (drag onto the RP2350 drive in BOOTSEL)
buzz_bridge_modec2_recovery.uf2 recovery image that forces the debug COM port on
buzz-bridge-ps2.exe the PC ISO patcher with layout 14 (unchanged from v1.4.0)
SHA256SUMS.txt checksums

To update: hold BOOTSEL, plug the Pico into the PC, copy buzz_bridge_modec2.uf2 onto the RP2350 drive. The saved mode (config c 0) is kept.

✅ Tested

Native tests of the new code pass: jitter bounds and determinism, the PS-retry state machine, and the unchanged report bytes of Modes A and B. The v1.4.0 firmware's Mode C (four handsets and game lamps through one DualShock pad, stock netemu, CFW PS3, Buzz!: The Schools Quiz) was confirmed by the owner.

⚠️ Not tested or not supported

  • The 1.4.1 firmware itself has not been run on a PS3. Whether the jitter and the PS retries keep the pad alive over a long idle is unproven. The 14-minute disable is established by the log; its cause (an idle timeout) is a hypothesis.
  • If the pad dies again: hold P1 red + P1 blue for 5 seconds, plug the Pico into the PC and run python pico/tools/bridge_cli.py ds3log, then send the saved log.
  • HEN, other games, other dongles and the original Pico (RP2040) are untested.
  • BuzzBridge.pkg is not part of this release (see v1.4.0).