Now... I have new results on all this mess. I am able to boot and correctly read U-Boot scripts from Lava-Dispatcher, but with sticks and ropes workaround?!

Since it does NOT stop after U-Boot prompt "=>" is issued (and I have correct .jinja2 settings there for all), I changed bootcmd command to display the arbitrary text, instead of booting from mmc0. Then, bootcmd executes, and ONLY after this NATIVE (from flash) U-Boot command is executed, the Lava dispatcher's U-Boot script starts running!?

And, then, the test finishes correctly (it boots from ram0, downloads all the components from the TFTP directory, as script upfront prepared, and passes the tests)?

Seems as Lava-Dispatcher is lagging one event behind... How this is possible?

Any explanation???

Thank you,

On Tue, Mar 6, 2018 at 11:55 AM, Zoran S <> wrote:
This is not the error preventing script to execute U-Boot commands. In other words, I made mistake referring to jinja2. Anyway, my prompt is =>, and I set it correctly.

The error to prevent U-Boot commands to execute is the following:

bootloader-interrupt: Wait for prompt Press SPACE to abort autoboot in 10 seconds (timeout 00:02:00)
spawn telnet localhost 8020
Trying ::1...
Connected to localhost.
Escape character is '^]'.
ser2net port 8020 device /dev/ttyUSB0 [115200 N81] (Debian GNU/Linux)
U-Boot SPL 2017.11 (Jan 08 2018 - 21:14:17)
Trying to boot from MMC1
reading u-boot.img
reading u-boot.img
U-Boot 2017.11 (Jan 08 2018 - 21:14:17 +0100)
CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Net:   cpsw, usb_ether
[space SHOULD BE placed here]
Press SPACE to abort autoboot in 10 seconds
[space is placed here]
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)
switch to partitions #0, OK
mmc0 is current device

So, in other words some timers are NOT set correctly! Since I do NOT detect the =>, which is understandable why: the command for detection came AFTER => appeared!!!

Could you, please, tell me where the timer definitions are for the test cases, so I can issue much earlier in the game first space?

Thank you,

On Tue, Mar 6, 2018 at 11:20 AM, Remi Duraffort <> wrote:
Anyway, I do not understand the jinja2 command:
{% set bootloader_prompt = bootloader_prompt|default('U-Boot') %} ???

The jinja2 documentation explains it all:

Rémi Duraffort