Understood. I’ll add that option to the dispatcher. Should be a quick fix.

Dave

> On 16 Sep 2015, at 16:19, Kevin Hilman <khil...@linaro.org> wrote:
> 
> Thanks.
> 
> FWIW, I'd rather not pass bl1, fip or any firmware.  IMO, there should
> be an option which says "just trust the firmware on the board" for
> cases when LAVA is not the only user of the board.
> 
> Kevin
> 
> 
> On Wed, Sep 16, 2015 at 8:11 AM, Dave Pigott <dave.pig...@linaro.org> wrote:
>> Hi Kevin
>> 
>> Ok. I wasn’t thinking when I typed that. I meant “false”.
>> 
>> I know why it’s doing that, so I’ll try and figure out a way to make that 
>> work for you. I think you’ll just have to set up a path to the bl1.bin and 
>> fip.bin that you want in the config.
>> 
>> Dave
>> 
>>> On 16 Sep 2015, at 15:56, Kevin Hilman <khil...@linaro.org> wrote:
>>> 
>>> Hi Dave,
>>> 
>>> Thanks for the suggestion.
>>> 
>>> But... it doesn't work.  The first thing it does is mount the USB mass
>>> storage, 'rm -rf *' and then extract the board-recovery tarball onto
>>> the usb device, wiping out the firmware I had installed[1]
>>> 
>>> For kicks, I tried setting same flag to False, but then it fails[2]
>>> trying to download "None"  ;)
>>> 
>>> Kevin
>>> 
>>> [1] http://lava.ished.com/scheduler/job/23/log_file#bottom
>>> [2] http://lava.ished.com/scheduler/job/24/log_file#bottom
>>> 
>>> On Wed, Sep 16, 2015 at 1:04 AM, Dave Pigott <dave.pig...@linaro.org> wrote:
>>>> Hi Kevin,
>>>> 
>>>> Given I wrote that support I *should* know the answer. :)
>>>> 
>>>> I *think* if you set
>>>> 
>>>> vexpress_complete_firmware = true
>>>> 
>>>> in the device config in /etc/lava-dispatcher/devices/(your-juno-name).conf
>>>> 
>>>> it should work.
>>>> 
>>>> Let me know how you get on!
>>>> 
>>>> Dave
>>>> 
>>>>> On 16 Sep 2015, at 01:22, Kevin Hilman <khil...@linaro.org> wrote:
>>>>> 
>>>>> How to tell LAVA to not try an update the firmware my  juno-r1 board?
>>>>> 
>>>>> The default juno device type points to a tarball[1] it uses to
>>>>> update/replace the juno firmware, unfortunately, that tarball seems to
>>>>> only be configured for Juno, not the juno R1.
>>>>> 
>>>>> After and unpack/flash/reboot, the juno board fails to boot with:
>>>>> 
>>>>> ERROR: File not found \MB\HBI0262C\board.txt
>>>>> 
>>>>> Note the 'C' in the board name HBI0262C, whereas the tarball only
>>>>> contains HBI0262B.
>>>>> 
>>>>> I have flashed working firmware onto my Juno R1 and would like LAVA to
>>>>> leave it alone.  Is there a way to do that?
>>>>> 
>>>>> Kevin
>>>>> 
>>>>> 
>>>>> [1] http://images.validation.linaro.org/juno/board-recovery-image.tgz
>>>>> _______________________________________________
>>>>> linaro-validation mailing list
>>>>> linaro-validation@lists.linaro.org
>>>>> https://lists.linaro.org/mailman/listinfo/linaro-validation
>>>> 
>> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to