From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: PXP test applications
Date: Fri, 10 Apr 2015 07:47:39 -0700 [thread overview]
Message-ID: <5527E28B.8040708@boundarydevices.com> (raw)
In-Reply-To: <CA+jg_OVSHUEXcp5ZdAZxF=f4sbUr_R+BVyqgW22BrthUk6A9Yg@mail.gmail.com>
Thanks Daiane,
On 04/10/2015 05:09 AM, Daiane Angolini wrote:
> On Thu, Apr 9, 2015 at 6:13 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> Does anyone know how to run the pxp_test.out program
>> from /unit_tests?
>>
>> I can run it, but it's not clear what is supposed to happen.
>>
>> root@nitrogen6x:/unit_tests# ./pxp_test.out -H
>> Usage: ./pxp_test.out -I "<options for each instance>" -H display this help
>>
>> options for each instance
>> -o <output file> Write output to file
>> If no output is specified, default is panel
>> -r <rotation angle>
>> -h <horizontal flip>
>> -v <vertical flip>
>> -l <left position for display>
>> -t <top position for display>
>> -i <pixel inversion>
>>
>> I can run it, but I'm not sure what it's supposed to do.
>>
>> root@nitrogen6x:/unit_tests# ./pxp_test.out -I "-h -v -l 10 -t 100 -i
>> akiyo.mp4"
>
> If you look under /unit_test folder, you find a pxp_autorun.sh script
> (or something like that)
>
> The autorun* scripts are a set of command lines to run "automatically"
> the *.out test.
>
> Maybe it can help you figure out how to use it
>
Oddly, the file pxp_autorun.sh isn't a script:
~/yocto/build/tmp/work/nitrogen6x-poky-linux-gnueabi/imx-test/1_3.10.53-1.1.0-r0/image/unit_tests$
ls -l *pxp*
-rwxr-xr-x 1 ericn ericn 382803 Mar 30 20:34 autorun-pxp.sh
-rwxr-xr-x 1 ericn ericn 382803 Mar 30 20:34 pxp_test.out
~/yocto/build/tmp/work/nitrogen6x-poky-linux-gnueabi/imx-test/1_3.10.53-1.1.0-r0/image/unit_tests$
file autorun-pxp.sh
autorun-pxp.sh: ELF 32-bit LSB executable, ARM, EABI5 version 1...
Something appears to be broken in the build process, since I do
find a script with some sample command-lines in the source tree:
pxp_v4l2_test.out -sx 480 -sy 272 -res 352:240 -dst 0:0:352:240 -a 100
-w 2 fb-352x240.yuv BLANK
pxp_v4l2_test.out -sx 480 -sy 272 -res 352:240 -a 0 -r 90 fb-352x240.yuv
BLANK
pxp_v4l2_test.out -sx 480 -sy 272 -res 352:240 -a 100 -o rgb24_file.s1
fb-352x240.yuv BLANK
pxp_v4l2_test.out -sx 480 -sy 272 -res 352:240 -a 100 -r 180
fb-352x240.yuv rgb24_file.s1
pxp_v4l2_out_test.sh (END)
Regards,
Eric
next prev parent reply other threads:[~2015-04-10 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 21:13 PXP test applications Eric Nelson
2015-04-10 12:09 ` Daiane Angolini
2015-04-10 14:47 ` Eric Nelson [this message]
2015-04-10 15:58 ` Daiane Angolini
2015-04-10 18:32 ` Eric Nelson
2015-04-11 14:28 ` Daiane Angolini
2015-04-11 16:30 ` Carlos Rafael Giani
2015-04-11 17:03 ` Eric Nelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5527E28B.8040708@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.