Hi Dean,
Sorry for the delay. I have reviewed your issue and have a few suggestions.
You have defined the following in your device-type configuration:
simulator_dtb = fvp-base-gicv2-psci.dtb
simulator_bl1 = bl1.bin
simulator_bl2 = BL2_AP_Trusted_RAM.bin
simulator_bl3 = BL31_AP_Trusted_RAM.bin
simulator_uefi = uefi_fvp-base.bin
LAVA uses these values to rename the various bits of firmware it
locates from the list defined below. This is not intuitive at all, but
our teams at Linaro use different firmware names in their images, so
LAVA has to enforce a common naming structure so that it can configure
the platform boot. You don't have this issue because you are
overriding the firmware bits in the JSON.
You should also define the lists of files that LAVA needs to search
the image for, assuming these exist in the image. If they do not, you
can just copy and base them from one of the existing FVP
configurations as these will be present in our Linaro images.
simulator_bl1_files =
bl1.bin
simulator_bl2_files =
BL2_AP_Trusted_RAM.bin
simulator_bl31_files =
BL31_AP_Trusted_RAM.bin
simulator_uefi_files =
uefi_fvp-base.bin
With these defined, it should break the UEFI boot loader prompt and
run your custom boot commands. Please let me know if you still have
issues.
Cheers,
On 1 September 2014 03:36, Dean Arnold <dean.arn...@arm.com> wrote:
> Hi All,
>
> I was wondering if you could help me please?
>
> I have been trying to add a new fastmodel variation to LAVA but I am seeing
> issues when attempting to interrupt the boot prompt. LAVA seems to be
> expecting to see the "linaro-test" prompt rather than "The default boot
> selection will start in" which is what I have set for the
> interrupt_boot_prompt variable. As a result of this UEFI attempts to boot
> the default selection and my jobs fail, as the defaults aren't valid.
>
> I suspect I have misconfigured my new device, so I just wanted to check that,
> other than setting the interrupt_boot_prompt variable to something sensible
> in my device config, is there anything else I need to set to force LAVA to
> interrupt the boot prompt?
>
> I have attached the log from my job along with my config files in case I have
> done something wrong when adding the device.
>
> Thanks for your time
> Dean
>
>
>
> -- 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 mailing list
> linaro-validation@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-validation
>
--
Tyler Baker
Tech Lead, LAVA
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
