Re: [meta-freescale] Technical queries on android BSP porting on imx6

2017-07-04 Thread sai lakshmi
Hi,

Thanks for your reply. I have looked into the community, BSP document on
linux is available but not on android. If you can send me the link of the
BSP, it would be of great help to me.

Thanks & Regards

On Tue, Jul 4, 2017 at 6:59 PM, Daiane Angolini 
wrote:

> On Thu, Jun 29, 2017 at 8:35 AM, sai lakshmi 
> wrote:
> > Hi,
> >
> > I am building a custom board on imx6. I want custom android image for my
> > board. I couldn't find BSP porting guide for android imx6. Please help
> me in
> > this regard.
>
> Basically it's only adding a new device. I know there are some DOC on
> imx.community related to this question.
>
> Daiane
> >
> > Awaiting your reply
> >
> > Thanks & Regards
> >
> > --
> > ___
> > meta-freescale mailing list
> > meta-freescale@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-freescale
> >
>
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] too large; maximum length error

2017-07-04 Thread Otavio Salvador
On Tue, Jul 4, 2017 at 6:41 AM, König, Florian  wrote:
> thanks alot, it compiles now, but at the last step  do_populate_sdk it throws 
> a error:
>
> Total size: 108 M
> Installed size: 310 M
> Running transaction check
> Transaction check succeeded.
> Running transaction test
> Error: Transaction check error:
>   file /opt/poky/2.3/sysroots/x86_64-pokysdk-linux/environment-setup.d 
> conflicts between attempted installs of 
> nativesdk-cmake-3.7.2-r0.x86_64_nativesdk and 
> nativesdk-qtbase-tools-5.8.0+git0+49dc9aa409-r0.x86_64_nativesdk
>
>
>
> I cannot find environment-setup.d file  or why cmake conflicts with 
> qtbase-tools ,perhaps someone got an answer ?

What branches?


-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] IPU alpha blending problems on mx6

2017-07-04 Thread Olivier Bourgois
Hi Andrea,

We are facing a similar problem but with the imx6quad plus.  Very similar use 
case, overlaying video onto a QT5 app with gstreamer on second framebuffer but 
with imxeglvivsink and color keying to make the video rectangle overlay.  We 
are using a split-mode LVDS link.  We get the same IPU_INT_STAT_5 and 
IPU_INT_STAT_10 followed by screen freezing.

What I noticed is that if I reduce the size of the second frame buffer to 
around 320x200 with fbset  (just for a test), the system seems to be able to 
cope with the small video overlay.  I am also capable of displaying two alpha 
blended full screen still images by "cat image > /dev/fbx" So it does look like 
there is a bandwidth bottleneck somewhere in the video pipeline.  Note that we 
have the same board also fitted with a standard imx6quad (not plus) and in this 
case things were working but somewhat lagging.

It almost seems to me that there are use-cases where the ipu can't cope with 
two 1080p streams at the same time (one for each frame buffer).  We are also 
still looking for a solution.

In our case we have only the 60Hz LVDS output, I wanted to try lowering to 30Hz 
to see if the problem goes away, but my TFT does not support it.  I have no 
HDMI port on my board.  What refresh rate are you using on HDMI port?  If it is 
60Hz, can you try modifying your video mode to 30Hz to see if it helps in your 
use-case?  This might confirm that we are facing some kind of video pipeline 
bandwidth issue at the IPU.  Alternately or in parallel, does a lower 
resolution say 720p give you the same issue?

Regards

Olivier
De : meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] De la part de Andrea Picaro
Envoyé : 3 juillet 2017 06:02
À : meta-freescale@yoctoproject.org
Objet : [meta-freescale] IPU alpha blending problems on mx6

Hello,
We use an imx6 quad processor to run a Qt application on fb0, then application 
runs gstreamer pipeline to play video on overlay buffer fb1. Our system was 
previously based on kernel 3.0.35 and using mfw_isink it worked perfectly up to 
1080p. Now we are porting on kernel 4.1.15 with Yocto Morty branch. Qt5.7 app 
on fb0 and play video through gstreamer on fb1 using imxg2dvideosink.
We use alpha blending with separate alpha buffers to uncover only the video 
rectangle on fb1.
In this configuration system is unstable with hdmi turning off and on 
repeatedly giving errors:
[ 1568.833307] imx-ipuv3 240.ipu: warning: wait for bg sync eof timeout
[ 1572.143078] imx-ipuv3 240.ipu: IPU Warning - IPU_INT_STAT_5 = 0x8880
[ 1572.143089] imx-ipuv3 240.ipu: IPU Warning - IPU_INT_STAT_10 = 0x0008
after a while screen blanks definitivelly and i have to reboot.
It seems to strictly depend on local alpha blending since i can replicate the 
issue also by running
 /unit_tests/autorun-ipu. If i use glabal alpha the problem do not appear and i 
