On 9 February 2018 at 09:00, Zoran S <zoran.stojsavljevic.de@gmail.com> wrote:

Hello to the Lava users,

I am the new Lava user. My aim is to use Lava (for now V1)

Welcome. Please take care with terminology. V1 is already dead, please don't start there. We will be unable to help you with your V1 setup. Your later comments refer to elements from V2, so please take care with which bits of documentation you are following.

What version of LAVA are you running? On Debian Jessie or Debian Stretch?

setup for my testing, from the beginning just to hook-up my Beagle Bone Black (BBB) to Lava worker, and from Lava apache to set the proper context for testing BBB HW.

As I am reading Lava framework, I got the following impression about the test suite:
[1] I need to prepare BBB's U-Boot for the Lava U-Boot jinja2 setup;

Jinja is V2 - so things are already getting confused. You can use the U-Boot that comes with the BBB but you will need to account for any changes in prompts etc. in the device configuration.

[2] I need to hook-up my EG-PMS2-LAN (energenie) to the Lava (to PO and POFF HW platform);

That looks like you have to manage the power control using a graphical interface and that's not going to work. You'll need to investigate how to control that unit using the command line only. Does it have a telnet API or other serial API? That will all be down to you to configure. You might want to look at using an APC PDU instead as those already have support in lavapdu (or can use SNMP if you configure the worker appropriately).

[3] I need to hook-up ser2net interface (which I already have working over TCP) to the Lava. so Lava can control it;

That goes into the device dictionary, as per the docs. Do you have the FTDI cable to attach to the BBB to get the serial connection? That will show up in /dev/serial/by-id/ and that becomes part of the ser2net configuration.

[4] I need to hook-up uImage, .dtb and ramdisk images to the Lava (which will be FTPed and set in memory for board setup and testing).

TFTP, not FTP.

That is all managed by LAVA in the test job submission. TFTP is already configured.

Question 1: Does manual have some Beagle Bone Black U-Boot default scripts, which should be provisioned to the BBB U-Boot for the correct Lava U-Boot behavior?

Typically, for the BBB, we use the mainline U-Boot that comes from Debian.

https://packages.debian.org/stretch/u-boot-omap

Question 2: How do I do [1], [2], [3] and [4], does Lava manual have some explanation as working example how to do these points?

Those are mostly specific to your local setup.

Question 3: Anything else I missed for the proper Lava test setting?

Start with QEMU, make sure that's working and get an understanding of how that works with the device dictionary, test job submission, test shell definitions and general LAVA UI usage.

Thank you in advance,
Zoran

_______________________________________________
Lava-users mailing list
Lava-users@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lava-users

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