From: "Terry Barnaby" <terry@beam.ltd.uk>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Wandboard WB-IMX6U-BW CAM-OV5645 camera
Date: Fri, 19 Feb 2021 13:45:12 +0000 [thread overview]
Message-ID: <17410ef9-b09c-7a49-79f9-9c81a8b3553d@beam.ltd.uk> (raw)
In-Reply-To: <CAHtQpK4s3A5hSTLMh-fu80zBdg4-0V8q4p8Oqthh2HoGdbtp4w@mail.gmail.com>
On 19/02/2021 13:34, Andrey Zhizhikin wrote:
> Hello Terry,
>
> On Fri, Feb 19, 2021 at 2:28 PM Terry Barnaby <terry@beam.ltd.uk> wrote:
>> Hi Andrey,
>>
>> On 19/02/2021 12:59, Andrey Zhizhikin wrote:
>>> Hello Terry and Fabio,
>>>
>>> On Fri, Feb 19, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
>>>> Hi Terry,
>>>>
>>>> On Fri, Feb 19, 2021 at 4:25 AM Terry Barnaby <terry@beam.ltd.uk> wrote:
>>>>
>>>>> The u-boot master of git://git.denx.de/u-boot.git u-boot-git/ does work
>>>>> fine on the Wandboard revD1, as I tested above, thanks for including
>>>>> this commit. It's the Yocto meta-freescale build I was having problems with.
>>>> Ok, I am adding Otavio on Cc.
>>>>
>>>> I have the impression that the Yocto meta-freescale is using an older U-Boot.
>>>>
>>>>> Maybe I am doing something wrong. I checked the
>>>>> http://freescale.github.io code out using:
>>>>>
>>>>> repo init -u https://github.com/Freescale/fsl-community-bsp-platform
>>>>>
>>>>> (also tried "repo init -u
>>>>> https://github.com/Freescale/fsl-community-bsp-platform -b dunfell")
>>>>>
>>>>> When I "bitbake u-boot" with this the u-boot build source tree does not
>>>>> contain "arch/arm/dts/imx6dl-wandboard-revd1.dts" which is a file that
>>>>> git commit would have added ?
>>>> It is the commit that I pointed out that introduces
>>>> arch/arm/dts/imx6dl-wandboard-revd1.dts.
>>>>
>>>> Such commit entered U-Boot 2020.07.
>>>>
>>>>> I assumed that the http://freescale.github.io Yocto master would be
>>>>> using the latest upsteam git u-boot if I didn't specify a particular
>>>>> branch, I guess I am wrong on that.
>>>> Hopefully, Otavio can help clarifying. It could be that the U-Boot
>>>> version needs to be bumped.
>>> Indeed, the u-boot-fslc that is a part of Community BSP has a version
>>> 2020.04 for [dunfell] branch. [master] branch has already been
>>> advanced to 2020.10 so it should have that DTS in that you're looking
>>> for.
>>>
>>> I do not know if it is safe to upgrade the U-Boot on the LTS version,
>>> I'd leave it to Otavio to decide.
>>>
>>> Terry,
>>> Can you try to initialize your BSP build from [master] branch and test
>>> to see if (a) you have a support for the OV5645; and (b) whether that
>>> would be an option for you to utilize [master] instead of [dunfell]?
>> Thanks for the reply.
>>
>> I'm a bit new to meta-freescale and the use of the "repo" utility. I did a:
>>
>> "repo init -u https://github.com/Freescale/fsl-community-bsp-platform"
>> ie without "-b <branch>" which I assumed would pull the master ?
> Actually, it had pulled a "default" branch, which appears to be [dunfell]. :)
>
> I've done the same, and here is the output of repo info command:
> ----
> repo info
> Manifest branch: dunfell
> Manifest merge branch: refs/heads/dunfell
> Manifest groups: all,-notdefault
> ----------------------------
> Project: Documentation
> Mount path: /development/tmp/sources/Documentation
> Current revision: 4558857539fd5395e9657500f84017e2722ba433
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: fsl-community-bsp-base
> Mount path: /development/tmp/sources/base
> Current revision: 9d7b7caeba7ebd6c315bf99950e4501662ddeb80
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: meta-freescale
> Mount path: /development/tmp/sources/meta-freescale
> Current revision: 11170950b155168ec414bbde48e3a4427fcac4bd
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: meta-freescale-3rdparty
> Mount path: /development/tmp/sources/meta-freescale-3rdparty
> Current revision: 058316a502cdba7fad02df8c857c72e218b7bc45
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: meta-freescale-distro
> Mount path: /development/tmp/sources/meta-freescale-distro
> Current revision: 5d882cdf079b3bde0bd9869ce3ca3db411acbf3b
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: meta-openembedded
> Mount path: /development/tmp/sources/meta-openembedded
> Current revision: de37512b25c1f8c6bb6ab2b3782ac0fe01443483
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> Project: poky
> Mount path: /development/tmp/sources/poky
> Current revision: a13bda44fcda4e79e9aed39ca1495eabecb6a7b7
> Manifest revision: dunfell
> Local Branches: 0
> ----------------------------
> ----
>
> As you can see, manifest default branch is set to [dunfell], so you
> should explicitly use [-b master].
>
Hi Andrey,
Ah, many thanks that will help !
I will try to build from that, might also sort out my issue with
"gstreamer1.0-plugins-imx".
Terry
next prev parent reply other threads:[~2021-02-19 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 8:39 Wandboard WB-IMX6U-BW CAM-OV5645 camera Terry Barnaby
2021-02-16 20:46 ` [meta-freescale] " Otavio Salvador
2021-02-16 20:55 ` Fabio Estevam
2021-02-17 5:31 ` Terry Barnaby
2021-02-19 1:19 ` Fabio Estevam
2021-02-19 7:24 ` Terry Barnaby
2021-02-19 11:09 ` Fabio Estevam
2021-02-19 12:59 ` Andrey Zhizhikin
2021-02-19 13:28 ` Terry Barnaby
2021-02-19 13:34 ` Andrey Zhizhikin
2021-02-19 13:45 ` Terry Barnaby [this message]
2021-02-19 15:22 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17410ef9-b09c-7a49-79f9-9c81a8b3553d@beam.ltd.uk \
--to=terry@beam.ltd.uk \
--cc=andrey.z@gmail.com \
--cc=festevam@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).