We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug TS-101 enters bootloop after 3 seconds (PD-Debug mode 6) with connected tip. Without tip, TS-101 boot regularly.
To Reproduce
Expected behavior Boot without reboot loop
Details of your device:
Additional context
PD Debug State 3 -> PD Debug State 3 No VBUS -> PD Debug State 6 -> Boot loop
Functional with V2.22E.C308FE8C
The text was updated successfully, but these errors were encountered:
Eugh; I dont see this here on my PD supplies. Do you have any means of capturing the PD traffic?
Sorry, something went wrong.
Sorry, i have no idea how to capturing PD traffic.
I'll test prebuilds, if you have an idea.
same with Baseus CCGAN2P-L01. On charger w/o PD ts101 boots normally
Baseus CCGAN2P-L01
sorry for my english
I'm seeing something similar using a ugreen power brick (brick does 130W max).
With the default firmware, everything works, but ironOS reboots after about 3 seconds on.
I've captured the PD negotiation (I think, assuming my dodgy cable assy is working).
Side-by-side logs of the PD negotiation are here: https://docs.google.com/spreadsheets/d/1SvuCWFnzG3vurIfFmuho2cohFiriwjAlfsj0Mu-qEQo/edit?usp=sharing
'Combined' sheet, the iron os starts column J.
Iron is the TS-101 flashed with 2.23rc1.
Ralim
No branches or pull requests
Describe the bug
TS-101 enters bootloop after 3 seconds (PD-Debug mode 6) with connected tip. Without tip, TS-101 boot regularly.
To Reproduce
Expected behavior
Boot without reboot loop
Details of your device:
Additional context
PD Debug State 3
->
PD Debug State 3 No VBUS
->
PD Debug State 6
->
Boot loop
Functional with V2.22E.C308FE8C
The text was updated successfully, but these errors were encountered: