|
|
Hello Besavior / Beloader Team,
I am reporting a reproducible firmware-level compatibility issue between the P5 General and the Titan Two when used on PlayStation 5. The issue manifests as extreme CPU load and polling instability on the Titan Two and appears to be caused by USB authentication and host scheduling behavior under PS5 security pressure.
Important clarification:
The P5 General cannot be connected directly to a PlayStation 5 and is explicitly designed to be used through adapters (Titan Two, XIM Matrix, etc.). This configuration is therefore intended and valid, not a misuse case.
Test configuration
- Titan Two firmware: 1.12.3.1
- Input-A: DualShock 4
- Input-B: P5 General (USB-B)
- Output: PlayStation 5
- PROG port connected to PC for monitoring via Gtuner IV
Observed behavior:
- With the Titan Two not connected to the PS5, CPU load remains stable at ~1–2%
- When the Titan Two is connected to the PS5 with the P5 General attached, CPU load rapidly increases and can reach ~250%
This results in:
- Polling instability (1000 Hz no longer maintained)
- Script execution delays
- Overall device slowdown
Removing only the P5 General from Input-B immediately restores CPU load to ~2% and normal operation
Key observations:
The issue does not occur when:
- The Titan Two is connected only to a PC
- The P5 General is not connected
This isolates the problem specifically to PS5 mode with a licensed authentication device present
Similar polling and stability issues have been reported on other adapters (e.g. XIM Matrix) when used with P5-style authentication devices
YouTube video: https://youtu.be/Vfu4NW0q3OI
Technical conclusion
The observed behavior is consistent with a USB authentication retry loop / interrupt storm occurring when the PS5 performs security validation through the adapter. Under these conditions, the Titan Two firmware appears to:
- Aggressively retry PS5 authentication without adequate backoff
- Allow excessive HID polling escalation initiated by the PS5
- Lack rate limiting or debounce in USB host callbacks
- Fail to yield or coalesce interrupts during authentication retries
Once triggered, the USB host task monopolizes CPU time, preventing the scheduler from idling and causing reported CPU load values to exceed 100%, resulting in degraded polling stability and script performance.
This strongly indicates a firmware-level USB host and authentication handling issue on the adapter side, not a hardware fault of the P5 General and not a configuration or scripting problem.
Request
Could you please coordinate with ConsoleTuner to:
- Investigate PS5 authentication handling when a licensed authentication device (P5 General) is connected
- Implement authentication retry backoff and rate limiting
- Improve USB host task scheduling and interrupt handling in PS5 mode
- Release a Titan Two firmware update that stabilizes CPU load and polling behavior when using the P5 General
Since the P5 General is designed specifically for adapter-based PS5 authentication, reliable interoperability is essential.
I am available to provide further test data or assist with reproduction if needed.
Kind regards,
|
|