automated hardware testing

automated hardware testing

[Robert Berger]

Hi,

I just noticed this [1] and there are rumors that in the next release
hardware testing will also work with yocto-autobuilder.

I do have a couple of boards deployer in my lab and build with
autobuilder images for them.

The consoles of my boards are connected via conservers to ethernet and I
can also remotely switch on/off power.

For the beagle bone white the setup is more complex in order to press
the reset button remotely and turn on/off the power over the USB cable
remotely.

My goal would be to build something with autobuilder, deploy to a board
and run some tests.

Is this feasible with my current infrastructure?
Can someone please guide me in the right directions.

Regards,

Robert

[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto-bsp/lib/oeqa/controllers/beaglebonetarget.py...I
read the system requirements label on a software package recently. It
said "requires Windows NT or better". So I installed Unix. -- from a FAQ

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

Re: automated hardware testing

[Paul Eggleton]

Hi Robert,

On Wednesday 09 July 2014 12:33:15 Robert Berger wrote:
> I just noticed this [1] and there are rumors that in the next release
> hardware testing will also work with yocto-autobuilder.
> 
> I do have a couple of boards deployer in my lab and build with
> autobuilder images for them.
> 
> The consoles of my boards are connected via conservers to ethernet and I
> can also remotely switch on/off power.
> 
> For the beagle bone white the setup is more complex in order to press
> the reset button remotely and turn on/off the power over the USB cable
> remotely.
> 
> My goal would be to build something with autobuilder, deploy to a board
> and run some tests.
> 
> Is this feasible with my current infrastructure?
> Can someone please guide me in the right directions.

Absolutely. As a starting point I'd recommend the following section of the
manual:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing

Some of the capabilities in this area were added after 1.6, i.e. they are
only in master.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: automated hardware testing

[Stoicescu, CorneliuX]

Hello Robert,

Sorry for the late reply, I missed this mail.

We do have an almost fully automated way of doing what you need. First of all, how do you want to run the automated tests? From the autobuilder as a build step OR from another machine (this will imply publishing the images on a http server).

To give you more info to chew on, what you have to do is http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing . The TEST_TARGET would have to be set to BeagleBoneTarget and other fields like TEST_SERIALCONTROL_CMD will also have to be set.

Regards,
Corneliu

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Robert Berger
> Sent: Wednesday, July 09, 2014 12:33 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] automated hardware testing
> 
> Hi,
> 
> I just noticed this [1] and there are rumors that in the next release hardware
> testing will also work with yocto-autobuilder.
> 
> I do have a couple of boards deployer in my lab and build with autobuilder
> images for them.
> 
> The consoles of my boards are connected via conservers to ethernet and I
> can also remotely switch on/off power.
> 
> For the beagle bone white the setup is more complex in order to press the
> reset button remotely and turn on/off the power over the USB cable
> remotely.
> 
> My goal would be to build something with autobuilder, deploy to a board and
> run some tests.
> 
> Is this feasible with my current infrastructure?
> Can someone please guide me in the right directions.
> 
> Regards,
> 
> Robert
> 
> [1]
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto-
> bsp/lib/oeqa/controllers/beaglebonetarget.py...I
> read the system requirements label on a software package recently. It said
> "requires Windows NT or better". So I installed Unix. -- from a FAQ
> 
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
> 
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: automated hardware testing

[gmane]

Hi,

On 2014-07-14 05:46, Paul Eggleton wrote:
> 
> Absolutely. As a starting point I'd recommend the following section of 
> the
> manual:
> 
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing

Thanks!

> 
> Some of the capabilities in this area were added after 1.6, i.e. they 
> are
> only in master.

I use a pretty recent yocto-autobuilder, but I guess I will need to 
update poky as well. Right?

> 
> Cheers,
> Paul

Regards,

Robert

Re: automated hardware testing

[gmane]

Hi,

On 2014-07-21 08:35, Stoicescu, CorneliuX wrote:
> Hello Robert,
> 
> Sorry for the late reply, I missed this mail.
> 
> We do have an almost fully automated way of doing what you need. First
> of all, how do you want to run the automated tests? From the
> autobuilder as a build step OR from another machine (this will imply
> publishing the images on a http server).

It's fine from the autobuilder as a build step.

> 
> To give you more info to chew on, what you have to do is
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing
> . The TEST_TARGET would have to be set to BeagleBoneTarget and other
> fields like TEST_SERIALCONTROL_CMD will also have to be set.

OK, Thanks!

I will be out of the office for the next couple of weeks which will give 
me time to read the "mega manual". What else would someone do on the 
beach;)

I'll certainly keep you updated about how things will go with 
autobuilder/auto hardware testing.

> 
> Regards,
> Corneliu
> 

Re: automated hardware testing

[Paul Eggleton]

On Sunday 03 August 2014 11:41:50 gmane@reliableembeddedsystems.com wrote:
> On 2014-07-14 05:46, Paul Eggleton wrote:
> > Some of the capabilities in this area were added after 1.6, i.e. they
> > are only in master.
> 
> I use a pretty recent yocto-autobuilder, but I guess I will need to
> update poky as well. Right?

That is correct, yes. In fact this functionality is implemented within the 
build system rather than the autobuilder.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre