how to configure mfw_isink in yocto ?

[sumanranjan]

Hi,

I am using dora branch for Yocto. I have added ‘packagegroup-fsl-gstreamer’ into IMAGE_INSTALL option to enable GStreamer plugins into output binary.

I have 'mfw_v4lsink' but I want to use 'mfw_isink' because of multi-overlay application use case. Can somebody tell me how to enable 'mfw_isink' in yocto ?

I checked in the folder below but it seems 'i_sink' folder is not going into compilation.

$ ls /fsl-community-bsp/build-fb/tmp/work/imx6qsabresd-poky-linux-gnueabi/gst-fsl-plugin/3.0.9-r0/gst-fsl-plugins-3.10.9-1.0.0/src/misc

   i_sink  tvsrc  v4l_sink  v4l_source

~Suman

[qiankunyue]

I have the similar problem with you. I don't kown why gstreamer works well on X11 but always has some problems on fb.

[gusarambula]

Would you please provide more information on your configuration?

- Image used
-Machine (board) used
-DISTRO_FEATURES

I tried to replicate by adding ‘packagegroup-fsl-gstreamer’ into IMAGE_INSTALL on the local.conf file for the i.MX6Q SABRE by adding:

+ IMAGE_INSTALL_append=” packagegroup-fsl-gstreamer”

And the compiled image (I used core-image-minimal to ensure that the gstreamer packages would be added to an otherwise gstreamer free image) did show isink when running

$ gst-launch isink

Just to test if it was found and did showed the MFW_GST_ISINK_PLUGIN 3.0.1

Please let me know the additional information shown above and make sure you are adding “append” to the IMAGE_INSTALL parameters (this can be easy to overlook)

[sumanranjan]

I have attached my recipe contents below in which 'packagegroup-fsl-gstreamer' is already added, and I have FSL plugins e.g. vpudec etc. working in my image. Below I have mentioned the procedure I have followed to get the sources and build the image. please have a look at it and suggest accordingly.

Sources:-

$ mkdir fsl-community-bsp

$ cd fsl-community-bsp

$ repo init -u http://github.com/Freescale/fsl-community-bsp-platform -b dora

$ mv .repo/manifest.xml .repo/manifest.orig

$  cp <location>/fsl-yocto-release-manifest.xml .repo/manifest.xml

$ repo sync

$ cp -r sources/meta-fsl-bsp-release/imx/meta-fsl-arm/conf/machine sources/metafsl-arm/conf

Building:-

$ MACHINE=imx6qsabresd source setup-environment build-fb

$ cd ..

$ source fsl-setup-release.sh -b build-fb -e fb

$ cd build-fb

$ bitbake fsl-image-fb

--------------------------------------------fsl-image-fb.bb---------------------------------------------------------------------

DESCRIPTION = "Freescale Image Frame Buffer Image"

IMAGE_FEATURES += "splash"

LICENSE = "MIT"

inherit core-image

inherit distro_features_check

CONFLICT_DISTRO_FEATURES = "x11 wayland directfb"

DISTRO_FEATURES += "pulseaudio "

WEB = "web-webkit"

# Add extra image features

EXTRA_IMAGE_FEATURES += " \

    nfs-server \

    tools-debug \

    tools-profile \

"

SOC_IMAGE_INSTALL = "gpu-viv-bin-mx6q gpu-viv-g2d"

IMAGE_INSTALL += " \

    ${SOC_IMAGE_INSTALL} \

    cpufrequtils \

    lighttpd \

    tslib \

    glib-2.0 \

    icu \

    udev \

    nano \

    openssh \

    openssl \

    gdbserver \

    socketcan \

    openssh-sftp-server \

    packagegroup-fsl-gstreamer \

    gst-plugins-base-meta \

    gst-plugins-good-meta \

    gst-plugins-bad-meta \

    packagegroup-fsl-tools-testapps \

    packagegroup-fsl-tools-benchmark \

   "

export IMAGE_BASENAME = "fsl-image-fb"

----------------------------------------

[gusarambula]

I apologize for the delay. Are you still having issues to include mfw_isink in your build?