can run full screen application and video with 50% blending with no problem so 
it doesn't seem to be a dma shortage.
Already tryed arg dmfc=3.
Could you help me?

Thank you

--
Andrea Picaro
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] unable to initialize libusb: -99

2017-07-04 Thread Otavio Salvador
On Tue, Jul 4, 2017 at 7:28 AM, Takashi Matsuzawa  wrote:
> Today I tried testing with the unmodified images.
>
> (just followed the build instruction on README from
> https://github.com/Freescale/fsl-community-bsp-platform), and the result was
> the below.
>
>
> lsusb on imx61sabreauto board:
>
>
> 2.0 (jethro) - OK
>
> 2.1 (krogoth) - NG
>
> 2.2 (morty) - NG
>
> 2.3 (pyro) - NG
>
>
> I am curious since it is OK (lsusb correctly list the USB devices) with
> jethro, but NG on krogoth and after.
> I may look into the delta but still not sure where to look into.
> Any comment/suggestion is welcomed.

I am adding Lauren on Cc. She may know something about it.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] "Could not open egl display" error and GPU problem on imx6dl

2017-07-04 Thread Daiane Angolini
On Fri, Jun 30, 2017 at 8:51 AM, Refik Tuzakli  wrote:
> Hello
>
>
>
> I am trying to build embedded Linux that runs QtWebengine via Buildroot.
>

Maybe it's better to send this email also to the buildroot mailing list.

>
>
> I applied a patch at this link to enable webengine on buildroot
> I enable imx-gpu-viv library, openGL support and eglfs support. to test both
> webengine and gpu, I run demobrowser with -platform eglfs from QT. It gives
> me "Could not open egl display"
>
> when I run demobrowser - platform directfb, application occupies half of CPU
> so GPU does not work and I cant use demobrowser.

Depending on the GPU version you're using, DirectFB is not supported.


Daiane
>
>
>
> which library is or configuration is missing?
>
>
> --
> Refik Tuzaklı
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] Technical queries on android BSP porting on imx6

2017-07-04 Thread Daiane Angolini
On Thu, Jun 29, 2017 at 8:35 AM, sai lakshmi  wrote:
> Hi,
>
> I am building a custom board on imx6. I want custom android image for my
> board. I couldn't find BSP porting guide for android imx6. Please help me in
> this regard.

Basically it's only adding a new device. I know there are some DOC on
imx.community related to this question.

Daiane
>
> Awaiting your reply
>
> Thanks & Regards
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] About loading drivers of camera_ov5640_mipi and to test it in warp7

2017-07-04 Thread Daiane Angolini
On Fri, Jun 30, 2017 at 2:30 AM, Vinay Hulagabali
 wrote:
> I just tried with the ov2680_mipi drivers using bitbake core-image-minimal
> but it is throwing error like it is getting the ov2680_mipi.c file so no
> rule to make target.
> So any idea how to make it work

As far as I know, it's not working.

There is some code for DTS on the android kernel, but it is not
completely implemented.


Daiane
>
> Regards
> Vinod
>
> On 29-Jun-2017 6:42 PM, "Daiane Angolini"  wrote:
>>
>> Hi Pierre-jean,
>>
>> On Wed, Jun 28, 2017 at 4:36 PM, TEXIER Pierre-Jean
>>  wrote:
>> >
>> > 2017-06-28 18:10 GMT+02:00 Daiane Angolini :
>> >>
>>
>> >
>> > Yes Daiane, you are right, currently the camera not working with the
>> > linux-warp7 Kernel.
>> >
>> > But it seems operational with the Android Kernel
>> >
>> > (https://github.com/WaRP7/linux-fslc/commit/525f946c85625f4ef97b737c3e9651dcd0cba213)
>> >
>> > I will try to work on the linux-warp7 support.
>>
>> My memory is not exactly accurate in this point. But what I have here is:
>>
>> ov2680 is supported, but the output is in bayer format, which is not
>> directly supported my imx7S (here I don't remember the reason
>> specifically). So the most we could get was one frame picture with raw
>> data (so, some additional processing was needed to render it to the PC
>> screen)
>>
>> I personally was not able to test it, because I had no time and
>> because I have never really gathered all the pieces needed.
>>
>> If you happens to get this working, please let me/us know. It would be
>> terrific.
>>
>> Thanks a lot,
>> Daiane
>>
>> >
>> > Regards,
>> >
>> > Pierre-jean
>> >
>> >
>> >
>> >>
>> >> Regards,
>> >> Daiane
>> >> >
>> >> > Your suggestions are appreciated thanks.
>> >> >
>> >> > Regards
>> >> > Vinod
>> >> >
>> >> > --
>> >> > ___
>> >> > meta-freescale mailing list
>> >> > meta-freescale@yoctoproject.org
>> >> > https://lists.yoctoproject.org/listinfo/meta-freescale
>> >> >
>> >> --
>> >> ___
>> >> meta-freescale mailing list
>> >> meta-freescale@yoctoproject.org
>> >> https://lists.yoctoproject.org/listinfo/meta-freescale
>> >
>> >
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] Change SSH Server Port

