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.
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-mainline/1043/

 

 

Thank you,

Jeremy



--

Neil Williams
=============
neil.williams@linaro.org
http://www.linux.codehelp.co.uk/