Re: [Lava-users] U-Boot command sequence ignores prompt waiting

On Thu, 29 Nov 2018 at 14:42, Andrejs Cainikovs Andrejs.Cainikovs@netmodule.com wrote:

Hi everyone,

I’m facing an issue when U-Boot commands are sent one after another without waiting for a prompt. Obviously, device is not able to boot.

Excerpt from logs:

(Much better to attach the complete log as downloaded from the menu on the job detail page, it includes timestamps and other useful content.) I'm afraid the content you've pasted into your original doesn't help. Please attach the complete test job log file, don't paste it into the body of the email where it will be mangled.

What version of lava-server and lava-dispatcher are you running?

One thing would be to obtain a U-Boot device which is already available on staging.validation.linaro.org or another instance and known to be working, then borrow the config from that. If you have something like that available already, it'll make things easier.

As you see, all commands that were sent between `dhcp` command and until it was able to complete or fail are simply dropped.

Device type config:

{% extends 'base-uboot.jinja2' %}

{% set device_type = "vcu" %}

This line isn't required and a couple of other lines are the defaults.

{% set console_device = 'ttyS2' %}

{% set baud_rate = 115200 %}

{% set interrupt_prompt = 'Press s to abort autoboot' %}

{% set interrupt_char = 's' %}

{% set bootloader_prompt = '=>' %}

{% set uboot_mkimage_arch = 'arm' %}

{% set bootz_kernel_addr = '0x80000000' %}

{% set bootz_ramdisk_addr = '0x83000000' %}

{% set bootz_dtb_addr = '0x82000000' %}

{% set extra_kernel_args = 'ti_cpsw.rx_packet_max=1526' %}

{% set kernel_start_message = 'Welcome to' %}

Device config:

{% extends 'vcu.jinja2' %}

{% set connection_command = 'telnet lava-disp-1.local 7000' %}

{% set power_on_command = 'relay-ctrl --relay 1 --state on' %}

{% set power_off_command = 'relay-ctrl --relay 1 --state off' %}

{% set hard_reset_command = 'relay-ctrl --relay 1 --toggle' %}

Boot action block from job definition:

• boot:

  timeout:

  minutes: 5
  
  

  method: u-boot

  commands: ramdisk

  auto_login:

  login_prompt: 'am335x-nmhw21 login: '
  
  username: root
  
  

  prompts:

  • 'fct@am335x-nmhw21:~# '

Have I misconfigured something? What I’m missing? Thanks!