Hello Tom, Wolfgang,
Am 19.02.2020 um 14:42 schrieb Tom Rini:
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 :)
Yes, there is room for optimizations in docs and examples ;-)
Harald just have a first rough version, which can start nicely test/py from U-Boot ... so I hope we have this soon "online" and in the docs.
Ok, next step is to bring some examples to a online repo... I see, this would help much for starting from scratch... beside of:
http://tbot.tools/quickstart.html http://tbot.tools/quickstart.html#testcases http://tbot.tools/quickstart.html#hardware-interaction
or
http://tbot.tools/configuration.html
But hey, tbot is open source, feel free to help.
bye, Heiko