Hi Milosz,
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: 25 June 2020 11:34 To: Stephen Lawrence stephen.lawrence@renesas.com Cc: lava-users@lists.lavasoftware.org; gandersson@genivi.org Subject: Re: [Lava-users] fastboot in docker support
[snip]
I need to correct myself once more. It actually works :) https://staging.validation.linaro.org/scheduler/job/273595
Proper deploy/boot/test sequence is:
- deploy: docker: image: miloszwasilewski/adb-fastboot timeout: minutes: 15 to: fastboot images: xloader: url: https://images.validation.linaro.org/snapshots.linaro.org/android/lkft/lkft-
aosp-master-x15/107/MLO bootloader: url: https://images.validation.linaro.org/snapshots.linaro.org/android/lkft/lkft- aosp-master-x15/107/u-boot.img os: debian
- boot: prompts:
timeout: minutes: 15 method: bootloader bootloader: u-boot commands: ['fastboot 1']
- "=>"
- test: docker: image: miloszwasilewski/adb-fastboot timeout: minutes: 30 definitions:
- from: inline name: fastboot-oem-format path: inline/fastboot.yaml repository: metadata: format: Lava-Test Test Definition 1.0 name: fastboot-oem description: fastboot oem run: steps: - fastboot oem format - fastboot erase super - fastboot erase boot
Full job definition in the link above.
I tried this largely following your own template as a first step. The major difference being I didn't fastboot flash u-boot as a first step as the correct version is already on the board.
The u-boot section worked as expected and successfully interrupted u-boot and executed fastboot.
However I hit a problem with the inline test section to run the custom fastboot commands. The docker image is never started as the WaitDeviceBoardID() check doesn't find the board and instead eventually times out: https://lava.genivi.org/scheduler/job/980#L210
That is weird as I know the device is available and indeed if I do a simple deploy to fastboot via docker image the device is found and the board flashed: https://lava.genivi.org/scheduler/job/982#L140
I took a look at the test docker.py and deploy docker.py. Although there is some difference between the code that gets to a board ID to pass in both appear to result in the same (correct) serial ID of 00025269, as the WaitDeviceBoardID debug code in udev.py reports.
Any ideas as to what could be causing the difference in behaviour?
Regards
Steve