I’m... not surprised
what you’ll need to do is see if there’s a way to instruct the cable to enter DFU. I know little of the interface but there’s a pin on the connector it uses, that if the conditions are right will cause it to enter DFU. I assume that cable should be able to
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
-
Replying to @littlesteve @laobaiTD
On DVT end EVT it’s easy but on production I am not sure
1 reply 0 retweets 1 like -
Replying to @1nsane_dev @laobaiTD
I'll repeat I won't touch one, but I have reversed the mechanism they use. Pin 7 on the connector pulls device reset and asserts Force_DFU for 20ms after reset, but SecureROM requires VBUS_DETECT to allow Force_DFU and don't know how to satisfy that requirement
1 reply 2 retweets 14 likes -
Er sorry, not pin 7, pin 6
1 reply 0 retweets 3 likes -
Replying to @littlesteve @laobaiTD
crystal clear, where is VBUS_DETECT expected?
1 reply 0 retweets 2 likes -
Replying to @1nsane_dev @laobaiTD
SecureROM reads it from the VBUS_DETECT register in the phy, so I would assume, pretty strongly that on the VBUS ball on the A10X, but I'm not exactly sure which one it is because its not in the GPIO block and I can't twiddle it like I did for ForceDFU to find it
2 replies 0 retweets 5 likes
I wouldn’t be surprised if in Production devices it’s NC 
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.