From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 19 Feb 2020 08:42:31 -0500 Subject: use invd instead of wbinvd in real mode start code In-Reply-To: <20200219131431.C826B240036@gemini.denx.de> References: <20200217150929.95930240036@gemini.denx.de> <20200217160405.97C2C240036@gemini.denx.de> <7d480cee-88aa-f4e3-7e3d-8740bbdcc224@denx.de> <20200219131431.C826B240036@gemini.denx.de> Message-ID: <20200219134231.GV18302@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Feb 19, 2020 at 02:14:31PM +0100, Wolfgang Denk wrote: > Dear Heiko, > > In message <7d480cee-88aa-f4e3-7e3d-8740bbdcc224@denx.de> you wrote: > > > > > How the feed back line is organized? I mean how host system will know that > > > a) we done flash correctly? > > > b) the booted image is bad or good? > > > > For both questions the answer is, that you need to write a testcase > > which answer this question. > > > > For a) you flash the image in some way through U-Boot commands. You > > start this commands from a tbot testcase written in python and parse > > the output and/or return code of the command and than decide ... > > > > Same for b) reboot the board, check if new version is installed > > by parsing the U-Boot bootlog, than start U-Boot commands to find > > out, if current installed version is good or bad. > > Maybe it would be nice for people who don't know tbot if you could > link to some examples for such testcases? I think this should even > be covered in the tbot docs? The tbot docs should cover things like running test/py and specifying testcases so you don't have to write things like "is the board alive?" from scratch :) -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: