Re: [meta-freescale] [Documentation][PATCH] Use release-notes machine-list.inc In user-guide

[Daiane Angolini]

On Thu, May 16, 2019 at 9:40 AM Thomas A. F. Thorne
 wrote:
>
> The user-guide gets little attention compared to the release notes.
> Frequently the correct list of supported machines is visible in the
> release notes but the user-guide is left very out of date.  This change
> switches to using the machine-list.inc file in the release directory in
> both documents to help ensure the user-guide stays up to date.
>
> This issue is described in GitHub Issue #28

Thanks for the patch. PR merged!

Daiane
>
> Signed-off-by: Thomas A. F. Thorne 
> ---
>  user-guide/source/machine-list.inc | 65 --
>  user-guide/source/machines.rst |  2 +-
>  2 files changed, 1 insertion(+), 66 deletions(-)
>  delete mode 100644 user-guide/source/machine-list.inc
>
> diff --git a/user-guide/source/machine-list.inc 
> b/user-guide/source/machine-list.inc
> deleted file mode 100644
> index f5f1f2a..000
> --- a/user-guide/source/machine-list.inc
> +++ /dev/null
> @@ -1,65 +0,0 @@
> -==  ==  
> ===  ==
> -   Machine Name  
>  SoC  Layer
> -==  ==  
> ===  ==
> -apalis-imx6 Toradex Apalis iMX6Q/D  
> i.MX6meta-fsl-arm-extra
> -cfa10036Crystalfontz CFA-10036  
> i.MX28   meta-fsl-arm-extra
> -cfa10037Crystalfontz CFA-10037  
> i.MX28   meta-fsl-arm-extra
> -cfa10049Crystalfontz CFA-10049  
> i.MX28   meta-fsl-arm-extra
> -cfa10055Crystalfontz CFA-10055  
> i.MX28   meta-fsl-arm-extra
> -cfa10056Crystalfontz CFA-10056  
> i.MX28   meta-fsl-arm-extra
> -cfa10057Crystalfontz CFA-10057  
> i.MX28   meta-fsl-arm-extra
> -cfa10058Crystalfontz CFA-10058  
> i.MX28   meta-fsl-arm-extra
> -cgtqmx6 Congatec QMX6 Evaluation board  
> i.MX6 Q/DL   meta-fsl-arm-extra
> -cm-fx6  CompuLab CM-FX6 
> i.MX6 Q/DL   meta-fsl-arm-extra
> -colibri-imx6Toradex Colibri iMX6DL/S
> i.MX6 DL/S   meta-fsl-arm-extra
> -colibri-imx7Toradex Colibri iMX7D/S 
> i.MX 7Dual / i.MX 7Solo  meta-fsl-arm-extra
> -colibri-vf  Toradex Colibri VF50/VF61   
> VF500/VF610  meta-fsl-arm-extra
> -cubox-i SolidRun CuBox-i and HummingBoard   
> i.MX6 Q/DL   meta-fsl-arm-extra
> -imx233-olinuxino-maxi   OLIMEX iMX233-OLinuXino-Maxi
> i.MX23   meta-fsl-arm-extra
> -imx233-olinuxino-micro  OLIMEX iMX233-OLinuXino-Micro   
> i.MX23   meta-fsl-arm-extra
> -imx233-olinuxino-mini   OLIMEX iMX233-OLinuXino-Mini
> i.MX23   meta-fsl-arm-extra
> -imx233-olinuxino-nano   OLIMEX iMX233-OLinuXino-Nano
> i.MX23   meta-fsl-arm-extra
> -imx23evkFreescale i.MX23 Evaluation Kit 
> i.MX23   meta-fsl-arm
> -imx28evkFreescale i.MX28 Evaluation Kit 
> i.MX28   meta-fsl-arm
> -imx51evkFreescale i.MX51 Evaluation Kit 
> i.MX51   meta-fsl-arm
> -imx53ardFreescale i.MX53 SABRE Automotive Board 
> i.MX53   meta-fsl-arm
> -imx53qsbFreescale i.MX53 Quick Start Board  
> i.MX53   meta-fsl-arm
> -imx6dl-riotboardRIoTboard   
> i.MX6S   meta-fsl-arm-extra
> -imx6dlsabreauto Freescale i.MX6DL SABRE Automotive  
> i.MX6DL  meta-fsl-arm
> -imx6dlsabresd   Freescale i.MX6DL SABRE Smart Device
> i.MX6DL  meta-fsl-arm
> -imx6q-dms-ba16  Advantech DMS BA16  
> i.MX6Q   meta-fsl-arm-extra
> -imx6qdl-variscite-som   Variscite i.MX6Q/DL VAR-SOM-MX6 
> i.MX6Q/DLmeta-fsl-arm-extra
> -imx6qpsabreauto Freescale i.MX6Q Plus SABRE Automotive  
> i.MX6QP  meta-fsl-arm
> -imx6qpsabresd

Re: [meta-freescale] [PATCH 0/3] improvements for mx8qxp

[Daiane Angolini]

On Mon, Jan 28, 2019 at 1:07 PM Max Krummenacher  wrote:
>
> Hi
>
> With this I could build a working wic image for the imx8qxpmek machine.
> (b0 silicon)
>
> Note that this series is based on Mings not yet applied m4 patch.
> https://lists.yoctoproject.org/pipermail/meta-freescale/2019-January/023808.html


Thanks a lot for the patch set. I have tested and it worked on my B0 board.

I've learned how to make a variable parsable in a wks file, thanks.

Otavio, I have created the PR (which includes Mings' patch), just in case:

https://github.com/Freescale/meta-freescale/pull/44

Daiane

>
> Regards
> Max
>
> Max Krummenacher (3):
>   imx-boot: drop adding m4 binaries to the boot container
>   imx-boot: imx-mkimage: do not compile with -static
>   imx-imx-boot-bootpart.wks: change default offset of bootloader
>
>  conf/machine/include/imx-base.inc  |  2 +-
>  recipes-bsp/imx-mkimage/imx-boot_0.2.bb| 14 
> --
>  recipes-bsp/imx-mkimage/imx-mkimage_git.bb |  2 +-
>  ...-imx-boot-bootpart.wks => imx-imx-boot-bootpart.wks.in} |  5 +++--
>  4 files changed, 9 insertions(+), 14 deletions(-)
>  rename wic/{imx-imx-boot-bootpart.wks => imx-imx-boot-bootpart.wks.in} (82%)
>
> --
> 2.13.6
>
> --
> ___
> 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] ERROR: Nothing PROVIDES 'virtual/libgles2'

[Daiane Angolini]

On Fri, Jan 18, 2019 at 9:27 AM Daiane Angolini  wrote:
>
> On Fri, Jan 18, 2019 at 9:25 AM srinivasan  wrote:
> >
> > imx8mmevk
> >
>
> I will try to reproduce the error on my side. Which is the DISTRO?

Would you mind creating a issue
https://github.com/Freescale/meta-freescale/issues ?

Please add your log, the MACHINE and DISTRO.

Thanks in advance,
Daiane
>
> Daiane
>
> > On Fri, Jan 18, 2019 at 12:20 PM Daiane Angolini  
> > wrote:
> > >
> > > On Fri, Jan 18, 2019 at 6:46 AM srinivasan  
> > > wrote:
> > > >
> > > > Dear Yocto Experts,
> > > >
> > > > I am seeing the below error when i am trying to integrate freescale
> > > > layers into my custom os?
> > >
> > > Which imx8 MACHINE are you trying?
> > >
> > > Daiane
> > > >
> > > > srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
> > > > bitbake -f -c clean custom-image-debug-imx8
> > > > WARNING: Host distribution "ubuntu-18.04" has not been validated with
> > > > this version of the build system; you may possibly experience
> > > > unexpected failures. It is recommended that you use a tested
> > > > distribution.
> > > > WARNING: 
> > > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
> > > > Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
> > > > file could not be found
> > > >   | ETA:  0:00:05
> > > > Parsing recipes: 100%
> > > > |#|
> > > > Time: 0:00:09
> > > > Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
> > > > targets, 382 skipped, 1 masked, 0 errors.
> > > > NOTE: Resolving any missing task queue dependencies
> > > > ERROR: Nothing PROVIDES 'virtual/libgles2' (but
> > > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
> > > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
> > > > DEPENDS on or otherwise requires it)
> > > > imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
> > > > with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> > > > NOTE: Runtime target 'qtbase' is unbuildable, removing...
> > > > Missing or unbuildable dependency chain was: ['qtbase', 
> > > > 'virtual/libgles2']
> > > > ERROR: Required build target 'custom-image-debug-imx8' has no
> > > > buildable providers.
> > > > Missing or unbuildable dependency chain was:
> > > > ['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']
> > > >
> > > > Summary: There were 2 WARNING messages shown.
> > > > Summary: There were 2 ERROR messages shown, returning a non-zero exit 
> > > > code.
> > > >
> > > >
> > > > Could you anyone please provide me some inputs for resolving the above 
> > > > issue?
> > > >
> > > > Many Thanks in advance
> > > > --
> > > > ___
> > > > 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] ERROR: Nothing PROVIDES 'virtual/libgles2'

[Daiane Angolini]

On Fri, Jan 18, 2019 at 9:25 AM srinivasan  wrote:
>
> imx8mmevk
>

I will try to reproduce the error on my side. Which is the DISTRO?

Daiane

> On Fri, Jan 18, 2019 at 12:20 PM Daiane Angolini  
> wrote:
> >
> > On Fri, Jan 18, 2019 at 6:46 AM srinivasan  wrote:
> > >
> > > Dear Yocto Experts,
> > >
> > > I am seeing the below error when i am trying to integrate freescale
> > > layers into my custom os?
> >
> > Which imx8 MACHINE are you trying?
> >
> > Daiane
> > >
> > > srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
> > > bitbake -f -c clean custom-image-debug-imx8
> > > WARNING: Host distribution "ubuntu-18.04" has not been validated with
> > > this version of the build system; you may possibly experience
> > > unexpected failures. It is recommended that you use a tested
> > > distribution.
> > > WARNING: 
> > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
> > > Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
> > > file could not be found
> > >   | ETA:  0:00:05
> > > Parsing recipes: 100%
> > > |#|
> > > Time: 0:00:09
> > > Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
> > > targets, 382 skipped, 1 masked, 0 errors.
> > > NOTE: Resolving any missing task queue dependencies
> > > ERROR: Nothing PROVIDES 'virtual/libgles2' (but
> > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
> > > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
> > > DEPENDS on or otherwise requires it)
> > > imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
> > > with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> > > NOTE: Runtime target 'qtbase' is unbuildable, removing...
> > > Missing or unbuildable dependency chain was: ['qtbase', 
> > > 'virtual/libgles2']
> > > ERROR: Required build target 'custom-image-debug-imx8' has no
> > > buildable providers.
> > > Missing or unbuildable dependency chain was:
> > > ['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']
> > >
> > > Summary: There were 2 WARNING messages shown.
> > > Summary: There were 2 ERROR messages shown, returning a non-zero exit 
> > > code.
> > >
> > >
> > > Could you anyone please provide me some inputs for resolving the above 
> > > issue?
> > >
> > > Many Thanks in advance
> > > --
> > > ___
> > > 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] ERROR: Nothing PROVIDES 'virtual/libgles2'

[Daiane Angolini]

On Fri, Jan 18, 2019 at 6:46 AM srinivasan  wrote:
>
> Dear Yocto Experts,
>
> I am seeing the below error when i am trying to integrate freescale
> layers into my custom os?

Which imx8 MACHINE are you trying?

Daiane
>
> srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
> bitbake -f -c clean custom-image-debug-imx8
> WARNING: Host distribution "ubuntu-18.04" has not been validated with
> this version of the build system; you may possibly experience
> unexpected failures. It is recommended that you use a tested
> distribution.
> WARNING: 
> /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
> Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
> file could not be found
>   | ETA:  0:00:05
> Parsing recipes: 100%
> |#|
> Time: 0:00:09
> Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
> targets, 382 skipped, 1 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing PROVIDES 'virtual/libgles2' (but
> /home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
> /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
> DEPENDS on or otherwise requires it)
> imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
> with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> NOTE: Runtime target 'qtbase' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
> ERROR: Required build target 'custom-image-debug-imx8' has no
> buildable providers.
> Missing or unbuildable dependency chain was:
> ['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']
>
> Summary: There were 2 WARNING messages shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
>
> Could you anyone please provide me some inputs for resolving the above issue?
>
> Many Thanks in advance
> --
> ___
> 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] Adding custom machine / dts files

[Daiane Angolini]

On Mon, Jan 14, 2019 at 9:08 AM Wiholm, Willie ActeSE
 wrote:
>
> Hello Prakash,
>
>
>
> The label in meta-fsl-arm is linux-imx-4.1.15
>
> Cloned from :
>
> repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b 
> imx-4.1-krogoth -m imx-4.1.15-2.0.0.xml
>
> repo sync
>
> $pwd
>
> /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx-4.1.15
>

Maybe this link can help somehow:
http://freescale.github.io/doc/release-notes/current/index.html#the-differences-between-project-name-and-freescale-release-name

And, if it's possible, it would be better to use some newer release/branch.

Daiane

>
>
> I realized that the problem was that there was another folder called “imx” 
> which I did not have in my custom-layer. Now I’m facing another problem when 
> compiling:
>
> | make[2]: *** No rule to make target 'e9697rsc6e5r.dts'.  Stop.
> | Makefile:146: recipe for target 'sub-make' failed
> | make[1]: *** [sub-make] Error 2
> | Makefile:24: recipe for target '__sub-make' failed
> | make: *** [__sub-make] Error 2
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile (log file is located at 
> /build/yocto/tmp_rsc61/work/rsc61-poky-linux-gnueabi/linux-fslc-imx/4.1-1.0.x+gitAUTOINC+59b38c323b-r0/temp/log.do_compile.11321)
> ERROR: Task 57 
> (/linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes-kernel/linux/linux-fslc-imx_4.1-1.0.x.bb,
>  do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1505 tasks of which 96 didn't need to be rerun 
> and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>   
> /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes-kernel/linux/linux-fslc-imx_4.1-1.0.x.bb,
>  do_compile
> Summary: There were 2 WARNING messages shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
>
>
> Should Yocto not compile the dts files into dtb itself? Do I need to find an 
> external program to first make them into dtb files before adding them into 
> the recipe-kernel?
>
>
>
> I also tried to add the patch with dts and dtsi directly in the 
> meta-fsl-arm/recipes-kernel/linux/linux-imx-4.1.15/imx/
>
> But it was not added in the build, is there anything additional i need to do 
> in order to apply my custom patches to the build?
>
> (I realize this is a bad habbit but I just want to verify that they work).
>
>
>
> Best Regards,
>
> Willie
>
> 
>
> Från: prakash m 
> Skickat: den 13 januari 2019 17:24:44
> Till: Wiholm, Willie ActeSE
> Kopia: meta-freescale@yoctoproject.org
> Ämne: Re: [meta-freescale] Adding custom machine / dts files
>
>
>
> Hi,
>
>
>
> I hope the naming convention is different from which you specified in your 
> custom layer, so kindly check in meta-freescale/recipes-kernel/linux for the 
> proper naming in freescale kernel recipes.
>
>
>
> I hope the proper naming would be linux-imx_4.1.15.bbappend.
>
>
>
>
>
> Thanks & Regards
>
> Pitchaiah M
>
>
>
>
>
> On Sun, 13 Jan, 2019, 13:59 Wiholm, Willie ActeSE  wrote:
>
> Hello prakash,
>
> Yes the meta-local is added in bblayers.
>
> Best regards,
>
> Willie
>
> Från: prakash m
>
> Skickat: söndag 13 januari 03:55
>
> Ämne: Re: [meta-freescale] Adding custom machine / dts files
>
> Till: Wiholm, Willie ActeSE
>
> Kopia: meta-freescale@yoctoproject.org
>
> Hi,
>
> Could you please check that your custom layer has been added to your 
> bblayer.conf which is under your build directory.
>
> Thanks & Regards
>
> Pitchaiah M
>
> On Sun, 13 Jan, 2019, 07:22 Wiholm, Willie ActeSE  wrote:
>
> Hello guys,
>
> (Sorry if i sent this in multiple lists)
>
> I'm trying to build an image for an custom board that is based in the 
> imx6dlsabresd, but I'm not sure how to add the custom dts files properly.
>
> First i built the kernel and created a patch in arch/arm/boot/dts where i 
> added my files.
>
> Then I created a meta-custom layer, in which i created :
>
> recipes-kernel/linux-imx-4.1.15/linux-imx-4.1.15.bbappend
>
> and the bbappend points to my patch.
>
> Then i created my own machine that is a copy of the imx6dlsabre in 
> conf/machine/custom.conf
>
> My question is, is this the right approach? The goal is to build full images 
> like "fsl-image-qt5" but I'm facing errors with core-image-minimal :
>
> No recipes available for:
>
>   
> /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-avalue/recipes-kernel/linux-imx-4.1.15/linux-imx-4.1.15.bbappend
>
> So i believe I'm making some fundamental errors.
>
> Any tips appreciated!
>
> Best Regards,
>
> Willie
>
> --
>
> ___
>
> 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] [PATCH] wic:mx8: Fix the image creation

[Daiane Angolini]

On Fri, Jan 11, 2019 at 2:39 PM Fabio Berton
 wrote:
>
> Hi Daiane!
>
> On Thu, Jan 10, 2019 at 10:36 PM Daiane Angolini
>  wrote:
> >
> > imx8 family boards use u-boot as boot loader in addition to some other
> > binaries. The final bootloader binary is gathered by mkimage into a file
> > called imx-boot.
> >
> > Add the wks file to create the wic image tailored for imx8 family.
> > Fix the symbolic link file create to point to imx-boot (so it works for
> > all the imx8 flavors).
> > Set the wks file as default for all imx8.
> >
> > Signed-off-by: Daiane Angolini 
> > ---
> >  conf/machine/include/imx-base.inc|  3 +++
> >  recipes-bsp/imx-mkimage/imx-boot_0.2.bb  |  2 +-
> >  recipes-bsp/u-boot/u-boot-imx_2017.03.bb |  2 +-
> >  wic/imx-imx-boot-bootpart.wks| 19 +++
> >  4 files changed, 24 insertions(+), 2 deletions(-)
> >  create mode 100644 wic/imx-imx-boot-bootpart.wks
> >
> > diff --git a/conf/machine/include/imx-base.inc 
> > b/conf/machine/include/imx-base.inc
> > index 572e8e5e..005b71e1 100644
> > --- a/conf/machine/include/imx-base.inc
> > +++ b/conf/machine/include/imx-base.inc
> > @@ -301,7 +301,10 @@ WKS_FILE_DEPENDS ?= " \
> >  bmap-tools-native \
> >  "
> >
> > +WKS_FILE_DEPENDS_mx8 += "imx-boot"
> > +
> >  SOC_DEFAULT_WKS_FILE ?= "imx-uboot-bootpart.wks"
> > +SOC_DEFAULT_WKS_FILE_mx8 ?= "imx-imx-boot-bootpart.wks"
>
> Why duplicate imx- prefix?

Because I replaced "uboot" by "imx-boot", which is the file name, and
didn't realized there were 2 imx.

What filename would you suggest?

Daiane
>
> >  SOC_DEFAULT_WKS_FILE_mxs ?= "imx-uboot-mxs-bootpart.wks.in"
> >
> >  WKS_FILE ?= "${SOC_DEFAULT_WKS_FILE}"
> > diff --git a/recipes-bsp/imx-mkimage/imx-boot_0.2.bb 
> > b/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
> > index 5ffddd0e..b232ed52 100644
> > --- a/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
> > +++ b/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
> > @@ -180,7 +180,7 @@ do_deploy() {
> >  install -m 0644 ${S}/${BOOT_CONFIG_MACHINE}-${target} ${DEPLOYDIR}
> >  done
> >  cd ${DEPLOYDIR}
> > -ln -sf ${BOOT_CONFIG_MACHINE}-${IMAGE_IMXBOOT_TARGET} 
> > ${BOOT_CONFIG_MACHINE}
> > +ln -sf ${BOOT_CONFIG_MACHINE}-${IMAGE_IMXBOOT_TARGET} ${BOOT_NAME}
> >  cd -
> >  }
> >  addtask deploy before do_build after do_compile
> > diff --git a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb 
> > b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
> > index 705ff164..86eca196 100644
> > --- a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
> > +++ b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
> > @@ -35,7 +35,7 @@ do_deploy_append_mx8m() {
> >  install -d ${DEPLOYDIR}/${BOOT_TOOLS}
> >  install -m 0777 
> > ${B}/${config}/arch/arm/dts/${UBOOT_DTB_NAME}  ${DEPLOYDIR}/${BOOT_TOOLS}
> >  install -m 0777 ${B}/${config}/tools/mkimage  
> > ${DEPLOYDIR}/${BOOT_TOOLS}/mkimage_uboot
> > -install -m 0777 ${B}/${config}/u-boot-nodtb.bin  
> > ${DEPLOYDIR}/${BOOT_TOOLS}/u-boot-nodtb.bin-${MACHINE}-${UBOOT_CONFIG}
> > +install -m 0777 ${B}/${config}/u-boot-nodtb.bin  
> > ${DEPLOYDIR}/${BOOT_TOOLS}/u-boot-nodtb.bin
> >  fi
> >  done
> >  unset  j
> > diff --git a/wic/imx-imx-boot-bootpart.wks b/wic/imx-imx-boot-bootpart.wks
> > new file mode 100644
> > index ..8bbcd6c0
> > --- /dev/null
> > +++ b/wic/imx-imx-boot-bootpart.wks
> > @@ -0,0 +1,19 @@
> > +# short-description: Create SD card image with a boot partition
> > +# long-description:
> > +# Create an image that can be written onto a SD card using dd for use
> > +# with i.MX SoC family
> > +# It uses u-boot
> > +#
> > +# The disk layout used is:
> > +#  - -- -- --
> > +# | | imx-boot | boot |rootfs   |
> > +#  - -- -- --
> > +# ^ ^  ^  ^
> > +# | |  |  |
> > +# 0 33kiB4MiB  16MiB + rootfs + IMAGE_EXTRA_SPACE (default 
> > 10MiB)
> > +#
> > +part u-boot --source rawcopy --sourceparams="file=imx-boot" --ondisk 
> > mmcblk --no-table --align 33
> > +part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat 
> > --label boot --active --align 4096 --size 16
> > +part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 
> > 4096
> > +
> > +bootloader --ptable msdos
> > \ No newline at end of file
> > --
> > 2.17.1
> >
> > --
> > ___
> > 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] [PATCH 01/41] fmc: update to c7576ab

[Daiane Angolini]

On Thu, Jan 10, 2019 at 1:50 PM Daiane Angolini  wrote:
>
> On Thu, Jan 10, 2019 at 12:50 PM C.r. Guo  wrote:
> >
> > From: Chunrong Guo 
> >
> > *update to lsdk 1812 tag
> > include the following changes:
> > c7576ab - Resolved compile warning on ubuntu with aarch64-linux-gnu-g++ v7.3
>
> Would you, please, rebase your patchset and send it again?
>
> I have faced conflicts at least on patch 6 and 11.

Hi Chunrong Guo,

I have created a PR with your v2. Could you, please take a look on this?

https://github.com/Freescale/meta-freescale/pull/34/commits

I saw some patches has [rocko] on subject, could you, please elaborate
what does it mean? Would it be a cherry pick to be backported to
rocko?

Thanks a lot,
Daiane

>
> Thanks in advance,
> Daiane
> >
> > Signed-off-by: Chunrong Guo 
> > ---
> >  dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb 
> > b/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> > index 4812ca3..cbf8e24 100644
> > --- a/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> > +++ b/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> > @@ -7,7 +7,7 @@ PR = "r2"
> >  DEPENDS = "libxml2 fmlib tclap"
> >
> >  SRC_URI = 
> > "git://source.codeaurora.org/external/qoriq/qoriq-components/fmc;nobranch=1"
> > -SRCREV = "09a497fe92aa6cf784140b9084bccf497700"
> > +SRCREV = "c7576ab7fb6fb09b68ebc40531e5452fc89e5cd5"
> >
> >  S = "${WORKDIR}/git"
> >
> > --
> > 2.7.4
> >
> > --
> > ___
> > 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] Status of i.MX8 support

[Daiane Angolini]

On Fri, Jan 11, 2019 at 6:13 AM Teemu K  wrote:
>
> On Thu, Jan 10, 2019 at 6:25 AM Teemu K  wrote:
> >
> > Hi,
> >
> > Interesting since linux-fslc-imx doesn't list mx8 as
> > 'compatible_machine', but linux-imx does.
> >
> > When setting preferred provider for virtual/kernel to linux-fslc-imx I
> > got this error:
> > "ERROR: Nothing PROVIDES 'virtual/kernel'
> > linux-imx PROVIDES virtual/kernel but was skipped:
> > PREFERRED_PROVIDER_virtual/kernel set to linux-fslc-imx, not
> > linux-imx"
>
> I updated to latest version of thud-branch which seems to be same as
> master. I saw that lots of new patches has been applied there
> including one that said to fix the u-boot/image creation issue.
>
> Yet today when I did fresh built no u-boot nor image was created. I
> was able to manually compile u-boot, but I'm not sure which command to
> use for manually forcing the wic - image creation.
Hi Teemu,

This is the line in BSP where the image file time is setup:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/tree/conf/machine/include/imx-base.inc#n289

You may have some configuration on top of the BSP which prevents it to
create the wic image.

Could you, please, test the following line to try to see which
configuration you have on your side?

bitbake -e | grep  IMAGE_FSTYPES

Regards,
Daiane
>
> -Teemu
> --
> ___
> 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] [PATCH] wic:mx8: Fix the image creation

[Daiane Angolini]

imx8 family boards use u-boot as boot loader in addition to some other
binaries. The final bootloader binary is gathered by mkimage into a file
called imx-boot.

Add the wks file to create the wic image tailored for imx8 family.
Fix the symbolic link file create to point to imx-boot (so it works for
all the imx8 flavors).
Set the wks file as default for all imx8.

