The another thing I have noticed: ii lava-dispatcher 2018.2.post2-1+stretch amd64 Linaro Automated Validation Architecture dispatcher ii lava-server 2018.2-1+stretch all Linaro Automated Validation Architecture server

lava-dispatcher is an amd64 architecture. And I am running BBB01 (which is, after all, armv7)? Or, maybe, this is just a host architecture shown VM is running on?

Thank you, Zoran _______

On Tue, Mar 6, 2018 at 10:09 AM, Zoran S zoran.stojsavljevic.de@gmail.com wrote:

I finally tracked down what is going on here:

Here is the point of the problem while running test script:

Press SPACE to abort autoboot in 10 seconds

end: 2.4.2 bootloader-interrupt (duration 00:00:02) [common] start: 2.4.3 bootloader-commands (timeout 00:01:58) [common] bootloader-commands: Wait for prompt ['=>'] (timeout 00:01:58)

Script does detect "Press SPACE to abort autoboot in 10 seconds", and issues a " ". Then it does NOT detect: Wait for prompt ['=>'].

I replaced old prompt ['U-Boot'] with ['=>'], but neither way it detects U-Boot prompt.

Anyway, I do not understand the jinja2 command: {% set bootloader_prompt = bootloader_prompt|default('U-Boot') %} ???

Hasn't => been always U-Boot prompt?

Thank you, Zoran _______

On Fri, Mar 2, 2018 at 11:44 AM, magnus@minimum.se wrote:

...

I believe your issue is that LAVA doesn't detect your U-boot prompt correctly and does not try to issue any commands. Meanwhile, your kernel is autobooting and at line 541 of your pastebin, LAVA gives up waiting for a U-boot prompt.

You may need to tweak your u-boot prompt settings and/or uboot interrupt sequence. I am not sure if LAVA is doing substring matching of the interrupt-prompt, so "Press SPACE to abort autoboot" _may_ not match a line that reads "Press SPACE to abort autoboot 10 seconds". But I'll leave that to the LAVA devs to answer.

BTW, you should avoid making copies of base-uboot.jinja2. Instead you can override these things from your device type config, for example to override the interrupt-string you can do:

{% set interrupt_prompt = 'Press SPACE to abort autoboot 10 seconds' %}

and it will override the default value specified in base-uboot.jinja2. Same goes for your TFTP commands,

{% set uboot_tftp_bootcmd = '- your list of uboot commands here as a yaml-list' %}

On Fri, Mar 2, 2018 at 10:58, Zoran S zoran.stojsavljevic.de@gmail.com wrote:

Some additional data to the use case from the initial email. I have changed /etc/lava-server/dispatcher-config/device-types/base-uboot.jinja2 (changed u-boot massge before prompt, since I am using U-Boot 2017.12, and also hard-coded SERVER_IP since I have two networks inside VM - one public - 10.0.2.0/24, second private - 192.168.15.0/24).

https://pastebin.com/T8Q7bhWj

Zoran _______

On Thu, Mar 1, 2018 at 4:56 PM, Zoran S zoran.stojsavljevic.de@gmail.com wrote:

Hello,

I have very interesting problem: I would like to do Lava testing of BBB01, but I am not suceeding.

Simple and plain, my U-Boot scripts gets somehow rejected, they are not executed.

I do download correctly, I have all the correct ingredients in place, but the U-Boot scripts are not activated, at the time of U-boot prompt.

Here is my output, from the testing: https://pastebin.com/hTQQSLU1

Rather, the thing gets executed from SDCard (from /boot on rootfs).

I have no idea why this is not executed.

Help appreciated!

Thank you, Zoran

---

Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users