This is usually down to your board not being able to cope with the rate of characters being sent to it. The uboot default is to dump entire strings to the board. Try adding {% set boot_character_delay = 300 %} to your device-type dict
On 30 October 2017 at 09:39, Dragos Iorgulescu Dragos.Iorgulescu@enea.com wrote:
Hi all!
We have been working on integrating a cn8304-based board (uses uboot). We noticed some strange behavior that might be related to LAVA2.
On average, 2 out of 3 job runs end up with errors/timeouts. We use the same job definition and device each and every time. Looking through LAVA logs, it seems that commands and some output gets truncated, thus malforming the commands being sent or the prompts that LAVA expects.
The prompt we expect is "EBB8304> ", but sometimes it gets truncated to "304>". Also, a command gets mixed up somehow, and instead of "setenv loadinitrd 'tftpboot 0x60000000 358/tftp-deploy-VLCRzw/ramdisk/ramdisk.ext4.gz.uboot'", the board receives "EBB8304> setenv loadkernel 'tftpboot 0x40setenv loadinitrd 'tftpboot 0x60000000 358/tftp-deploy-VLCRzw/ramdisk/ramdisk.ext4.gz.uboot'"
Details:
The job definition: https://paste.debian.net/993349/ An excerpt from the LAVA2 job log/output, showing what gets mixed up: https://paste.debian.net/993350/ The plain job log is attached to this e-mail
Many thanks in advance!
/Dragoş
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users