From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukasz Majewski Date: Wed, 28 Sep 2016 11:32:30 +0200 Subject: [U-Boot] U-Boot DFU test and Ctrl+C In-Reply-To: <20160927154633.GF4884@bill-the-cat> References: <20160927154633.GF4884@bill-the-cat> Message-ID: <20160928113230.308b5d6c@amdc2363> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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. > -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group