I’m curious about the environment setup and the manifest.xml that you’re copying as the latest versions of the Freescale Community BSP and the Freescale BSP Release do not require to copy the manifest manually and use a different environment setup:

     fsl-community-bsp uses setup-environment and the build to be used

     fsl-release-bsp uses fsl-setup-release.sh which calls setup environment and this script also accepts the backend option to be used.

Since you want to use the fsl-image-fb you would like to use the fsl-release-bsp which uses a specific commit (perhaps this is why you’re copying the manifest file but I would check the latest bsp commit on the documentation).

You should be able to sync using the BSP commit and then:

$ MACHINE=imx6qsabresd source fsl-setup-release.sh -b buildfb -e fb

If it succeeds in initializing the environment you should now be inside the build directory now created and ready to bake.

[sumanranjan]

You are right about manifest copying manually. So, you recommend to use fsl-release-bsp which is having fsl-image-fb recipe. However, I do not see fsl-release-bsp present in GitHub at the moment. All I see is fsl-community-bsp-platform.

Can you please check and provide me a link for repo sync ?

[gusarambula]

You may find the steps to download the i.MX6 BSP Release on the L3.10.17 i.MX6 Documentation Bundle available on the documentation page. Please look for L3.10.17_1.0.0_LINUX_DOCS (Linux 3.10.17 BSP & MM Bundle)

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&fpsp=1&tab=Design_Tools_Tab

Then look for Freescale Yocto Project User's Guide.

Just to ease things the key information would be the repo which is:

$ mkdir fsl-release-bsp

$ cd fsl-release-bsp

$ repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-3.10.17-1.0.0_ga

$ repo sync

$ MACHINE=< machine name> source fsl-setup-release.sh -b <build directory> -e <backend fb,dfb, wayland, x11>

[nagendrasarma]

hi

i tried, but did not find any mfw_isink  plugin

can you please give me how to add mfw_isink plugin, i mean -fsl-image-fb.bb  configuration for mfw_isink

regards

Nagendra

[nagendrasarma]

hi all

i am building yocto image for sabersd board , the machine info is

MACHINE=imx6qsabresd source fsl-setup-release.sh -b build -e fb

and building using command

bitbake fsl-image-fb

the images are created  under the folder "tmp" and working fine.

now queries

1. i have removed images folder accidentally , how can i retrieve ? (running bitbake fsl-image-fb is not helping)

2. with minimal change in source, how can i rebuild all images compiling only changed files ?

regards

nagendra

[nagendrasarma]

can anybody update my queries please ?

[qiankunyue]

Hi,nagendra,

  I just make it work, please follow the steps:

     1.   $ vim ~/yocto/fsl-community-bsp/sources/meta-fsl-bsp-release/imx/meta-fsl-demos/recipes-fsl/images/fsl-image-fb.bb

      then just add "packagegroup-fsl-gstreamer \" like this below,

           .........

           .........

           IMAGE_INSTALL += " \

           ${SOC_IMAGE_INSTALL} \

           cpufrequtils \

           nano \

           packagegroup-fsl-gstreamer \

           packagegroup-fsl-tools-testapps \

           packagegroup-fsl-tools-benchmark \

           "

           export IMAGE_BASENAME = "fsl-image-fb"

     2.   $ . ./setup-environment build-fb/ 

     3.   $ bitbake fsl-image-fb

When finished, there are a new *.sdcard and rootfs, you will succeed. if not, just check your yocto environment, the yocto maybe not rebuild.

The gstreamer plugins had alreadly build when you use default fsl-image-fb environment, they are in ~/yocto/fsl-community-bsp/build-fb/tmp/sysroots/imx6qsabresd/usr/lib/gstreamer-0.10/, they are just some *.so and *.a library. What we need to do is just install them in

rootfs ----- /usr/lib.

Good luck!

[gusarambula]

While making some research I came across a bug regarding "mfw_isink", I’m trying to figure out if this is the reason why it’s not being included even though the source code is loaded.

Bug 5331 - error play video via gstreamer with "mfw_isink"

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5331

I’ll update when I find more information on this.

[sumanranjan]

Can somebody reply to my query please ?