Signed-off-by: Daiane Angolini 
---
 conf/machine/include/imx-base.inc|  3 +++
 recipes-bsp/imx-mkimage/imx-boot_0.2.bb  |  2 +-
 recipes-bsp/u-boot/u-boot-imx_2017.03.bb |  2 +-
 wic/imx-imx-boot-bootpart.wks| 19 +++
 4 files changed, 24 insertions(+), 2 deletions(-)
 create mode 100644 wic/imx-imx-boot-bootpart.wks

diff --git a/conf/machine/include/imx-base.inc 
b/conf/machine/include/imx-base.inc
index 572e8e5e..005b71e1 100644
--- a/conf/machine/include/imx-base.inc
+++ b/conf/machine/include/imx-base.inc
@@ -301,7 +301,10 @@ WKS_FILE_DEPENDS ?= " \
 bmap-tools-native \
 "
 
+WKS_FILE_DEPENDS_mx8 += "imx-boot"
+
 SOC_DEFAULT_WKS_FILE ?= "imx-uboot-bootpart.wks"
+SOC_DEFAULT_WKS_FILE_mx8 ?= "imx-imx-boot-bootpart.wks"
 SOC_DEFAULT_WKS_FILE_mxs ?= "imx-uboot-mxs-bootpart.wks.in"
 
 WKS_FILE ?= "${SOC_DEFAULT_WKS_FILE}"
diff --git a/recipes-bsp/imx-mkimage/imx-boot_0.2.bb 
b/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
index 5ffddd0e..b232ed52 100644
--- a/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
+++ b/recipes-bsp/imx-mkimage/imx-boot_0.2.bb
@@ -180,7 +180,7 @@ do_deploy() {
 install -m 0644 ${S}/${BOOT_CONFIG_MACHINE}-${target} ${DEPLOYDIR}
 done
 cd ${DEPLOYDIR}
-ln -sf ${BOOT_CONFIG_MACHINE}-${IMAGE_IMXBOOT_TARGET} 
${BOOT_CONFIG_MACHINE}
+ln -sf ${BOOT_CONFIG_MACHINE}-${IMAGE_IMXBOOT_TARGET} ${BOOT_NAME}
 cd -
 }
 addtask deploy before do_build after do_compile
diff --git a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb 
b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
index 705ff164..86eca196 100644
--- a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
+++ b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
@@ -35,7 +35,7 @@ do_deploy_append_mx8m() {
 install -d ${DEPLOYDIR}/${BOOT_TOOLS}
 install -m 0777 
${B}/${config}/arch/arm/dts/${UBOOT_DTB_NAME}  ${DEPLOYDIR}/${BOOT_TOOLS}
 install -m 0777 ${B}/${config}/tools/mkimage  
${DEPLOYDIR}/${BOOT_TOOLS}/mkimage_uboot
-install -m 0777 ${B}/${config}/u-boot-nodtb.bin  
${DEPLOYDIR}/${BOOT_TOOLS}/u-boot-nodtb.bin-${MACHINE}-${UBOOT_CONFIG}
+install -m 0777 ${B}/${config}/u-boot-nodtb.bin  
${DEPLOYDIR}/${BOOT_TOOLS}/u-boot-nodtb.bin
 fi
 done
 unset  j
diff --git a/wic/imx-imx-boot-bootpart.wks b/wic/imx-imx-boot-bootpart.wks
new file mode 100644
index ..8bbcd6c0
--- /dev/null
+++ b/wic/imx-imx-boot-bootpart.wks
@@ -0,0 +1,19 @@
+# short-description: Create SD card image with a boot partition
+# long-description:
+# Create an image that can be written onto a SD card using dd for use
+# with i.MX SoC family
+# It uses u-boot
+#
+# The disk layout used is:
+#  - -- -- --
+# | | imx-boot | boot |rootfs   |
+#  - -- -- --
+# ^ ^  ^  ^
+# | |  |  |
+# 0 33kiB4MiB  16MiB + rootfs + IMAGE_EXTRA_SPACE (default 10MiB)
+#
+part u-boot --source rawcopy --sourceparams="file=imx-boot" --ondisk mmcblk 
--no-table --align 33
+part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label 
boot --active --align 4096 --size 16
+part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4096
+
+bootloader --ptable msdos
\ No newline at end of file
-- 
2.17.1

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

[meta-freescale] [PATCH] wic:mx8: Fix the image creation

[Daiane Angolini]

I have just sent a patch for review, however it looks like my server
is a little bit busy and it looks like my patch is on hold somewhere.

Meanwhile, I create the PR:

https://github.com/Freescale/meta-freescale/pull/33/files

Could you, please, review my PR?

Some imx8 tapeout expects to find the bootloader at 32 offset, some
expects to find it at 33.

Can you think on a way to handle this without creating an additional
file and specifying the wks file on the machine file?

Thanks in advance,
Daiane
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [PATCH 01/41] fmc: update to c7576ab

[Daiane Angolini]

On Thu, Jan 10, 2019 at 12:50 PM C.r. Guo  wrote:
>
> From: Chunrong Guo 
>
> *update to lsdk 1812 tag
> include the following changes:
> c7576ab - Resolved compile warning on ubuntu with aarch64-linux-gnu-g++ v7.3

Would you, please, rebase your patchset and send it again?

I have faced conflicts at least on patch 6 and 11.

Thanks in advance,
Daiane
>
> Signed-off-by: Chunrong Guo 
> ---
>  dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb 
> b/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> index 4812ca3..cbf8e24 100644
> --- a/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> +++ b/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb
> @@ -7,7 +7,7 @@ PR = "r2"
>  DEPENDS = "libxml2 fmlib tclap"
>
>  SRC_URI = 
> "git://source.codeaurora.org/external/qoriq/qoriq-components/fmc;nobranch=1"
> -SRCREV = "09a497fe92aa6cf784140b9084bccf497700"
> +SRCREV = "c7576ab7fb6fb09b68ebc40531e5452fc89e5cd5"
>
>  S = "${WORKDIR}/git"
>
> --
> 2.7.4
>
> --
> ___
> 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] u-boot fslc support for imx8

[Daiane Angolini]

On Wed, Aug 29, 2018 at 12:39 PM Kevin Lannen  wrote:
>
> Thanks for pointing me to those patches Daiane.
>
>
> It looks like those patches all apply to u-boot-imx which is at version 
> 2017.03 still. Is anyone doing any work to bring i.MX8 support to the 
> u-boot-fslc so that a newer u-boot version such as 2017.11 can be used?
>

I don't think there is someone working on this already.

And u-boot-fslc is 2018.07, which already supports the EVK board [1]

http://git.denx.de/?p=u-boot.git;a=tree;f=arch/arm/mach-imx/mx8m;h=9563bfdf067ad23af59b298fa8a4f729631122e8;hb=8c5d4fd0ec222701598a27b26ab7265d4cee45a3

Daiane
>
> Thanks,
>
>
> Kevin
>
>
>
> ________
> From: angol...@gmail.com  on behalf of Daiane Angolini 
> 
> Sent: Wednesday, August 29, 2018 7:55:57 AM
> To: Kevin Lannen
> Cc: meta-freescale Mailing List
> Subject: Re: [meta-freescale] u-boot fslc support for imx8
>
> On Tue, Aug 28, 2018 at 8:59 PM Kevin Lannen  wrote:
> >
> > Hi all,
> >
> >
> > I am trying to use mender on an i.MX8M system-on-module to handle 
> > over-the-air updates. I ran into issues with the meta-fsl-bsp-release which 
> > uses the imx-uboot that is too old.
> >
> >
> > Is there work being done on upstreaming the i.MX8M bsp from 
> > meta-fsl-bsp-release into the meta-freescale layer? If so when is that 
> > likely to be available?
> >
>
> There are patches on patchwork (for example [1]) but I understand they
> are still being reviewed.
>
> [1] https://patchwork.openembedded.org/patch/153411/
>
>
> Daiane
> >
> > I am happy to help out with some testing on it and to help out with the 
> > upstreaming if someone could give me some guidance on where to start with 
> > it. I am pretty new to Yocto so this could be good for me to learn about.
> >
> >
> > Thanks,
> >
> >
> > Kevin Lannen
> >
> > --
> > ___
> > 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] u-boot fslc support for imx8

[Daiane Angolini]

On Tue, Aug 28, 2018 at 8:59 PM Kevin Lannen  wrote:
>
> Hi all,
>
>
> I am trying to use mender on an i.MX8M system-on-module to handle 
> over-the-air updates. I ran into issues with the meta-fsl-bsp-release which 
> uses the imx-uboot that is too old.
>
>
> Is there work being done on upstreaming the i.MX8M bsp from 
> meta-fsl-bsp-release into the meta-freescale layer? If so when is that likely 
> to be available?
>

There are patches on patchwork (for example [1]) but I understand they
are still being reviewed.

[1] https://patchwork.openembedded.org/patch/153411/


Daiane
>
> I am happy to help out with some testing on it and to help out with the 
> upstreaming if someone could give me some guidance on where to start with it. 
> I am pretty new to Yocto so this could be good for me to learn about.
>
>
> Thanks,
>
>
> Kevin Lannen
>
> --
> ___
> 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] Significance of the fslc vendor field in arm-fslc-linux-gnueabi-gcc

[Daiane Angolini]

On Tue, Aug 28, 2018 at 9:01 AM Phil Williams  wrote:
>
> Hello,
>
> What is the significance of the vendor being set to fslc in the
> toolchain? Is it simply a label, or does it have some compatibility
> differences (compared with -unknown-).

I don't think there is any significant change. But I would recommend
you make some tests for your use-case.

Daiane
>
> The reason I ask is because I was wondering if there would be any issues
> using off the shelf Rust or Go compilers and specifying the target as
> arm-unknown-linux-gnueabi.
>
> Thanks,
>
> Phil
>
> --
> ___
> 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] GStreamer1.0 imx6-dlsabresd how to

[Daiane Angolini]

On Mon, Aug 27, 2018 at 5:27 AM Mauro Ziliani  wrote:
>
> I cannot move to Rocko or Sumo due to board supports.
> I need to play an mp4 video over /dev/video17 using imx pipeline.
> But it is not so clear for me how to do that via gst-lanuch-1.0

I don't remember when gstreamer was migrated from gst0.1 to gst1.0.

You can try to backport the gst1.0 support, or include support for
your board on newer branches.

Or you are looking for help on how to create a gstreamer pipeline?

Daiane
>
> Then I need to port the gst-launch-1.0 pipeline into my sw base on Qt5.6
>
> MZ
>
> Il 24/08/2018 13:50, Daiane Angolini ha scritto:
> > On Thu, Aug 23, 2018 at 1:26 PM Mauro Ziliani  wrote:
> >> Hi all.
> >>
> >> I need some explanation about GStreamer 1.0 over imx6dl-sabresd and
> >> Jethro/Krogoth because I'd like to use IPV/VPU to play an H264 video.
> > Could you elaborate your question.
> >
> > I think the main recommendation now is to use rocko or sumo instead of
> > old jethro or krogoth
> >
> > Best Regards,
> > Daiane
> >> I developing my apps with qt-5.6 on x11 and fsl-imx-x11 dsitro.
> >>
> >>
> >> Thanks all
> >>
> >>  Mauro
> >>
> >> --
> >> ___
> >> 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] Preferred kernel for mx7 machine

[Daiane Angolini]

On Fri, Aug 24, 2018 at 9:46 AM Matija Tuđan  wrote:
>
> Hi Daiane,
>
> Let me redefine my question: does the tree from codeaurora provide better 
> support for mx7 machines?

It depends on what you consider to be best and which support. That's
why this kind of question is not useful.

> I am asking this because mx7 is not set as compatible machine in 
> linux-fslc_4.17.bb recipe. This is where my confusion came from.

I'm sorry to take so long to understand it. I think it's a mistake.
Would you mind sending a patch to add mx7 as compatible machine?

Daiane
>
> Best Regards,
> Matija Tuđan
> Senior Hardware Developer
> Mobilisis d.o.o.
> +385 99 311 5473
>
> -Original Message-----
> From: angol...@gmail.com  On Behalf Of Daiane Angolini
> Sent: Friday, August 24, 2018 1:48 PM
> To: Matija Tuđan 
> Cc: meta-freescale Mailing List 
> Subject: Re: [meta-freescale] Preferred kernel for mx7 machine
>
> On Fri, Aug 24, 2018 at 2:27 AM Matija Tuđan  wrote:
> >
> > Hello,
> >
> > What is the recommended kernel tree for i.MX7 based machines?
> >
> > The linux-imx repo from codeaurora has the 4.9.88 as newest version:
> > https://source.codeaurora.org/external/imx/linux-imx
> >
> > Additionally, mx7 is not set as compatible machine in linux-fslc_4.17.bb 
> > recipe which is based on linux-fslc repo:
> >
> > https://github.com/Freescale/linux-fslc
> >
> > which should be forked from mainline kernel repo.
> >
>
> Yes, it is
>
> >
> > But I have tested the linux-stable repo and 4.18.y version and it works 
> > fine:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> >
> In this case, update patches are welcome.
>
> >
> >
> > What are the key differences between codeaurora’s repo which provides older 
> > kernel version and linux-fslc/linux-stable repos.
> >
> > Which repo should be used when dealing with i.MX7 based machines?
>
> I think, because you are asking, you should start using the kernel from 
> codeaurora. The difference is huge (mainly because of version number, but 
> also the number of available drivers)
>
> If you think you are going to submit tickets to NXP (if you are in contact 
> with a FAE or using [1]). However, if you prefer to ask for help in the Linux 
> Kernel mailing list, the recomendation is to use the latest kernel version 
> (linux-fslc would be an starting point)
>
> However, the answer to the question "which kernel should I use" is extremely 
> personal and driven by use case. If you really think you need help deciding 
> this, I recommend you to contact a professional service from a consultant.
>
> [1]https://community.nxp.com/community/imx
>
> Best Regards,
> Daiane
> >
> >
> >
> > Best regards,
> >
> > Matija
> >
> >
> >
> >
> > Matija Tuđan
> > Senior Hardware Developer
> >
> >
> >
> > Mobilisis d.o.o.
> > Varaždinska ulica br. 8, II. odvojak
> > 42000 Varaždin - Jalkovec, Croatia
> >
> >
> >
> >
> >
> > m.
> >
> >
> >
> >
> >
> > +385 99 311 5473
> >
> > t.
> >
> > +385 42 311 777
> >
> > f.
> >
> > +385 42 493 955
> >
> > w.
> >
> > www.mobilisis.hr
> >
> >
> >
> > This mail is from Mobilisis d.o.o. and may contain confidential business 
> > information. It is intended solely for the use of the individual to whom it 
> > is addressed. If you are not the intended recipient, please contact the 
> > sender and delete this message and any attachment from your system. 
> > Unauthorized publication, use, dissemination, forwarding, printing or 
> > copying of this email and it's associated attachments is strictly 
> > prohibited.
> >
> >
> > Please consider the environment before printing this email. Thank you!
> >
> >
> >
> >
> >
> > --
> > ___
> > 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] [yocto] Howto overwrite CXXFLAGS in SDK Environment

[Daiane Angolini]

On Fri, Aug 10, 2018 at 5:41 AM Nikhil  wrote:
>
> Hello community,
>
> I am using Freescale community BSP - rocko release and have built and
> installed SDK.
> Is there a way to remove -g flag from being in the list of default
> options  for CXXFLAGS.  ?  Thanks.
>

I think this is a good starting point:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-CXXFLAGS

Daiane
> Regards
> Nikhil
> --
> ___
> yocto mailing list
> yo...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] U-Boot and Video Issues

[Daiane Angolini]

On Fri, Aug 10, 2018 at 2:33 PM Dan Riegsecker <1baldg...@gmail.com> wrote:
>
> I'm working with an NXP SABRESD board which has an i.MX 6Q processor, 
> building images with the Yocto Project, Sumo version. I am building the 
> fsl-image-multimedia with the settings listed below. These images are being 
> deployed to an SD card and boot from that SD card.
>
> MACHINE ??= 'imx6qdlsabresd'
> DISTRO ?= 'fslc-framebuffer'
>
> The U-Boot that is being built is u-boot-fslc from 
> https://github.com/Freescale/u-boot-fslc and branch 2018.07+fslc. I am not 
> seeing the dynamically generated video_args being passed to the the kernel 
> command line via the mmcargs U-Boot environment variable. When I examine the 
> u-boot-fslc/include/configs/mx6sabre_common.h file I see the following at 
> line 112.
>
> "mmcargs=setenv bootargs console=${console},${baudrate} " \
> "root=PARTUUID=${uuid} rootwait rw\0" \
> VIDEO_ARGS "\0" \
>
> Wouldn't the NULL termination at the end of "rootwait rw" have the effect of 
> not allowing the VIDEO_ARGS to be appended to the mmcargs and therefore not 
> appended to the bootargs? When I cat /proc/cmdline on the booted system, I do 
> not see any video settings passed to the kernel.
>

Would you, please, generate and test a patch for this issue?

> Not seeing any video settings being sent to the kernel, I changed my mmcargs 
> as listed below.
>
> setenv mmcargs 'setenv bootargs console=${console},${baudrate} 
> root=PARTUUID=${uuid} rootwait rw ${video_args}'
> saveenv
> reset
>
> Now if I have a display connected the the HDMI port, I have tried two 
> different displays, the kernel will not run and does not output anything, 
> like a panic, over the serial console. When I boot the Sabre board with 
> nothing plugged into the HDMI port the kernel loads and the video setting can 
> be seen in /proc/cmdline. I am able to boot the NXP images, version 
> imx-4.9.88-2.0.0_ga, with the same board and HDMI displays, having video 
> working as expected. What would be causing the kernel to not load when an 
> HDMI display is connected and video settings are passed to the the kernel via 
> the command line, using only the Freescale community layers of Yocto?
>

Can you, please, confirm if it's this issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6703


Best Regards,
Daiane

> Any advice or suggestions would be greatly appreciated.
>
> Thanks,
> Dan
>
>
> --
> ___
> 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] GStreamer1.0 imx6-dlsabresd how to

[Daiane Angolini]

On Thu, Aug 23, 2018 at 1:26 PM Mauro Ziliani  wrote:
>
> Hi all.
>
> I need some explanation about GStreamer 1.0 over imx6dl-sabresd and
> Jethro/Krogoth because I'd like to use IPV/VPU to play an H264 video.

Could you elaborate your question.

I think the main recommendation now is to use rocko or sumo instead of
old jethro or krogoth

Best Regards,
Daiane
>
> I developing my apps with qt-5.6 on x11 and fsl-imx-x11 dsitro.
>
>
> Thanks all
>
> Mauro
>
> --
> ___
> 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] Preferred kernel for mx7 machine

[Daiane Angolini]

On Fri, Aug 24, 2018 at 2:27 AM Matija Tuđan  wrote:
>
> Hello,
>
> What is the recommended kernel tree for i.MX7 based machines?
>
> The linux-imx repo from codeaurora has the 4.9.88 as newest version:
> https://source.codeaurora.org/external/imx/linux-imx
>
> Additionally, mx7 is not set as compatible machine in linux-fslc_4.17.bb 
> recipe which is based on linux-fslc repo:
>
> https://github.com/Freescale/linux-fslc
>
> which should be forked from mainline kernel repo.
>

Yes, it is

>
> But I have tested the linux-stable repo and 4.18.y version and it works fine:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>
In this case, update patches are welcome.

>
>
> What are the key differences between codeaurora’s repo which provides older 
> kernel version and linux-fslc/linux-stable repos.
>
> Which repo should be used when dealing with i.MX7 based machines?

I think, because you are asking, you should start using the kernel
from codeaurora. The difference is huge (mainly because of version
number, but also the number of available drivers)

If you think you are going to submit tickets to NXP (if you are in
contact with a FAE or using [1]). However, if you prefer to ask for
help in the Linux Kernel mailing list, the recomendation is to use the
latest kernel version (linux-fslc would be an starting point)

However, the answer to the question "which kernel should I use" is
extremely personal and driven by use case. If you really think you
need help deciding this, I recommend you to contact a professional
service from a consultant.

[1]https://community.nxp.com/community/imx

Best Regards,
Daiane
>
>
>
> Best regards,
>
> Matija
>
>
>
>
> Matija Tuđan
> Senior Hardware Developer
>
>
>
> Mobilisis d.o.o.
> Varaždinska ulica br. 8, II. odvojak
> 42000 Varaždin - Jalkovec, Croatia
>
>
>
>
>
> m.
>
>
>
>
>
> +385 99 311 5473
>
> t.
>
> +385 42 311 777
>
> f.
>
> +385 42 493 955
>
> w.
>
> www.mobilisis.hr
>
>
>
> This mail is from Mobilisis d.o.o. and may contain confidential business 
> information. It is intended solely for the use of the individual to whom it 
> is addressed. If you are not the intended recipient, please contact the 
> sender and delete this message and any attachment from your system. 
> Unauthorized publication, use, dissemination, forwarding, printing or copying 
> of this email and it's associated attachments is strictly prohibited.
>
>
> Please consider the environment before printing this email. Thank you!
>
>
>
>
>
> --
> ___
> 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] [PATCH] imx-alsa-plugins: Make imx7ulp a compatible machine

[Daiane Angolini]

>From [1] we know the imx-alsa-plugins_1.0.26 does support all imx7, and
it is defined in the BSP as MACHINE_EXTRA_RRECOMMENDS, so this patch add
imx7ulp as compatible.

It also fixes the following error (when building for imx7ulpevk):

ERROR: Nothing RPROVIDES 'imx-alsa-plugins' (but
/home/daiane/code/yocto/master/sources/poky/meta/recipes-core/images/core-image-base.bb,
/home/daiane/code/yocto/master/sources/poky/meta/recipes-core/packagegroups/packagegroup-base.bb
RDEPENDS on or otherwise requires it)
imx-alsa-plugins was skipped: incompatible with machine imx7ulpevk (not
in COMPATIBLE_MACHINE)

[1]
https://source.codeaurora.org/external/imx/meta-fsl-bsp-release/tree/imx/meta-bsp/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb?h=rocko-4.9.88-2.0.0_ga

Signed-off-by: Daiane Angolini 
---
 recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb 
b/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
index 834b2971..9b30911c 100644
--- a/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
+++ b/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
@@ -35,5 +35,5 @@ FILES_${PN} += "${libdir}/alsa-lib/libasound_*.so"
 FILES_${PN}-dbg += "${libdir}/alsa-lib/.debug"
 FILES_${PN}-dev += "${libdir}/alsa-lib/*.la"
 
-COMPATIBLE_MACHINE = "(mx6dl|mx6q|mx6sl|mx6sx|mx6ul|mx6ull|mx7d)"
+COMPATIBLE_MACHINE = "(mx6dl|mx6q|mx6sl|mx6sx|mx6ul|mx6ull|mx7d|mx7ulp)"
 PACKAGE_ARCH = "${MACHINE_SOCARCH}"
-- 
2.11.0

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

[meta-freescale] [PATCH v2] u-boot-fslc: Add bison-native dependency for 2018.07

[Daiane Angolini]

The u-boot-fslc now depends on bison to complete the build.

This patch fixes the following error message:

| rm -f .tmp_quiet_recordmcount
| make -f
/home/daiane/code/yocto/master/build/tmp/work/imx7dsabresd-fslc-linux-gnueabi/u-boot-fslc/v2018.07+gitAUTOINC+bc558729a7-r0/git/scripts/Makefile.build
obj=scripts/kconfig mx7dsabresd_config
|   bison -oscripts/kconfig/zconf.tab.c -t -l
/home/daiane/code/yocto/master/build/tmp/work/imx7dsabresd-fslc-linux-gnueabi/u-boot-fslc/v2018.07+gitAUTOINC+bc558729a7-r0/git/scripts/kconfig/zconf.y
| /bin/sh: 1: bison: not found
| scripts/Makefile.lib:228: recipe for target
'scripts/kconfig/zconf.tab.c' failed
| make[2]: *** [scripts/kconfig/zconf.tab.c] Error 12

Signed-off-by: Daiane Angolini 
---
 recipes-bsp/u-boot/u-boot-fslc_2018.07.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb 
b/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
index 5659e16c..6c391ad3 100644
--- a/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
+++ b/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
@@ -6,7 +6,7 @@ order to provide support for some backported features and 
fixes, or because it \
 was submitted for revision and it takes some time to become part of a stable \
 version, or because it is not applicable for upstreaming."
 
-DEPENDS_append = " dtc-native"
+DEPENDS_append = " dtc-native bison-native"
 
 PROVIDES += "u-boot"
 
-- 
2.11.0

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

Re: [meta-freescale] [PATCH] u-boot-fslc: Add bison-native dependency for 2018.07

[Daiane Angolini]

On Wed, Aug 22, 2018 at 4:42 PM Fabio Estevam  wrote:
>
> On Wed, Aug 22, 2018 at 1:13 PM, Daiane Angolini
>  wrote:
> > Signed-off-by: Daiane Angolini 
>
> Some explanation in the commit log would be helpfu.

Fabio, do you remember exactly when (or which version) bison
dependency was included? I could include this information in the
commit log, but I don' t remember.

I can also re-generate the log error and include in the commit log.

But basically the explanation is "now u-boot wants bison during compilation"

Thanks in advance,
Daiane

> --
> ___
> 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] [PATCH] u-boot-fslc: Add bison-native dependency for 2018.07

[Daiane Angolini]

Signed-off-by: Daiane Angolini 
---
 recipes-bsp/u-boot/u-boot-fslc_2018.07.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb 
b/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
index 5659e16c..6c391ad3 100644
--- a/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
+++ b/recipes-bsp/u-boot/u-boot-fslc_2018.07.bb
@@ -6,7 +6,7 @@ order to provide support for some backported features and 
fixes, or because it \
 was submitted for revision and it takes some time to become part of a stable \
 version, or because it is not applicable for upstreaming."
 
-DEPENDS_append = " dtc-native"
+DEPENDS_append = " dtc-native bison-native"
 
 PROVIDES += "u-boot"
 
-- 
2.11.0

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

[meta-freescale] help with bitbake-metadata2doc

[Daiane Angolini]

I was working to upgrade the Release Notes to include the changes from
Sumo and I got this crash.

Can you, please, help me how to solve this?

Thanks in advance,
Daiane

ERROR: 
/media/disco2/yocto/rocko/sources/poky/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb:
Error executing a python function in
:## | ETA:  0:00:01

The stack trace of python calls that resulted in this exception/failure was:
File: '', lineno: 4, function: 
 
0001:__anon_22__media_disco2_yocto_rocko_sources_poky_meta_conf_machine_include_arm_feature_arm_thumb_inc(d)
 
0002:__anon_25__media_disco2_yocto_rocko_sources_poky_meta_classes_patch_bbclass(d)
 
0003:__anon_160__media_disco2_yocto_rocko_sources_poky_meta_classes_base_bbclass(d)
 *** 
0004:__anon_686__media_disco2_yocto_rocko_sources_poky_meta_classes_base_bbclass(d)
 
0005:__anon_64__media_disco2_yocto_rocko_sources_meta_freescale_classes_fsl_dynamic_packagearch_bbclass(d)
 
0006:__anon_1305__media_disco2_yocto_rocko_sources_poky_meta_classes_insane_bbclass(d)
 
0007:__anon_250__media_disco2_yocto_rocko_sources_poky_meta_classes_package_bbclass(d)
 
0008:__anon_711__media_disco2_yocto_rocko_sources_poky_meta_classes_package_rpm_bbclass(d)
File: '/media/disco2/yocto/rocko/sources/poky/meta/classes/base.bbclass',
lineno: 399, function:
__anon_686__media_disco2_yocto_rocko_sources_poky_meta_classes_base_bbclass
 0395:#
 0396:# PACKAGECONFIG ??= ""
 0397:# PACKAGECONFIG[foo] =
"--enable-foo,--disable-foo,foo_depends,foo_runtime_depends,foo_runtime_recommends"
 0398:pkgconfigflags = d.getVarFlags("PACKAGECONFIG") or {}
 *** 0399:if pkgconfigflags:
 0400:pkgconfig = (d.getVar('PACKAGECONFIG') or "").split()
 0401:pn = d.getVar("PN")
 0402:
 0403:mlprefix = d.getVar("MLPREFIX")
File: '/media/disco2/yocto/rocko/sources/poky/bitbake/lib/bb/data_smart.py',
lineno: 874, function: getVarFlags
 0870:flags = {}
 0871:
 0872:if local_var:
 0873:for i in local_var:
 *** 0874:if i.startswith("_") and not internalflags:
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] The sumo branch of meta-freescale

[Daiane Angolini]

On Wed, May 23, 2018 at 3:17 PM, Otavio Salvador
 wrote:

>
> i.MX8 is a huge addition and once we branch sumo it is going to be too
> risk to backport. I don't have a big problem in let it for next
> release but it is something people must to agree uppon it.

I agree.

I think we can focus on sumo right now and think about imx8 later.

Daiane

>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9 9981-7854  Mobile: +1 (347) 903-9750
> --
> ___
> 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] [PATCH 2/2] wic: Fix image generation for i.MX MXS SoC family

[Daiane Angolini]

On Thu, Apr 26, 2018 at 1:53 PM, Otavio Salvador
<otavio.salva...@ossystems.com.br> wrote:
> On Thu, Apr 26, 2018 at 1:19 PM Daiane Angolini <daiane.l...@gmail.com>
> wrote:
> ...
>> I think to remove the word "bootstream" is enough.
>
> I sent a v2. Please take a look.

v2 is good to me. Thanks a lot

Daiane

>
> --
> 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] [PATCH 2/2] wic: Fix image generation for i.MX MXS SoC family

[Daiane Angolini]

On Wed, Apr 25, 2018 at 10:31 AM, Otavio Salvador
<otavio.salva...@ossystems.com.br> wrote:
> On Tue, Apr 24, 2018 at 7:40 PM, Daiane Angolini <daiane.l...@gmail.com> 
> wrote:
>> On Tue, Apr 24, 2018 at 3:51 PM, Otavio Salvador
>> <ota...@ossystems.com.br> wrote:
>>> The image needs to use the U-Boot, bootstream, generated for the uSD
>>> card and a dependency on that must be added so we get it deployed
>>> before using the file. Besides that, the fstype needs to be changed so
>>> it sets the partition mark allowing the bootrom to find it.
>>
>> I have tested the patch set and it worked very fine to me.
>>
>> I found nothing to comment in the patches, however, Otavio, when you
>> apply those, would you, please, clarity what you meant by:
>>
>> "The image needs to use the U-Boot, bootstream, generated for the uSD"
>>
>> I think the comma might be replaced by an "and"
>
> Probably the commit log can be improved.
>
> What I meant is that the image needs to use the u-boot binary that
> goes over the mxsboot specifically tailored for use with the SD cards.
> The binary needs to be ready for use by the wic before the wic image
> generation is done, hence the new dependency.
>
> How do you think we can improve it?

I think to remove the word "bootstream" is enough.

Daiane
>
> --
> 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] [PATCH 2/2] wic: Fix image generation for i.MX MXS SoC family

[Daiane Angolini]

On Tue, Apr 24, 2018 at 3:51 PM, Otavio Salvador
 wrote:
> The image needs to use the U-Boot, bootstream, generated for the uSD
> card and a dependency on that must be added so we get it deployed
> before using the file. Besides that, the fstype needs to be changed so
> it sets the partition mark allowing the bootrom to find it.

I have tested the patch set and it worked very fine to me.

I found nothing to comment in the patches, however, Otavio, when you
apply those, would you, please, clarity what you meant by:

"The image needs to use the U-Boot, bootstream, generated for the uSD"

I think the comma might be replaced by an "and"

Daiane

>
> Signed-off-by: Otavio Salvador 
> ---
>
>  classes/image_types_fsl.bbclass  | 5 +
>  conf/machine/include/imx-base.inc| 2 +-
>  ...-uboot-mxs-bootpart.wks => imx-uboot-mxs-bootpart.wks.in} | 2 +-
>  wic/{imx-uboot-mxs.wks => imx-uboot-mxs.wks.in}  | 2 +-
>  4 files changed, 8 insertions(+), 3 deletions(-)
>  rename wic/{imx-uboot-mxs-bootpart.wks => imx-uboot-mxs-bootpart.wks.in} 
> (83%)
>  rename wic/{imx-uboot-mxs.wks => imx-uboot-mxs.wks.in} (79%)
>
> diff --git a/classes/image_types_fsl.bbclass b/classes/image_types_fsl.bbclass
> index 4709af95..65b2a9a8 100644
> --- a/classes/image_types_fsl.bbclass
> +++ b/classes/image_types_fsl.bbclass
> @@ -312,3 +312,8 @@ IMAGE_TYPEDEP_sdcard_append = " \
>  ${@bb.utils.contains('IMAGE_FSTYPES', 'uboot-mxsboot-sdcard', 
> 'uboot-mxsboot-sdcard', '', d)} \
>  ${@bb.utils.contains('IMAGE_FSTYPES', 'barebox-mxsboot-sdcard', 
> 'barebox-mxsboot-sdcard', '', d)} \
>  "
> +
> +do_image_wic[depends] += " \
> +${@bb.utils.contains('IMAGE_FSTYPES', 'uboot-mxsboot-sdcard', \
> +  
> '${IMAGE_BASENAME}:do_image_uboot_mxsboot_sdcard', '', d)} \
> +"
> diff --git a/conf/machine/include/imx-base.inc 
> b/conf/machine/include/imx-base.inc
> index ab9fcf30..50de9a70 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -257,7 +257,7 @@ WKS_FILE_DEPENDS ?= " \
>  "
>
>  SOC_DEFAULT_WKS_FILE ?= "imx-uboot-bootpart.wks"
> -SOC_DEFAULT_WKS_FILE_mxs ?= "imx-uboot-mxs-bootpart.wks"
> +SOC_DEFAULT_WKS_FILE_mxs ?= "imx-uboot-mxs-bootpart.wks.in"
>
>  WKS_FILE ?= "${SOC_DEFAULT_WKS_FILE}"
>
> diff --git a/wic/imx-uboot-mxs-bootpart.wks 
> b/wic/imx-uboot-mxs-bootpart.wks.in
> similarity index 83%
> rename from wic/imx-uboot-mxs-bootpart.wks
> rename to wic/imx-uboot-mxs-bootpart.wks.in
> index 0e96ab3a..29fe1a50 100644
> --- a/wic/imx-uboot-mxs-bootpart.wks
> +++ b/wic/imx-uboot-mxs-bootpart.wks.in
> @@ -12,7 +12,7 @@
>  # | | |  |
>  # 0 1kiB4MiB  16MiB + rootfs + IMAGE_EXTRA_SPACE (default 10MiB)
>  #
> -part u-boot --source rawcopy --sourceparams="file=u-boot.sb" --ondisk mmcblk 
> --no-table --align 1
> +part u-boot --source rawcopy 
> --sourceparams="file=${IMAGE_NAME}.rootfs.uboot-mxsboot-sdcard" --ondisk 
> mmcblk --fstype=ontrackdm6aux3 --align 1
>  part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label 
> boot --active --align 4096 --size 16
>  part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 
> 4096
>
> diff --git a/wic/imx-uboot-mxs.wks b/wic/imx-uboot-mxs.wks.in
> similarity index 79%
> rename from wic/imx-uboot-mxs.wks
> rename to wic/imx-uboot-mxs.wks.in
> index 0f5c51d4..ae30c903 100644
> --- a/wic/imx-uboot-mxs.wks
> +++ b/wic/imx-uboot-mxs.wks.in
> @@ -12,7 +12,7 @@
>  # | | |  |
>  # 0 1kiB4MiB + rootfs + IMAGE_EXTRA_SPACE (default 10MiB)
>  #
> -part u-boot --source rawcopy --sourceparams="file=u-boot.sb" --ondisk mmcblk 
> --no-table --align 1
> +part u-boot --source rawcopy 
> --sourceparams="file=${IMAGE_NAME}.rootfs.uboot-mxsboot-sdcard" --ondisk 
> mmcblk --fstype=ontrackdm6aux3 --align 1
>  part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 
> 4096
>
>  bootloader --ptable msdos
> --
> 2.17.0
>
> --
> ___
> 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] [PATCH][distro] distro/fsl-framebuffer: Remove vulkan distro feature

[Daiane Angolini]

meta-poky commit 6016ec177af2406cacfeb3276dfcb8bfc3df8fce enabled
vulkan by default. As framebuffer distro doesn't have x11 or wayland,
we need to remove vulkan distro feature.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/distro/fsl-framebuffer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/fsl-framebuffer.conf b/conf/distro/fsl-framebuffer.conf
index cb5feae..7e44259 100644
--- a/conf/distro/fsl-framebuffer.conf
+++ b/conf/distro/fsl-framebuffer.conf
@@ -6,4 +6,4 @@ DISTRO = "fsl-framebuffer"
 DISTRO_NAME = "FSL FrameBuffer"
 
 # Remove conflicting backends.
-DISTRO_FEATURES_remove = "x11 wayland directfb "
+DISTRO_FEATURES_remove = "x11 wayland directfb vulkan "
-- 
2.7.4

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

[meta-freescale] [PATCH 2/2] distro/fsl-base: Configure u-boot provider properly

[Daiane Angolini]

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/distro/include/fsl-base.inc | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/conf/distro/include/fsl-base.inc b/conf/distro/include/fsl-base.inc
index 55e7982..a930252 100644
--- a/conf/distro/include/fsl-base.inc
+++ b/conf/distro/include/fsl-base.inc
@@ -20,6 +20,13 @@ PREFERRED_PROVIDER_u-boot_mx6ul = "u-boot-imx"
 PREFERRED_PROVIDER_u-boot_mx6ull = "u-boot-imx"
 PREFERRED_PROVIDER_u-boot_mx7d = "u-boot-imx"
 
+UBOOT_MACHINE_mx6 = "mx6qsabresd_config"
+UBOOT_SUFFIX_mx6 = "imx"
+SPL_BINARY_mx6 = ""
+UBOOT_MAKE_TARGET_mx6 = "u-boot.imx"
+WKS_FILE = "imx-uboot-bootpart.wks"
+
+
 PREFERRED_PROVIDER_virtual/bootloader_mx6dl = "u-boot-imx"
 PREFERRED_PROVIDER_virtual/bootloader_mx6q = "u-boot-imx"
 PREFERRED_PROVIDER_virtual/bootloader_mx6sl = "u-boot-imx"
-- 
2.7.4

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

[meta-freescale] [PATCH][distro] distro/fsl-framebuffer: Remove vulkan distro feature

[Daiane Angolini]

meta-poky commit 6016ec177af2406cacfeb3276dfcb8bfc3df8fce enabled
vulkan by default. As framebuffer distro doesn't have x11 or wayland,
we need to remove vulkan distro feature.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/distro/fsl-framebuffer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/fsl-framebuffer.conf b/conf/distro/fsl-framebuffer.conf
index cb5feae..7e44259 100644
--- a/conf/distro/fsl-framebuffer.conf
+++ b/conf/distro/fsl-framebuffer.conf
@@ -6,4 +6,4 @@ DISTRO = "fsl-framebuffer"
 DISTRO_NAME = "FSL FrameBuffer"
 
 # Remove conflicting backends.
-DISTRO_FEATURES_remove = "x11 wayland directfb "
+DISTRO_FEATURES_remove = "x11 wayland directfb vulkan "
-- 
2.7.4

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

[meta-freescale] [PATCH][distro] distro/fsl-framebuffer: Remove vulkan distro feature

[Daiane Angolini]

meta-poky commit 6016ec177af2406cacfeb3276dfcb8bfc3df8fce enabled
vulkan by default. As framebuffer distro doesn't have x11 or wayland,
we need to remove vulkan distro feature.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/distro/fsl-framebuffer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/fsl-framebuffer.conf b/conf/distro/fsl-framebuffer.conf
index cb5feae..7e44259 100644
--- a/conf/distro/fsl-framebuffer.conf
+++ b/conf/distro/fsl-framebuffer.conf
@@ -6,4 +6,4 @@ DISTRO = "fsl-framebuffer"
 DISTRO_NAME = "FSL FrameBuffer"
 
 # Remove conflicting backends.
-DISTRO_FEATURES_remove = "x11 wayland directfb "
+DISTRO_FEATURES_remove = "x11 wayland directfb vulkan "
-- 
2.7.4

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

Re: [meta-freescale] [3rdparty] imx7s-warp reference support: How to add additional firmware blobs?

[Daiane Angolini]

On Thu, Nov 23, 2017 at 11:36 AM, Simon Hughes  wrote:
> Summary
>
>
>
> What’s the **right way** to add additional firmware blobs to
> MACHINE=imx7s-warp DISTRO=xxx images, so we follow a sensible pattern? There
> are at least 2 alternatives:
>
> -  The imx6sl-warp.conf way which leverages openembedded-core
> linux-firmware_git.bb.
>
> -  The imx7s-warp.conf way which is standalone (doesn’t leverage
> openembedded-core linux-firmware_git.bb).
>
>
>
> We’re working on imx7s-warp support in our own tree but want to be able to
> upstream the changes to the community as a reference implementation rather
> than bodging the job.
>

Would it be a new different machine?

>
>
> Details
>
>
>
> To help work through the issues, let’s assume we have:
>
> -  a layer meta-foo for storing .bbappend recipes etc.
>
> -  a machine feature “bar” which we want people to be able to turn
> on/off in the their images using MACHINE_FEATURES += “ bar”
>
> -  distros include packagegroup-core and packagegroup-base (so that
> processing can be hooked).
>
>
>
> Aim: To install the following firmware files into the image :
>
> - chip vendor license agreement e.g. LICENCE.broadcom_bcm43xx
>
> - chip vendor firmware binary file e.g. brcmfmac43340-sdio.bin
>
> - chip vendor support file e.g. brcmfmac43430-sdio.txt
>
> - their supporting files e.g. BCM43430A1.hcd, GPL
>
>
>
>
>
> The dependency graph from
> meta-freescale-3rdparty/conf/machine/imx7s-warp.conf looks like this:
>
>
>
> imx7s-warp.conf
>
>  firmware-imx.bb
>
>  firmware-imx.inc (provides FILES_${PN}-brcm i.e. firmware-imx-brmm
> )
>
>  firmware-imx.bbappend
>
>
>
> Note:
>
> -  firmware-imx.bb can be customised with
> meta-foo/recipe-bsp/firmware-imx/firmware-imx.bbappend.
>
> -  firmware-imx.bb installs to /lib/firmware/bcm
>
>
>
> However, the dependency graph for
> meta-freescale-3rdparty/conf/machine/imx6sl-warp.conf looks like this:
>
>
>
> imx6sl-warp.conf
>
>  bcm4330-nvram-config.bb
>
>  broadcom-nvram-config.inc
>
>  linux-firmware_git.bb
>
>  linux-firmware_git.bbappend
>
>

The boards imx6s-warp and imx7s-warp use different WiFi device, so
they need different firmware. At time of adding the board support it
was decided to use different firmware source. Maybe today it can be
changed (need to verify)

>
> linux-firmware_git.bb can be customised with
> meta-foo/recipe-bsp/linux-firmware/ linux-firmware_git.bbappend. This seems
> a better approach because linux-firmware_git.bb already has (partial)
> support for our goal:

In case the change in bbappend is relevant for more projects, I would
upstream the change to openembedded-core instead.

>
>
>
> FILES_${PN}-bcm43340 = " \
>
>   ${nonarch_base_libdir}/firmware/brcm/brcmfmac43340-sdio.bin \
>
> "
>
>
>
> LICENSE_${PN}-bcm43340 = "Firmware-broadcom_bcm43xx"
>
>
>
> LIC_FILES_CHKSUM = "\
>
> ...
>
> file://LICENCE.broadcom_bcm43xx;md5=3160c14df7228891b868060e1951dfbc \
>
> ...
>
>
>
> Notes:
>
> - one of the files we specifically want to install (brcmfmac43340-sdio.bin)
> is managed in linux-firmware_git.bin
>
> - linux-firmware_git.bb installs to /lib/firmware/brcm, which is different
> to firmware-imx.inc.
>
>
>
> It seems like our best short term option is as follows:
>
> - define imx7s-warp-foo.conf,
>
> - in imx7s-warp-foo.conf add “require imx7s-warp.conf”, add MACHINE_FEATURES
> += “ bar”, and remove anything from imx7s-warp.conf referenced symbols (e.g.
> MACHINE_EXTRA_RRECOMMENDS) that inhibits the next step.
>
> - follow the imx6sl-warp.conf pattern to leverage linux-firmware_git.bb.
>
>
>
> Then we’d upstream in the following way:
>
> - upstream imx7s-warp-foo.conf into
> meta-freescale-3rdparty/conf/machine/imx7s-warp.conf
>
> - upstream linux-firmware_%.bbappend to linux-firmware_git.bb.
>
>
>
> Please could you share your opinions on the best way to proceed?

What is difference between imx7s-warp and imx7s-warp-foo? Without
really knowing the difference, I would say I prefer a complete new
machine with no requirement on another machine.

In case the set of similarities is big, I would create an
imx7s-warp.inc and require this file in both machines.

Daiane
>
>
>
> Thanks
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> --
> ___
> 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] [PATCH] Revert "imx-gst1.0-plugin: Change git repository URL"

[Daiane Angolini]

The reverted commit not only change the URL for the package. It also
upgrade the package version by mistake.

The version pointed by the patch is still not ready to use the gstreamer
1.12.

Meanwhile the root cause is found and fixed, revert the patch.

This reverts commit 8605319d17b08da79534681dc85b0a23e2e87c73.
---
 recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb 
b/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
index 89a14d5..afc380d 100644
--- a/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
+++ b/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
@@ -23,13 +23,14 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
 file://COPYING-LGPL-2;md5=5f30f0716dfdd0d91eb439ebec522ec2 
\
 
file://COPYING-LGPL-2.1;md5=fbc093901857fcd118f065f900982c24"
 
-SRCBRANCH = "nxp/MM_04.02.01_1705_L4.9.11_CONSOLIDATED_GA"
-
 SRC_URI = " \
-
git://source.codeaurora.org/external/imx/gst1.0-plugins-fsl.git;protocol=https;branch=${SRCBRANCH}
 \
+${FSL_MIRROR}/imx-gst1.0-plugin-${PV}.tar.gz \
 "
 
-S = "${WORKDIR}/git"
+SRC_URI[md5sum] = "8c939f68b7d7ce8659618bd34b93a508"
+SRC_URI[sha256sum] = 
"fcd5b8536758c50491c80ed26e86770fe17f29744ab4ccba1e5ca1c475a209c3"
+
+S = "${WORKDIR}/imx-gst1.0-plugin-${PV}"
 
 inherit autotools pkgconfig
 
-- 
2.7.4

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

[meta-freescale] [PATCH 0/7] Change from git.freescale.com to Code Aurora

[Daiane Angolini]

This patchset changes the URL to the git repository as code aurora is a mirror
for git.freescale.com.

Some patches also change from package (tar.gz) to git and add the needed changes
for make it work.

The branch names are also changed to match.

Daiane Angolini (7):
  linux-imx: Change git repository URL
  u-boot-imx: Change git repository URL
  imx-lib:  Change git repository URL
  imx-test: Change git repository URL
  imx-alsa-plugins: Change SRC_URI to point to git
  imx-gst1.0-plugin: Change git repository URL
  xf86-video-imxfb-vivante: Change SRC_URI to point to git

 recipes-bsp/imx-lib/imx-lib_git.bb   | 4 ++--
 recipes-bsp/imx-test/imx-test_git.bb | 4 ++--
 recipes-bsp/u-boot/u-boot-imx_2017.03.bb | 4 ++--
 recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc| 6 --
 .../xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb  | 4 ++--
 recipes-kernel/linux/linux-imx.inc   | 2 +-
 recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb   | 8 +---
 recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb  | 9 -
 8 files changed, 22 insertions(+), 19 deletions(-)

-- 
2.7.4

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

[meta-freescale] [PATCH 1/7] linux-imx: Change git repository URL

[Daiane Angolini]

The git.freescale.com repository has been facing critical fetch issues,
this patch uses source.codeaurora.org because it's a mirror for this
kernel provider version.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-kernel/linux/linux-imx.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-imx.inc 
b/recipes-kernel/linux/linux-imx.inc
index b13363e..9a8a035 100644
--- a/recipes-kernel/linux/linux-imx.inc
+++ b/recipes-kernel/linux/linux-imx.inc
@@ -11,7 +11,7 @@ LOCALVERSION ?= ""
 SCMVERSION ?= "y"
 SRCBRANCH ?= ""
 
-SRC_URI = "git://git.freescale.com/imx/linux-imx.git;branch=${SRCBRANCH} \
+SRC_URI = 
"git://source.codeaurora.org/external/imx/linux-imx;protocol=https;branch=${SRCBRANCH}
 \
file://defconfig \
 "
 
-- 
2.7.4

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

[meta-freescale] [PATCH 6/7] imx-gst1.0-plugin: Change git repository URL

[Daiane Angolini]

Change the git URL to Code Aurora as it mirrors the git.freescale.com.
It also changes the branch name to the matching one.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb | 9 -
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb 
b/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
index afc380d..89a14d5 100644
--- a/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
+++ b/recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.1.6.bb
@@ -23,14 +23,13 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
 file://COPYING-LGPL-2;md5=5f30f0716dfdd0d91eb439ebec522ec2 
\
 
file://COPYING-LGPL-2.1;md5=fbc093901857fcd118f065f900982c24"
 
+SRCBRANCH = "nxp/MM_04.02.01_1705_L4.9.11_CONSOLIDATED_GA"
+
 SRC_URI = " \
-${FSL_MIRROR}/imx-gst1.0-plugin-${PV}.tar.gz \
+
git://source.codeaurora.org/external/imx/gst1.0-plugins-fsl.git;protocol=https;branch=${SRCBRANCH}
 \
 "
 
-SRC_URI[md5sum] = "8c939f68b7d7ce8659618bd34b93a508"
-SRC_URI[sha256sum] = 
"fcd5b8536758c50491c80ed26e86770fe17f29744ab4ccba1e5ca1c475a209c3"
-
-S = "${WORKDIR}/imx-gst1.0-plugin-${PV}"
+S = "${WORKDIR}/git"
 
 inherit autotools pkgconfig
 
-- 
2.7.4

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

[meta-freescale] [PATCH 3/7] imx-lib: Change git repository URL

[Daiane Angolini]

Change the git URL to Code Aurora as it mirrors the git.freescale.com.
It also changes the branch name to the matching one.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-bsp/imx-lib/imx-lib_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/imx-lib/imx-lib_git.bb 
b/recipes-bsp/imx-lib/imx-lib_git.bb
index d48ff5a..8e477de 100644
--- a/recipes-bsp/imx-lib/imx-lib_git.bb
+++ b/recipes-bsp/imx-lib/imx-lib_git.bb
@@ -13,8 +13,8 @@ PE = "1"
 
 PV = "5.8+${SRCPV}"
 
-SRCBRANCH = "imx_4.9.11_1.0.0_ga"
-SRC_URI = 
"git://git.freescale.com/imx/imx-lib.git;protocol=git;branch=${SRCBRANCH}"
+SRCBRANCH = "nxp/imx_4.9.11_1.0.0_ga"
+SRC_URI = 
"git://source.codeaurora.org/external/imx/imx-lib.git;protocol=https;branch=${SRCBRANCH}"
 SRCREV = "f5f14fc24581e5d6e689f42a56b5f2992f978ef4"
 
 S = "${WORKDIR}/git"
-- 
2.7.4

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

[meta-freescale] [PATCH 5/7] imx-alsa-plugins: Change SRC_URI to point to git

[Daiane Angolini]

Change SRC_URI to point to git repo on Code Aurora as it mirrors the
git.freescale.com.
It also changes the working directory to reflect the git structure.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb 
b/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
index 6f453af..834b297 100644
--- a/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
+++ b/recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
@@ -19,9 +19,11 @@ LIC_FILES_CHKSUM = 
"file://COPYING.GPL;md5=94d55d512a9ba36caa9b7df079bae19f"
 
 inherit autotools pkgconfig
 
-SRC_URI = "${FSL_MIRROR}/${PN}-${PV}.tar.gz"
-SRC_URI[md5sum] = "8fe4bcfddeca82dd01a9c4c6ce9471df"
-SRC_URI[sha256sum] = 
"0a7e8d90fdde2f6780605ecfee674e6e13523915a7bcd64078bc507ac1a8deb8"
+SRCBRANCH = "nxp/master"
+SRC_URI = 
"git://source.codeaurora.org/external/imx/imx-alsa-plugins.git;protocol=https;branch=${SRCBRANCH}"
+SRCREV = "9a63071e7734bd164017f3761b8d1944c017611f"
+
+S = "${WORKDIR}/git"
 
 INCLUDE_DIR = "-I${STAGING_KERNEL_DIR}/include/uapi 
-I${STAGING_KERNEL_DIR}/include"
 
-- 
2.7.4

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

[meta-freescale] [PATCH 7/7] xf86-video-imxfb-vivante: Change SRC_URI to point to git

[Daiane Angolini]

Change SRC_URI to point to git repo on Code Aurora as it mirrors the
git.freescale.com.
It also changes the working directory to reflect the git structure.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc   | 6 --
 .../xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb | 4 ++--
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc 
b/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc
index e284fbc..a6d722b 100644
--- a/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc
+++ b/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc
@@ -12,8 +12,10 @@ DEPENDS += "virtual/xserver virtual/libx11 
virtual/libgal-x11 imx-gpu-viv pixman
 
 LIC_FILES_CHKSUM = "file://COPYING-MIT;md5=b5e9d9f5c02ea831ab3ecf802bb7c4f3"
 
-SRC_URI = "${FSL_MIRROR}/xserver-xorg-video-imx-viv-${PV}.tar.gz \
-file://rc.autohdmi"
+SRC_URI = 
"git://source.codeaurora.org/external/imx/xf86-video-imx-vivante.git;protocol=https;branch=${SRCBRANCH}
 \
+   file://rc.autohdmi"
+
+S = "${WORKDIR}/git/"
 
 INITSCRIPT_PACKAGES = "xserver-xorg-extension-viv-autohdmi"
 INITSCRIPT_NAME = "rc.autohdmi"
diff --git 
a/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb 
b/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb
index 91456f2..a15033e 100644
--- a/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb
+++ b/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb
@@ -6,5 +6,5 @@ require xf86-video-imxfb-vivante.inc
 
 SRC_URI += "file://Stop-using-Git-to-write-local-version.patch"
 
-SRC_URI[md5sum] = "8acb51c9b1b0fd25137eeabd786d"
-SRC_URI[sha256sum] = 
"3eed38193e31bb5ba8d2c817bd9b4f6e2fe7540d2cab36de9098cb4f11946a9f"
+SRCBRANCH = "nxp/imx_4.9.11_1.0.0_ga"
+SRCREV = "07ef065dfe09f1c05a1a188c371577faa3677a17"
-- 
2.7.4

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

[meta-freescale] [PATCH 4/7] imx-test: Change git repository URL

[Daiane Angolini]

Change the git URL to Code Aurora as it mirrors the git.freescale.com.
It also changes the branch name to the matching one.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-bsp/imx-test/imx-test_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/imx-test/imx-test_git.bb 
b/recipes-bsp/imx-test/imx-test_git.bb
index 4a2472b..ddc87a9 100644
--- a/recipes-bsp/imx-test/imx-test_git.bb
+++ b/recipes-bsp/imx-test/imx-test_git.bb
@@ -7,8 +7,8 @@ PV = "6.0+${SRCPV}"
 
 PARALLEL_MAKE="-j 1"
 
-SRCBRANCH = "imx_4.9.11_1.0.0_ga"
-SRC_URI = 
"git://git.freescale.com/imx/imx-test.git;protocol=git;branch=${SRCBRANCH}"
+SRCBRANCH = "nxp/imx_4.9.11_1.0.0_ga"
+SRC_URI = 
"git://source.codeaurora.org/external/imx/imx-test.git;protocol=https;branch=${SRCBRANCH}"
 SRCREV = "fb250a795ce0d25c19610e9e19e1cd815fc64cb9"
 
 S = "${WORKDIR}/git"
-- 
2.7.4

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

[meta-freescale] [PATCH 2/7] u-boot-imx: Change git repository URL

[Daiane Angolini]

Change the git URL to Code Aurora as it mirrors the git.freescale.com.
It also changes the branch name to the matching one.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-bsp/u-boot/u-boot-imx_2017.03.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb 
b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
index b0e5f9f..6360874 100644
--- a/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
+++ b/recipes-bsp/u-boot/u-boot-imx_2017.03.bb
@@ -10,8 +10,8 @@ DEPENDS_append = "dtc-native"
 LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = 
"file://Licenses/gpl-2.0.txt;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
-SRCBRANCH = "imx_v2017.03_4.9.11_1.0.0_ga"
-SRC_URI = 
"git://git.freescale.com/imx/uboot-imx.git;protocol=git;branch=${SRCBRANCH}"
+SRCBRANCH = "nxp/imx_v2017.03_4.9.11_1.0.0_ga"
+SRC_URI = 
"git://source.codeaurora.org/external/imx/uboot-imx.git;protocol=https;branch=${SRCBRANCH}"
 SRCREV = "a2fea67d3eb3092f19f250d53a4a27fa1a0c815f"
 
 S = "${WORKDIR}/git"
-- 
2.7.4

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

[meta-freescale] [PATCH] linux-imx: Change git repository URL

[Daiane Angolini]

The git.freescale.com repository has been facing critical fetch issues,
this patch uses source.codeaurora.org because it's a mirror for this
kernel provider version.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-kernel/linux/linux-imx.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-imx.inc 
b/recipes-kernel/linux/linux-imx.inc
index b13363e..9a8a035 100644
--- a/recipes-kernel/linux/linux-imx.inc
+++ b/recipes-kernel/linux/linux-imx.inc
@@ -11,7 +11,7 @@ LOCALVERSION ?= ""
 SCMVERSION ?= "y"
 SRCBRANCH ?= ""
 
-SRC_URI = "git://git.freescale.com/imx/linux-imx.git;branch=${SRCBRANCH} \
+SRC_URI = 
"git://source.codeaurora.org/external/imx/linux-imx;protocol=https;branch=${SRCBRANCH}
 \
file://defconfig \
 "
 
-- 
2.7.4

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

[meta-freescale] [PATCH] linux-imx: Change git repository URL

[Daiane Angolini]

The git.freescale.com repository has been facing critical fetch issues,
this patch uses source.codeaurora.org because it's a mirror for this
kernel provider version.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-kernel/linux/linux-imx.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-imx.inc 
b/recipes-kernel/linux/linux-imx.inc
index b13363e..9a8a035 100644
--- a/recipes-kernel/linux/linux-imx.inc
+++ b/recipes-kernel/linux/linux-imx.inc
@@ -11,7 +11,7 @@ LOCALVERSION ?= ""
 SCMVERSION ?= "y"
 SRCBRANCH ?= ""
 
-SRC_URI = "git://git.freescale.com/imx/linux-imx.git;branch=${SRCBRANCH} \
+SRC_URI = 
"git://source.codeaurora.org/external/imx/linux-imx;protocol=https;branch=${SRCBRANCH}
 \
file://defconfig \
 "
 
-- 
2.7.4

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

[meta-freescale] [PATCH v3] imx6ullevk: Add machine file

[Daiane Angolini]

CPU:   Freescale i.MX6ULL rev1.0 at 396MHz
CPU:   Commercial temperature grade (0C to 95C) at 41C
Reset cause: POR
Board: MX6ULL 14x14 EVK
I2C:   ready
DRAM:  512 MiB

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/machine/imx6ullevk.conf | 24 
 1 file changed, 24 insertions(+)
 create mode 100644 conf/machine/imx6ullevk.conf

diff --git a/conf/machine/imx6ullevk.conf b/conf/machine/imx6ullevk.conf
new file mode 100644
index 000..7cf9c32
--- /dev/null
+++ b/conf/machine/imx6ullevk.conf
@@ -0,0 +1,24 @@
+#@TYPE: Machine
+#@NAME: Freescale i.MX6ULL Evaluation Kit
+#@SOC: i.MX6ULL
+#@DESCRIPTION: Machine configuration for Freescale i.MX6ULL EVK
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
+
+MACHINEOVERRIDES =. "mx6:mx6ull:"
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa7.inc
+
+KERNEL_DEVICETREE = "imx6ull-14x14-evk.dtb imx6ull-14x14-evk-btwifi.dtb"
+
+UBOOT_CONFIG ??= "sd"
+UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
+UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-imx"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx"
+PREFERRED_PROVIDER_virtual/kernel = "linux-imx"
+
+SERIAL_CONSOLE = "115200 ttymxc0"
+
+MACHINE_FEATURES += "wifi bluetooth"
-- 
2.7.4

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

[meta-freescale] [PATCH v2] imx6ullevk: Add machine file

[Daiane Angolini]

CPU:   Freescale i.MX6ULL rev1.0 at 396MHz
CPU:   Commercial temperature grade (0C to 95C) at 41C
Reset cause: POR
Board: MX6ULL 14x14 EVK
I2C:   ready
DRAM:  512 MiB

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/machine/imx6ullevk.conf | 24 
 1 file changed, 24 insertions(+)
 create mode 100644 conf/machine/imx6ullevk.conf

diff --git a/conf/machine/imx6ullevk.conf b/conf/machine/imx6ullevk.conf
new file mode 100644
index 000..2b3891e
--- /dev/null
+++ b/conf/machine/imx6ullevk.conf
@@ -0,0 +1,24 @@
+#@TYPE: Machine
+#@NAME: Freescale i.MX6ULL Evaluation Kit
+#@SOC: i.MX6ULL
+#@DESCRIPTION: Machine configuration for Freescale i.MX6ULL EVK
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
+
+MACHINEOVERRIDES =. "mx6:mx6ull:"
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa7.inc
+
+KERNEL_DEVICETREE = "imx6ull-14x14-evk.dtb imx6ull-14x14-evk-btwifi.dtb"
+
+UBOOT_CONFIG ??= "sd"
+UBOOT_CONFIG[sd] = "mx6ull_14x14_evk_config,sdcard"
+UBOOT_CONFIG[mfgtool] = "mx6ull_14x14_evk_config"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-imx"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx"
+PREFERRED_PROVIDER_virtual/kernel = "linux-imx"
+
+SERIAL_CONSOLE = "115200 ttymxc0"
+
+MACHINE_FEATURES += " pci wifi bluetooth"
-- 
2.7.4

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

Re: [meta-freescale] [3rdparty PATCH] Rework machines to use wic support

[Daiane Angolini]

On Thu, Oct 5, 2017 at 1:56 PM, Otavio Salvador <ota...@ossystems.com.br> wrote:
> This rework existing machines to use the wic support. It allows for a
> lot of code removal as the image dependencies can be defined in a more
> accurate way.
>
> Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>

Reviewed-by: Daiane Angolini <daiane.angol...@nxp.com>


> ---
>
>  conf/machine/cgtqmx6.conf   |  2 +-
>  conf/machine/cubox-i.conf   |  6 +-
>  conf/machine/imx6dl-riotboard.conf  |  5 +
>  conf/machine/imx6qdl-variscite-som.conf |  1 +
>  conf/machine/nitrogen6sx.conf   | 22 --
>  conf/machine/nitrogen6x-lite.conf   | 22 --
>  conf/machine/nitrogen6x.conf| 25 -
>  conf/machine/nitrogen7.conf | 22 --
>  conf/machine/wandboard.conf |  5 +
>  9 files changed, 37 insertions(+), 73 deletions(-)
>
> diff --git a/conf/machine/cgtqmx6.conf b/conf/machine/cgtqmx6.conf
> index fd85be0..5be7971 100644
> --- a/conf/machine/cgtqmx6.conf
> +++ b/conf/machine/cgtqmx6.conf
> @@ -15,8 +15,8 @@ UBOOT_MAKE_TARGET = ""
>  UBOOT_SUFFIX = "img"
>  SPL_BINARY = "SPL"
>  UBOOT_CONFIG ??= "cgtqmx6"
> -
>  UBOOT_CONFIG[cgtqmx6] = "cgtqmx6eval_defconfig"
> +WKS_FILE = "imx-uboot-spl-bootpart.wks"
>
>  # Use linux kernel QMX6
>  PREFERRED_PROVIDER_virtual/kernel ??= "linux-congatec"
> diff --git a/conf/machine/cubox-i.conf b/conf/machine/cubox-i.conf
> index 24e8519..4c9ae2e 100644
> --- a/conf/machine/cubox-i.conf
> +++ b/conf/machine/cubox-i.conf
> @@ -23,6 +23,7 @@ UBOOT_CONFIG ??= "sd"
>  UBOOT_CONFIG[sd] = "mx6cuboxi_defconfig,sdcard"
>  UENV_FILENAME = "uEnv-${MACHINE}.txt"
>  SPL_BINARY = "SPL"
> +WKS_FILES = "imx-uboot-spl.wks"
>
>  UBOOT_EXTLINUX = "1"
>  UBOOT_EXTLINUX_ROOT = "root=PARTUUID=${uuid}"
> @@ -40,8 +41,3 @@ MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
>  kernel-devicetree \
>  u-boot-fslc \
>  "
> -
> -WKS_FILES ?= "imx-uboot-spl.wks"
> -WKS_FILE_DEPENDS ?= ""
> -
> -IMAGE_FSTYPES = "wic.gz"
> diff --git a/conf/machine/imx6dl-riotboard.conf 
> b/conf/machine/imx6dl-riotboard.conf
> index 7823cd5..157e2c9 100644
> --- a/conf/machine/imx6dl-riotboard.conf
> +++ b/conf/machine/imx6dl-riotboard.conf
> @@ -22,7 +22,4 @@ MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
>  u-boot-fslc \
>  "
>
> -WKS_FILES ?= "imx-uboot.wks"
> -WKS_FILE_DEPENDS ?= ""
> -
> -IMAGE_FSTYPES = "wic.gz"
> +WKS_FILES = "imx-uboot.wks"
> diff --git a/conf/machine/imx6qdl-variscite-som.conf 
> b/conf/machine/imx6qdl-variscite-som.conf
> index c397649..c42741a 100644
> --- a/conf/machine/imx6qdl-variscite-som.conf
> +++ b/conf/machine/imx6qdl-variscite-som.conf
> @@ -28,6 +28,7 @@ KERNEL_IMAGETYPE = "uImage"
>  UBOOT_SPL_BUILD = "yes"
>  UBOOT_MAKE_TARGET = "all"
>  UBOOT_SUFFIX = "img"
> +WKS_FILE = "imx-uboot-spl-bootpart.wks"
>
>  PREFERRED_PROVIDER_virtual/bootloader = "u-boot-variscite"
>  PREFERRED_PROVIDER_u-boot = "u-boot-variscite"
> diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf
> index ae6fff2..1dec579 100644
> --- a/conf/machine/nitrogen6sx.conf
> +++ b/conf/machine/nitrogen6sx.conf
> @@ -16,23 +16,17 @@ PREFERRED_PROVIDER_u-boot = "u-boot-boundary"
>  PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary"
>  PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc"
>
> -# Use SPI NOR U-Boot by default
> -IMAGE_BOOTLOADER ?= ""
> -
> -# Ensure boot scripts will be available at rootfs time
> -do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
> -
>  # wic support
> -WKS_FILE ?= "sdimage-bootpart.wks"
> -IMAGE_BOOT_FILES = " \
> +WKS_FILE = "sdimage-bootpart.wks"
> +IMAGE_BOOT_FILES_append = " \
>  6x_bootscript-${MACHINE};6x_bootscript \
> -${KERNEL_IMAGETYPE} \
> -${KERNEL_IMAGETYPE}-imx6sx-nitrogen6sx.dtb;imx6sx-nitrogen6sx.dtb \
>  "
> -WKS_FILE_DEPENDS ?= ""
> -
> -# Boot scripts to install
> -BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
> +WKS_FILE_DEPENDS = " \
> +u-boot-script-boundary \
> +\
> +e2fsprogs-native \
> +bmap-tools-native \
> +"
>
>  UBOOT_MACHINE ?= "nitrogen6sx_config"

Re: [meta-freescale] [3rdparty][PATCH] imx7s-warp: Add wic image support

[Daiane Angolini]

On Wed, Oct 4, 2017 at 6:29 PM, Pierre-Jean TEXIER <texier@gmail.com> wrote:
> Signed-off-by: Pierre-Jean TEXIER <texier@gmail.com>

Reviewed-by: Daiane Angolini <daiane.angol...@nxp.com>

> ---
>  conf/machine/imx7s-warp.conf | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/conf/machine/imx7s-warp.conf b/conf/machine/imx7s-warp.conf
> index 7a23fd6..68c82e6 100644
> --- a/conf/machine/imx7s-warp.conf
> +++ b/conf/machine/imx7s-warp.conf
> @@ -18,4 +18,8 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-warp7"
>  UBOOT_CONFIG ??= "sd"
>  UBOOT_CONFIG[sd] = "warp7_secure_defconfig,sdcard"
>
> +# wic
> +IMAGE_FSTYPES = "wic.gz"
> +WKS_FILE ?= "imx-uboot-bootpart.wks"
> +
>  MACHINE_EXTRA_RRECOMMENDS += "firmware-imx-brcm"
> --
> 2.7.4
>
> --
> ___
> 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] [PATCH 1/2] image_types_fsl: define SDCARD_GENERATION_COMMAND for use-mainline-bsp

[Daiane Angolini]

On Thu, Oct 5, 2017 at 2:11 PM, Otavio Salvador
 wrote:
> Hello Hiraku,
>
> On Thu, Oct 5, 2017 at 1:21 AM, Hiraku Toyooka
>  wrote:
>> When we use the use-mainline-bsp override, SDCARD_GENERATION_COMMAND
>> becomes empty. As a result, incomplete SD card image is generated.
>> This patch fixes the problem by specifying appropriate command.
>>
>> Signed-off-by: Hiraku Toyooka 
>
> I apologize but I won't apply this patch; we are in an effort of
> moving away from the class. The wic support is ready for use with the
> use-mainline-bsp so this is preferred instead of the class as I intend
> to remove the class in next release.
>
> If possible please test the master-next branch as it includes all the
> changes you need (including your 2/2 change).

I agree the best option is to go in the wic direction, however I think
this patch is important.

If not to be on the master, because the class sdcard is going to be
deprecated. At least to be backported to the branches using the
use-mainline-bsp override.

It would be at least Pyro.


Regards,
Daiane
>
> --
> 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
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [PATCH] Use wic.gz for all i.MX machines by default

[Daiane Angolini]

On Wed, Oct 4, 2017 at 6:12 PM, Otavio Salvador <ota...@ossystems.com.br> wrote:
> This change moves the default image for all i.MX machines. We moved
> from sdcard.gz to wic.gz.
>
> Following machines were change:
>
>  - imx25pdk: use imx-uboot.wks
>  - imx6qdlsabreauto: use imx-uboot-spl-bootpart.wks
>  - imx6qdlsabresd: use imx-uboot-spl-bootpart.wks
>  - imx6ulevk: use imx-uboot-spl-bootpart.wks
>
> Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>

Reviewed-by: Daiane Angolini <daiane.angol...@nxp.com>

> ---
>
>  conf/machine/imx25pdk.conf | 2 +-
>  conf/machine/imx6qdlsabreauto.conf | 1 +
>  conf/machine/imx6qdlsabresd.conf   | 1 +
>  conf/machine/imx6ulevk.conf| 1 +
>  conf/machine/include/imx-base.inc  | 7 +++
>  5 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/conf/machine/imx25pdk.conf b/conf/machine/imx25pdk.conf
> index f35d0db4..e22d9f4e 100644
> --- a/conf/machine/imx25pdk.conf
> +++ b/conf/machine/imx25pdk.conf
> @@ -17,7 +17,7 @@ SERIAL_CONSOLE = "115200 ttymxc0"
>
>  MACHINE_FEATURES = "usbgadget usbhost vfat alsa touchscreen"
>
> -WKS_FILE ?= "imx-uboot.wks"
> +WKS_FILE = "imx-uboot.wks"
>  MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
>  kernel-image \
>  kernel-devicetree \
> diff --git a/conf/machine/imx6qdlsabreauto.conf 
> b/conf/machine/imx6qdlsabreauto.conf
> index 8967c150..0eed1e5c 100644
> --- a/conf/machine/imx6qdlsabreauto.conf
> +++ b/conf/machine/imx6qdlsabreauto.conf
> @@ -31,6 +31,7 @@ UBOOT_MACHINE ?= "mx6sabreauto_defconfig"
>  UBOOT_MAKE_TARGET = "all"
>  UBOOT_SUFFIX = "img"
>  SPL_BINARY = "SPL"
> +WKS_FILE = "imx-uboot-spl-bootpart.wks"
>
>  SERIAL_CONSOLE = "115200 ttymxc3"
>
> diff --git a/conf/machine/imx6qdlsabresd.conf 
> b/conf/machine/imx6qdlsabresd.conf
> index 92c92884..91ca9b45 100644
> --- a/conf/machine/imx6qdlsabresd.conf
> +++ b/conf/machine/imx6qdlsabresd.conf
> @@ -31,6 +31,7 @@ UBOOT_MACHINE ?= "mx6sabresd_defconfig"
>  UBOOT_MAKE_TARGET = "all"
>  UBOOT_SUFFIX = "img"
>  SPL_BINARY = "SPL"
> +WKS_FILE = "imx-uboot-spl-bootpart.wks"
>
>  SERIAL_CONSOLE = "115200 ttymxc0"
>
> diff --git a/conf/machine/imx6ulevk.conf b/conf/machine/imx6ulevk.conf
> index dadd525b..1b55a4ad 100644
> --- a/conf/machine/imx6ulevk.conf
> +++ b/conf/machine/imx6ulevk.conf
> @@ -23,3 +23,4 @@ UBOOT_CONFIG[sd] = "mx6ul_14x14_evk_config,sdcard"
>  UBOOT_CONFIG[emmc] = "mx6ul_14x14_evk_emmc_config,sdcard"
>  UBOOT_CONFIG[qspi1] = "mx6ul_14x14_evk_qspi1_config"
>  UBOOT_CONFIG[mfgtool] = "mx6ul_14x14_evk_config"
> +WKS_FILE = "imx-uboot-spl-bootpart.wks"
> diff --git a/conf/machine/include/imx-base.inc 
> b/conf/machine/include/imx-base.inc
> index c96216de..d2414472 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -222,8 +222,8 @@ IMX_DEFAULT_KERNEL_use-mainline-bsp = "linux-fslc"
>
>  PREFERRED_PROVIDER_virtual/kernel ??= "${IMX_DEFAULT_KERNEL}"
>
> -SOC_DEFAULT_IMAGE_FSTYPES = "sdcard.gz"
> -SOC_DEFAULT_IMAGE_FSTYPES_mxs = "uboot-mxsboot-sdcard sdcard.gz"
> +SOC_DEFAULT_IMAGE_FSTYPES = "wic.gz"
> +SOC_DEFAULT_IMAGE_FSTYPES_mxs = "uboot-mxsboot-sdcard wic.gz"
>
>  SDCARD_ROOTFS ?= "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.ext4"
>  IMAGE_FSTYPES ?= "${SOC_DEFAULT_IMAGE_FSTYPES}"
> @@ -240,8 +240,7 @@ WKS_FILE_DEPENDS ?= " \
>  e2fsprogs-native \
>  bmap-tools-native \
>  "
> -
> -SOC_DEFAULT_IMAGE_FSTYPES_mx25 = "wic.gz"
> +WKS_FILE ?= "imx-uboot-bootpart.wks"
>
>  SERIAL_CONSOLE = "115200 ttymxc0"
>  SERIAL_CONSOLE_mxs = "115200 ttyAMA0"
> --
> 2.14.2
>
> --
> ___
> 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] [PATCH] imx-base.inc: Generate a default IMAGE_BOOT_FILES

[Daiane Angolini]

On Wed, Oct 4, 2017 at 5:40 PM, Otavio Salvador <ota...@ossystems.com.br> wrote:
> When the machine requires a boot partition, it needs to define the
> IMAGE_BOOT_FILES to include the device tree files and Linux kernel
> image. This is essentially a generic solution so instead of defining
> it for all machines we are providing a default value for them.
>
> To implement that, we borrowed an utility function from Raspberry Pi
> BSP. It is copied as is at conf/machine/include/utilities.inc file.

Nice solution. Thanks for the patch

>
> Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>

Reviewed-by: Daiane Angolini <daiane.angol...@nxp.com>

> ---
>
>  conf/machine/include/imx-base.inc  |  7 +++
>  conf/machine/include/utilities.inc | 28 
>  2 files changed, 35 insertions(+)
>  create mode 100644 conf/machine/include/utilities.inc
>
> diff --git a/conf/machine/include/imx-base.inc 
> b/conf/machine/include/imx-base.inc
> index 06f93fcb..c96216de 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -3,6 +3,8 @@
>  include conf/machine/include/fsl-default-settings.inc
>  include conf/machine/include/fsl-default-versions.inc
>
> +require conf/machine/include/utilities.inc
> +
>  # Set specific make target and binary suffix
>  PREFERRED_PROVIDER_u-boot ??= "u-boot-fslc"
>  PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot-fslc"
> @@ -226,6 +228,11 @@ SOC_DEFAULT_IMAGE_FSTYPES_mxs = "uboot-mxsboot-sdcard 
> sdcard.gz"
>  SDCARD_ROOTFS ?= "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.ext4"
>  IMAGE_FSTYPES ?= "${SOC_DEFAULT_IMAGE_FSTYPES}"
>
> +IMAGE_BOOT_FILES ?= " \
> +${KERNEL_IMAGETYPE} \
> +${@make_dtb_boot_files(d)} \
> +"
> +
>  ### wic default support
>  WKS_FILE_DEPENDS ?= " \
>  virtual/bootloader \
> diff --git a/conf/machine/include/utilities.inc 
> b/conf/machine/include/utilities.inc
> new file mode 100644
> index ..bcb1c2a7
> --- /dev/null
> +++ b/conf/machine/include/utilities.inc
> @@ -0,0 +1,28 @@
> +### Machine definition file utilities
> +
> +def make_dtb_boot_files(d):
> +# Generate IMAGE_BOOT_FILES entries for device tree files listed in
> +# KERNEL_DEVICETREE.
> +alldtbs = d.getVar('KERNEL_DEVICETREE')
> +imgtyp = d.getVar('KERNEL_IMAGETYPE')
> +
> +def transform(dtb):
> +if dtb.endswith('dtb'):
> +# eg: whatever/bcm2708-rpi-b.dtb has:
> +# DEPLOYDIR file: ${KERNEL_IMAGETYPE}-bcm2708-rpi-b.dtb
> +# destination: bcm2708-rpi-b.dtb
> +base = os.path.basename(dtb)
> +src = '{}-{}'.format(imgtyp, base)
> +dst = base
> +return '{};{}'.format(src, dst)
> +elif dtb.endswith('dtbo'):
> +# overlay dtb:
> +# eg: overlays/hifiberry-amp.dtbo has:
> +# DEPLOYDIR file: ${KERNEL_IMAGETYPE}-hifiberry-amp.dtbo
> +# destination: overlays/hifiberry-amp.dtbo
> +base = os.path.basename(dtb)
> +src = '{}-{}'.format(imgtyp, base)
> +dst = dtb
> +return '{};{}'.format(src, dtb)
> +
> +return ' '.join([transform(dtb) for dtb in alldtbs.split(' ') if dtb])
> --
> 2.14.2
>
> --
> ___
> 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] [PATCH] u-boot-fslc: Bump revision to be634a9

[Daiane Angolini]

This includes the following changes:

be634a9 mx6sabre_common: Dynamically change the video output
f5f42f3 mx6sabre_common: Place video related settings in common code
43d4159 mx6cuboxi: Move CONFIG_CMD_SATA to Kconfig

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-bsp/u-boot/u-boot-fslc_2017.07.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-fslc_2017.07.bb 
b/recipes-bsp/u-boot/u-boot-fslc_2017.07.bb
index f2cd8e5..ecb54bd 100644
--- a/recipes-bsp/u-boot/u-boot-fslc_2017.07.bb
+++ b/recipes-bsp/u-boot/u-boot-fslc_2017.07.bb
@@ -2,5 +2,5 @@ include u-boot-fslc.inc
 
 PV = "v2017.07+git${SRCPV}"
 
-SRCREV = "801fd445636a6d136ffb1a991245e183643a8934"
+SRCREV = "f5f42f39f35568ea380bb4190b4ff155cc7cb151"
 SRCBRANCH = "2017.07+fslc"
-- 
2.7.4

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

Re: [meta-freescale] [PATCH v6] u-boot-fslc: Upgrade to 2017.07-based release

[Daiane Angolini]

On Wed, Jul 12, 2017 at 10:56 AM, Otavio Salvador
 wrote:
> On Wed, Jul 12, 2017 at 10:40 AM, Fabio Berton
>  wrote:
>> Why not rename machine file to imx6sabresd and imx6sabreauto, once these
>> machine are for solo, dual, quad and quad plus, or "qdl" doesn't mean that
>> the machine configuration is only for quad and dual?
>
> That is a good question indeed.
>
> Essentially we are following the kernel here. Basically the Quad and
> DualLite are the two SoC die we support as the Dual and Solo are
> reduced versions of those. The QuadPlus is a Quad with a newer
> revision so in the end of the day it is right ;-)

I don't have strong arguments on this topic. But I think Fabio's
suggestions is way more beautiful.

(the argument here is beauty, so weak argument. And in fact I can say
it without stumbling)


Daiane
>
> --
> 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
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [PATCH v5] u-boot-fslc: Upgrade to 2017.07-based release

[Daiane Angolini]

On Tue, Jul 11, 2017 at 4:47 PM, Otavio Salvador
<ota...@ossystems.com.br> wrote:
> This release provides a huge improvement regarding the support for SPL
> to more boards.
>
> We now uses this and migrated following boards:
>
>  - imx6qpsabresd -> imx6qdlsabresd
>  - imx6qsabresd -> imx6qdlsabresd
>  - imx6dlsabresd -> imx6qdlsabresd
>  - imx6solosabresd -> imx6qdlsabresd
>  - imx6qpsabreauto -> imx6qdlsabreauto
>  - imx6qsabreauto -> imx6qdlsabreauto
>  - imx6dlsabreauto -> imx6qdlsabreauto
>  - imx6solosabreauto -> imx6qdlsabreauto
>
> So now, the 8 boards are covered by 2 machine files. This drastically
> reduces the build time and allow for a better user experience as we
> can use the same image to test different boards.
>
> In summary an image built for imx6qdlsabresd or imx6qdlsabreauto is
> capable of run on a its respective board which contains a i.MX6
> QuadPlus, Quad, Dual, DualLite or Solo SoC removing the need of a
> specific image for each SoC type.
>
> On top of the official 2017.07 release, following patches are
> included:
>
> embestmx6boards: Use PARTUUID to specify the rootfs location
> c1d345f7c8 mx6cuboxi: Use PARTUUID to specify the rootfs location
> e14549a3bb wandboard: Use PARTUUID to specify the rootfs location
> bacd34492f wandboard: Set fdt based on board_rev and board_name
> de5d7a4200 warp: Use PARTUUID to specify the rootfs location
> d1e1e41022 mx6sabresd: Enable video interfaces in bootargs
> 4bca837948 mx6sabresd: Use LDO dtb file until LDO bypass support is added
> 70d1a84da3 mx6slevk: Use LDO dtb file until LDO bypass support is added
> 481444d361 mx6sabre: Use PARTUUID to specify the rootfs location
> 3ea2fba306 mx6sabreauto: Do not enable WEIM by default
> 09d36d3fa1 mx6sabreauto: Update to SPL only mode
> 210157f1ad mx6qsabreauto: Add SPL support
> 8ab1542497 mx6: soc: Move mxs_dma_init() into the mxs nand driver
>
> Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>

Acked-by: Daiane Angolini <daiane.angol...@nxp.com>

> ---
>
> Changes in v5:
> - add comment inside machine file so users can find old machine
>   reference (Daiane)
>
> Changes in v4:
> - replace warp patch with the PARTUUID from Fabio Estevam
>
> Changes in v3:
> - add mx6sabre: Use PARTUUID to specify the rootfs location
> - add mx6sabreauto: Do not enable WEIM by default
> - improve machine description to mention QP support as  well (Daiane)
> - improve commit log to make it clear that same image can be used
>   across different boards (Daiane)
>
> Changes in v2:
> - include fslc specific patches
> - fix typo on commit log (Fabio Estevam)
> - improve log to mention specific patches
>
>  conf/machine/imx6dlsabreauto.conf  | 19 ---
>  conf/machine/imx6dlsabresd.conf| 19 ---
>  conf/machine/imx6qdlsabreauto.conf | 39 
> ++
>  conf/machine/imx6qdlsabresd.conf   | 39 
> ++
>  conf/machine/imx6qpsabreauto.conf  | 24 -
>  conf/machine/imx6qpsabresd.conf| 20 ---
>  conf/machine/imx6qsabreauto.conf   | 20 ---
>  conf/machine/imx6qsabresd.conf | 17 --
>  conf/machine/imx6solosabreauto.conf| 21 
>  conf/machine/imx6solosabresd.conf  | 19 ---
>  conf/machine/imx6sxsabreauto.conf  |  9 -
>  conf/machine/imx6sxsabresd.conf|  9 -
>  conf/machine/include/imx6sabreauto-common.inc  | 10 --
>  conf/machine/include/imx6sabresd-common.inc| 10 --
>  ...t_2016.09.bb => u-boot-fslc-mxsboot_2017.07.bb} |  6 ++--
>  recipes-bsp/u-boot/u-boot-fslc_2017.03.bb  |  6 
>  recipes-bsp/u-boot/u-boot-fslc_2017.07.bb  |  6 
>  17 files changed, 103 insertions(+), 190 deletions(-)
>  delete mode 100644 conf/machine/imx6dlsabreauto.conf
>  delete mode 100644 conf/machine/imx6dlsabresd.conf
>  create mode 100644 conf/machine/imx6qdlsabreauto.conf
>  create mode 100644 conf/machine/imx6qdlsabresd.conf
>  delete mode 100644 conf/machine/imx6qpsabreauto.conf
>  delete mode 100644 conf/machine/imx6qpsabresd.conf
>  delete mode 100644 conf/machine/imx6qsabreauto.conf
>  delete mode 100644 conf/machine/imx6qsabresd.conf
>  delete mode 100644 conf/machine/imx6solosabreauto.conf
>  delete mode 100644 conf/machine/imx6solosabresd.conf
>  delete mode 100644 conf/machine/include/imx6sabreauto-common.inc
>  delete mode 100644 conf/machine/include/imx6sabresd-common.inc
>  rename recipes-bsp/u-boot/{u-boot-fslc-mxsboot_2016.09.bb => 

Re: [meta-freescale] [Yacto Project] Issue with Implementation of "Wi-Fi Access Point" on IMX7

[Daiane Angolini]

On Mon, Jul 10, 2017 at 2:06 AM, Vikram Bidkar  wrote:
> Dear All,
>
> I am trying to implement "Wi-Fi Access Point" on the IMX7 evaluation board
> having Murata Wi-Fi chip(LBEH5HMZPC).
>
> Below are my changes in .config file.
>
> CONFIG_BCMDHD_FW_PATH="/lib/firmware/bcm/ZP_BCM4339/fw_bcmdhd_apsta.bin"
> CONFIG_BCMDHD_NVRAM_PATH="/lib/firmware/bcm/ZP_BCM4339/bcmdhd.ZP.SDIO.cal"

Can you configure your kernel to load the WiFi driver by module
instead of builtin?

>
> CONFIG_HOSTAP=y
> CONFIG_HOSTAP_FIRMWARE=y
>
> but when I do "ifconfig wlan0 up" I am getting following error
>
> root@imx7dsabresd:~# ifconfig wlan0 up
>
> Dongle Host Driver, version 1.141.92 (r)
> Compiled in drivers/net/wireless/bcmdhd
> wl_android_wifi_on in
> mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
> mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
> mmc1: queuing unknown CIS tuple 0x80 (6 bytes)
> F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x0
> DHD: dongle ram size is set to 786432(orig 786432) at 0x18
> dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
> dhd_bus_rxctl: resumed on timeout, INT status=0x208000C0
> dhd_bus_rxctl: rxcnt_timeout=1, rxlen=0
> dhd_check_hang: Event HANG send up due to re=1 te=0 e=-110 s=2
> dhd_open : wl_android_wifi_on failed (-14)
>
> What could be the issue?
>
> Note: Wi-Fi is working fine in client mode. It can able to scan and all.
>

Which kernel are you using?

>
>
> possible issue may be
>
>
>
> 1) I think I have missed some patches as mentioned in the document
> (http://www.nxp.com/docs/en/application-note/AN5414.pdf)
> Can I get the patches as mentioned in ("section :2 Prepare source code for
> applying Wi-Fi patches" from doc
> http://www.nxp.com/docs/en/application-note/AN5414.pdf )

I don't know this AN and I don't know hte patchset rellated, sorry.


Daiane
>
>
>
>
>
> Please help me to resolve the issue
>
>
>
> Thanks and Regards,
>
> Vikram
>
>
> 
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential,
> proprietary or legally privileged information. In case you are not the
> original intended Recipient of the message, you must not, directly or
> indirectly, use, disclose, distribute, print, or copy any part of this
> message and you are requested to delete it and inform the sender. Any views
> expressed in this message are those of the individual sender unless
> otherwise stated. Nothing contained in this message shall be construed as an
> offer or acceptance of any offer by Sasken Technologies Limited ( formerly
> known as "Sasken Communication Technologies Limited" ) unless sent with that
> express intent and with due authority of Sasken. Sasken has taken enough
> precautions to prevent the spread of viruses. However the company accepts no
> liability for any damage caused by any virus transmitted by this email.
> Read Disclaimer at http://www.sasken.com/mail-disclaimer/
>
> 
>
> --
> ___
> 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] How to use mfgtool 2 to boot iMX7dsabresd from NAND

[Daiane Angolini]

On Fri, Jul 7, 2017 at 4:54 PM, Bejar-Colonia, Carlos
<carlos.bejar-colo...@philips.com> wrote:
> Hi Daiane,
>
> I haven't flashed the NAND manually yet. I am new to Yocto Project-based 
> image build and having some difficulties to build the image (NAND boot, UBIFS 
> file system), I thought I would try first loading the images that comes in 
> MfgTool.

I don't have NAND to try on my imx7D board, so I have no idea if
mfgtools works out of box or not.

However, I would first start booting from sdcard, then you manually
copy the image from NAND and boot from there

Only to make sure your hardware is OK

Daiane
>
> I am using L4.1.15_1.2.0_ga-mfg-tools.tar.gz. and we would like to use it for 
> flashing new boards
>
> Thanks,
> Carlos
>
> -Original Message-
> From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of Daiane 
> Angolini
> Sent: Friday, July 07, 2017 3:29 PM
> To: Bejar-Colonia, Carlos <carlos.bejar-colo...@philips.com>
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] How to use mfgtool 2 to boot iMX7dsabresd from 
> NAND
>
> On Thu, Jul 6, 2017 at 4:14 PM, Bejar-Colonia, Carlos 
> <carlos.bejar-colo...@philips.com> wrote:
>> Dear NXP,
>>
>>
>>
>> I have an iMX7dsabresd board and would like to boot it from NAND using
>> MfgTool V2.
>
> Have you tried your NAND already? I mean, have you flashed it manually? Only 
> to make sure all the support is in place?
>
>>
>> I have tried to use mfgtool2-yocto-mx-sabresd-nand.vbs script provided
>> in MfgTool V2, but failed.
>>
>> I replaced the “sabreauto” with “sabresd” in the same script and I
>> also rebuild Mfg Tools firmware (fsl-arm-yocto-bsp.git) and updated
>> fsl-image-mfgtool-initramfs-imx7dsabresd.cpio.gz.u-boot in the
>> MfgTool. But still fails
>>
>
> I would prefer to use the scripts with the board name included.
> Anyway, can you, please, share the exact version of mfgtools you are using 
> only to make sure we're in the same page?
>
>
>>
>>
>> These are the last lines from the console output:
>>
>>
>>
>> UTP: received command '$ mount -t debugfs debugfs /sys/kernel/debug'
>> UTP: executing "mount -t debugfs debugfs /sys/kernel/debug"
>> UTP: sending Success to kernel for command $ mount -t debugfs debugfs
>> /sys/kernel/debug.
>> utp_poll: pass returned.
>> UTP: received command '$ flash_erase /dev/mtd0 0 0'
>> UTP: executing "flash_erase /dev/mtd0 0 0"
>> flash_erase: error!: /dev/mtd0
>>  error 2 (No such file or directory)
>> UTP: sending Non-success to kernel for command $ flash_erase /dev/mtd0 0 0.
>> utp_poll: exit with status 65280
>>
>>
>>
>> Is mfgtool2-yocto-mx-sabresd-nand.vbs the right file to flash NAND for
>> iMX7dsabresd board or I need to create my own script?
>>
>> I checked the iMX Yocto Project Guide, iMX Linux User Guide, MfgTool2
>> documentation, but was not able to figure out. Could you provide the
>> steps to flash NAND?
>
> As far as I know, only the MfgTool documentation can help on this.
>
> Do you really need to use mfgtool?
>
> Daiane
>>
>>
>>
>> Best Regards,
>>
>> Carlos
>>
>>
>>
>>
>> 
>> The information contained in this message may be confidential and
>> legally protected under applicable law. The message is intended solely
>> for the addressee(s). If you are not the intended recipient, you are
>> hereby notified that any use, forwarding, dissemination, or
>> reproduction of this message is strictly prohibited and may be
>> unlawful. If you are not the intended recipient, please contact the
>> sender by return e-mail and destroy all copies of the original message.
>>
>> --
>> ___
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>
> 
> The information contained in this message may be confidential and legally 
> protected under applicable law. The message is intended solely for the 
> addressee(s). If you are not the intended recipient, you are hereby notified 
> that any use, forwarding, dissemination, or reproduction of this message is 
> strictly prohibited and may be unlawful. If you are not the intended 
> recipient, please contact the sender by return e-mail and destroy all copies 
> of the original message.
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [PATCH v2] u-boot-fslc: Upgrade to 2017.07-based release

[Daiane Angolini]

On Mon, Jul 10, 2017 at 4:05 PM, Otavio Salvador
<ota...@ossystems.com.br> wrote:
> This release provides a huge improvement regarding the support for SPL
> to more boards.
>

> diff --git a/conf/machine/imx6qdlsabresd.conf 
> b/conf/machine/imx6qdlsabresd.conf
> new file mode 100644
> index ..d221da15
> --- /dev/null
> +++ b/conf/machine/imx6qdlsabresd.conf
> @@ -0,0 +1,32 @@
> +#@TYPE: Machine
> +#@NAME: NXP i.MX6Q/DL SABRE Smart Device
> +#@SOC: i.MX6Q
> +#@DESCRIPTION: Machine configuration for NXP i.MX6Q/DL SABRE Smart Device

It also includes imx6QP

I think we must have a README explaining in a more verbose way this change.

I suggest a comment:


// This machine works for:
// * imx6qpsabresd
// * imx6qsabresd
// * imx6dlsabresd
// This means one SDCard flashed with one image targeting this machine
is able to boot all those boards.

I think it's important to include the machine name as it was before
the change, and make sure to say why it has changed "one binary for
all machines".

Daiane

> +#@MAINTAINER: Otavio Salvador <ota...@ossystems.com.br>
> +
> +MACHINEOVERRIDES =. "mx6:mx6q:mx6dl:"
> +
> +require conf/machine/include/imx-base.inc
> +require conf/machine/include/tune-cortexa9.inc
> +
> +KERNEL_DEVICETREE = " \
> +imx6qp-sabresd.dtb imx6qp-sabresd-btwifi.dtb imx6qp-sabresd-hdcp.dtb \
> +imx6qp-sabresd-ldo.dtb imx6qp-sabresd-ldo-pcie-cert.dtb \
> +\
> +imx6q-sabresd.dtb imx6q-sabresd-ldo.dtb imx6q-sabresd-hdcp.dtb \
> +imx6q-sabresd-enetirq.dtb imx6q-sabresd-btwifi.dtb \
> +\
> +imx6dl-sabresd.dtb imx6dl-sabresd-ldo.dtb imx6dl-sabresd-hdcp.dtb \
> +imx6dl-sabresd-enetirq.dtb imx6dl-sabresd-btwifi.dtb \
> +"
> +
> +UBOOT_MACHINE ?= "mx6sabresd_defconfig"
> +UBOOT_MAKE_TARGET = "all"
> +UBOOT_SUFFIX = "img"
> +SPL_BINARY = "SPL"
> +
> +SERIAL_CONSOLE = "115200 ttymxc0"
> +
> +MACHINE_FIRMWARE_append_mx6 = " linux-firmware-ath6k"
> +
> +MACHINE_FEATURES += " pci wifi bluetooth"
> diff --git a/conf/machine/imx6qpsabreauto.conf 
> b/conf/machine/imx6qpsabreauto.conf
> deleted file mode 100644
> index 505d341c..
> --- a/conf/machine/imx6qpsabreauto.conf
> +++ /dev/null
> @@ -1,24 +0,0 @@
> -#@TYPE: Machine
> -#@NAME: NXP i.MX6Q Plus SABRE Automotive
> -#@SOC: i.MX6QP
> -#@DESCRIPTION: Machine configuration for NXP i.MX6QP SABRE Automotive
> -#@MAINTAINER: Lauren Post <lauren.p...@nxp.com>
> -
> -MACHINEOVERRIDES =. "mx6:mx6q:"
> -
> -require conf/machine/include/imx6sabreauto-common.inc
> -
> -KERNEL_DEVICETREE = "imx6qp-sabreauto.dtb imx6qp-sabreauto-ecspi.dtb 
> imx6qp-sabreauto-flexcan1.dtb \
> - imx6qp-sabreauto-gpmi-weim.dtb"
> -
> -PREFERRED_PROVIDER_u-boot = "u-boot-imx"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx"
> -PREFERRED_PROVIDER_virtual/kernel = "linux-imx"
> -
> -UBOOT_CONFIG ??= "sd"
> -UBOOT_CONFIG[sd] = "mx6qpsabreauto_config,sdcard"
> -UBOOT_CONFIG[eimnor] = "mx6qpsabreauto_eimnor_config"
> -UBOOT_CONFIG[nand] = "mx6qpsabreauto_nand_config,ubifs"
> -UBOOT_CONFIG[spinor] = "mx6qpsabreauto_spinor_config"
> -UBOOT_CONFIG[sata] = "mx6qpsabreauto_sata_config"
> -UBOOT_CONFIG[mfgtool] = "mx6qpsabreauto_config"
> diff --git a/conf/machine/imx6qpsabresd.conf b/conf/machine/imx6qpsabresd.conf
> deleted file mode 100644
> index 369d5b7d..
> --- a/conf/machine/imx6qpsabresd.conf
> +++ /dev/null
> @@ -1,20 +0,0 @@
> -#@TYPE: Machine
> -#@NAME: NXP i.MX6Q Plus SABRE Smart Device
> -#@SOC: i.MX6QP
> -#@DESCRIPTION: Machine configuration for NXP i.MX6QP SABRE Smart Device
> -#@MAINTAINER: Lauren Post <lauren.p...@nxp.com>
> -
> -MACHINEOVERRIDES =. "mx6:mx6q:"
> -
> -require conf/machine/include/imx6sabresd-common.inc
> -
> -KERNEL_DEVICETREE = "imx6qp-sabresd.dtb imx6qp-sabresd-btwifi.dtb 
> imx6qp-sabresd-hdcp.dtb \
> - imx6qp-sabresd-ldo.dtb imx6qp-sabresd-ldo-pcie-cert.dtb"
> -
> -PREFERRED_PROVIDER_u-boot = "u-boot-imx"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx"
> -
> -UBOOT_CONFIG ??= "sd"
> -UBOOT_CONFIG[sd] = "mx6qpsabresd_config,sdcard"
> -UBOOT_CONFIG[sata] = "mx6qpsabresd_sata_config"
> -UBOOT_CONFIG[mfgtool] = "mx6qpsabresd_config"
> diff --git a/conf/machine/imx6qsabreauto.conf 
> b/conf/machine/imx6qsabreauto.conf
> deleted file mode 100644
> index e419c5d4..
> --- a/conf/machine/imx6qsabreauto.c

Re: [meta-freescale] Got error while building the image

[Daiane Angolini]

On Tue, Jul 4, 2017 at 1:49 AM, lakshmikanth r
 wrote:
> Hi,
>
> I 'm trying to do bitbake using Morty branch with respective boundary image.
>
> I was got error keeps appearing like this
>
> Firmware-imx- 1_5.4-r0 do_fetch error.
>
> Unable to fetch the firmware. I'm looking forward for your response.
>

Can you, please, try again?

This server has been unstable.

Daiane
>
> Thanks & Regards ,
> Lakshmikanth R
>
> --
> ___
> 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] How to use mfgtool 2 to boot iMX7dsabresd from NAND

[Daiane Angolini]

On Thu, Jul 6, 2017 at 4:14 PM, Bejar-Colonia, Carlos
 wrote:
> Dear NXP,
>
>
>
> I have an iMX7dsabresd board and would like to boot it from NAND using
> MfgTool V2.

Have you tried your NAND already? I mean, have you flashed it
manually? Only to make sure all the support is in place?

>
> I have tried to use mfgtool2-yocto-mx-sabresd-nand.vbs script provided in
> MfgTool V2, but failed.
>
> I replaced the “sabreauto” with “sabresd” in the same script and I also
> rebuild Mfg Tools firmware (fsl-arm-yocto-bsp.git) and updated
> fsl-image-mfgtool-initramfs-imx7dsabresd.cpio.gz.u-boot in the MfgTool. But
> still fails
>

I would prefer to use the scripts with the board name included.
Anyway, can you, please, share the exact version of mfgtools you are
using only to make sure we're in the same page?


>
>
> These are the last lines from the console output:
>
>
>
> UTP: received command '$ mount -t debugfs debugfs /sys/kernel/debug'
> UTP: executing "mount -t debugfs debugfs /sys/kernel/debug"
> UTP: sending Success to kernel for command $ mount -t debugfs debugfs
> /sys/kernel/debug.
> utp_poll: pass returned.
> UTP: received command '$ flash_erase /dev/mtd0 0 0'
> UTP: executing "flash_erase /dev/mtd0 0 0"
> flash_erase: error!: /dev/mtd0
>  error 2 (No such file or directory)
> UTP: sending Non-success to kernel for command $ flash_erase /dev/mtd0 0 0.
> utp_poll: exit with status 65280
>
>
>
> Is mfgtool2-yocto-mx-sabresd-nand.vbs the right file to flash NAND for
> iMX7dsabresd board or I need to create my own script?
>
> I checked the iMX Yocto Project Guide, iMX Linux User Guide, MfgTool2
> documentation, but was not able to figure out. Could you provide the steps
> to flash NAND?

As far as I know, only the MfgTool documentation can help on this.

Do you really need to use mfgtool?

Daiane
>
>
>
> Best Regards,
>
> Carlos
>
>
>
>
> 
> The information contained in this message may be confidential and legally
> protected under applicable law. The message is intended solely for the
> addressee(s). If you are not the intended recipient, you are hereby notified
> that any use, forwarding, dissemination, or reproduction of this message is
> strictly prohibited and may be unlawful. If you are not the intended
> recipient, please contact the sender by return e-mail and destroy all copies
> of the original message.
>
> --
> ___
> 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

[Daiane Angolini]

On Wed, Jul 5, 2017 at 3:28 AM, Vinay Hulagabali
<vinayhulagab...@gmail.com> wrote:
> Ok, thanks.  And can you just tell me on which website the Android kernel
> will be available and I need to use it for warp 7 so will you please suggest
> me.

I don't know. I would follow the warp7 github account.

Daiane
>
> Regards
> Vinod
>
> On 04-Jul-2017 6:58 PM, "Daiane Angolini" <daiane.l...@gmail.com> wrote:
>>
>> On Fri, Jun 30, 2017 at 2:30 AM, Vinay Hulagabali
>> <vinayhulagab...@gmail.com> 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" <daiane.l...@gmail.com> wrote:
>> >>
>> >> Hi Pierre-jean,
>> >>
>> >> On Wed, Jun 28, 2017 at 4:36 PM, TEXIER Pierre-Jean
>> >> <texier@gmail.com> wrote:
>> >> >
>> >> > 2017-06-28 18:10 GMT+02:00 Daiane Angolini <daiane.l...@gmail.com>:
>> >> >>
>> >>
>> >> >
>> >> > 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] Technical queries on android BSP porting on imx6

[Daiane Angolini]

On Wed, Jul 5, 2017 at 12:46 AM, sai lakshmi <sairamanu...@gmail.com> wrote:
> 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.

If I happen to find it again I fw you the link, but in fact I don't
have it right now.

Daiane
>
> Thanks & Regards
>
> On Tue, Jul 4, 2017 at 6:59 PM, Daiane Angolini <daiane.l...@gmail.com>
> wrote:
>>
>> On Thu, Jun 29, 2017 at 8:35 AM, sai lakshmi <sairamanu...@gmail.com>
>> 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] "Could not open egl display" error and GPU problem on imx6dl

[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

[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

[Daiane Angolini]

On Fri, Jun 30, 2017 at 2:30 AM, Vinay Hulagabali
<vinayhulagab...@gmail.com> 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" <daiane.l...@gmail.com> wrote:
>>
>> Hi Pierre-jean,
>>
>> On Wed, Jun 28, 2017 at 4:36 PM, TEXIER Pierre-Jean
>> <texier@gmail.com> wrote:
>> >
>> > 2017-06-28 18:10 GMT+02:00 Daiane Angolini <daiane.l...@gmail.com>:
>> >>
>>
>> >
>> > 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] About loading drivers of camera_ov5640_mipi and to test it in warp7

[Daiane Angolini]

Hi Pierre-jean,

On Wed, Jun 28, 2017 at 4:36 PM, TEXIER Pierre-Jean
<texier@gmail.com> wrote:
>
> 2017-06-28 18:10 GMT+02:00 Daiane Angolini <daiane.l...@gmail.com>:
>>

>
> 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] About loading drivers of camera_ov5640_mipi and to test it in warp7

[Daiane Angolini]

On Wed, Jun 28, 2017 at 1:20 AM, Vinay Hulagabali
 wrote:
> Hi,
>  I have loaded the camera drivers of ov5640_mipi in warp7 but I am not
> sure whether it is correct or not and will you please suggest me how to load
> drivers and to test it.

Last time I worked with warp7 camera it was not working (so if you are
using the default linux from meta-freescale-3rdparty chances are it's
not supposed to work.

I cannot really remember the camera partnumber, but it was not the
OV5XXX, it was an OV2XXX

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

Re: [meta-freescale] u-boot-fslc: migration from morty to pyro with a signed image using CST

[Daiane Angolini]

On Wed, Jun 14, 2017 at 1:45 PM, Romain Bazile  wrote:
> Hello everyone,
>
> I'm in the process of migrating from Morty to Pyro and I'm having some
> troubles with u-boot-fslc.
>
> In Morty, we were using u-boot-fslc_2016.11, in Pyro, we are migrating to
> u-boot-fslc_2017.03. Our processor is an i.MX6ul.
>
>
> We have in our bbappend a custom task, `sign_uboot`. This task uses the IMX
> Code Signing Tool distributed by NXP to sign `u-boot.img` .
>
>
> During the migration, I had a compilation problem. Basically, the build
> system would complain that authenticate_image was an undefined reference.
> When having a look at u-boot code, it seemed normal since it was not built
> in the absence of `CONFIG_SECURE_BOOT`.
> I added a patchfile changing this in `mx6ul_14x14_defconfig`, but now, a
> different problem appears.
>
> Basically, the do_compile task is failing when it tries to copy `u-boot.img`
> (as defined in my bbappend `UBOOT_BINARY`). This is "normal", since this
> file is not in the filesystem, and likely not built. However, I do have a
> `u-boot-ivt.img` (but this file is supposed to be created at a later stage
> by the task `sign_uboot`).
>
> Also, just before, a couple of errors appears, where a script complains
> about `bc` and `comm` not being found, except they are installed in the
> build machine. This may not be related and not have consequences, I believe
> this could be linked to the per-recipe sysroot.
>
>
> Sorry for the long post, I can also share the details if needed (the task
> `sign_uboot` and the scripts used to sign).
>
> My questions are as follows:
> Do I still need to use this custom script if I use `CONFIG_SECURE_BOOT`?

What I understand is that secure boot is different from signed image.
So I would say they are complementary, so you would also need  both.

> How can I insure that u-boot-fslc will be correctly built?

I don't really understand your build problem. From what I understand,
you should override the UBOOT_BINARY name in your bbappend, so bitbake
will find your binary and stop complaining.


Daiane

>
>
> Thanks for the help,
>
> Sincerely,
> --
> Romain Bazile
> Hardware R Engineer
> www.ubiant.com
> --
> ___
> 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] How to apply Preempt-rt patch for i.mx6ul board in yocto

[Daiane Angolini]

On Fri, Jun 16, 2017 at 3:20 AM, Hiro Sato  wrote:
> Hi all,
>
>
> I would like to apply PREEMPT-RT patch for i.mx6ul board in yocto.
>
> However I was not able to do it, so I would like you to tell me the way.
>
>
>
> Right now I use yocto 2.0 (Jethro).
>
> I found linux-yocto-rt_4.1.bb file in
> sources/poky/meta/recipes-kernel/linux.
>
> After bitbake I checked $ uname -a, but it did not say PREEMPT RT.
>
>
>
> I think I would be able to make preempt rt kernel image if I could correctly
> apply linux-yocto-rt_4.1.bb.
>
> How can I apply the recipe ? Or if there are other way to make preempt rt
> kernel image, would you tell me the way please?
>
>
>
> And I found a readme file which says "In order to build the image with the
> linux-yocto-rt kernel, be sure to include the following line in your
> local.conf, bblayers.conf, or your $MACHINE.conf.
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" " in
> sources/poky/meta/recipes-rt.
>
> So I added the line in my bblayers.conf and local.conf, but I could not make
> rt image.
>
> In the readme file, it also says about core-image-minimal. It means that we
> can use linux-yocto-rt only in core-image-minimal image? I would like to use
> other image.
>
>
>
> Furthermore, I found linux-fslc-mx6-rt_3.14-1.0.x.bb in
> sources/meta-fsl-arm/receipes-kernel/linux.
>
> Does it have relation?

Have you tried this kernel? I don't remember if it has imx6UL support,
but at least it's a closer base kernel with imx6 support.

I don't think linux-yocto-rt_4.1 has imx6UL support also, as imx6UL
was not around on jethro. imx6ulevk machine file was introduced only
2016.

Maybe it's easier to use a more current yocto release instead.


Daiane

>
>
>
> Thank you for reading.
>
> I am looking forward to your reply.
>
>
>
> Best regards,
>
> Sato
>
>
> --
> ___
> 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] [PATCH] imx-kobs: Fix a typo

[Daiane Angolini]

Thanks, the fix got applied faster than my build

Daiane

On Fri, May 19, 2017 at 2:29 PM, Otavio Salvador
 wrote:
> On Fri, May 19, 2017 at 2:17 PM, Khem Raj  wrote:
>>
>> ---
>
>
> Applied! :-)
>
> --
> 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
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [3rdparty][PATCH] WaRP7: Change board maintainer

[Daiane Angolini]

On Thu, May 18, 2017 at 10:15 AM, Pierre-Jean TEXIER
<texier@gmail.com> wrote:
> Signed-off-by: Pierre-Jean TEXIER <texier@gmail.com>

Acked-by: Daiane Angolini <daiane.angol...@nxp.com>


> ---
>  conf/machine/imx7s-warp.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/machine/imx7s-warp.conf b/conf/machine/imx7s-warp.conf
> index 5ded4e4..7a23fd6 100644
> --- a/conf/machine/imx7s-warp.conf
> +++ b/conf/machine/imx7s-warp.conf
> @@ -2,7 +2,7 @@
>  #@NAME: WaRP7
>  #@SOC: i.MX7S
>  #@DESCRIPTION: Machine configuration for i.MX7S WaRP board.
> -#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
> +#@MAINTAINER: Pierre-Jean Texier <texier@gmail.com>
>
>  MACHINEOVERRIDES =. "mx7:mx7d:"
>
> --
> 1.9.1
>
> --
> ___
> 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] [3rdparty][PATCH] linux-warp7: Bump revision to a543d1b

[Daiane Angolini]

On Thu, May 18, 2017 at 3:29 AM, Pierre-Jean TEXIER
<texier@gmail.com> wrote:
> It includes the following changes:
> c602497 : Rename the intermediate node to imx7s-warp
> 9f76487 : [WaRP7] PMIC swbst reg always-on
>
> Signed-off-by: Pierre-Jean TEXIER <texier@gmail.com>

Oh, I'm sorry. Regarding the patch itself:

Acked-by: Daiane Angolini <daiane.angol...@nxp.com>

> ---
>  recipes-kernel/linux/linux-warp7_4.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-warp7_4.1.bb 
> b/recipes-kernel/linux/linux-warp7_4.1.bb
> index 7328a47..71341dc 100644
> --- a/recipes-kernel/linux/linux-warp7_4.1.bb
> +++ b/recipes-kernel/linux/linux-warp7_4.1.bb
> @@ -9,7 +9,7 @@ with additional patches to cover devices specific on WaRP7 
> board."
>  DEPENDS += "lzop-native bc-native"
>
>  SRCBRANCH = "4.1-1.0.x-imx"
> -SRCREV = "db742e847b1ea1a01c241703014b6f2182fc21a5"
> +SRCREV = "a543d1bd884028bed97c06ae4087e051a9176499"
>  LOCALVERSION = "-${SRCBRANCH}-warp7"
>
>  SRC_URI = "git://github.com/warp7/linux-fslc.git;branch=${SRCBRANCH} \
> --
> 1.9.1
>
> --
> ___
> 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] [3rdparty][PATCH] linux-warp7: Bump revision to a543d1b

[Daiane Angolini]

Hi Pierre-Jean,

You've been working a lot with WaRP7 kernel, would you mind to be the
WaRP7 maintainer in meta-freescale-3dparty [1]?

If you accept, please send the patch

[1] 
https://github.com/Freescale/meta-freescale-3rdparty/blob/master/conf/machine/imx7s-warp.conf#L5

Thanks in advance,
Daiane

On Thu, May 18, 2017 at 3:29 AM, Pierre-Jean TEXIER
 wrote:
> It includes the following changes:
> c602497 : Rename the intermediate node to imx7s-warp
> 9f76487 : [WaRP7] PMIC swbst reg always-on
>
> Signed-off-by: Pierre-Jean TEXIER 
> ---
>  recipes-kernel/linux/linux-warp7_4.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-warp7_4.1.bb 
> b/recipes-kernel/linux/linux-warp7_4.1.bb
> index 7328a47..71341dc 100644
> --- a/recipes-kernel/linux/linux-warp7_4.1.bb
> +++ b/recipes-kernel/linux/linux-warp7_4.1.bb
> @@ -9,7 +9,7 @@ with additional patches to cover devices specific on WaRP7 
> board."
>  DEPENDS += "lzop-native bc-native"
>
>  SRCBRANCH = "4.1-1.0.x-imx"
> -SRCREV = "db742e847b1ea1a01c241703014b6f2182fc21a5"
> +SRCREV = "a543d1bd884028bed97c06ae4087e051a9176499"
>  LOCALVERSION = "-${SRCBRANCH}-warp7"
>
>  SRC_URI = "git://github.com/warp7/linux-fslc.git;branch=${SRCBRANCH} \
> --
> 1.9.1
>
> --
> ___
> 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] [PATCH] Update machine description fields

[Daiane Angolini]

Change description fields from Freescale to NXP in machine files to align to
2016 corporate transfer to NXP.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/machine/b4420qds-64b.conf   | 4 ++--
 conf/machine/b4420qds.conf   | 4 ++--
 conf/machine/b4860qds-64b.conf   | 4 ++--
 conf/machine/b4860qds.conf   | 4 ++--
 conf/machine/c293pcie.conf   | 4 ++--
 conf/machine/imx23evk.conf   | 4 ++--
 conf/machine/imx28evk.conf   | 4 ++--
 conf/machine/imx51evk.conf   | 4 ++--
 conf/machine/imx53ard.conf   | 4 ++--
 conf/machine/imx53qsb.conf   | 4 ++--
 conf/machine/ls1021atwr.conf | 4 ++--
 conf/machine/p2041rdb.conf   | 4 ++--
 conf/machine/p3041ds.conf| 4 ++--
 conf/machine/p4080ds.conf| 4 ++--
 conf/machine/p5020ds-64b.conf| 4 ++--
 conf/machine/p5020ds.conf| 4 ++--
 conf/machine/p5040ds-64b.conf| 4 ++--
 conf/machine/p5040ds.conf| 4 ++--
 conf/machine/t1023rdb-64b.conf   | 4 ++--
 conf/machine/t1023rdb.conf   | 4 ++--
 conf/machine/t1024rdb-64b.conf   | 4 ++--
 conf/machine/t1024rdb.conf   | 4 ++--
 conf/machine/t1040d4rdb-64b.conf | 4 ++--
 conf/machine/t1040d4rdb.conf | 4 ++--
 conf/machine/t1042d4rdb-64b.conf | 4 ++--
 conf/machine/t1042d4rdb.conf | 4 ++--
 conf/machine/t2080qds-64b.conf   | 4 ++--
 conf/machine/t2080qds.conf   | 4 ++--
 conf/machine/t2080rdb-64b.conf   | 4 ++--
 conf/machine/t2080rdb.conf   | 4 ++--
 conf/machine/t4160qds-64b.conf   | 4 ++--
 conf/machine/t4160qds.conf   | 4 ++--
 conf/machine/t4240qds-64b.conf   | 4 ++--
 conf/machine/t4240qds.conf   | 4 ++--
 conf/machine/t4240rdb-64b.conf   | 4 ++--
 conf/machine/t4240rdb.conf   | 4 ++--
 conf/machine/twr-vf65gs10.conf   | 4 ++--
 37 files changed, 74 insertions(+), 74 deletions(-)

diff --git a/conf/machine/b4420qds-64b.conf b/conf/machine/b4420qds-64b.conf
index 333ee73..2db738e 100644
--- a/conf/machine/b4420qds-64b.conf
+++ b/conf/machine/b4420qds-64b.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale B4420QDS-64B
+#@NAME: NXP B4420QDS-64B
 #@SOC: b4420
-#@DESCRIPTION: Machine configuration for Freescale QorIQ Qonverge B4420
+#@DESCRIPTION: Machine configuration for NXP QorIQ Qonverge B4420
 #  Application Development System with ppce6500 core in
 #  64b mode
 #@MAINTAINER: Chunrong Guo <b40...@freescale.com>
diff --git a/conf/machine/b4420qds.conf b/conf/machine/b4420qds.conf
index e78f6d8..bba3f97 100644
--- a/conf/machine/b4420qds.conf
+++ b/conf/machine/b4420qds.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale B4420QDS
+#@NAME: NXP B4420QDS
 #@SOC: b4420
-#@DESCRIPTION: Machine configuration for Freescale QorIQ Qonverge B4420
+#@DESCRIPTION: Machine configuration for NXP QorIQ Qonverge B4420
 #  Application Development System with ppce6500 core in
 #  32b mode
 #@MAINTAINER: Chunrong Guo <b40...@freescale.com>
diff --git a/conf/machine/b4860qds-64b.conf b/conf/machine/b4860qds-64b.conf
index 6dc2a2b..a7a5c50 100644
--- a/conf/machine/b4860qds-64b.conf
+++ b/conf/machine/b4860qds-64b.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale B4860QDS-64B
+#@NAME: NXP B4860QDS-64B
 #@SOC: b4860
-#@DESCRIPTION: Machine configuration for Freescale QorIQ Qonverge B4860
+#@DESCRIPTION: Machine configuration for NXP QorIQ Qonverge B4860
 #  Application Development System with ppce6500 core in
 #  64b mode
 #@MAINTAINER: Chunrong Guo <b40...@freescale.com>
diff --git a/conf/machine/b4860qds.conf b/conf/machine/b4860qds.conf
index 13fc664..ee4180b 100644
--- a/conf/machine/b4860qds.conf
+++ b/conf/machine/b4860qds.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale B4860QDS
+#@NAME: NXP B4860QDS
 #@SOC: b4860
-#@DESCRIPTION: Machine configuration for Freescale QorIQ Qonverge B4860
+#@DESCRIPTION: Machine configuration for NXP QorIQ Qonverge B4860
 #  Application Development System with ppce6500 core in
 #  32b mode
 #@MAINTAINER: Chunrong Guo <b40...@freescale.com>
diff --git a/conf/machine/c293pcie.conf b/conf/machine/c293pcie.conf
index 3cf443b..da61920 100644
--- a/conf/machine/c293pcie.conf
+++ b/conf/machine/c293pcie.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale C293PCIE
+#@NAME: NXP C293PCIE
 #@SOC: c293pcie
-#@DESCRIPTION: Machine configuration for Freescale C29x Crypto Coprocessor
+#@DESCRIPTION: Machine configuration for NXP C29x Crypto Coprocessor
 #  PCI Express Adapter Platform with ppce500v2 core
 #@MAINTAINER: Chunrong Guo <b40...@freescale.com>
 
diff --git a/conf/machine/imx23evk.conf b/conf/machine/imx23evk.conf
index 6c4daa5..5b977ca 100644
--- a/conf/machine/imx23evk.conf
+++ b/conf/machine/imx23evk.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
-#@NAME: Freescale i.MX23 Evaluation Kit
+#@NAME: NXP i.MX23 Evaluation Kit
 #@SOC: i.MX23
-#@DESCRIPTION: Machine configuration for Freescale i.MX23 Evaluation Kit
+#@DESCRIPTION: 

[meta-freescale] Updates to Documentation (morty and master) in 2017-02-01

[Daiane Angolini]

Hello,

I pushed following updates:


commit 81c8e562b464e686b01c9a6189e1f1be24690a72
Author: Fabio Berton <fabio.ber...@ossystems.com.br>
Date:   Tue Jan 31 16:41:23 2017 -0200

RN: Updates from bitbake-metadata2doc.sh

Signed-off-by: Fabio Berton <fabio.ber...@ossystems.com.br>
Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>

commit 95d02ac489815e26f69b05e3338f3c85251be2fb
Author: Fabio Berton <fabio.ber...@ossystems.com.br>
Date:   Tue Jan 31 16:41:22 2017 -0200

README: Update Debian/Ubuntu dependency package list

Morty release uses python3 to generate Sphinx documentation, also
we need to install fonts-liberation package to generate blockdiag.

Signed-off-by: Fabio Berton <fabio.ber...@ossystems.com.br>
Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>


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

Re: [meta-freescale] [Documentation][PATCH 1/2] README: Update Debian/Ubuntu dependency package list

[Daiane Angolini]

On Tue, Jan 31, 2017 at 4:23 PM, Fabio Berton
<fabio.ber...@ossystems.com.br> wrote:
> Hi Daiane,
>
> Oh my mistake, the correct is python3-pip, I'll send a v2.
>
> If you install python3-pip and run pip3 install reportlab
> sphinxcontrib-blockdiag the soc-tree.diag is build correctly?

In fact, for some reason, even before I upgrade the packages on my
host machine I could see the soc-tree properly displayed (I was not
able to notice any change).

I'm not against the upgrade (which I understand is natural). But I was
not able to note the difference.

I'm going to merge your patches at the end of my day.

Thanks,
Daiane


>
> Thanks!
>
> On Tue, Jan 31, 2017 at 4:12 PM, Daiane Angolini <daiane.l...@gmail.com>
> wrote:
>>
>> Hi Fabio,
>>
>>
>> On Fri, Jan 27, 2017 at 5:03 PM, Fabio Berton
>> <fabio.ber...@ossystems.com.br> wrote:
>> > Morty release uses python3 to generate Sphinx documentation, also
>> > we need to install fonts-liberation package to generate blockdiag.
>> >
>> > Signed-off-by: Fabio Berton <fabio.ber...@ossystems.com.br>
>> > ---
>> >  README | 7 ---
>> >  1 file changed, 4 insertions(+), 3 deletions(-)
>> >
>> > diff --git a/README b/README
>> > index d1048a8..8185ad5 100644
>> > --- a/README
>> > +++ b/README
>> > @@ -4,9 +4,10 @@ Freescale Community BSP Documentation
>> >  The documentation is written using the Sphinx documentation system. To
>> >  install it in Debian/Ubuntu, please do:
>> >
>> > -  #: apt-get install libfreetype6-dev libjpeg8-dev python-dev
>> > python-pip \
>> > - python-sphinx texlive-fonts-recommended texlive-latex-extra
>> > zlib1g-dev
>> > -  #: pip install reportlab sphinxcontrib-blockdiag
>> > +  #: apt-get install libfreetype6-dev libjpeg8-dev python3-dev
>> > python-pip3 \
>>
>> python-pip3 did not worked for me.
>>
>> Would it be pytthon3-pip of we should start diverging the Debian from
>> the Ubuntu procedure?
>>
>>
>> Daiane
>>
>> > + python3-sphinx texlive-fonts-recommended texlive-latex-extra
>> > zlib1g-dev \
>> > + fonts-liberation
>> > +  #: pip3 install reportlab sphinxcontrib-blockdiag
>> >
>> >  Once this has been completed, you can run 'make' in each of the
>> > Documentation
>> >  folders to review the available targets for building.
>> > --
>> > 2.11.0
>> >
>> > --
>> > ___
>> > 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] [Documentation][PATCH 1/2] README: Update Debian/Ubuntu dependency package list

[Daiane Angolini]

Hi Fabio,


On Fri, Jan 27, 2017 at 5:03 PM, Fabio Berton
 wrote:
> Morty release uses python3 to generate Sphinx documentation, also
> we need to install fonts-liberation package to generate blockdiag.
>
> Signed-off-by: Fabio Berton 
> ---
>  README | 7 ---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/README b/README
> index d1048a8..8185ad5 100644
> --- a/README
> +++ b/README
> @@ -4,9 +4,10 @@ Freescale Community BSP Documentation
>  The documentation is written using the Sphinx documentation system. To
>  install it in Debian/Ubuntu, please do:
>
> -  #: apt-get install libfreetype6-dev libjpeg8-dev python-dev python-pip \
> - python-sphinx texlive-fonts-recommended texlive-latex-extra zlib1g-dev
> -  #: pip install reportlab sphinxcontrib-blockdiag
> +  #: apt-get install libfreetype6-dev libjpeg8-dev python3-dev python-pip3 \

python-pip3 did not worked for me.

Would it be pytthon3-pip of we should start diverging the Debian from
the Ubuntu procedure?


Daiane

> + python3-sphinx texlive-fonts-recommended texlive-latex-extra zlib1g-dev 
> \
> + fonts-liberation
> +  #: pip3 install reportlab sphinxcontrib-blockdiag
>
>  Once this has been completed, you can run 'make' in each of the Documentation
>  folders to review the available targets for building.
> --
> 2.11.0
>
> --
> ___
> 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] [PATCH] machine: Change maintainer email to nxp.com for Daiane Angolini

[Daiane Angolini]

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 conf/machine/imx51evk.conf| 2 +-
 conf/machine/imx53ard.conf| 2 +-
 conf/machine/imx6dlsabreauto.conf | 2 +-
 conf/machine/imx6qsabreauto.conf  | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/conf/machine/imx51evk.conf b/conf/machine/imx51evk.conf
index e6904f9..9b5757a 100644
--- a/conf/machine/imx51evk.conf
+++ b/conf/machine/imx51evk.conf
@@ -2,7 +2,7 @@
 #@NAME: Freescale i.MX51 Evaluation Kit
 #@SOC: i.MX51
 #@DESCRIPTION: Machine configuration for Freescale i.MX51 Evaluation Kit
-#@MAINTAINER: Daiane Angolini <daiane.angol...@freescale.com>
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
 
 MACHINEOVERRIDES =. "mx5:mx51:"
 
diff --git a/conf/machine/imx53ard.conf b/conf/machine/imx53ard.conf
index f416c95..71ceb95 100644
--- a/conf/machine/imx53ard.conf
+++ b/conf/machine/imx53ard.conf
@@ -2,7 +2,7 @@
 #@NAME: Freescale i.MX53 SABRE Automotive Board
 #@SOC: i.MX53
 #@DESCRIPTION: Machine configuration for Freescale i.MX53 SABRE Automotive 
Board
-#@MAINTAINER: Daiane Angolini <daiane.angol...@freescale.com>
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
 
 MACHINEOVERRIDES =. "mx5:mx53:"
 
diff --git a/conf/machine/imx6dlsabreauto.conf 
b/conf/machine/imx6dlsabreauto.conf
index ae3e815..51fb702 100644
--- a/conf/machine/imx6dlsabreauto.conf
+++ b/conf/machine/imx6dlsabreauto.conf
@@ -2,7 +2,7 @@
 #@NAME: NXP i.MX6DL SABRE Automotive
 #@SOC: i.MX6DL
 #@DESCRIPTION: Machine configuration for NXP i.MX6DL SABRE Automotive
-#@MAINTAINER: Daiane Angolini <daiane.angol...@freescale.com>
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
 
 MACHINEOVERRIDES =. "mx6:mx6dl:"
 
diff --git a/conf/machine/imx6qsabreauto.conf b/conf/machine/imx6qsabreauto.conf
index 7bb0cfa..e419c5d 100644
--- a/conf/machine/imx6qsabreauto.conf
+++ b/conf/machine/imx6qsabreauto.conf
@@ -2,7 +2,7 @@
 #@NAME: NXP i.MX6Q SABRE Automotive
 #@SOC: i.MX6Q
 #@DESCRIPTION: Machine configuration for NXP i.MX6Q SABRE Automotive
-#@MAINTAINER: Daiane Angolini <daiane.angol...@freescale.com>
+#@MAINTAINER: Daiane Angolini <daiane.angol...@nxp.com>
 
 MACHINEOVERRIDES =. "mx6:mx6q:"
 
-- 
2.7.4

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

[meta-freescale] Updates to Documentation (master and morty) in 2017-01-25

[Daiane Angolini]

Hello,

I pushed following updates:

commit b12ce9cecf35c8923dde3614c816dd82e85f259b
Author: Fabio Berton 
Date:   Fri Jan 20 15:21:43 2017 -0200

RN: Updates from bitbake-metadata2doc.sh

Signed-off-by: Fabio Berton 

commit 1ae16ee817e0be02ba58d98a6af4cb9d0deda4a3
Author: Fabio Berton 
Date:   Fri Jan 20 15:21:42 2017 -0200

scripts/bitbake-metadata2doc: Filter soc-family to generate soc-tree

SOC_FAMILY variable was removed from Freescale's layers and we need to
use MACHINEOVERRIDES variable to get data and generate soc tree
diagram.

Signed-off-by: Fabio Berton 


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

Re: [meta-freescale] [Question] IMAGE_FSTYPES has no effect on master

[Daiane Angolini]

On Sat, Jan 7, 2017 at 2:08 AM, Amin Bandali <amin.band...@gmail.com> wrote:
> Hello Daiane,
>
> Thanks for the reply, that indeed worked! It'd be nice to have this
> change merged upstream.

Great!

Can you, please, prepare the patch and send it to review?


Daiane
>
> Amin
>
> On Fri, Jan 6, 2017 at 10:30 AM, Daiane Angolini <daiane.l...@gmail.com> 
> wrote:
>> On Thu, Jan 5, 2017 at 9:33 PM, Amin Bandali <amin.band...@gmail.com> wrote:
>>> Hello,
>>>
>>> Up until krogoth, I could adjust IMAGE_FSTYPES in my local.conf to generate
>>> various types of archives:
>>>
>>> IMAGE_FSTYPES += "tar.bz2 tar.gz"
>>>
>>> However, I've noticed that this has no effect on master, and only wic.gz
>>> archives are generated.
>>>
>>> The only relevant piece of information I came across was the following 
>>> commit:
>>>
>>> https://github.com/Freescale/meta-freescale-3rdparty/commit/038b0b737f55ebd2cbc29c91c8274fed422142d4
>>>
>>> Any thoughts on how I could generate other image types on master, like I 
>>> used to
>>> on krogoth?
>>
>> Please, try to change the code on
>> https://github.com/Freescale/meta-freescale-3rdparty/blob/master/conf/machine/wandboard.conf#L49
>>
>> Instead of
>> IMAGE_FSTYPES = "wic.gz"
>>
>> use
>>
>> IMAGE_FSTYPES ?= "wic.gz"
>>
>>
>> Keep IMAGE_FSTYPES += "tar.bz2 tar.gz" in your local.conf, give it a
>> try and let us know.
>>
>> Daiane
>>>
>>> (I need a tar.gz or tar.bz2 so that I can un-tar them with sudo so that all 
>>> the
>>> files and directories have correct permissions. Because the files and 
>>> folders
>>> generated by bitbake in this directory
>>> {YOCTO_BUILD_DIR}/tmp/work/wandboard-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs
>>> are owned by a regular user and when booting over NFS, those permissions 
>>> cause
>>> trouble.)
>>>
>>> Thanks,
>>> Amin
>>> --
>>> ___
>>> 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] [Question] IMAGE_FSTYPES has no effect on master

[Daiane Angolini]

On Thu, Jan 5, 2017 at 9:33 PM, Amin Bandali  wrote:
> Hello,
>
> Up until krogoth, I could adjust IMAGE_FSTYPES in my local.conf to generate
> various types of archives:
>
> IMAGE_FSTYPES += "tar.bz2 tar.gz"
>
> However, I've noticed that this has no effect on master, and only wic.gz
> archives are generated.
>
> The only relevant piece of information I came across was the following commit:
>
> https://github.com/Freescale/meta-freescale-3rdparty/commit/038b0b737f55ebd2cbc29c91c8274fed422142d4
>
> Any thoughts on how I could generate other image types on master, like I used 
> to
> on krogoth?

Please, try to change the code on
https://github.com/Freescale/meta-freescale-3rdparty/blob/master/conf/machine/wandboard.conf#L49

Instead of
IMAGE_FSTYPES = "wic.gz"

use

IMAGE_FSTYPES ?= "wic.gz"


Keep IMAGE_FSTYPES += "tar.bz2 tar.gz" in your local.conf, give it a
try and let us know.

Daiane
>
> (I need a tar.gz or tar.bz2 so that I can un-tar them with sudo so that all 
> the
> files and directories have correct permissions. Because the files and folders
> generated by bitbake in this directory
> {YOCTO_BUILD_DIR}/tmp/work/wandboard-poky-linux-gnueabi/{IMAGE}/1.0-r0/rootfs
> are owned by a regular user and when booting over NFS, those permissions cause
> trouble.)
>
> Thanks,
> Amin
> --
> ___
> 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] u-boot-imx-mfgtool recipe builds nothing

[Daiane Angolini]

On Fri, Jan 6, 2017 at 10:19 AM, Rogers, Simon
 wrote:
> Hi
>
> I’m using Yocto fido and trying to build a U-boot for the Manufacturing Tool
> for a Hummingboard in order to do a USB OTG download.


I don't remember what happened on fido. But I think hummingboard and
manufacturing tool would not work together without changing the source
code.

But I'm guessing, I have never really built mfgtools before.

Daiane
>
> Documentation suggests that the recipe u-boot-imx-mfgtool in meta-fsl-arm
> should create a U-boot for the mfgtool, but if I bitbake it I find that
> nothing gets compiled, and RPM packages are created which are empty, despite
> it downloading a U-boot 2014.04 repository. There are no warnings or errors.
>
>
>
> Should this recipe work? If not could anyone tell me how to build a U-boot
> for Mfgtool please? My standard U-boot being built for my target by Yocto is
> 2013.10.
>
>
>
> Thanks
>
> Simon
>
>
>
> **
> This e-mail is from Ultra Electronics Limited and any attachments to it are
> confidential to the
> intended recipient and may also be privileged. If you have received it in
> error please notify the
> sender and delete it from your system. If you are not the intended recipient
> you must not copy
> it or use it for any purpose nor disclose or distribute its contents to any
> other person.
>
> All communications may be subject to interception or monitoring for
> operational and/or security purposes.
> Please rely on your own virus checking as the sender cannot accept any
> liability for any damage arising
> from any bug or virus infection. Ultra Electronics Limited is a company
> registered in England and Wales,
> registration number 2830644. The address of its registered office is 417
> Bridport Road, Greenford,
> Middlesex, UB6 8UA.
> **
>
>
> --
> ___
> 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] [meta-freescale-distro][PATCH 5/6] add fsl-qoriq distro conf file

[Daiane Angolini]

Would be possible to add a DESCRIPTION or a comment header to explain
what is purpose of this distro and what is the main goal?

For example, I see there is a WHITELIST flag for license, there are
definitions for java providers.

I'm not sure, but I feel like out of context looking to this distro.


Daiane

On Thu, Jan 5, 2017 at 7:51 AM, Zhenhua Luo  wrote:
> Signed-off-by: Zhenhua Luo 
> ---
>  conf/distro/fsl-qoriq.conf | 26 ++
>  1 file changed, 26 insertions(+)
>  create mode 100644 conf/distro/fsl-qoriq.conf
>
> diff --git a/conf/distro/fsl-qoriq.conf b/conf/distro/fsl-qoriq.conf
> new file mode 100644
> index 000..4b0e44b
> --- /dev/null
> +++ b/conf/distro/fsl-qoriq.conf
> @@ -0,0 +1,26 @@
> +require conf/distro/poky.conf
> +
> +DISTRO = "fsl-qoriq"
> +DISTRO_NAME = "QorIQ SDK (FSL Reference Distro)"
> +SDK_VENDOR = "-fsl"
> +MAINTAINER = "Zhenhua Luo "
> +
> +TARGET_VENDOR = "-fsl"
> +
> +POKY_DEFAULT_DISTRO_FEATURES_remove = " ptest"
> +DISTRO_FEATURES_DEFAULT_remove = " pcmcia 3g"
> +DISTRO_FEATURES_DEFAULT_append = " benchmark vfat ext2 mtd pam \
> +alsa pulseaudio perl ppp python usbhost virtualization db"
> +
> +# When meta-openenbedded layer included, bitbake will complain that
> +# multiple providers are available for jpeg (jpeg, libjpeg-turbo)
> +PREFERRED_PROVIDER_jpeg ?= "jpeg"
> +PREFERRED_PROVIDER_jpeg-native ?= "jpeg-native"
> +
> +QEMU_TARGETS_append_pn-qemu-native = " ppc64"
> +PREFERRED_PROVIDER_virtual/java-initial-native = "cacao-initial-native"
> +PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
> +PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
> +
> +# whiteliste restricted license
> +LICENSE_FLAGS_WHITELIST = "non-commercial_netperf commercial_lame"
> --
> 2.7.4
>
> --
> ___
> 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] [meta-freescale-distro][PATCH 2/6] packagegroup-fsl-virtualization: add recipe

[Daiane Angolini]

On Thu, Jan 5, 2017 at 7:51 AM, Zhenhua Luo  wrote:
> packagegroup-fsl-virtualization defines the packages group for virtualization
> support.
>
> Signed-off-by: Zhenhua Luo 
> ---
>  .../packagegroup-fsl-virtualization.bb | 24 
> ++
>  1 file changed, 24 insertions(+)
>  create mode 100644 
> recipes-fsl/packagegroups/packagegroup-fsl-virtualization.bb
>
> diff --git a/recipes-fsl/packagegroups/packagegroup-fsl-virtualization.bb 
> b/recipes-fsl/packagegroups/packagegroup-fsl-virtualization.bb
> new file mode 100644
> index 000..de4454a
> --- /dev/null
> +++ b/recipes-fsl/packagegroups/packagegroup-fsl-virtualization.bb
> @@ -0,0 +1,24 @@
> +# Copyright (C) 2016 NXP Semiconductors
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +DESCRIPTION = "Package group used by NXO Community to provide virtualization 
> packages"

s/NXO/NXP

Can you, please, elaborate what you mean by "virtualization"? Can you,
please, try to elaborate why this packagegroup is important?


Daiane
> +SUMMARY = "NXP Community Package group - virtualization"
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit packagegroup
> +
> +PACKAGES = "${PN}"
> +
> +DOCKER-PKGS = ""
> +DOCKER-PKGS_qoriq-arm = "docker docker-registry"
> +DOCKER-PKGS_qoriq-arm64 = "docker docker-registry"
> +
> +RDEPENDS_${PN}_qoriq = "${@bb.utils.contains('DISTRO_FEATURES', 'x11', \
> +'libvirt \
> +libvirt-libvirtd \
> +libvirt-virsh \
> +lxc \
> +qemu', \
> +'', d)} \
> +${DOCKER-PKGS} \
> +"
> --
> 2.7.4
>
> --
> ___
> 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] [meta-freescale-distro][PATCH 1/6] packagegroup-fsl-networking: add recipe

[Daiane Angolini]

On Thu, Jan 5, 2017 at 7:51 AM, Zhenhua Luo  wrote:
> packagegroup-fsl-networking defines the packages group for networking
> support.
>
> Signed-off-by: Zhenhua Luo 
> ---
>  .../packagegroups/packagegroup-fsl-networking.bb   | 173 
> +
>  1 file changed, 173 insertions(+)
>  create mode 100644 recipes-fsl/packagegroups/packagegroup-fsl-networking.bb
>
> diff --git a/recipes-fsl/packagegroups/packagegroup-fsl-networking.bb 
> b/recipes-fsl/packagegroups/packagegroup-fsl-networking.bb
> new file mode 100644
> index 000..f2f83b9
> --- /dev/null
> +++ b/recipes-fsl/packagegroups/packagegroup-fsl-networking.bb
> @@ -0,0 +1,173 @@
> +# Copyright (C) 2016 NXP Semiconductors
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +DESCRIPTION = "Package group used by NXO Community to provide networking 
> packages"

s/NXO/NXP



Daiane
> +SUMMARY = "NXP Community Package group - networking"
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit packagegroup
> +
> +PACKAGES = "${PN}-core ${PN}-core-extend \
> +${PN}-client ${PN}-server \
> +${PN}-extend"
> +
> +QORIQ-PKGS = ""
> +# NOTE: Remove the conditional pkc-host inclusion and all traces of c29x_pkc
> +# DISTRO_FEATURE if pkc-host no longer requires customized cryptodev patches
> +QORIQ-PKGS_qoriq = "asf merge-files udev-rules-qoriq \
> +${@bb.utils.contains('DISTRO_FEATURES', 'c29x_pkc', 'pkc-host', '', d)} \
> +"
> +
> +QORIQ-PKGS_append_qoriq-ppc = " \
> +apptrk \
> +dpa-offload \
> +eth-config \
> +usdpaa-apps \
> +hypervisor-partman \
> +"
> +QORIQ-PKGS_append_fsl-lsch3 = " restool"
> +QORIQ-PKGS_append_e500v2 = "apptrk testfloat"
> +QORIQ-PKGS_append_e6500-64b = " kernel-module-ceetm"
> +
> +# e6500 only support 64bit hypervisor
> +QORIQ-PKGS_remove_e6500 = "hypervisor-partman"
> +QORIQ-PKGS_append_e6500 = " lib64-hypervisor-partman"
> +
> +QORIQ-PKGS_append_c293pcie = " skmm-ep"
> +QORIQ-PKGS_append_ls1043ardb = " eth-config usdpaa usdpaa-apps dpa-offload"
> +QORIQ-PKGS_append_ls1046rrdb = " eth-config usdpaa usdpaa-apps dpa-offload"
> +QORIQ-PKGS_append_p1023rdb = " fmc eth-config"
> +QORIQ-PKGS_append_b4860qds = "\
> +ipc-ust \
> +kernel-module-ipc-multi \
> +kernel-module-ipc-single \
> +"
> +QORIQ-PKGS_append_b4420qds = "\
> +ipc-ust \
> +kernel-module-ipc-multi \
> +kernel-module-ipc-single \
> +"
> +QORIQ-PKGS__append_p4080ds = "\
> +skmm-ep \
> +skmm-host \
> +"
> +QORIQ-PKGS_append_t4240qds = "\
> +skmm-ep \
> +skmm-host \
> +"
> +QORIQ-PKGS_append_t1040 = " \
> +ceetm \
> +kernel-module-ar \
> +kernel-module-uio-seville \
> +"
> +QORIQ-PKGS_append_t1042 = " \
> +ceetm \
> +kernel-module-ar \
> +"
> +
> +RDEPENDS_${PN}-core_qoriq = " \
> +coreutils \
> +elfutils \
> +e2fsprogs \
> +e2fsprogs-badblocks \
> +e2fsprogs-e2fsck \
> +e2fsprogs-tune2fs  \
> +file \
> +i2c-tools \
> +kmod \
> +libhugetlbfs \
> +lmsensors-sensors \
> +memtester \
> +minicom \
> +pkgconfig \
> +python-subprocess \
> +python-datetime \
> +python-json \
> +procps \
> +psmisc \
> +sysfsutils \
> +sysklogd \
> +sysstat \
> +${QORIQ-PKGS} \
> +"
> +
> +RDEPENDS_${PN}-core-extend_qoriq = " \
> +bc \
> +chkconfig \
> +cronie \
> +db \
> +debianutils \
> +dtc \
> +lsof \
> +man \
> +man-pages \
> +oprofile \
> +parted \
> +perf \
> +rng-tools \
> +rt-tests \
> +sqlite3 \
> +strongswan \
> +texinfo \
> +u-boot-mkimage \
> +unzip \
> +usbutils \
> +watchdog \
> +which \
> +xz  \
> +zip \
> +"
> +
> +RDEPENDS_${PN}-client_qoriq = " \
> +bridge-utils \
> +ethtool \
> +iproute2 \
> +iproute2-tc \
> +iptables \
> +iputils \
> +inetutils \
> +inetutils-ftp \
> +inetutils-hostname \
> +inetutils-ifconfig \
> +inetutils-logger \
> +inetutils-ping \
> +inetutils-ping6 \
> +inetutils-rsh \
> +inetutils-syslogd \
> +inetutils-telnet \
> +inetutils-tftp \
> +inetutils-traceroute \
> +ipsec-tools \
> +ipsec-demo \
> +net-tools \
> +tcpdump \
> +"
> +
> +RDEPENDS_${PN}-server_qoriq = " \
> +inetutils-inetd \
> +inetutils-ftpd \
> +inetutils-rshd \
> +inetutils-tftpd \
> +inetutils-telnetd \
> +"
> +
> +RDEPENDS_${PN}-client_append_qoriq = "\
> +packagegroup-fsl-networking-server \
> +"
> +
> +RDEPENDS_${PN}-extend_qoriq = " \
> +bind \
> +curl \
> +dhcp-client \
> +libnfnetlink \
> +linuxptp \
> +ntpdate \
> +ppp \
> +ppp-dialin \
> +ptpd \
> +resolvconf \
> +rp-pppoe \
> +samba \
> +wget \
> +xinetd \
> +"
> --
> 2.7.4
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> 

Re: [meta-freescale] [meta-freescale-distro][PATCH 3/6] add fsl-image-networking demo image

[Daiane Angolini]

On Thu, Jan 5, 2017 at 7:51 AM, Zhenhua Luo  wrote:
> fsl-image-networking is the small demo image for networking core features
> support.
>
> Signed-off-by: Zhenhua Luo 
> ---
>  recipes-fsl/images/fsl-image-networking.bb | 13 +
>  1 file changed, 13 insertions(+)
>  create mode 100644 recipes-fsl/images/fsl-image-networking.bb
>
> diff --git a/recipes-fsl/images/fsl-image-networking.bb 
> b/recipes-fsl/images/fsl-image-networking.bb
> new file mode 100644
> index 000..ace2051
> --- /dev/null
> +++ b/recipes-fsl/images/fsl-image-networking.bb
> @@ -0,0 +1,13 @@
> +require recipes-core/images/core-image-minimal.bb
> +
> +SUMMARY = "Core image used for evaluating the NXP SOCs"
> +DESCRIPTION = "Core image which includes some helpful tools and NXP specific 
> \
> +packages. It is much more embedded-oriented to evaluate the NXP SOCs."

I don't understand what "much more embedded-oriented" means in this context.

Why the "networking" keyword is present in image name but there is no
reference of this in DESCRIPTION?

Daiane
> +
> +LICENSE = "MIT"
> +
> +IMAGE_INSTALL_append_qoriq = " \
> +packagegroup-fsl-networking-core \
> +packagegroup-fsl-networking-client \
> +packagegroup-fsl-tools-benchmark \
> +"
> --
> 2.7.4
>
> --
> ___
> 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] [3rdparty][PATCH] linux-warp7: Upgrade to version 4.1.36

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

Upgrade the kernel version and add a DESCRIPTION.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 recipes-kernel/linux/linux-warp7_4.1.bb | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-warp7_4.1.bb 
b/recipes-kernel/linux/linux-warp7_4.1.bb
index 3992824..c616c2d 100644
--- a/recipes-kernel/linux/linux-warp7_4.1.bb
+++ b/recipes-kernel/linux/linux-warp7_4.1.bb
@@ -3,10 +3,13 @@
 
 include recipes-kernel/linux/linux-fslc.inc
 
+DESCRIPTION = "Linux kernel based on linux-fsl-imx branch 4.1-1.0.x-imx from 
FSL Community BSP \
+with additional patches to cover devices specific on WaRP7 board."
+
 DEPENDS += "lzop-native bc-native"
 
 SRCBRANCH = "4.1-1.0.x-imx"
-SRCREV = "511f37a20970db04ae3e1aff5e48ca4626e9197b"
+SRCREV = "0b8a33ea8330d59202c0eb09f7deb7be046ce20a"
 LOCALVERSION = "-${SRCBRANCH}-warp7"
 
 SRC_URI = "git://github.com/warp7/linux-fslc.git;branch=${SRCBRANCH} \
-- 
2.7.4

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

Re: [meta-freescale] FSL_MIRROR error 404

[Daiane Angolini]

On Thu, Dec 8, 2016 at 5:29 AM, Takashi Matsuzawa
 wrote:
>
> Hello.
>
>
> it turned out that I am failing with all of the following manifests on 
> imx-4.1-krogoth branch on fsl-arm-yocto-bsp.git:
>
>
> default
>
> 4.1.15-2.0.0
>
> 4.1.15-2.0.1
>

I knew there are some files with problems. It looks like it's a IT
problem with the server I think.

I know they are working to fix it.

Daiane
>
> 
> From: Takashi Matsuzawa
> Sent: Thursday, December 8, 2016 3:19 PM
> To: meta-freescale@yoctoproject.org
> Subject: Re: FSL_MIRROR error 404
>
>
> Well, the blow also talks about this error.
>
>
> https://community.nxp.com/thread/433949
>
> Yocto failing fetch url for imx-vpu_5.4.33.bb | NXP Community
> community.nxp.com
> Hi, I have problem with downloading package with newest yocto for imx6: 
> WARNING: Failed to fetch URL
>
>
>
>
> 
> From: Takashi Matsuzawa
> Sent: Thursday, December 8, 2016 2:56 PM
> To: meta-freescale@yoctoproject.org
> Subject: FSL_MIRROR error 404
>
>
> Hello.
> I am trying to build freescale BSP from scratch (so none of my previous 
> downloads are used), and I am getting following error.
>
> >WARNING: imx-vpu-1_5.4.35-r0 do_fetch: Failed to fetch URL
> >http://www.freescale.com/lgfiles/NMG/MAD/YOCTO//imx-vpu-5.4.35.bin;fsl-eula=true,
> > attempting MIRRORS if available
> >ERROR: imx-vpu-1_5.4.35-r0 do_fetch: Fetcher failure: Fetch command failed 
> >with exit code 8, output:
> >http://www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-vpu-5.4.35.bin:
> >2016-12-08 14:24:51 ERROR 404: Not Found.
>
> I tried to open below through browser, or tried curl against above URL, and 
> getting 404 not found error.
>
> http://www.freescale.com/lgfiles/NMG/MAD/YOCTO/
>
> Should this be temporary and recovered soon?
>
>
> --
> ___
> 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] Updates to Documentation (master and morty)

[Daiane Angolini]

Hello,

I pushed following updates:

commit 9628be5d37395d6bc457afb76ad2fb8896942973
Author: Daiane Angolini <daiane.angol...@nxp.com>
Date:   Wed Nov 30 18:05:09 2016 -0200

bsp-scope: Include meta-freescale section

Since morty meta-fsl-arm and meta-fsl-ppc must not be used.

Use meta-freescale instead.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>

commit 6e57db6d24be02ef78bac6db63e574f7d6130ff8
Author: Daiane Angolini <daiane.angol...@nxp.com>
Date:   Wed Nov 30 18:05:08 2016 -0200

RN: Fix typo

    Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>

commit 07fd97286d1e8b3cb51df3a220b3d719fc3b5c07
Author: Daiane Angolini <daiane.angol...@nxp.com>
Date:   Wed Nov 30 18:05:07 2016 -0200

FAQ: Remove this document

There is no evidence this document is used. It's a while since last update.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>

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

Re: [meta-freescale] [Documentation][PATCH 2/2] bsp-scope: Include meta-freescale section

[Daiane Angolini]

On Tue, Nov 29, 2016 at 12:44 AM, Zhenhua Luo  wrote:
> Hi Daiane,
>

>> +
>> +The **meta-freescale** meta layer goal is to integrate the ARM SoC
> [Zhenhua Luo] QorIQ PPC targets are supported as well.
>
>> +based source code from Freescale, it includes **i.MX**, **Vybrid** and
>> **Layerscape** BSPs.
> [Zhenhua Luo] Please add QorIQ PPC in the list.
>
>


I just sent the v2. Thanks for the review ;-)

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

[meta-freescale] [Documentation][PATCH v2 3/3] bsp-scope: Include meta-freescale section

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

Since morty meta-fsl-arm and meta-fsl-ppc must not be used.

Use meta-freescale instead.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
changes since v1:
-Add PCC and QorIQ to the list
 release-notes/source/bsp-scope.rst | 33 +
 1 file changed, 33 insertions(+)

diff --git a/release-notes/source/bsp-scope.rst 
b/release-notes/source/bsp-scope.rst
index 44e1a8e..fd476c9 100644
--- a/release-notes/source/bsp-scope.rst
+++ b/release-notes/source/bsp-scope.rst
@@ -15,6 +15,39 @@ The scope of the |project_name| includes the meta layers:
provides the source code for |project_name| Release Notes (RN) and User 
Guide
(UG).
 
+Meta-freescale
+==
+
+Since the Yocto Project release 2.2 (Morty) the |project_name| changed the meta
+layers names. You can see the announcement
+`here 
<https://lists.yoctoproject.org/pipermail/meta-freescale/2016-October/019429.html>`_.
+
+The following table show the renaming upgrade path:
+
+== ==
+KrogothMorty
+== ==
+meta-fsl-arm   meta-freescale
+meta-fsl-ppc   meta-freescale
+meta-fsl-arm-extra meta-freescale-3rdparty
+meta-fsl-demos meta-freescale-distros
+== ==
+
+The **meta-fsl-arm** and **meta-fsl-ppc** meta layers are deprecated. The last
+release for these meta layers is **krogoth**. Do not expect any update to the
+layer other than critical bug-fixes. **Meta-fsl-arm** and **meta-fsl-ppc** must
+be replaced by **meta-freescale**.
+
+The **meta-freescale** meta layer goal is to integrate the ARM and PPC SoC
+based source code from Freescale, it includes **i.MX**, **Vybrid**, **QorIQ**
+and **Layerscape** BSPs.
+
+The **meta-fsl-arm-extra** now is **meta-freescale-3rdparty**, any local copy
+should work as there is a mirror set.
+
+The **meta-fsl-demos** now is **meta-freescale-distros**, any local copy
+should work as there is a mirror set.
+
 License
 ===
 
-- 
2.7.4

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

[meta-freescale] [Documentation][PATCH v2 2/3] RN: Fix typo

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
changes since v1:
- split the patch

 release-notes/source/bsp-scope.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/release-notes/source/bsp-scope.rst 
b/release-notes/source/bsp-scope.rst
index 9e73065..44e1a8e 100644
--- a/release-notes/source/bsp-scope.rst
+++ b/release-notes/source/bsp-scope.rst
@@ -10,7 +10,7 @@ The scope of the |project_name| includes the meta layers:
provides support for 3rd party and partner boards;
  * `meta-freescale-distro 
<https://github.com/Freescale/meta-freescale-distro/tree/morty>`_:
provides distros support, images recipes, demo recipes, and packagegroups
-   used to easy the development with Yocto Project.
+   used to ease the development with Yocto Project.
  * `Documentation <https://github.com/Freescale/Documentation/tree/morty>`_:
provides the source code for |project_name| Release Notes (RN) and User 
Guide
(UG).
-- 
2.7.4

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

[meta-freescale] [Documentation][PATCH v2 1/3] FAQ: Remove this document

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

There is no evidence this document is used. It's a while since last update.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
changes since v1:
- remove FAQ reference from bsp-scope.rst file.

 FAQ/Makefile   | 153 ---
 FAQ/make.bat   | 190 -
 FAQ/source/all.rst | 144 --
 FAQ/source/conf.py | 242 -
 FAQ/source/index.rst   |  21 
 release-notes/source/bsp-scope.rst |   4 +-
 6 files changed, 2 insertions(+), 752 deletions(-)
 delete mode 100644 FAQ/Makefile
 delete mode 100644 FAQ/make.bat
 delete mode 100644 FAQ/source/all.rst
 delete mode 100644 FAQ/source/conf.py
 delete mode 100644 FAQ/source/index.rst

diff --git a/FAQ/Makefile b/FAQ/Makefile
deleted file mode 100644
index f31e089..000
--- a/FAQ/Makefile
+++ /dev/null
@@ -1,153 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS=
-SPHINXBUILD   = sphinx-build
-PAPER =
-BUILDDIR  = build
-
-# Internal variables.
-PAPEROPT_a4 = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) 
source
-# the i18n builder cannot share the environment and doctrees with the others
-I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp 
epub latex latexpdf text man changes linkcheck doctest gettext
-
-help:
-   @echo "Please use \`make ' where  is one of"
-   @echo "  html   to make standalone HTML files"
-   @echo "  dirhtmlto make HTML files named index.html in directories"
-   @echo "  singlehtml to make a single large HTML file"
-   @echo "  pickle to make pickle files"
-   @echo "  json   to make JSON files"
-   @echo "  htmlhelp   to make HTML files and a HTML help project"
-   @echo "  qthelp to make HTML files and a qthelp project"
-   @echo "  devhelpto make HTML files and a Devhelp project"
-   @echo "  epub   to make an epub"
-   @echo "  latex  to make LaTeX files, you can set PAPER=a4 or 
PAPER=letter"
-   @echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-   @echo "  text   to make text files"
-   @echo "  manto make manual pages"
-   @echo "  texinfoto make Texinfo files"
-   @echo "  info   to make Texinfo files and run them through makeinfo"
-   @echo "  gettextto make PO message catalogs"
-   @echo "  changesto make an overview of all changed/added/deprecated 
items"
-   @echo "  linkcheck  to check all external links for integrity"
-   @echo "  doctestto run all doctests embedded in the documentation 
(if enabled)"
-
-clean:
-   -rm -rf $(BUILDDIR)/*
-
-html:
-   $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-   @echo
-   @echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-dirhtml:
-   $(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-   @echo
-   @echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-singlehtml:
-   $(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-   @echo
-   @echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-   $(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-   @echo
-   @echo "Build finished; now you can process the pickle files."
-
-json:
-   $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-   @echo
-   @echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-   $(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-   @echo
-   @echo "Build finished; now you can run HTML Help Workshop with the" \
- ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-   $(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-   @echo
-   @echo "Build finished; now you can run "qcollectiongenerator" with the" 
\
- ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-   @echo "# qcollectiongenerator 
$(BUILDDIR)/qthelp/FreescaleCommunityBSPFAQ.qhcp"
-   @echo "To view the help file:"
-   @echo "# assistant -collectionFile 
$(BUILDDIR)/qthelp/FreescaleCommunityBSPFAQ.qhc"
-
-devhelp:
-   $(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUIL

[meta-freescale] [Documentation][PATCH 1/2] FAQ: Remove this document

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

There is no evidence this document is used. It's a while since last update.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 FAQ/Makefile | 153 
 FAQ/make.bat | 190 
 FAQ/source/all.rst   | 144 --
 FAQ/source/conf.py   | 242 ---
 FAQ/source/index.rst |  21 -
 5 files changed, 750 deletions(-)
 delete mode 100644 FAQ/Makefile
 delete mode 100644 FAQ/make.bat
 delete mode 100644 FAQ/source/all.rst
 delete mode 100644 FAQ/source/conf.py
 delete mode 100644 FAQ/source/index.rst

diff --git a/FAQ/Makefile b/FAQ/Makefile
deleted file mode 100644
index f31e089..000
--- a/FAQ/Makefile
+++ /dev/null
@@ -1,153 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS=
-SPHINXBUILD   = sphinx-build
-PAPER =
-BUILDDIR  = build
-
-# Internal variables.
-PAPEROPT_a4 = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) 
source
-# the i18n builder cannot share the environment and doctrees with the others
-I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp 
epub latex latexpdf text man changes linkcheck doctest gettext
-
-help:
-   @echo "Please use \`make ' where  is one of"
-   @echo "  html   to make standalone HTML files"
-   @echo "  dirhtmlto make HTML files named index.html in directories"
-   @echo "  singlehtml to make a single large HTML file"
-   @echo "  pickle to make pickle files"
-   @echo "  json   to make JSON files"
-   @echo "  htmlhelp   to make HTML files and a HTML help project"
-   @echo "  qthelp to make HTML files and a qthelp project"
-   @echo "  devhelpto make HTML files and a Devhelp project"
-   @echo "  epub   to make an epub"
-   @echo "  latex  to make LaTeX files, you can set PAPER=a4 or 
PAPER=letter"
-   @echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-   @echo "  text   to make text files"
-   @echo "  manto make manual pages"
-   @echo "  texinfoto make Texinfo files"
-   @echo "  info   to make Texinfo files and run them through makeinfo"
-   @echo "  gettextto make PO message catalogs"
-   @echo "  changesto make an overview of all changed/added/deprecated 
items"
-   @echo "  linkcheck  to check all external links for integrity"
-   @echo "  doctestto run all doctests embedded in the documentation 
(if enabled)"
-
-clean:
-   -rm -rf $(BUILDDIR)/*
-
-html:
-   $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-   @echo
-   @echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-dirhtml:
-   $(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-   @echo
-   @echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-singlehtml:
-   $(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-   @echo
-   @echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-   $(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-   @echo
-   @echo "Build finished; now you can process the pickle files."
-
-json:
-   $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-   @echo
-   @echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-   $(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-   @echo
-   @echo "Build finished; now you can run HTML Help Workshop with the" \
- ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-   $(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-   @echo
-   @echo "Build finished; now you can run "qcollectiongenerator" with the" 
\
- ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-   @echo "# qcollectiongenerator 
$(BUILDDIR)/qthelp/FreescaleCommunityBSPFAQ.qhcp"
-   @echo "To view the help file:"
-   @echo "# assistant -collectionFile 
$(BUILDDIR)/qthelp/FreescaleCommunityBSPFAQ.qhc"
-
-devhelp:
-   $(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
-   @echo
-   @echo "Build finished."
-   @echo "To view the help file:"
-   @echo "# mkdir -p $$HOME/.lo

[meta-freescale] [Documentation][PATCH 2/2] bsp-scope: Include meta-freescale section

[Daiane Angolini]

From: Daiane Angolini <daiane.angol...@nxp.com>

Since morty meta-fsl-arm and meta-fsl-ppc must not be used.

Use meta-freescale instead.

Signed-off-by: Daiane Angolini <daiane.angol...@nxp.com>
---
 release-notes/source/bsp-scope.rst | 34 +-
 1 file changed, 33 insertions(+), 1 deletion(-)

diff --git a/release-notes/source/bsp-scope.rst 
b/release-notes/source/bsp-scope.rst
index 97ca49d..931e07b 100644
--- a/release-notes/source/bsp-scope.rst
+++ b/release-notes/source/bsp-scope.rst
@@ -10,11 +10,43 @@ The scope of the |project_name| includes the meta layers:
provides support for 3rd party and partner boards;
  * `meta-freescale-distro 
<https://github.com/Freescale/meta-freescale-distro/tree/morty>`_:
provides distros support, images recipes, demo recipes, and packagegroups
-   used to easy the development with Yocto Project.
+   used to ease the development with Yocto Project.
  * `Documentation <https://github.com/Freescale/Documentation/tree/morty>`_:
provides the source code for |project_name| Release Notes (RN), User Guide
(UG) and Frequently Asked Questions (FAQ)
 
+Meta-freescale
+==
+
+Since the Yocto Project release 2.2 (Morty) the |project_name| changed the meta
+layers names. You can see the announcement
+`here 
<https://lists.yoctoproject.org/pipermail/meta-freescale/2016-October/019429.html>`_.
+
+The following table show the renaming upgrade path:
+
+== ==
+KrogothMorty
+== ==
+meta-fsl-arm   meta-freescale
+meta-fsl-ppc   meta-freescale
+meta-fsl-arm-extra meta-freescale-3rdparty
+meta-fsl-demos meta-freescale-distros
+== ==
+
+The **meta-fsl-arm** and **meta-fsl-ppc** meta layers are deprecated. The last
+release for these meta layers is **krogoth**. Do not expect any update to the
+layer other than critical bug-fixes. **Meta-fsl-arm** and **meta-fsl-ppc** must
+be replaced by **meta-freescale**.
+
+The **meta-freescale** meta layer goal is to integrate the ARM SoC based source
+code from Freescale, it includes **i.MX**, **Vybrid** and **Layerscape** BSPs.
+
+The **meta-fsl-arm-extra** now is **meta-freescale-3rdparty**, any local copy
+should work as there is a mirror set.
+
+The **meta-fsl-demos** now is **meta-freescale-distros**, any local copy
+should work as there is a mirror set.
+
 License
 ===
 
-- 
2.7.4

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

Re: [meta-freescale] Freescale Yocto Question - Building imx6dl-riotboard

[Daiane Angolini]

On Tue, Nov 15, 2016 at 2:36 PM,  <eric.zalu...@emerson.com> wrote:
> Daiane, my test steps & results are described below.
> I followed the README steps on the imx-4.1-krogoth branch of the 
> fsl-arm-yocto-bsp repo for building. I used the default.xml.
>
> After 'repo sync', I ran the following, 'MACHINE=imx6dl-riotboard 
> DISTRO=fsl-imx-fb source ./fsl-setup-release.sh -b bld-fb'
>
> Since I am using Framebuffer backend type, I did a 'bitbake 
> fsl-image-machine-test'. This image is a console-only image that includes 
> gstreamer packages, Freescale's multimedia packages (VPU and GPU) when 
> available, and test and benchmark applications.
>
> During bitbake's parsing, I received an error saying nothing RPROVIDES 
> 'imx-codec-test-bin'. I modified the imx-codec_4.1.4.bb package recipe to add 
> 'imx6dl-riotboard' as a 'COMPATIBLE_MACHINE'. The machine configuration file 
> for riotboard could also include ' SOC_FAMILY = "mx6:mx6s" '  to resolve 
> error, since 'mx6' is already listed as a COMPATIBLE_MACHINE in imx-codec.
>
> After the codec recipe change, the fsl-image-machine-test image completed, 
> successfully. 
> 'fsl-image-machine-test-imx6dl-riotboard-20161114220105.rootfs.sdcard'
>
> I following the RIoTboard wiki to flash BSP image on SD card. [1] But once 
> the device is powered on, the debug terminal is blank and I do not see any 
> kernel output logs, boot messages, or the freescale splash screen. 
> Additionally, I built and tested the fsl-image-gui with x11 distro. Same 
> results on RIoTboard.
> The RIoTboard BSP image on the imx-3.10.17-1.0.0_ga branch would boot 
> correctly following these steps.
>
> When comparing the RIoTboard's BSP & MACHINE configurations files from the 
> two branches of the fsl-arm-yocto-bsp repositories, I have observed that many 
> of the RIoTboard BSP's conf and device tree files were renamed from 'solo' to 
> 'dl'. From my understanding there is only a solo RIoTboard. What made the 
> naming convention change so much from solo to dual lite?
>
> Can you escalate this to anyone else in the community who is maintaining the 
> FSL Community BSP release of the imx6dl-riotboard? @MAINTAINER: Nikolay 
> Dimitrov <picmas...@mail.bg>
>

From what you describe, you are not using FSL Community BSP, you are
using fsl-arm-yocto-bsp, which is not exactly supposed to work for non
freescale reference boards.

Can you, please, test it using FSL Community BSP instead?


I don't remember the reason for the solo -> dl renaming any clue form
git history?

I'm CCing Nikolay.

Nikolay, can you help here?


Daiane
> [1]
> http://riotboard.org/download/Wiki-Beginner-Flash%20a%20precompiled%20BSP%20image%20to%20an%20SD%20card.pdf
>
> Thanks,
> -Eric Zaluzec
> (eric.zalu...@emerson.com)
>
>
> -Original Message-
> From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of Daiane 
> Angolini
> Sent: Monday, November 14, 2016 12:53 PM
> To: Zaluzec, Eric [NETPWR/AL]
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Freescale Yocto Question - Building 
> imx6dl-riotboard
>
> On Mon, Nov 14, 2016 at 4:00 PM,  <eric.zalu...@emerson.com> wrote:
>> Thanks Daiane, maybe I am getting ahead of myself with the questions.
>> Under the FSL Community BSP's "Support Board List", I see the 
>> "imx6dl-riotboard / RIotboard / i.MX6S / meta-fsl-arm-extra".
>> http://freescale.github.io/doc/release-notes/2.1/index.html#supported-
>> boards Is this imx6dl-riotboard BSP and machine configuration file the
>> one that can run on the RIoTboard evaluation platform found on 
>> http://riotboard.org/ ?
>
> Yes. I don't have the board so I haven't tested it in a while. Please test 
> and let us know.
>
> Daiane
>
>> If it is not, do you have reference or a web URL for the one RIoTboard that 
>> you support?
>>
>> Regards,
>> -Eric Zaluzec
>> (eric.zalu...@emerson.com)
>>
>>
>> -Original Message-
>> From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of
>> Daiane Angolini
>> Sent: Monday, November 14, 2016 11:20 AM
>> To: Zaluzec, Eric [NETPWR/AL]
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] Freescale Yocto Question - Building
>> imx6dl-riotboard
>>
>> On Fri, Nov 11, 2016 at 3:12 PM,  <eric.zalu...@emerson.com> wrote:
>>> Greeting,
>>>
>>> I have a quick question concerning the imx6dl-riotboard machine
>>> configuration file, maintained by the Yocto Freescale community.
>>>
>>> We have an upcoming project for which we are considering a i.MX6 Dual
>>> Lite pro

[meta-freescale] Updates to Documentation (master and morty) in 2016-11-14

[Daiane Angolini]

commit ccbfddecbba3147ddc505d22e2b89733cdee56fd
Author: Fabio Berton 
Date:   Wed Nov 9 15:30:25 2016 -0200

UG: Update version to 2.2 (Morty)

- Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update devtasks, nsteps and metadata to use Morty branch and distro
fslc-framebuffer
  - Remove qt-in-use-image and qte-in-use-image from image list
  - Add FSLC distros description
  - Use DISTRO fslc-wayland in weston example

Signed-off-by: Fabio Berton 

commit 4da9ea8a7ad14325f6e3232f597c30b737732ee0
Author: Fabio Berton 
Date:   Wed Nov 9 15:30:24 2016 -0200

RN: Update version to 2.2 (Morty)

- Update FSL layers names
  - Update Yocto Project Bugzilla url address
  - Add FSLC distros description

Signed-off-by: Fabio Berton 

commit b12aebec37766ec073dd04fc1c8c72b6b13eb59d
Author: Fabio Berton 
Date:   Wed Nov 9 15:30:23 2016 -0200

FAQ: Update version to 2.2 (Morty)

- Update documentation url address to use current realease
  - Update Yocto Project Bugzilla url address
  - Update copyright year

Signed-off-by: Fabio Berton 

commit 32f16b1625dfd60c1fbec1fb25a0b3ed4e048ad7
Author: Fabio Berton 
Date:   Wed Nov 9 15:30:22 2016 -0200

RN: Updates from bitbake-metadata2doc.sh

Signed-off-by: Fabio Berton 

commit 88e9f62fa34b9da317c859a26e40f09f335c19cd
Author: Fabio Berton 
Date:   Wed Nov 9 15:30:21 2016 -0200

scripts: Update to version 2.2 (Morty)

- Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update Yocto Project Bugzilla url address

Signed-off-by: Fabio Berton 
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] Freescale Yocto Question - Building imx6dl-riotboard

[Daiane Angolini]

On Mon, Nov 14, 2016 at 4:00 PM,  <eric.zalu...@emerson.com> wrote:
> Thanks Daiane, maybe I am getting ahead of myself with the questions.
> Under the FSL Community BSP's "Support Board List", I see the 
> "imx6dl-riotboard / RIotboard / i.MX6S / meta-fsl-arm-extra".
> http://freescale.github.io/doc/release-notes/2.1/index.html#supported-boards
> Is this imx6dl-riotboard BSP and machine configuration file the one that can 
> run on the RIoTboard evaluation platform found on http://riotboard.org/ ?

Yes. I don't have the board so I haven't tested it in a while. Please
test and let us know.

Daiane

> If it is not, do you have reference or a web URL for the one RIoTboard that 
> you support?
>
> Regards,
> -Eric Zaluzec
> (eric.zalu...@emerson.com)
>
>
> -Original Message-----
> From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of Daiane 
> Angolini
> Sent: Monday, November 14, 2016 11:20 AM
> To: Zaluzec, Eric [NETPWR/AL]
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Freescale Yocto Question - Building 
> imx6dl-riotboard
>
> On Fri, Nov 11, 2016 at 3:12 PM,  <eric.zalu...@emerson.com> wrote:
>> Greeting,
>>
>> I have a quick question concerning the imx6dl-riotboard machine
>> configuration file, maintained by the Yocto Freescale community.
>>
>> We have an upcoming project for which we are considering a i.MX6 Dual
>> Lite processor. But since there are no Dual Lite evaluation boards, at
>> this time, we were provided an i.mx6 solo RIoTboard to use for initial
>> testing, by Avnet and NXP distributors.
>>
>>
>>
>> First off, thank you for providing up-to-date Yocto build repositories
>> and documentation! This makes kicking-off a new Yocto BSP Project much 
>> simpler!
>> Cheers.
>>
>> I read the Freescale Yocto User Guide here:
>> http://www.bcmcom.com/CustomerDL/AR6MX/Yocto/Freescale_Yocto_Project_U
>> ser's_Guide.pdf I then read the  RIoTboard Yocto build guide here:
>> https://www.element14.com/community/community/designcenter/single-boar
>> d-computers/riotboard/blog/2014/09/22/riotboard-yocto-part1-getting-st
>> arted
>>
>> Using both resources, I successfully built a Yocto image and was able
>> to install onto my RIoTboard.
>>
>>
>>
>>
>>
>> Now, using Yocto, I would like to build a RIoTboard image with a fido
>> or krogoth branch of Yocto, to make use of the updated packages &
>> bitbake recipes, like boost and java, These versions are dependencies
>> to my metadata layer’s packages.
>>
>> I went to the fsl-arm-yocto-bsp git repository site and found the
>> imx-4.1-krogoth branch:
>> http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/?h=imx
>> -4.1-krogoth
>>
>>
>>
>> I followed the User Guide steps, but this time cloned the
>> imx-4.1-krogoth branch. I noticed the riotboard.conf machine
>> configuration file no longer existed, but a imx6dl-riotboard machine
>> was present in the meta-fsl-arm-extra & meta-freescale-3rdparty
>> metadata layers. I successfully built an image with this machine conf
>> file, but then realized that it was ‘dl’ (Dual Lite?) and would not
>> boot with the solo RIoTboard that I was using.
>>
>>
>>
>> Question :
>>
>> Are there any branches on for the fsl-arm-yocto-bsp repository that
>> are fido/jethro/krogoth compatible, that include the riotboard solo
>> machine configuration file?
>> http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git
>>
>> If not, is it possible for users, like me, to base a riotboard solo
>> machine conf file off the imx6dl-riotboard machine and create a
>> successful BSP image? Or are these unavoidable conflicts?
>>
>>
>>
>> The critical piece here is not necessarily having a v4.1 kernel but
>> just the use of the updated package recipes & the dependency to custom
>> packages trying to be installed & tested on the riotboard!
>>
>>
>>
>> Any help, suggestions, or feedback would greatly be appreciated! Right
>> now I am just tinkering with learning about the riotboard machine conf
>> file to see if I can port it to the imx-4.1-krogoth branch.
>>
>
> I'm not sure you're going to be able to use imx-4.1-krogoth branch with the 
> riot board. Please, take a look at [1]
>
> We have support for one riot board, double check if this is what you are 
> looking for.
>
> [1] 
> http://freescale.github.io/doc/release-notes/2.1/index.html#the-differences-between-project-name-and-freescale-release-name
>
>
> Daiane
>>
>>
>> Thanks!
>> -Eric Zaluzec
>> (eric.zalu...@emerson.com)
>>
>>
>>
>>
>> --
>> ___
>> 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] Freescale Yocto Question - Building imx6dl-riotboard

[Daiane Angolini]

On Fri, Nov 11, 2016 at 3:12 PM,   wrote:
> Greeting,
>
> I have a quick question concerning the imx6dl-riotboard machine
> configuration file, maintained by the Yocto Freescale community.
>
> We have an upcoming project for which we are considering a i.MX6 Dual Lite
> processor. But since there are no Dual Lite evaluation boards, at this time,
> we were provided an i.mx6 solo RIoTboard to use for initial testing, by
> Avnet and NXP distributors.
>
>
>
> First off, thank you for providing up-to-date Yocto build repositories and
> documentation! This makes kicking-off a new Yocto BSP Project much simpler!
> Cheers.
>
> I read the Freescale Yocto User Guide here:
> http://www.bcmcom.com/CustomerDL/AR6MX/Yocto/Freescale_Yocto_Project_User's_Guide.pdf
> I then read the  RIoTboard Yocto build guide here:
> https://www.element14.com/community/community/designcenter/single-board-computers/riotboard/blog/2014/09/22/riotboard-yocto-part1-getting-started
>
> Using both resources, I successfully built a Yocto image and was able to
> install onto my RIoTboard.
>
>
>
>
>
> Now, using Yocto, I would like to build a RIoTboard image with a fido or
> krogoth branch of Yocto, to make use of the updated packages & bitbake
> recipes, like boost and java, These versions are dependencies to my metadata
> layer’s packages.
>
> I went to the fsl-arm-yocto-bsp git repository site and found the
> imx-4.1-krogoth branch:
> http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/?h=imx-4.1-krogoth
>
>
>
> I followed the User Guide steps, but this time cloned the imx-4.1-krogoth
> branch. I noticed the riotboard.conf machine configuration file no longer
> existed, but a imx6dl-riotboard machine was present in the
> meta-fsl-arm-extra & meta-freescale-3rdparty metadata layers. I successfully
> built an image with this machine conf file, but then realized that it was
> ‘dl’ (Dual Lite?) and would not boot with the solo RIoTboard that I was
> using.
>
>
>
> Question :
>
> Are there any branches on for the fsl-arm-yocto-bsp repository that are
> fido/jethro/krogoth compatible, that include the riotboard solo machine
> configuration file?
> http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git
>
> If not, is it possible for users, like me, to base a riotboard solo machine
> conf file off the imx6dl-riotboard machine and create a successful BSP
> image? Or are these unavoidable conflicts?
>
>
>
> The critical piece here is not necessarily having a v4.1 kernel but just the
> use of the updated package recipes & the dependency to custom packages
> trying to be installed & tested on the riotboard!
>
>
>
> Any help, suggestions, or feedback would greatly be appreciated! Right now I
> am just tinkering with learning about the riotboard machine conf file to see
> if I can port it to the imx-4.1-krogoth branch.
>

I'm not sure you're going to be able to use imx-4.1-krogoth branch
with the riot board. Please, take a look at [1]

We have support for one riot board, double check if this is what you
are looking for.

[1] 
http://freescale.github.io/doc/release-notes/2.1/index.html#the-differences-between-project-name-and-freescale-release-name


Daiane
>
>
> Thanks!
> -Eric Zaluzec
> (eric.zalu...@emerson.com)
>
>
>
>
> --
> ___
> 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