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...
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi Basil,
I'm not ignoring you on this issue, I just don't have a clue how to go about doing that. Someone in the LAVA team might be able to help, but we're all very busy this week :-O
Regards, Ryan.
On 28 October 2013 14:38, Basil Eljuse Basil.Eljuse@arm.com wrote:
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…
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi,
On Mon, Oct 28, 2013 at 7:38 AM, Basil Eljuse Basil.Eljuse@arm.com wrote:
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?
If you have a DEB package with your kernel, you can use the command line tool "linaro-hwpack-replace" to replace a package contained in a hardware pack. It is part of "linaro-image-tools":
https://launchpad.net/linaro-image-tools
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’?
You should be able to call "linaro-hwpack-replace" by adding instructions in the YAML file, as long as it is installed and available in the PATH. Hope it might help.
Putting Tyler / Fathi / Ryan in the cc so they get removed from the subsequent threads.
Hi Milo,
Leaving Tyler / Fathi / Ryan in bcc so they gets removed in future threads.
Thanks for the pointer.
Yes, I tried the Linaro-hwpack-replace with a Ubuntu 13.07 vexpress-lsk hwpack where I replaced linux-image-*.deb and linux-headers-*.deb
I could see that the newly booted image provides the updated kernel version when invoked with uname -a.
So we now need to figure out generating these deb packages from our local kernel builds. If you could point to some existing jobs from your end it would be helpful for us to replicate. (??)
Thanks Basil Eljuse...
-----Original Message----- From: Milo Casagrande [mailto:milo.casagrande@linaro.org] Sent: 29 October 2013 18:39 To: Basil Eljuse Cc: Tyler Baker; Fathi Boudra; ryan.harkin@linaro.org; Linaro Validation; Dean Arnold Subject: Re: [Linaro-validation] 64-bit model LAVA support - How To replace hw-pack contents for testing?
Hi,
On Mon, Oct 28, 2013 at 7:38 AM, Basil Eljuse Basil.Eljuse@arm.com wrote:
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?
If you have a DEB package with your kernel, you can use the command line tool "linaro-hwpack-replace" to replace a package contained in a hardware pack. It is part of "linaro-image-tools":
https://launchpad.net/linaro-image-tools
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’?
You should be able to call "linaro-hwpack-replace" by adding instructions in the YAML file, as long as it is installed and available in the PATH. Hope it might help.
-- Milo Casagrande | Automation Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi,
On 30 October 2013 17:26, Basil Eljuse Basil.Eljuse@arm.com wrote:
Putting Tyler / Fathi / Ryan in the cc so they get removed from the subsequent threads.
Hi Milo,
Leaving Tyler / Fathi / Ryan in bcc so they gets removed in future threads.
Thanks for the pointer.
Yes, I tried the Linaro-hwpack-replace with a Ubuntu 13.07 vexpress-lsk hwpack where I replaced linux-image-*.deb and linux-headers-*.deb
I could see that the newly booted image provides the updated kernel version when invoked with uname -a.
So we now need to figure out generating these deb packages from our local kernel builds. If you could point to some existing jobs from your end it would be helpful for us to replicate. (??)
you can use builddeb (as part of the kernel source) or we have a wrapper in our tools: bzr branch lp:linaro-ci lci-build-tools bash lci-build-tools/jenkins_kernel_build_inst
You'll have to set a few env var to match your expectation. Here's a real world example: export use_config_fragment=1 export MAKE_DTBS=true export toolchain_url="http://releases.linaro.org/13.09/components/toolchain/binaries/gcc-linaro-ar..." export hwpack_type="vexpress" export kernel_flavour="vexpress" export conf_filenames="linaro/configs/linaro-base.conf linaro/configs/distribution.conf linaro/configs/kvm-guest.conf linaro/configs/big-LITTLE-IKS.conf linaro/configs/vexpress.conf"
Thanks Basil Eljuse...
-----Original Message----- From: Milo Casagrande [mailto:milo.casagrande@linaro.org] Sent: 29 October 2013 18:39 To: Basil Eljuse Cc: Tyler Baker; Fathi Boudra; ryan.harkin@linaro.org; Linaro Validation; Dean Arnold Subject: Re: [Linaro-validation] 64-bit model LAVA support - How To replace hw-pack contents for testing?
Hi,
On Mon, Oct 28, 2013 at 7:38 AM, Basil Eljuse Basil.Eljuse@arm.com wrote:
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 frlom 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?
If you have a DEB package with your kernel, you can use the command line tool "linaro-hwpack-replace" to replace a package contained in a hardware pack. It is part of "linaro-image-tools":
https://launchpad.net/linaro-image-tools
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’?
You should be able to call "linaro-hwpack-replace" by adding instructions in the YAML file, as long as it is installed and available in the PATH. Hope it might help.
-- Milo Casagrande | Automation Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
linaro-validation@lists.linaro.org
-
Basil Eljuse -
Fathi Boudra -
Milo Casagrande -
Ryan Harkin