On Mon, Sep 07, 2020 at 07:57:12AM -0600, Simon Glass wrote: > Hi Andy, > > On Mon, 7 Sep 2020 at 02:04, Andy Shevchenko <andy.shevche...@gmail.com> > wrote: > > > > On Sat, Sep 5, 2020 at 6:23 AM Simon Glass <s...@chromium.org> wrote: > > > On Fri, 4 Sep 2020 at 03:46, Andy Shevchenko > > > <andriy.shevche...@linux.intel.com> wrote: > > > > On Thu, Sep 03, 2020 at 07:28:51PM -0600, Simon Glass wrote: > > > > > I do have a question though. How does the board decide whether to wait > > > for the xFSTK tool to connect? Sometimes when I reset it it, it does. > > > Sometimes it goes straight into receiving application. I am not > > > pressing any button other than reset. Once it makes it mind up, it > > > seems to stick to it until the power is removed? But it is powered by > > > USB too, so removing power is not so easy. > > > > It's a good question. I don't know the answer unfortunately. I think > > the parties that are involved here are PMIC and thus its firmware (I > > don't have access to it and even if ask will not get), DnX protocol, > > USB implementation on IFWI level (no access to me either). And I truly > > believe there are bugs in all of them, though I dunno if they are > > related to the above behaviour. > > Btw, pressing the reset button helps? > > Pressing reset either boots quickly or waits 10 seconds for xFSTK to > connect. It's like cracking a code and I haven't cracked it yet. I'll > have another go at some point, and maybe finally get this board into > my lab.
On a tangent, when it comes to lab stuff I picked up https://www.yepkit.com/products/ykush a while back precisely for "device can be USB powered on purpose/accident" in order to have software-controlled USB ports I can bring up/down. -- Tom
signature.asc
Description: PGP signature