Hi Tyler / Fathi / Ryan,

 

Hope one of you would be able to help us out with this question.

 

Dean has got a local LAVA instance setup at our end for the 64-bit Base model testing based on the deployment from your end.  On our live setup we had an issue w.r.t database upgrade which Dean has addressed in a separate thread. It would be good if we could get help in resolving that issue.

 

We have got now demonstrated LAVA runs on AEMv8 , Cortex_Base_Model4x4 and Cortex_Base_Model1x1 following Linaro instructions.

 

One of the key usecases we have is for the ability to swap out the kernel or the firmware binaries from previously released hardware pack, and test the release candidate binaries using LAVA setup.

 

Q:: Can you advice how best to go about within LAVA setup to swap out the contents of the hardware pack for testing?

 

When we did the OOB testing we could see that the hardware pack contents get eventually unpacked to a ‘fastmodel’ folder.

 

In LAVA I can see some logs referring to

 

`/tmp/tmpilF6yY/rootfs/boot/Image-3.12.0-1-linaro-vexpress64' -> `/tmp/tmpilF6yY/boot-disc/Image-3.12.0-1-linaro-vexpress64'

 `/tmp/tmpilF6yY/boot-disc/fvp/BL2_AP_Trusted_RAM.bin' -> `/srv/lava/instances/fastmodel-trial/var/www/lava-server/images/tmpb9uqba/BL2_AP_Trusted_RAM.bin'

 `/tmp/tmpilF6yY/boot-disc/fvp/BL2_AP_Trusted_RAM.bin' -> `/tmp/tmpilF6yY/boot-disc/BL2_AP_Trusted_RAM.bin'

 `/tmp/tmpilF6yY/boot-disc/fvp/BL31_AP_Trusted_RAM.bin' -> `/srv/lava/instances/fastmodel-trial/var/www/lava-server/images/tmpb9uqba/BL31_AP_Trusted_RAM.bin'

 `/tmp/tmpilF6yY/boot-disc/fvp/BL31_AP_Trusted_RAM.bin' -> `/tmp/tmpilF6yY/boot-disc/BL31_AP_Trusted_RAM.bin'

 

Can you help us decipher these?

 

Is there an option where somehow I can specify via test definition, a location for the binaries which have to be replaced in the hw-pack ‘unpacked location’?

 

Please let us know a suggested way forward in this case?

 

Thanks

Basil Eljuse…