adbd service isn't always available when we reach the boot prompt causing the pipeline to fail
The pipelines have an incorrect assumption of when
adbd have started on target.
Example of failing pipelines:
If I understand https://git.morello-project.org/morello/morello-ci-pipelines/-/blob/master/lava/templates/fvp-android-binder.yaml correct the tests are executed when
console:/ is printed on uart0.
However there is no connection between the shell on uart0 and state of
While there are some lines that are closer such as
init: Created socket '/dev/socket/adbd', mode 660, user 1000, group 1000 this still do not indicate with 100% that
adbd is ready.
The CI need to poll with
adb get-state or similar.
I have attached a example of uart0 output to illustrate.
Line 522 have the terminal prompt and the
adbd service is about to start at line 717.