I came up with another solution which I did try manually and it works. I need to check if this can be done via LAVA (and here I need your experience).
This is the worflow:
On the LAVA worker:
1) Download the wic.gz image
2) Uncompress the image
3) Split the image in chunks of 800M (anyway less than 1GB
4) Start tftp server serving those chunks of data
On the RPI3:
1) boot at uboot and initialise network
2) tftp the first chunk
3) write the chunk to mmc
4) tftp the second chunk
5) write the chunk to mmc
…
x) reboot the board
Few things to note:
* our image has u-boot in it
Now I have few questions:
* Can such workflow be implemented in LAVA?
This looks possible yes.
Where is uboot stored? On the mmc or on another media?
Because you should avoid touching the default uboot.
* How can I achieve the multiple calls of tftp on the RPI3 in order to be dynamic (e.g.: image size changes)?
You will have to add some code in LAVA in order to send the right commands. So LAVA will know the addresses and can send the right strings.