mirror of
https://github.com/safijari/openpuck.git
synced 2026-11-03 22:30:22 +00:00
[GH-ISSUE #90] "A transfer error has occurred" when attempting to reboot to serial DFU #38
Labels
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
safijari/openpuck#38
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joshbirnholz on GitHub (Jun 27, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/90
I've been having the issue with disconnects in steam controller mode (#72) and I want to try out this firmware . This would be my first time installing new firmware on my board since I got it and initially flashed the OpenPuck firmware.
When clicking Reboot to Serial DFU on the web config page, the device disconnects, but still reconnects as a steam puck, so I can't install new firmware. The same happens when clicking Reboot to UF2 Bootloader, and even when trying to factory erase. In the factor erase case, the settings and pairings are erased, but the device still connects as a steam puck.
I see these read and write errors in the log.
@safijari commented on GitHub (Jun 27, 2026):
Can you get into DFU by shorting the RST and GND pins twice in quick succession?
@joshbirnholz commented on GitHub (Jun 27, 2026):
Yes, that worked. Figured this should be reported however since those options were not working
@safijari commented on GitHub (Jul 3, 2026):
I can't repro unfortunately. What board are you using?
@joshbirnholz commented on GitHub (Jul 3, 2026):
I was using an AITRIP board but I bought another brand (https://www.aliexpress.us/item/3256807018711621.html) as well that was also having the issue. I tried everything again using https://safijari.github.io/openpuck/ and the latest commit from main and I'm no longer having the issue on either board.
@safijari commented on GitHub (Jul 4, 2026):
Ok. Gonna close then. Thank you.