Hi Milosz,
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: 25 June 2020 10:49 To: Stephen Lawrence stephen.lawrence@renesas.com Cc: lava-users@lists.lavasoftware.org; gandersson@genivi.org Subject: Re: [Lava-users] fastboot in docker support
Stephen,
I think what you want already works (sort of)
Thank you for your very quick reply and in particular taking the time to actually try out the solution and your follow ups :) The sequencing of the sections and the u-boot control example were educational.
I'm now taking some vacation till the end of the week, but based on a initial look I just wanted to ask a couple of questions to check I have it right for when I try this out Monday.
Looking at your job you would get: 1. deploy: flash boot loader 2. boot: board into fastboot in u-boot 3. interactive test: to perform bespoke fastboot cmds 4. deploy: flash rest of android images (as normal) 5. test: as normal
So as long as the fastboot cmds in the interactive test section in step 3 do not require specific sequencing with the images being flashed in step 4, e.g that you must send 'oem format' after boot.img, but before vbmeta.img it should work. Do I have that right?
I think with your example I could also sequence a job definition that called the script to flash the board from a test section. The only issue there is getting the images into the container in an automated way.
Thanks again. I look forward to trying it out.
Cheers
Steve