Status of i.MX8 support

Status of i.MX8 support

[Teemu K]

Hi,

What is the state of the meta-freescale i.MX8 support? I'm trying to
compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).

I'm using thud - branch of everything, but while compiling and using
kernel linux-imx_4.9.123 (that's the only one with i.MX8 support as
far as I can tell based on recipes) the kernel fails to build
properly. I think it's more of the kernel modules that create some
bitbake related errors.

--
ERROR: linux-imx-4.9.123-r0 do_package_write_deb: Fatal errors
occurred in subprocesses:
 dpkg-deb -b /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-usb-audio-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc
/home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/deploy-debs/imx8qxpmek'
returned non-zero exit status 2: Traceback (most recent call last):
  File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/lib/oe/utils.py",
line 272, in run
    ret = self._target(*self._args, **self._kwargs)
  File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/classes/package_deb.bbclass",
line 274, in deb_write_pkg
    shell=True)
  File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.5/subprocess.py", line 708, in run
    output=stdout, stderr=stderr)
--

I cut that some and there are more of similar errors coming. If I
remove those modules from kernel I'll get error on some other module.

Just wondering if that should work? I know it's quite new and may have
some problems so if it's known not to work then I guess I'll do
something else.

-TeemuK

Re: Status of i.MX8 support

[Teemu K]

On Tue, Jan 8, 2019 at 9:04 AM Teemu K <maillinglists18@gmail.com> wrote:
>
> Hi,
>
> What is the state of the meta-freescale i.MX8 support? I'm trying to
> compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).
>
> I'm using thud - branch of everything, but while compiling and using
> kernel linux-imx_4.9.123 (that's the only one with i.MX8 support as
> far as I can tell based on recipes) the kernel fails to build
> properly. I think it's more of the kernel modules that create some
> bitbake related errors.
>
> --
> ERROR: linux-imx-4.9.123-r0 do_package_write_deb: Fatal errors
> occurred in subprocesses:
>  dpkg-deb -b /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-usb-audio-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc
> /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/deploy-debs/imx8qxpmek'
> returned non-zero exit status 2: Traceback (most recent call last):
>   File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/lib/oe/utils.py",
> line 272, in run
>     ret = self._target(*self._args, **self._kwargs)
>   File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/classes/package_deb.bbclass",
> line 274, in deb_write_pkg
>     shell=True)
>   File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
>     **kwargs).stdout
>   File "/usr/lib/python3.5/subprocess.py", line 708, in run
>     output=stdout, stderr=stderr)
> --
>
> I cut that some and there are more of similar errors coming. If I
> remove those modules from kernel I'll get error on some other module.
>
> Just wondering if that should work? I know it's quite new and may have
> some problems so if it's known not to work then I guess I'll do
> something else.
>
> -TeemuK

I did some digging and it seems that the dpkg-deb - command, fails to
this error when run manually:

dpkg-deb: error: failed to open package info file
'/home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-hwdep-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc/DEBIAN/control'
for reading: No such file or directory

How has anyone else managed to build Yocto image for i.MX8? Or has
anyone done that?

-Teemu

Re: Status of i.MX8 support

[Vincent Prince]

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

Hi,

Did you try to compile with rpm support instead?
Also, it seems that default kernel for imx8 is linux-fslc-imx and not
linux-imx:

IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"

Regards,
Vincent

Le mer. 9 janv. 2019 à 09:30, Teemu K <maillinglists18@gmail.com> a écrit :

> On Tue, Jan 8, 2019 at 9:04 AM Teemu K <maillinglists18@gmail.com> wrote:
> >
> > Hi,
> >
> > What is the state of the meta-freescale i.MX8 support? I'm trying to
> > compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).
> >
> > I'm using thud - branch of everything, but while compiling and using
> > kernel linux-imx_4.9.123 (that's the only one with i.MX8 support as
> > far as I can tell based on recipes) the kernel fails to build
> > properly. I think it's more of the kernel modules that create some
> > bitbake related errors.
> >
> > --
> > ERROR: linux-imx-4.9.123-r0 do_package_write_deb: Fatal errors
> > occurred in subprocesses:
> >  dpkg-deb -b
> /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-usb-audio-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc
> >
> /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/deploy-debs/imx8qxpmek'
> > returned non-zero exit status 2: Traceback (most recent call last):
> >   File
> "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/lib/oe/utils.py",
> > line 272, in run
> >     ret = self._target(*self._args, **self._kwargs)
> >   File
> "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/classes/package_deb.bbclass",
> > line 274, in deb_write_pkg
> >     shell=True)
> >   File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> >     **kwargs).stdout
> >   File "/usr/lib/python3.5/subprocess.py", line 708, in run
> >     output=stdout, stderr=stderr)
> > --
> >
> > I cut that some and there are more of similar errors coming. If I
> > remove those modules from kernel I'll get error on some other module.
> >
> > Just wondering if that should work? I know it's quite new and may have
> > some problems so if it's known not to work then I guess I'll do
> > something else.
> >
> > -TeemuK
>
> I did some digging and it seems that the dpkg-deb - command, fails to
> this error when run manually:
>
> dpkg-deb: error: failed to open package info file
>
> '/home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-hwdep-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc/DEBIAN/control'
> for reading: No such file or directory
>
> How has anyone else managed to build Yocto image for i.MX8? Or has
> anyone done that?
>
> -Teemu
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

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

