The bootloader-commands step breaks into u-boot and begins to issue commands, but some commands are issued prior to receiving the prompt. I've attempted changing the boot_char_delay, but it doesn't solve the issue.
I'm getting symptoms much like the ones in this thread, except I'm sending space rather than a newline, so the fix is not relevant to me. https://lists.linaro.org/pipermail/lava-users/2018-May/001069.html
Jeremy Stashluk Embedded Software Engineer
[cid:image002.jpg@01D45B04.B75D2A40]
Geophysical Survey Systems, Inc. 40 Simon Street * Nashua, NH 03060-3075
603. 893.1109 main * 603.681.2045 direct * 603.889.3984 fax stashlukj@geophysical.commailto:stashlukj@geophysical.com * www.geophysical.comhttp://www.geophysical.com/
On Wed, 3 Oct 2018 at 15:46, Jeremy Stashluk StashlukJ@geophysical.com wrote:
The bootloader-commands step breaks into u-boot and begins to issue commands, but some commands are issued prior to receiving the prompt.
I’ve attempted changing the boot_char_delay, but it doesn’t solve the issue.
I’m getting symptoms much like the ones in this thread, except I’m sending space rather than a newline, so the fix is not relevant to me.
You've attached the job description - that's just used for unit tests. What is needed here is the test job submission - what you submit to LAVA to start the test job. That allows us to see what commands are actually being specified.
Also, compare your test job and output with https://lkft-staging.validation.linaro.org/scheduler/job/8724 which is a similar kind of test job.
We don't run U-Boot TFTP jobs on X15 - those test jobs are using fastboot which only requires sending a single command to U-Boot but does require LXC, so the jobs are more complex: https://staging.validation.linaro.org/scheduler/job/240825
To set a character delay between sending each character of each line during the boot action, add this to your device dictionary (in this example 30 milliseconds):
{% set boot_character_delay = 30 %}
Please also attach the device dictionary in the reply.
https://lists.linaro.org/pipermail/lava-users/2018-May/001069.html
Jeremy Stashluk
Embedded Software Engineer
Geophysical Survey Systems, Inc.
40 Simon Street • Nashua, NH 03060-3075
- 893.1109 main • 603.681.2045 direct • 603.889.3984 fax
stashlukj@geophysical.com • www.geophysical.com
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
I’ve attached the job submission and the jinja2 and rendered device dictionary.
I cribbed the job submission from the beaglebone-black health check.
Thank you, Jeremy
On Wed, 3 Oct 2018 at 17:54, Jeremy Stashluk StashlukJ@geophysical.com wrote:
I’ve attached the job submission and the jinja2 and rendered device dictionary.
I understand where you saw this syntax but it's pointless within the device dictionary itself, it's only useful in a device-type jinja2 file.
The value of any variable in the device dictionary should be a real value, not an expression. A default is provided to support overrides but there is on override available above the device dictionary, so this syntax just confuses things.
{% set interrupt_char = interrupt_char|default(' ') %}
Just use:
{% set interrupt_char = ' ' %}
Similarly with {% set interrupt_prompt = interrupt_prompt|default('Press SPACE to abort autoboot') %}
should just be:
{% set interrupt_prompt = 'Press SPACE to abort autoboot' %}
I cribbed the job submission from the beaglebone-black health check.
I did run some TFTP test jobs on an X15 in the early parts of the device integration but the AOSP use case was more desirable so we use that to deploy OE now. https://staging.validation.linaro.org/scheduler/job/240839/definition#deflin... https://lkft.validation.linaro.org/scheduler/job/451011/definition
I have found some updated build files and the X15 booted but didn't like the NFS: https://staging.validation.linaro.org/scheduler/job/240937#bottom VFS: Unable to mount root fs on unknown-block(2,0)
I also tried your test job files: https://staging.validation.linaro.org/scheduler/job/240938
The device ran TFTP correctly but the kernel doesn't boot.
However, there are U-Boot files available from that new build which you might want to try: http://snapshots.linaro.org/openembedded/lkft/morty/am57xx-evm/rpb/linux-mai...
Thank you,
Jeremy
The job works now that I’ve switched to the x11 poky image u-boot which takes any key.
I was just running into this issue because I was running RCN’s u-boot: https://git.lavasoftware.org/lava/lava/issues/95
Thanks for the device dictionary tips.
Now to figure out convince the poky image to flash the on board eMMC.
Thanks for all the help, Jeremy
From: Neil Williams neil.williams@linaro.org Sent: Thursday, October 4, 2018 4:21 AM To: Jeremy Stashluk StashlukJ@Geophysical.com Cc: Lava Users Mailman list lava-users@lists.linaro.org Subject: Re: [Lava-users] bootloader-commands not waiting for prompt
On Wed, 3 Oct 2018 at 17:54, Jeremy Stashluk <StashlukJ@geophysical.commailto:StashlukJ@geophysical.com> wrote: I’ve attached the job submission and the jinja2 and rendered device dictionary.
I understand where you saw this syntax but it's pointless within the device dictionary itself, it's only useful in a device-type jinja2 file.
The value of any variable in the device dictionary should be a real value, not an expression. A default is provided to support overrides but there is on override available above the device dictionary, so this syntax just confuses things.
{% set interrupt_char = interrupt_char|default(' ') %}
Just use:
{% set interrupt_char = ' ' %}
Similarly with {% set interrupt_prompt = interrupt_prompt|default('Press SPACE to abort autoboot') %}
should just be:
{% set interrupt_prompt = 'Press SPACE to abort autoboot' %}
I cribbed the job submission from the beaglebone-black health check.
I did run some TFTP test jobs on an X15 in the early parts of the device integration but the AOSP use case was more desirable so we use that to deploy OE now. https://staging.validation.linaro.org/scheduler/job/240839/definition#deflin... https://lkft.validation.linaro.org/scheduler/job/451011/definition
I have found some updated build files and the X15 booted but didn't like the NFS: https://staging.validation.linaro.org/scheduler/job/240937#bottom VFS: Unable to mount root fs on unknown-block(2,0)
I also tried your test job files: https://staging.validation.linaro.org/scheduler/job/240938
The device ran TFTP correctly but the kernel doesn't boot.
However, there are U-Boot files available from that new build which you might want to try: http://snapshots.linaro.org/openembedded/lkft/morty/am57xx-evm/rpb/linux-mai...
Thank you, Jeremy
--
Neil Williams ============= neil.williams@linaro.orgmailto:neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Glad it worked!
We'll get to bug #95 in due course, at least you've got a working configuration in the meantime.
On Thu, 4 Oct 2018 at 16:05, Jeremy Stashluk StashlukJ@geophysical.com wrote:
The job works now that I’ve switched to the x11 poky image u-boot which takes any key.
I was just running into this issue because I was running RCN’s u-boot: https://git.lavasoftware.org/lava/lava/issues/95
Thanks for the device dictionary tips.
Now to figure out convince the poky image to flash the on board eMMC.
Thanks for all the help,
Jeremy
*From:* Neil Williams neil.williams@linaro.org *Sent:* Thursday, October 4, 2018 4:21 AM *To:* Jeremy Stashluk StashlukJ@Geophysical.com *Cc:* Lava Users Mailman list lava-users@lists.linaro.org *Subject:* Re: [Lava-users] bootloader-commands not waiting for prompt
On Wed, 3 Oct 2018 at 17:54, Jeremy Stashluk StashlukJ@geophysical.com wrote:
I’ve attached the job submission and the jinja2 and rendered device dictionary.
I understand where you saw this syntax but it's pointless within the device dictionary itself, it's only useful in a device-type jinja2 file.
The value of any variable in the device dictionary should be a real value, not an expression. A default is provided to support overrides but there is on override available above the device dictionary, so this syntax just confuses things.
{% set interrupt_char = interrupt_char|default(' ') %}
Just use:
{% set interrupt_char = ' ' %}
Similarly with {% set interrupt_prompt = interrupt_prompt|default('Press SPACE to abort autoboot') %}
should just be:
{% set interrupt_prompt = 'Press SPACE to abort autoboot' %}
I cribbed the job submission from the beaglebone-black health check.
I did run some TFTP test jobs on an X15 in the early parts of the device integration but the AOSP use case was more desirable so we use that to deploy OE now.
https://staging.validation.linaro.org/scheduler/job/240839/definition#deflin...
https://lkft.validation.linaro.org/scheduler/job/451011/definition
I have found some updated build files and the X15 booted but didn't like the NFS:
https://staging.validation.linaro.org/scheduler/job/240937#bottom
VFS: Unable to mount root fs on unknown-block(2,0)
I also tried your test job files:
https://staging.validation.linaro.org/scheduler/job/240938
The device ran TFTP correctly but the kernel doesn't boot.
However, there are U-Boot files available from that new build which you might want to try:
http://snapshots.linaro.org/openembedded/lkft/morty/am57xx-evm/rpb/linux-mai...
Thank you,
Jeremy
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
-
Jeremy Stashluk -
Neil Williams