public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot DFU test and Ctrl+C
Date: Fri, 30 Sep 2016 21:56:03 -0400	[thread overview]
Message-ID: <20161001015603.GG4884@bill-the-cat> (raw)
In-Reply-To: <539db4b1-b324-a4d9-1330-1483e2b980c7@wwwdotorg.org>

On Wed, Sep 28, 2016 at 11:49:52AM -0600, Stephen Warren wrote:
> On 09/28/2016 03:32 AM, Lukasz Majewski wrote:
> >Hi Tom,
> >
> >>Hey guys,
> >>
> >>As I use the DFU tests more and more, I keep hitting what I'm pretty
> >>sure is a false failure in the tests.  Sometimes the tests fail at:
> >>>      u_boot_console.wait_for('Ctrl+C to exit ...')
> >>
> >>and the last bit of the console log is:
> >>Starting download:
> >>[#################################################################]
> >>finished! unable to read DFU status #File System is consistent
> >>file found, deleting
> >>update journal finished
> >>File System is consistent
> >>update journal finished
> >>65 bytes written in 12380 ms (0 Bytes/s)
> >>=>
> >>
> >>So perhaps we should make the test look for the prompt itself rather
> >>than 'Ctrl+C' ?  Thanks!
> >
> >As fair as I remember, dfu-util provides and u-boot's dfu supports -e
> >switch behavior. This switch causes the dfu u-boot command to go
> >directly to u-boot prompt.
> >
> >Tom, I suppose that this is what you would need.
> >Just add -e to your host's dfu-util command.
> 
> Using -e is the opposite of what Tom wants. The test/py script
> expects the dfu command to continue running after an
> upload/download, since that's the default behaviour.

Right.  It sounds like DWC3 might have an intermittent issue I need to
find some time to try and debug, or talk someone else into debugging :)

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160930/1d97aa9d/attachment.sig>

      reply	other threads:[~2016-10-01  1:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160927154639eucas1p2a18ee8e6dbf39188e63d87ff5fd41072@eucas1p2.samsung.com>
2016-09-27 15:46 ` [U-Boot] U-Boot DFU test and Ctrl+C Tom Rini
2016-09-27 16:42   ` Stephen Warren
2016-09-28  9:32   ` Lukasz Majewski
2016-09-28 17:49     ` Stephen Warren
2016-10-01  1:56       ` Tom Rini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161001015603.GG4884@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox