Building for SabreSD

Building for SabreSD

[Gary Thomas]

I'm trying to build the latest master for SabreSD.
meta              = "master:3c741a8d33acbf4b3d5eecc04533bc76e2f37253"
meta-fsl-arm      = "master:fbe06aa1dd82265f74a62ae410d0df83f2f1947c"

In my local.conf I have:
   MACHINE = "imx6qsabresd"
   PREFERRED_PROVIDER_virtual/kernel_imx6qsabresd = "linux-fslc"
which ends up building linux-fslc/3.17+gitAUTOINC+6725f55a77-r0

Sadly, this fails
   | NOTE: make -j 4 imx6q-sabresd.dtb
   |   DTC     arch/arm/boot/dts/imx6q-sabresd.dtb
   | NOTE: make -j 4 imx6q-sabresd-ldo.dtb
   | make[1]: *** No rule to make target `arch/arm/boot/dts/imx6q-sabresd-ldo.dtb'.  Stop.
   | make: *** [imx6q-sabresd-ldo.dtb] Error 2

Any hints on how to build the kernel for my SabreSD board?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Building for SabreSD

[Fabio Estevam]

Hi Gary,

On Mon, Nov 24, 2014 at 2:00 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> I'm trying to build the latest master for SabreSD.
> meta              = "master:3c741a8d33acbf4b3d5eecc04533bc76e2f37253"
> meta-fsl-arm      = "master:fbe06aa1dd82265f74a62ae410d0df83f2f1947c"
>
> In my local.conf I have:
>   MACHINE = "imx6qsabresd"
>   PREFERRED_PROVIDER_virtual/kernel_imx6qsabresd = "linux-fslc"
> which ends up building linux-fslc/3.17+gitAUTOINC+6725f55a77-r0
>
> Sadly, this fails
>   | NOTE: make -j 4 imx6q-sabresd.dtb
>   |   DTC     arch/arm/boot/dts/imx6q-sabresd.dtb
>   | NOTE: make -j 4 imx6q-sabresd-ldo.dtb
>   | make[1]: *** No rule to make target
> `arch/arm/boot/dts/imx6q-sabresd-ldo.dtb'.  Stop.
>   | make: *** [imx6q-sabresd-ldo.dtb] Error 2
>
> Any hints on how to build the kernel for my SabreSD board?

You should remove imx6q-sabresd-ldo.dtb from the list of dtbs:

--- a/conf/machine/imx6qsabresd.conf
+++ b/conf/machine/imx6qsabresd.conf
@@ -8,7 +8,7 @@ require conf/machine/include/imx6sabresd-common.inc

 SOC_FAMILY = "mx6:mx6q"

-KERNEL_DEVICETREE = "imx6q-sabresd.dtb imx6q-sabresd-ldo.dtb
imx6q-sabresd-hdcp.dtb"
+KERNEL_DEVICETREE = "imx6q-sabresd.dtb"

 UBOOT_CONFIG ??= "sd"
 UBOOT_CONFIG[sd] = "mx6qsabresd_config,sdcard"

imx6q-sabresd-ldo.dtb and  imx6q-sabresd-hdcp.dtb only exist on FSL
kernel, not in mainline.

Re: Building for SabreSD

[Gary Thomas]

