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
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