2017-07-04 Thread Fabio Berton
You can create an bbappend to openssh_7.4p1.bb and add your ssh config 
settings. In your openssh_%.bbappend file put:


FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

and then create a directory openssh with sshd_config file.

The result is these two files:

meta-your-layer/recipes-connectivity/openssh/openssh_%.bbappend
meta-your-layer/recipes-connectivity/openssh/openssh/sshd_config

You can change ssh_config file or add other any file using SRC_URI variable.

Fabio Berton

On 07/04/2017 08:30 AM, Mauricio Cirelli wrote:

Dear community,

How can I change the default SSH Server port (22) in my image?
Is it possible to customize it during build or only at runtime?

Thank you for your attention.



Mauricio Cirelli



--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


[meta-freescale] Change SSH Server Port

2017-07-04 Thread Mauricio Cirelli
Dear community,

How can I change the default SSH Server port (22) in my image?
Is it possible to customize it during build or only at runtime?

Thank you for your attention.



Mauricio Cirelli
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] unable to initialize libusb: -99

2017-07-04 Thread Takashi Matsuzawa
Hello.

Today I tried testing with the unmodified images.

(just followed the build instruction on README from 
https://github.com/Freescale/fsl-community-bsp-platform), and the result was 
the below.


lsusb on imx61sabreauto board:


2.0 (jethro) - OK

2.1 (krogoth) - NG

2.2 (morty) - NG

2.3 (pyro) - NG

I am curious since it is OK (lsusb correctly list the USB devices) with jethro, 
but NG on krogoth and after.
I may look into the delta but still not sure where to look into.
Any comment/suggestion is welcomed.


From: Takashi Matsuzawa
Sent: Friday, June 30, 2017 9:03 PM
To: meta-freescale@yoctoproject.org
Subject: Re: unable to initialize libusb: -99


Hello.

I am still looking into this, since without USB working the board is les use.

And, I noticed there is an post regarding imx6qdl-sabreauto.dtsi issue 
regarding pca953x control.


https://community.nxp.com/thread/435299

In fact before in the boot log, I see the followings before "Can't register 
ci_hdrc platform device, err=-517" errors.
I an hardly imagine none of the sabreauto board users (on linux-fslc) can use 
USB.   And also I could use USB on NXP release BSP, so board hardware is not 
broken.

If there is a fix patch or workaround known, or if it is my configuration 
problem, I would like to learn.

>  pca953x 2-0030: failed reading register
>  pca953x: probe of 2-0030 failed with error -11
>  pca953x 2-0032: failed reading register
>  pca953x: probe of 2-0032 failed with error -11
>  pca953x 2-0034: failed reading register
>  pca953x: probe of 2-0034 failed with error -11

>  CPU PMU: Failed to parse /soc/pmu/interrupt-affinity[0]

>  Unknown username "adit" in message bus configuration file

>  mag3110 2-000e: read chip ID 0xfff5 is not equal to 0xc4!
>  mag3110: probe of 2-000e failed with error -22

>  mma8451 2-001c: read chip ID 0x1 is not equal to 0x1a or 0x2a!
>  mma8451: probe of 2-001c failed with error -22

>  imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517
>  imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517
>  imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517
>  imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517

Any sugestion is highly appreciated.



From: Takashi Matsuzawa
Sent: Thursday, June 29, 2017 3:09 PM
To: meta-freescale@yoctoproject.org
Subject: unable to initialize libusb: -99


Hello.

I am trying an image based on morty (2.2) fsl communty BSP on sabre-ai board, 
and see the lsusb -99 error.


Any suggestion/comment on which part of the configuration I should be look into!
(I already googl'ed and found some old questions/answers on libusb -99 errors, 
but I could not figure out if they are just the same as my case or not.)


My issue is that SB is not working (lsusb gives me error), as below.

I checked and make sure CONFIG_USB_EHCI_HCD/CONFIG_USB_XHCI_HCD are there.


>root@imx6qsabreauto:~# export LIBUSB_DEBUG=9
>root@imx6qsabreauto:~# lsusb -v
>libusb: debug [libusb_init] created default context
>libusb: debug [libusb_init] libusb v1.0.20.11004
>libusb: error [op_init] could not find usbfs
>unable to initialize libusb: -99


I am also seeing errors like below in journalctl log, but I am not sure what 
they mean.

>Jun 28 12:02:02 imx6qsabreauto kernel[313]: hdm_usb: hdm_usb_init()
>Jun 28 12:02:02 imx6qsabreauto kernel[313]: usbcore: registered new interface 
>driver hdm_usb
>Jun 28 12:02:02 imx6qsabreauto kernel[313]: usbcore: registered new interface 
>driver k2l-mocca
>Jun 28 12:02:02 imx6qsabreauto kernel[313]: imx_usb 2184000.usb: Can't 
>register ci_hdrc platform device, err=-517
>Jun 28 12:02:02 imx6qsabreauto kernel[313]: imx_usb 2184200.usb: Can't 
>register ci_hdrc platform device, err=-517
>...

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale


Re: [meta-freescale] too large; maximum length error

2017-07-04 Thread König , Florian
Hi,
thanks alot, it compiles now, but at the last step  do_populate_sdk it throws a 
error:



Total size: 108 M
Installed size: 310 M
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
  file /opt/poky/2.3/sysroots/x86_64-pokysdk-linux/environment-setup.d 
conflicts between attempted installs of 
nativesdk-cmake-3.7.2-r0.x86_64_nativesdk and 
nativesdk-qtbase-tools-5.8.0+git0+49dc9aa409-r0.x86_64_nativesdk



I cannot find environment-setup.d file  or why cmake conflicts with 
qtbase-tools ,perhaps someone got an answer ?




-Ursprüngliche Nachricht-
Von: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] Im Auftrag von Fabio Berton
Gesendet: Montag, 3. Juli 2017 13:39
An: meta-freescale@yoctoproject.org
Betreff: Re: [meta-freescale] too large; maximum length error