On 2014-11-24 09:11, Fabio Estevam wrote:
> Hi Gary,
>
> On Mon, Nov 24, 2014 at 2:00 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I'm trying to build the latest master for SabreSD.
>> meta              = "master:3c741a8d33acbf4b3d5eecc04533bc76e2f37253"
>> meta-fsl-arm      = "master:fbe06aa1dd82265f74a62ae410d0df83f2f1947c"
>>
>> In my local.conf I have:
>>    MACHINE = "imx6qsabresd"
>>    PREFERRED_PROVIDER_virtual/kernel_imx6qsabresd = "linux-fslc"
>> which ends up building linux-fslc/3.17+gitAUTOINC+6725f55a77-r0
>>
>> Sadly, this fails
>>    | NOTE: make -j 4 imx6q-sabresd.dtb
>>    |   DTC     arch/arm/boot/dts/imx6q-sabresd.dtb
>>    | NOTE: make -j 4 imx6q-sabresd-ldo.dtb
>>    | make[1]: *** No rule to make target
>> `arch/arm/boot/dts/imx6q-sabresd-ldo.dtb'.  Stop.
>>    | make: *** [imx6q-sabresd-ldo.dtb] Error 2
>>
>> Any hints on how to build the kernel for my SabreSD board?
>
> You should remove imx6q-sabresd-ldo.dtb from the list of dtbs:
>
> --- a/conf/machine/imx6qsabresd.conf
> +++ b/conf/machine/imx6qsabresd.conf
> @@ -8,7 +8,7 @@ require conf/machine/include/imx6sabresd-common.inc
>
>   SOC_FAMILY = "mx6:mx6q"
>
> -KERNEL_DEVICETREE = "imx6q-sabresd.dtb imx6q-sabresd-ldo.dtb
> imx6q-sabresd-hdcp.dtb"
> +KERNEL_DEVICETREE = "imx6q-sabresd.dtb"
>
>   UBOOT_CONFIG ??= "sd"
>   UBOOT_CONFIG[sd] = "mx6qsabresd_config,sdcard"
>
> imx6q-sabresd-ldo.dtb and  imx6q-sabresd-hdcp.dtb only exist on FSL
> kernel, not in mainline.
>

Thanks this fixes the build.  I'm not sure about your comment
though since I am building linux-fslc

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Building for SabreSD

[Fabio Estevam]

On Mon, Nov 24, 2014 at 2:18 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> Thanks this fixes the build.  I'm not sure about your comment
> though since I am building linux-fslc

Glad the build worked.

What I meant is that 'imx6q-sabresd-ldo.dtb' does not exist in the
linux-fsl (which is based on the stable 3.17.x kernel tree).

imx6q-sabresd-ldo.dtb is part of the 3.10.x FSL kernels.

Re: Building for SabreSD

[Gary Thomas]

On 2014-11-24 09:55, Fabio Estevam wrote:
> On Mon, Nov 24, 2014 at 2:37 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>
>> Should I be using linux-imx_3.10.31 instead?
>
> I don't know. What is your goal exactly? Why did you want to try
> linux-fsl in the first place?
>

Because it was complaining that I had two choices for the kernel,
so I picked one.

At the moment my need is minimal - I'm just using that board
to check the functioning of a PCIe network card.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Building for SabreSD

[Fabio Estevam]

On Mon, Nov 24, 2014 at 3:22 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> Because it was complaining that I had two choices for the kernel,
> so I picked one.
>
> At the moment my need is minimal - I'm just using that board
> to check the functioning of a PCIe network card.

Maybe a core-image-minimal would suffice then?

Re: Building for SabreSD

[Robin Findley]

Fabio Estevam wrote:
> On Mon, Nov 24, 2014 at 3:22 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> 
> > Because it was complaining that I had two choices for the kernel,
> > so I picked one.
> >
> > At the moment my need is minimal - I'm just using that board
> > to check the functioning of a PCIe network card.
> 
> Maybe a core-image-minimal would suffice then?

For what it's worth, I've successfully tested a few PCIe network cards on
SabreSD with Wandboard kernel v3.10.17, and Wandboard device-tree with
irrelevant and incompatible stuff disabled.  SabreSD worked great.  

Long story as to why I used Wandboard kernel, but boils down to the fact that
I started out trying to get PCIe working on a Wandboard-based system...
couldn't get it working, so moved on to TechNexion Fairy board... which
somewhat worked, but only with one network card, and only most of the time...
then went to SabreSD, which worked beautifully with all of the PCIe devices I
tested, including a RealTek GbE, an Intel GbE, and a 6-port PCIe switch.