On Thu, May 30, 2019 at 1:25 AM Otavio Salvador
wrote:
>
> On Mon, Apr 8, 2019 at 7:52 AM Teemu K wrote:
> > I'm trying to build newer image for imx53 based hw (it's actually
> > QSB-development board that has support in meta-freescale) with thud -
> > version of yocto/m
Hi,
I'm trying to build newer image for imx53 based hw (it's actually
QSB-development board that has support in meta-freescale) with thud -
version of yocto/meta-freescale.
I was able to build the image, but sdcard - fs-type support was
dropped so I replaced it with wic. The result is that unit
was looking old messages and there was patch to remove it late
January and then comment that it's not the right way. So how should
the imx-m4-demos to be dealt with? Atm. latest meta-freescale is
non-buildable at least for imx8qxp.
-Teemu K.
--
___
meta
On Fri, Jan 11, 2019 at 2:26 PM Daiane Angolini 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
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:
nce
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
On Tue, Jan 8, 2019 at 9:04 AM Teemu K 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
>
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
On Mon, Aug 27, 2018 at 11:00 AM Teemu K wrote:
>
> Hi,
>
> This is somewhat simple thing that turned out not to be so simple.
>
> We have custom i.MX6Q based HW running Yocto 2.4 and Linux 4.1-2.0...
> and VDDARM_IN is set to 1.425V. Also VDDSOC_IN is set to 1.425V.
Hi,
This is somewhat simple thing that turned out not to be so simple.
We have custom i.MX6Q based HW running Yocto 2.4 and Linux 4.1-2.0...
and VDDARM_IN is set to 1.425V. Also VDDSOC_IN is set to 1.425V. They
both come from external PMIC as usually do.
Now the VDD_SOC_CAP should be set to
On Tue, May 22, 2018 at 11:57 PM, Otavio Salvador
wrote:
> On Thu, May 3, 2018 at 12:21 AM, Keskinarkaus, Teemu
> wrote:
>> I’m using latest Yocto 2.4 (rocko) and latest meta-freescale with i.MX6Q
>> custom target. I’m trying
>&5
arm-poky-linux-gnueabi-gcc: error: unrecognized command line option
'-pipe-DLINUX'
configure:3213: $? = 1
configure:3251: result: no
configure: failed program was:
--
I'm not automake/configure expert so I'm not sure where does that
option come from.
-Teemu K.
--
_
12 matches
Mail list logo