Hi,

You need this commit:

http://cgit.openembedded.org/openembedded-core/commit/?id=5d3df78367be0afbfe001b4fa776a98a82e6ce54

Fabio Berton

On 07/03/2017 03:08 AM, König, Florian wrote:
> Hi,
> 
> when i try to build  bitbake core-image-minimal -c populate_sdk  i get 
> the following error :
> 
> ERROR: nativesdk-u-boot-mkimage: chrpath command failed with exit code 7:
> 
> b'/home/moba/git/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-u-boot-mkimage/1_2017.01-r0/package/opt/poky/2.3/sysroots/x86_64-pokysdk-linux/usr/bin/uboot-mkimage:
>  
> RPATH=/home/moba/git/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linu
> x/nativesdk-u-boot-mkimage/1_2017.01-r0/recipe-sysroot-native/usr/lib:
> /home/moba/git/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nati
> vesdk-u-boot-mkimage/1_2017.01-r0/recipe-sysroot-native/lib\n'b"new
> rpath
> '$ORIGIN/../../../../../../../home/moba/git/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-u-boot-mkimage/1_2017.01-r0/recipe-sysroot-native/usr/lib:$ORIGIN/../../../../../../../home/moba/git/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-u-boot-mkimage/1_2017.01-r0/recipe-sysroot-native/lib'
>  
> too large; maximum length 263\n"
> 
> Its impossible to build/populate the sdk with this error. I found 
> https://patchwork.openembedded.org/patch/34653/  but there is no real 
> solution. As you can see I still get this error with "pyro" branch.
> 
> Do I miss something or is populate_sdk broken ?
> 
> thanks
> 
> Mit freundlichen Grüßen
> 
> Florian König
> 
> Entwicklung
> 
> MOBA Mobile Automation AG
> 
> Kapellenstraße 15
> 
> 6 Limburg / Germany
> 
> Tel.: +49 6431 9577-297
> 
> Fax: +49 6431 9577-297
> 
> Vorsitzender des Aufsichtsrats: Harald Robl; Vorstand: Volker G. 
> Harms, Dr. Holger Barthel, Alfons Horn
> 
> Sitz der Gesellschaft: Limburg; Registergericht Limburg, HRB 2552,
> USt-IdNr.:  DE 113865988
> 
> Chairman of the supervisory board: Harald Robl; Executive board: 
> Volker G. Harms, Dr. Holger Barthel, Alfons Horn
> 
> Corporate headquarters: Limburg; Register court: Limburg, HRB 2552,
> USt-IdNr.: DE 113865988
> 
> Diese Nachricht ist nur für den Empfänger bestimmt, da sie 
> persönliche, vertrauliche Informationen enthält. Der Inhalt
> 
> darf an keinen anderen außer an den Empfänger weitergeleitet werden. 
> Unbefugte Empfänger werden gebeten, die
> 
> Vertraulichkeit zu wahren und den Absender sofort über den 
> Übertragungsfehler zu informieren.
> 
> This message is intended for the addressee only as it contains private 
> and confidential information. The contents are not
> 
> to be disclosed to anyone other than the addressee. Unauthorized 
> recipients are requested to comply with the above and
> 
> inform the sender immediately of any error in transmission.
> 
> 
> 
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale