New HW to U-boot and Yocto to support it

New HW to U-boot and Yocto to support it

[Keskinarkaus, Teemu]

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

Hi,

We have imx6 based HW and so far I've been using the develboard (sabresd) to simulate it and do software development.

Now I want to make U-boot(kernel and rest is not the problem atm) support that hw directly without modifying the existing hw. I used the mx6sabresd as a based and copied/modified stuff to my hw name. I can execute following command in u-boot src dir: make myhw_defconfig and u-boot it setup.

Then in my machine config in Yocto I've setup following (copied from mx6sabre again):

UBOOT_CONFIG ??= "sd"
UBOOT_CONFIG[sd] = "myhw_config,sdcard" (I tried defconfig here, but no change)
UBOOT_CONFIG[mfgtool] = "myhw_config"

This causes following problems:

| In file included from / yocto/build/tmp/work/vit-poky-linux-gnueabi/u-boot-fslc/v2014.10+gitAUTOINC+5fd0b607d0-r0.20/git/include/common.h:18:0:
| include/config.h:6:22: fatal error: configs/.h: No such file or directory
|  #include <configs/.h>

So obviously the config doesn't transfer to U-boot when using Yocto system to compile U-boot. Also autoconf files are missing etc.

Seems that it might be Yocto side problem more than U-boot since there really isn't much on U-boot when adding new board there. Any idea what might be the problem? I'm running out of ideas. Being debugging this issue for few hours already.

I tried to search for how-to documents how to add new hw to u-boot and I've basically done all the steps already so that's why I'm assuming that it might be Yocto side problem.

Teemu Keskinarkaus



________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

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

Re: New HW to U-boot and Yocto to support it

[Daiane Angolini]

On Mon, Aug 17, 2015 at 4:52 AM, Keskinarkaus, Teemu
<Teemu.Keskinarkaus@maximatecc.com> wrote:
> Hi,
>
>
>
> We have imx6 based HW and so far I’ve been using the develboard (sabresd) to
> simulate it and do software development.
>
> Now I want to make U-boot(kernel and rest is not the problem atm) support
> that hw directly without modifying the existing hw. I used the mx6sabresd as
> a based and copied/modified stuff to my hw name. I can execute following
> command in u-boot src dir: make myhw_defconfig and u-boot it setup.
>
> Then in my machine config in Yocto I’ve setup following (copied from
> mx6sabre again):
>
> UBOOT_CONFIG ??= "sd"
>
> UBOOT_CONFIG[sd] = "myhw_config,sdcard" (I tried defconfig here, but no
> change)
>
> UBOOT_CONFIG[mfgtool] = "myhw_config"
>
> This causes following problems:
>
> | In file included from /
> yocto/build/tmp/work/vit-poky-linux-gnueabi/u-boot-fslc/v2014.10+gitAUTOINC+5fd0b607d0-r0.20/git/include/common.h:18:0:
>
> | include/config.h:6:22: fatal error: configs/.h: No such file or directory
>
> |  #include <configs/.h>

Have you already double checked if this isn't a typo on your file?

Maybe email app only messed your text, but looks like typo to me.

>
> So obviously the config doesn’t transfer to U-boot when using Yocto system
> to compile U-boot. Also autoconf files are missing etc.
>
> Seems that it might be Yocto side problem more than U-boot since there
> really isn’t much on U-boot when adding new board there. Any idea what might
> be the problem? I’m running out of ideas. Being debugging this issue for few
> hours already.
>
> I tried to search for how-to documents how to add new hw to u-boot and I’ve
> basically done all the steps already so that’s why I’m assuming that it
> might be Yocto side problem.

In order to isolate if this is a yocto problem or not. You can build
u-boot using a stand alone toolchain instead. As soon as you have it
working you start to integrate it on yocto. This way you are sure
u-boot source code is ok.

Daiane
>
>
>
> Teemu Keskinarkaus
>
>
>
>
> ________________________________
>
> Actuant Corporation Email Notice
>
> This message is intended only for the use of the Addressee and may contain
> information that is PRIVILEGED and/or CONFIDENTIAL.
> This email is intended only for the personal and confidential use of the
> recipient(s) named above. If the reader of this email is not an intended
> recipient, you have received this email in error and any review,
> dissemination, distribution or copying is strictly prohibited.
> If you have received this email in error, please notify the sender
> immediately by return mail and permanently delete the copy you received.
>
> Thank you.
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>