[meta-freescale] i.MX6SL EVK
eric.nelson at boundarydevices.com
Sat Mar 16 09:00:51 PDT 2013
On 03/16/2013 07:08 AM, Otavio Salvador wrote:
> On Fri, Mar 15, 2013 at 9:30 PM, Eric Nelson
> <eric.nelson at boundarydevices.com> wrote:
>> On 03/14/2013 09:44 AM, Otavio Salvador wrote:
>>> On Thu, Mar 14, 2013 at 1:10 PM, Michael Urbaniak <MikeU at ebtron.com>
>>>> I am very interested in moving from LTIB to Yocto for an i.MX6SL project
>>>> currently have.
>>> I am glad to learn it ;-)
>>>> Is there support at this time for the i.MX6SL-EVK? If not I suppose I
>>>> to learn about modifying BSP’s.
>>> Not at this moment as said by Daiane; it shouldn't be hard but it does
>>> need to be done.
>> FWIW, the Yocto build for Nitrogen6X boots right up with a Solo
>> In order to get VPU acceleration, you'll need to copy in the
>> firmware file "vpu_fw_imx6d.bin" though.
>> The GPU seems to come right up.
> We need to adapt to use the official kernel for the board.
Of course. The i.MX6SL-EVK will need both custom U-Boot and kernel.
My message was really for Nitrogen6X customers that might
be interested in evaluating the performance of Solo or Dual-Lite
> I think it did work for your board because Boundary's U-Boot already
> handles it however we currently use U-Boot 2013.01 by default here and
> this still doesn't cope with the other variants of i.MX6 SoC.
Yep. This is a benefit of booting to SPI-NOR.
> What is the Boundary's plans for the kernel? A single kernel tree or
> two (as done by FSL)?
We did this by creating "pads-mx6_sabrelite.h" and including it
twice: once for Dual/Quad and again for Solo/Dual-Lite:
This allows us to boot all of our SD cards on all of our boards.
We even have a boot script for Adeneo's Windows CE7 to make it
easy to swap.
More information about the meta-freescale