Re: Status of i.MX8 support

[Max Krummenacher]

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

Hi

> What is the state of the meta-freescale i.MX8 support? I'm trying to
> compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).

Please have a look at this patchset:
https://lists.yoctoproject.org/pipermail/meta-freescale/2019-January/023633.html

Note that I used master but that should not make a difference.

This likely makes your build go further.
I guess you will then also be stuck at the image wic build step, however
you would get kernel/dtb/rootfs (Which I did not have to time to test on a
board)

Regards,
Max

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

Re: Status of i.MX8 support

[Teemu K]

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"

So something is wrong/missing there.

But I was able to compile image for i.MX8 once I started using rpm
instead deb. Next thing is that do I get the board booting from that
image.

-Teemu

On Wed, Jan 9, 2019 at 11:44 AM Vincent Prince
<vincent.prince.fr@gmail.com> wrote:
>
> Hi,
>
> Did you try to compile with rpm support instead?
> Also, it seems that default kernel for imx8 is linux-fslc-imx and not linux-imx:
>
> IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"
>
> Regards,
> Vincent
>
> Le mer. 9 janv. 2019 à 09:30, Teemu K <maillinglists18@gmail.com> a écrit :
>>
>> On Tue, Jan 8, 2019 at 9:04 AM Teemu K <maillinglists18@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > What is the state of the meta-freescale i.MX8 support? I'm trying to
>> > compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).
>> >
>> > I'm using thud - branch of everything, but while compiling and using
>> > kernel linux-imx_4.9.123 (that's the only one with i.MX8 support as
>> > far as I can tell based on recipes) the kernel fails to build
>> > properly. I think it's more of the kernel modules that create some
>> > bitbake related errors.
>> >
>> > --
>> > ERROR: linux-imx-4.9.123-r0 do_package_write_deb: Fatal errors
>> > occurred in subprocesses:
>> >  dpkg-deb -b /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-usb-audio-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc
>> > /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/deploy-debs/imx8qxpmek'
>> > returned non-zero exit status 2: Traceback (most recent call last):
>> >   File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/lib/oe/utils.py",
>> > line 272, in run
>> >     ret = self._target(*self._args, **self._kwargs)
>> >   File "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/classes/package_deb.bbclass",
>> > line 274, in deb_write_pkg
>> >     shell=True)
>> >   File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
>> >     **kwargs).stdout
>> >   File "/usr/lib/python3.5/subprocess.py", line 708, in run
>> >     output=stdout, stderr=stderr)
>> > --
>> >
>> > I cut that some and there are more of similar errors coming. If I
>> > remove those modules from kernel I'll get error on some other module.
>> >
>> > Just wondering if that should work? I know it's quite new and may have
>> > some problems so if it's known not to work then I guess I'll do
>> > something else.
>> >
>> > -TeemuK
>>
>> I did some digging and it seems that the dpkg-deb - command, fails to
>> this error when run manually:
>>
>> dpkg-deb: error: failed to open package info file
>> '/home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-hwdep-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc/DEBIAN/control'
>> for reading: No such file or directory
>>
>> How has anyone else managed to build Yocto image for i.MX8? Or has
>> anyone done that?
>>
>> -Teemu
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: Status of i.MX8 support

[Teemu K]

On Thu, Jan 10, 2019 at 6:25 AM Teemu K <maillinglists18@gmail.com> 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.

-Teemu

Re: Status of i.MX8 support

[Daiane Angolini]

On Fri, Jan 11, 2019 at 6:13 AM Teemu K <maillinglists18@gmail.com> wrote:
>
> On Thu, Jan 10, 2019 at 6:25 AM Teemu K <maillinglists18@gmail.com> 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

Re: Status of i.MX8 support

[Teemu K]

On Fri, Jan 11, 2019 at 2:26 PM Daiane Angolini <daiane.list@gmail.com> wrote:
> 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
Hi,

I got bit further. It seemed that local.conf IMAGE_FSTYPES did
override the SOC_DEFAULT_IMAGE_FSTYPES. I commented it out and now I
got next problem that I get this error when trying to compile image:

ERROR: Nothing PROVIDES 'imx-m4-demos'
ERROR: Required build target 'core-my-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-my-image',
'imx-boot', 'imx-m4-demos']

I searched for imx-m4-demos and I only found it for rocko - branch,
but not for thud.

-Teemu


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