Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[vmach]

Hi,
recently I have upgraded my Yocto image and SDK from Morty to Pyro. (I'm not ready to upgrade to Rocko since meta-boundary layer is not prepared yet. My SoC is Boundary Devices Nitrogen6x_MAX QP). After the upgrade and rebuilt with the new SDK my software has two problems:
 
1) moving with elements on the touch screen (eg. QSlider) is not continuous and has got a visible delay (about 1 sec)
2) imxeglvivsink is able to view the gstreamer video correctly only within the first start of the application (after power on). When I kill the application and try to run it for the second time, imxeglvivsink shows only a black screen. I have the same problem with a basic pipeline:
export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform ! imxeglvivsink
 
On the other hand, the following pipeline works OK.
gst-launch-1.0 videotestsrc ! imxg2dvideotransform ! imxg2dvideosink
 
What should I change in my Qt or imx configuration after the upgrade to Pyro? The only change in the recipe list between Morty and Pyro is that in Pyro I have removed OpenCV recipe. But I don't use OpenCV explicitly in my software anyway. Furthermore, I use X11 and matchbox-window-manager.
 
Best regards,
Vaclav Mach

Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[Ian Coolidge]

[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]

Hello,

Just FYI, meta-boundary isn't strictly necessary for anything unless you
need the QCA wifi driver built into the kernel. You could delete everything
except recipes-kernel/ and conf/ from meta-boundary@pyro, then you'd be
good to go.

Or go without that all together and just use fsl-community-bsp-platform at
rocko branch.

-Ian

On Tue, Jan 16, 2018 at 7:38 AM, <vmach@ramet.as> wrote:

> Hi,
> recently I have upgraded my Yocto image and SDK from Morty to Pyro. (I'm
> not ready to upgrade to Rocko since meta-boundary layer is not prepared
> yet. My SoC is Boundary Devices Nitrogen6x_MAX QP). After the upgrade and
> rebuilt with the new SDK my software has two problems:
>
> 1) moving with elements on the touch screen (eg. QSlider) is not
> continuous and has got a visible delay (about 1 sec)
> 2) imxeglvivsink is able to view the gstreamer video correctly only within
> the first start of the application (after power on). When I kill the
> application and try to run it for the second time, imxeglvivsink shows only
> a black screen. I have the same problem with a basic pipeline:
> export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
> ! imxeglvivsink
>
> On the other hand, the following pipeline works OK.
> gst-launch-1.0 videotestsrc ! imxg2dvideotransform ! imxg2dvideosink
>
> What should I change in my Qt or imx configuration after the upgrade to
> Pyro? The only change in the recipe list between Morty and Pyro is that in
> Pyro I have removed OpenCV recipe. But I don't use OpenCV explicitly in my
> software anyway. Furthermore, I use X11 and matchbox-window-manager.
>
> Best regards,
> Vaclav Mach
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

[-- Attachment #2: Type: text/html, Size: 2487 bytes --]

Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[vmach]

[-- Attachment #1: Type: text/html, Size: 4301 bytes --]

Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[Otavio Salvador]

On Fri, Apr 20, 2018 at 9:58 AM,  <vmach@ramet.as> wrote:
> I finally moved to Rocko branch, avoided the meta-boundary layer and made an
> image. Kernel version is linux_boundary_4.1.15, Gstreamer version is 1.12.2.
> The behavior is very similar:
>
> 1) export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
> ! imxg2dvideosink
> works fine without any troubles
>
> 2) export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
> ! imxeglvivsink
>     a) crashes with segfault during the first run after power on of the
> Nitrogen6x_MAX QP
>     b) second and every other following run of this pipeline causes X window
> with black screen. No videotest pictures.
>
> In all cases, GST_DEBUG=3 has no warnings or errors. Do you have any
> suggestion how to make the imxeglvivsink work?

This is mostly likely to be due the different between the GPU driver
module inside the kernel source versus the binary drivers.

Check if you are using our external module and it should work.
-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Odp: Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[vmach]

[-- Attachment #1: Type: text/html, Size: 4054 bytes --]

Re: Odp: Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[Otavio Salvador]

On Fri, Apr 27, 2018 at 7:58 AM <vmach@ramet.as> wrote:
> Do you mean this module: meta-freescale/recipes-graphics/imx-gpu-viv ?
The version is 5.0.11.p8.6.
> How can I find out the version of module inside the kernel source and
binary driver?

You need to check in the buildhistory, RPM or Opkg the module release. Also
you should check the 'dmesg' output.

> Based on further experiments I have more details about the behaviour:
> When I start any Qt application with GUI and then I try to run
> export DISPLAY=:0.0 && gst-launch-1.0 videotestsrc ! imxg2dvideotransform
! imxeglvivsink,
> I see only a black screen inside the window.

> But when I restart X server and run the same Gstreamer pipeline again
(without running GUI application before), the I can see the videotest
output successfully.
> Can this description help you to find any recommendations?

You does seem to have a problem. Honestly, I think moving to rocko is the
easiest solution as it is the current stable release.

Did you consider doing it?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Odp: Re: Odp: Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[vmach]

[-- Attachment #1: Type: text/html, Size: 3655 bytes --]

Re: Odp: Re: Odp: Re: Odp: Re: Troubles with Qt after upgrade from Morty to Pyro (plaintext email)

[Otavio Salvador]

On Fri, Apr 27, 2018 at 10:21 AM <vmach@ramet.as> wrote:
> dmesg says:
> [    1.466724] [drm] Initialized vivante 1.0.0 20120216 on minor 0

> dnf says:
> imx-gpu-viv.armv7at2hf_neon_mx6qdl : imx-gpu-viv version
5.0.11.p8.6-hfp-r0
> kernel-module-imx-gpu-viv.nitrogen6x
  5.0.11.p8.6+fslc+git0+a05d9b23b9-r0

> The subject of this thread is misleading. My very first question was
focused on Pyro, but in the meantime we have moved to Rocko. So we are
currently working on Rocko.

> Any ideas, please? The dmesg output seems to be strange...

You need to confirm if galcore is being loaded. Apart from that, it needs
debugging... so nothing we can assist without digging into it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750