Date   

Re: [yocto] Support UBI u-boot

JH
 

Anyway, hacked the Makefile and mtdpart.c, finally got it compiled to
support UBI. I think some latest branch might fix the problems I
haven't tested, if not, I am happy to make patches.

Thank you all.

Kind regards,

- jh

On 2/9/20, JH <jupiter.hce@...> wrote:
Changed to https://source.codeaurora.org/external/imx/uboot-imx.git
branch imx_v2018.03_4.14.98_2.0.0_ga, it can now support
CONFIG_CMD_MTDPARTS ind defconfg, all MTDPARTS error gone, but then
2018.03-r0/git/cmd/ubi.c missed dependencies of del_mtd_partitions,
add_mtd_partitions, mtd_get_device_size all in mtdpart.c which can
only be enabled by CONFIG_MTD_PARTITIONS:

obj-$(CONFIG_MTD_PARTITIONS) += mtdpart.o

But that CONFIG_MTD_PARTITIONS is not supported in defconfig.

Could anyone advise which branch works for UBI?

Thank you.

Kind regards,

- jh


Re: [yocto] Support UBI u-boot

JH
 

Changed to https://source.codeaurora.org/external/imx/uboot-imx.git
branch imx_v2018.03_4.14.98_2.0.0_ga, it can now support
CONFIG_CMD_MTDPARTS ind defconfg, all MTDPARTS error gone, but then
2018.03-r0/git/cmd/ubi.c missed dependencies of del_mtd_partitions,
add_mtd_partitions, mtd_get_device_size all in mtdpart.c which can
only be enabled by CONFIG_MTD_PARTITIONS:

obj-$(CONFIG_MTD_PARTITIONS) += mtdpart.o

But that CONFIG_MTD_PARTITIONS is not supported in defconfig.

Could anyone advise which branch works for UBI?

Thank you.

Kind regards,

- jh


Re: [yocto] Support UBI u-boot

JH
 

Hi Gabriele,

Thanks for the help.

On 2/8/20, Gabriele Zampieri <gabbla.malist@...> wrote:
If you just want to run the menuconfig run
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig
and
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- savedefconfig
In any environment.
It does not seem the OE / Yocto build issue, rather than the u-boot
build issue.

I can build OE / Yocto to load my mx6ull_14x14_evk_nand_defconfig to
replace the original source
git/configs/mx6ull_14x14_evk_nand_defconfig.

The git/scripts/kconfig was able to run defconfig mode that
git/scripts/kconfig/conf.c and git/scripts/kconfig/confdata.c was able
to enable CONFIG_CMD_UBI and to write to the .config based on my
mx6ull_14x14_evk_nand_defconfig, but git/scripts/kconfig/conf.c and
git/scripts/kconfig/confdata.c were not able to generate
CONFIG_CMD_MTDPARTS (I could not find CONFIG_CMD_MTDPARTS when I made
menuconig from menu config either).

The git/cmd/Makefile requires CONFIG_CMD_MTDPARTS set up to run
mtdparts.c, without CONFIG_CMD_MTDPARTS, mtdparts.c was not compiled,
and other cmd source files were not compiled, thus missing all
dependencies for ubi (undefined reference).

Is it buggy in u-boot source downloaded from
https://source.codeaurora.org/external/imx/uboot-imx.git (commit
"8be98e9322040c655b9e5c9fb2c494e002e3fad9"), or is just my silly
stupidity to miss things?

Could anyone in u-boot source development help to comment our if
https://source.codeaurora.org/external/imx/uboot-imx.git (commit
"8be98e9322040c655b9e5c9fb2c494e002e3fad9") works for ubi or not? Or
what I could be missing?

Apologize to cc source contributors.

Thank you.

Kind regards,

- jh


Re: [yocto] Support UBI u-boot

Gabriele <gabbla.malist@...>
 

Hi,

On Fri, Feb 7, 2020 at 2:55 AM JH <jupiter.hce@...> wrote:
Hi Gabriele,

On 2/6/20, Gabriele Zampieri <gabbla.malist@...> wrote:
> As far as I know uboot (usually virtual/bootloader) does not have a task to
> run menuconfig directly from bitbake.
> I usually have a local clone of uboot and I simply run `make [...]
> menuconfig|savedefconfig` , then I create a patch
> to add my defconfig (custom_defconfig) to configs/ and specify
> UBOOT_MACHINE = "custom_defconfig"

Are there any document to use cross compiler tools to build u-boot-imx
on Ubuntu 18 host machine? It seems that build environment will not be
the same as the Yocto build environment I am currently running on
Ubuntu 18 host.

I compile uboot using the Yocto generated SDK. Simply
source /opt/poky/.../env-script
make -j4

If you just want to run the menuconfig run
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig
and
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- savedefconfig
In any environment.
Thank you Gabriele for great helps.
 
Kind regards,

- jh

Gabriele


Re: [OE-core] [yocto] Support UBI u-boot

JH
 

Hi Quentin,

Thanks for your response, so glad you help me here again :-).

On 2/7/20, Quentin Schulz <quentin.schulz@...> wrote:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:448:
undefined reference to `mtdparts_init'
This function is not defined. So you look it up in the sources, find
where it's defined.
That is a function call in cmd/ubi.c:

int ubi_detach(void)
{
if (mtdparts_init() != 0) {
printf("Error initializing mtdparts!\n");
return 1;
}
.....

That function is in cmd/mtdparts.c:
int mtdparts_init(void) {
.......
}

It is in the same source directory, I'll have to look it deep, why it
does not compile cmd/mtdparts.c?


Is it in a file which is compiled/included somewhere?
Is it surrounded by #ifdef? And by surrounded, I mean the #ifdef can
be several thousands of lines above the function definition.
Actually, there is no macros to surround that function.


In that case, I couldn't find the sources of u-boot-imx (didn't take the
time) but from upstream:
https://elixir.bootlin.com/u-boot/v2017.03/source/cmd/nand.c#L35
The meta-freescale downloaded the u-boot source from
https://source.codeaurora.org/external/imx/uboot-imx.git

It's surrounded by #if defined(CONFIG_CMD_MTDPARTS) so you need
CMD_MTDPARTS to be enabled. Do the same for all the other calls. There's
no magic thing, you thus have to look it up yourself most of the time.
Even though arguably, that's a mistake from upstream (there should be a
dependency on MTDPARTS in Kconfig, anyway...).
You are right, the CONFIG_CMD_MTDPARTS is defined in many defconfig
except it is not in my mx6ull_14x14_evk_defconfig, there are lots of
definitions are defined in other defconfig, but missing in
mx6ull_14x14_evk_defconfig. When I run make menuconfig, I enabled all
MTD, NAND and UBI parts except UBI Fastmap (Experimental feature) in
menuconfig, but I still could not find CONFIG_CMD_MTDPARTS and other
definitions. Need to look it carefully.

I suspect that to run make menuconfig might not be right command, I
tried bitbake -c menuconfig u-boot:

ERROR: Task do_menuconfig does not exist for target u-boot
(./meta-freescale/recipes-bsp/u-boot/u-boot-imx_2017.03.bb:do_menuconfig).
Close matches:
do_configure

To run kernel menuconfig, I can add KERNEL_CONFIG_COMMAND =
"oe_runmake_call -C ${S} O=${B} imx_v6_v7_defconfig" to a bbappend
file to run bitbake -c menuconfig kernel. Is there an equivelent
UBOOT_CONFIG_COMMAND to run oe_runmake?

Thank you.

- jh


Re: [OE-core] [yocto] Support UBI u-boot

Quentin Schulz <quentin.schulz@...>
 

Hi JH,

On Fri, Feb 07, 2020 at 07:52:35PM +1100, JH wrote:
Hi Pelle,

Aplogize for cross posting.

On 2/7/20, Pelle Windestam <Pelle.Windestam@...> wrote:
In my case u-boot uses a default config called imx8qxp_var_som_defconfig
stored under the configs directory in u-boot (not sure if its in the
official repositories, I use a vendor supplied u-boot repo, but the
procedure should be the same either way), then I have created a
.bbappend-file for the u-boot recipe, and added a patch that modifies the
defconfig file to include the options I want to enable. Then as u-boot is
built, it will use the patched defconfig with the appropriate options
enabled. In the meta-freescale layer the u-boot recipes are under
meta-freescale/recipes-bsp/u-boot.
Thanks for the tip, that is quite helpful. I created bbappend file,
run the make menuconfig to enable NAND and CONFIG_CMD_UBI, but then
failed in build, missing all MTD, NAND, UBI references, the MTD, NAND,
UBI are all selected, what I could be missing?

/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:448:
undefined reference to `mtdparts_init'
This function is not defined. So you look it up in the sources, find
where it's defined.

Is it in a file which is compiled/included somewhere?
Is it surrounded by #ifdef? And by surrounded, I mean the #ifdef can
be several thousands of lines above the function definition.

In that case, I couldn't find the sources of u-boot-imx (didn't take the
time) but from upstream:
https://elixir.bootlin.com/u-boot/v2017.03/source/cmd/nand.c#L35

It's surrounded by #if defined(CONFIG_CMD_MTDPARTS) so you need
CMD_MTDPARTS to be enabled. Do the same for all the other calls. There's
no magic thing, you thus have to look it up yourself most of the time.
Even though arguably, that's a mistake from upstream (there should be a
dependency on MTDPARTS in Kconfig, anyway...).

Quentin


Re: [yocto] Support UBI u-boot

JH
 

Hi Pelle,

Aplogize for cross posting.

On 2/7/20, Pelle Windestam <Pelle.Windestam@...> wrote:
In my case u-boot uses a default config called imx8qxp_var_som_defconfig
stored under the configs directory in u-boot (not sure if its in the
official repositories, I use a vendor supplied u-boot repo, but the
procedure should be the same either way), then I have created a
.bbappend-file for the u-boot recipe, and added a patch that modifies the
defconfig file to include the options I want to enable. Then as u-boot is
built, it will use the patched defconfig with the appropriate options
enabled. In the meta-freescale layer the u-boot recipes are under
meta-freescale/recipes-bsp/u-boot.
Thanks for the tip, that is quite helpful. I created bbappend file,
run the make menuconfig to enable NAND and CONFIG_CMD_UBI, but then
failed in build, missing all MTD, NAND, UBI references, the MTD, NAND,
UBI are all selected, what I could be missing?

/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:448:
undefined reference to `mtdparts_init'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:468:
undefined reference to `del_mtd_partitions'
| arm-oe-linux-gnueabi-ld.bfd: cmd/built-in.o: in function `ubi_part':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:489:
undefined reference to `find_dev_and_part'
| arm-oe-linux-gnueabi-ld.bfd: cmd/built-in.o: in function `ubi_dev_scan':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:415:
undefined reference to `find_dev_and_part'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:423:
undefined reference to `add_mtd_partitions'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/cmd/ubi.c:437:
undefined reference to `del_mtd_partitions'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`add_volume':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:294:
undefined reference to `rb_insert_color'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_add_to_av':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:589:
undefined reference to `rb_insert_color'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_remove_av':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:634:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:640:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:636:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`scan_all':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1265:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`self_check_ai':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1515:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1558:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`scan_all':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1266:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1265:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1266:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`self_check_ai':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1558:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1515:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1629:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1631:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1629:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1631:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1717:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1717:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1718:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/attach.c:1718:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`get_bad_peb_limit':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/build.c:623:
undefined reference to `mtd_get_device_size'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`process_lvol':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/vtbl.c:407:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/vtbl.c:407:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ltree_add_entry':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/eba.c:180:
undefined reference to `rb_insert_color'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`leb_read_unlock':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/eba.c:225:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_eba_init':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/eba.c:1423:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_move_aeb_to_list':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/include/../drivers/mtd/ubi/ubi.h:1013:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_eba_init':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/eba.c:1423:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`find_wl_entry':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:314:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`wl_tree_add':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:170:
undefined reference to `rb_insert_color'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`get_peb_for_wl':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1777:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ensure_wear_leveling':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:992:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`wear_leveling_worker':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:721:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:736:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:742:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:748:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_wl_put_peb':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1226:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1229:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_wl_scrub_peb':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1298:
undefined reference to `rb_erase'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`ubi_wl_init':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1569:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1570:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1570:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:1569:
undefined reference to `rb_next'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`find_mean_wl_entry':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:355:
undefined reference to `rb_first'
| arm-oe-linux-gnueabi-ld.bfd:
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:356:
undefined reference to `rb_last'
| arm-oe-linux-gnueabi-ld.bfd: drivers/mtd/ubi/built-in.o: in function
`wl_get_wle':
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/mtd/ubi/wl.c:395:
undefined reference to `rb_erase'
| /build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git/Makefile:1234:
recipe for target 'u-boot' failed
| make[1]: *** [u-boot] Error 1
| make[1]: Leaving directory
'/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/build/mx6ull_14x14_evk_config'
| Makefile:150: recipe for target 'sub-make' failed
| make: *** [sub-make] Error 2
| make: Leaving directory
'/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/git'
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/build/Installer/sa_platform_build/Source/Yocto/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2017.03-r0/temp/log.do_compile.11257)

$ cat

#
# Automatically generated file; DO NOT EDIT.
# U-Boot 2017.03 Configuration
#
CONFIG_CREATE_ARCH_SYMLINK=y
# CONFIG_ARC is not set
CONFIG_ARM=y
# CONFIG_AVR32 is not set
# CONFIG_BLACKFIN is not set
# CONFIG_M68K is not set
# CONFIG_MICROBLAZE is not set
# CONFIG_MIPS is not set
# CONFIG_NDS32 is not set
# CONFIG_NIOS2 is not set
# CONFIG_OPENRISC is not set
# CONFIG_PPC is not set
# CONFIG_SANDBOX is not set
# CONFIG_SH is not set
# CONFIG_SPARC is not set
# CONFIG_X86 is not set
# CONFIG_XTENSA is not set
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="mx6"
CONFIG_SYS_VENDOR="freescale"
CONFIG_SYS_BOARD="mx6ullevk"
CONFIG_SYS_CONFIG_NAME="mx6ullevk"

#
# ARM architecture
#
CONFIG_HAS_VBAR=y
CONFIG_HAS_THUMB2=y
CONFIG_CPU_V7=y
CONFIG_SYS_ARM_ARCH=7
CONFIG_SYS_CACHE_SHIFT_6=y
CONFIG_SYS_CACHELINE_SIZE=64
# CONFIG_ARM_SMCCC is not set
# CONFIG_SEMIHOSTING is not set
CONFIG_SYS_L2CACHE_OFF=y
# CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK is not set
CONFIG_USE_ARCH_MEMCPY=y
CONFIG_SPL_USE_ARCH_MEMCPY=y
CONFIG_USE_ARCH_MEMSET=y
CONFIG_SPL_USE_ARCH_MEMSET=y
# CONFIG_ARM64_SUPPORT_AARCH32 is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_TARGET_EDB93XX is not set
# CONFIG_TARGET_ASPENITE is not set
# CONFIG_TARGET_GPLUGD is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_KIRKWOOD is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_TARGET_DEVKIT3250 is not set
# CONFIG_TARGET_WORK_92105 is not set
# CONFIG_TARGET_MX25PDK is not set
# CONFIG_TARGET_ZMX25 is not set
# CONFIG_TARGET_APF27 is not set
# CONFIG_TARGET_APX4DEVKIT is not set
# CONFIG_TARGET_XFI3 is not set
# CONFIG_TARGET_M28EVK is not set
# CONFIG_TARGET_MX23EVK is not set
# CONFIG_TARGET_MX28EVK is not set
# CONFIG_TARGET_MX23_OLINUXINO is not set
# CONFIG_TARGET_BG0900 is not set
# CONFIG_TARGET_SANSA_FUZE_PLUS is not set
# CONFIG_TARGET_SC_SPS_1 is not set
# CONFIG_ORION5X is not set
# CONFIG_TARGET_SPEAR300 is not set
# CONFIG_TARGET_SPEAR310 is not set
# CONFIG_TARGET_SPEAR320 is not set
# CONFIG_TARGET_SPEAR600 is not set
# CONFIG_TARGET_STV0991 is not set
# CONFIG_TARGET_X600 is not set
# CONFIG_TARGET_IMX31_PHYCORE is not set
# CONFIG_TARGET_IMX31_PHYCORE_EET is not set
# CONFIG_TARGET_MX31ADS is not set
# CONFIG_TARGET_MX31PDK is not set
# CONFIG_TARGET_WOODBURN is not set
# CONFIG_TARGET_WOODBURN_SD is not set
# CONFIG_TARGET_FLEA3 is not set
# CONFIG_TARGET_MX35PDK is not set
# CONFIG_ARCH_BCM283X is not set
# CONFIG_TARGET_VEXPRESS_CA15_TC2 is not set
# CONFIG_TARGET_VEXPRESS_CA5X2 is not set
# CONFIG_TARGET_VEXPRESS_CA9X4 is not set
# CONFIG_TARGET_BRXRE1 is not set
# CONFIG_TARGET_BRPPT1 is not set
# CONFIG_TARGET_DRACO is not set
# CONFIG_TARGET_THUBAN is not set
# CONFIG_TARGET_RASTABAN is not set
# CONFIG_TARGET_ETAMIN is not set
# CONFIG_TARGET_PXM2 is not set
# CONFIG_TARGET_RUT is not set
# CONFIG_TARGET_TI814X_EVM is not set
# CONFIG_TARGET_TI816X_EVM is not set
# CONFIG_TARGET_BCM23550_W1D is not set
# CONFIG_TARGET_BCM28155_AP is not set
# CONFIG_TARGET_BCMCYGNUS is not set
# CONFIG_TARGET_BCMNSP is not set
# CONFIG_ARCH_EXYNOS is not set
# CONFIG_ARCH_S5PC1XX is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_KEYSTONE is not set
# CONFIG_ARCH_MESON is not set
# CONFIG_ARCH_MX7ULP is not set
# CONFIG_ARCH_MX7 is not set
CONFIG_ARCH_MX6=y
# CONFIG_ARCH_MX5 is not set
# CONFIG_TARGET_M53EVK is not set
# CONFIG_TARGET_MX51EVK is not set
# CONFIG_TARGET_MX53ARD is not set
# CONFIG_TARGET_MX53EVK is not set
# CONFIG_TARGET_MX53LOCO is not set
# CONFIG_TARGET_MX53SMD is not set
# CONFIG_OMAP34XX is not set
# CONFIG_OMAP44XX is not set
# CONFIG_OMAP54XX is not set
# CONFIG_AM43XX is not set
# CONFIG_AM33XX is not set
# CONFIG_ARCH_RMOBILE is not set
# CONFIG_TARGET_S32V234EVB is not set
# CONFIG_ARCH_SNAPDRAGON is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_TARGET_CM_T43 is not set
# CONFIG_ARCH_SUNXI is not set
# CONFIG_TARGET_TS4600 is not set
# CONFIG_TARGET_TS4800 is not set
# CONFIG_TARGET_VF610TWR is not set
# CONFIG_TARGET_COLIBRI_VF is not set
# CONFIG_TARGET_PCM052 is not set
# CONFIG_TARGET_BK4R1 is not set
# CONFIG_ARCH_ZYNQ is not set
# CONFIG_ARCH_ZYNQMP is not set
# CONFIG_ARCH_IMX8 is not set
# CONFIG_ARCH_IMX8M is not set
# CONFIG_TEGRA is not set
# CONFIG_TARGET_VEXPRESS64_AEMV8A is not set
# CONFIG_TARGET_VEXPRESS64_BASE_FVP is not set
# CONFIG_TARGET_VEXPRESS64_BASE_FVP_DRAM is not set
# CONFIG_TARGET_VEXPRESS64_JUNO is not set
# CONFIG_TARGET_LS2080A_EMU is not set
# CONFIG_TARGET_LS2080A_SIMU is not set
# CONFIG_TARGET_LS2080AQDS is not set
# CONFIG_TARGET_LS2080ARDB is not set
# CONFIG_TARGET_HIKEY is not set
# CONFIG_TARGET_LS1012AQDS is not set
# CONFIG_TARGET_LS1012ARDB is not set
# CONFIG_TARGET_LS1012AFRDM is not set
# CONFIG_TARGET_LS1021AQDS is not set
# CONFIG_TARGET_LS1021ATWR is not set
# CONFIG_TARGET_LS1021AIOT is not set
# CONFIG_TARGET_LS1043AQDS is not set
# CONFIG_TARGET_LS1043ARDB is not set
# CONFIG_TARGET_LS1046AQDS is not set
# CONFIG_TARGET_LS1046ARDB is not set
# CONFIG_TARGET_H2200 is not set
# CONFIG_TARGET_ZIPITZ2 is not set
# CONFIG_TARGET_COLIBRI_PXA270 is not set
# CONFIG_ARCH_UNIPHIER is not set
# CONFIG_STM32 is not set
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_TARGET_THUNDERX_88XX is not set
# CONFIG_ARCH_ASPEED is not set
CONFIG_SYS_MALLOC_F_LEN=0x400
# CONFIG_SECURE_BOOT is not set
CONFIG_MX6=y
CONFIG_MX6UL=y
CONFIG_MX6ULL=y
# CONFIG_LDO_BYPASS_CHECK is not set
# CONFIG_CMD_BEE is not set
# CONFIG_MODULE_FUSE is not set
# CONFIG_TARGET_ADVANTECH_DMS_BA16 is not set
# CONFIG_TARGET_APALIS_IMX6 is not set
# CONFIG_TARGET_ARISTAINETOS is not set
# CONFIG_TARGET_ARISTAINETOS2 is not set
# CONFIG_TARGET_ARISTAINETOS2B is not set
# CONFIG_TARGET_CGTQMX6EVAL is not set
# CONFIG_TARGET_CM_FX6 is not set
# CONFIG_TARGET_COLIBRI_IMX6 is not set
# CONFIG_TARGET_EMBESTMX6BOARDS is not set
# CONFIG_TARGET_GE_B450V3 is not set
# CONFIG_TARGET_GE_B650V3 is not set
# CONFIG_TARGET_GE_B850V3 is not set
# CONFIG_TARGET_GW_VENTANA is not set
# CONFIG_TARGET_KOSAGI_NOVENA is not set
# CONFIG_TARGET_MCCMON6 is not set
# CONFIG_TARGET_MX6CUBOXI is not set
# CONFIG_TARGET_MX6QARM2 is not set
# CONFIG_TARGET_MX6Q_ICORE is not set
# CONFIG_TARGET_MX6Q_ICORE_RQS is not set
# CONFIG_TARGET_MX6QSABREAUTO is not set
# CONFIG_TARGET_MX6SABRESD is not set
# CONFIG_TARGET_MX6SLEVK is not set
# CONFIG_TARGET_MX6SLLEVK is not set
# CONFIG_TARGET_MX6SLL_ARM2 is not set
# CONFIG_TARGET_MX6SXSABRESD is not set
# CONFIG_TARGET_MX6SXSABREAUTO is not set
# CONFIG_TARGET_MX6SX_14X14_ARM2 is not set
# CONFIG_TARGET_MX6SX_17X17_ARM2 is not set
# CONFIG_TARGET_MX6SX_19X19_ARM2 is not set
# CONFIG_TARGET_MX6UL_9X9_EVK is not set
# CONFIG_TARGET_MX6UL_14X14_EVK is not set
# CONFIG_TARGET_MX6UL_NXPU_IOPB is not set
# CONFIG_TARGET_MX6UL_14X14_DDR3_ARM2 is not set
# CONFIG_TARGET_MX6UL_14X14_LPDDR2_ARM2 is not set
# CONFIG_TARGET_MX6UL_GEAM is not set
# CONFIG_TARGET_MX6ULL_DDR3_ARM2 is not set
CONFIG_TARGET_MX6ULL_14X14_EVK=y
# CONFIG_TARGET_MX6ULL_9X9_EVK is not set
# CONFIG_TARGET_PICOSOM_IMX6UL is not set
# CONFIG_TARGET_PICO_IMX6DL is not set
# CONFIG_TARGET_MX6UL_SPRIOT is not set
# CONFIG_TARGET_NITROGEN6X is not set
# CONFIG_TARGET_OT1200 is not set
# CONFIG_TARGET_PICO_IMX6UL is not set
# CONFIG_TARGET_LITEBOARD is not set
# CONFIG_TARGET_PLATINUM_PICON is not set
# CONFIG_TARGET_PLATINUM_TITANIUM is not set
# CONFIG_TARGET_PCM058 is not set
# CONFIG_TARGET_SECOMX6 is not set
# CONFIG_TARGET_TBS2910 is not set
# CONFIG_TARGET_TITANIUM is not set
# CONFIG_TARGET_TQMA6 is not set
# CONFIG_TARGET_UDOO is not set
# CONFIG_TARGET_UDOO_NEO is not set
# CONFIG_TARGET_SAMTEC_VINING_2000 is not set
# CONFIG_TARGET_WANDBOARD is not set
# CONFIG_TARGET_WARP is not set
# CONFIG_TARGET_XPRESS is not set
# CONFIG_TARGET_ZC5202 is not set
# CONFIG_TARGET_ZC5601 is not set
# CONFIG_TARGET_MX6DQSCM is not set
# CONFIG_TARGET_MX6SXSCM is not set
# CONFIG_ARMV7_LPAE is not set
# CONFIG_IMX_OPTEE is not set
# CONFIG_GPT_TIMER is not set
CONFIG_ROM_UNIFIED_SECTIONS=y
# CONFIG_IMX_RDC is not set
# CONFIG_IMX_BOOTAUX is not set
# CONFIG_USE_IMXIMG_PLUGIN is not set
# CONFIG_DBG_MONITOR is not set
# CONFIG_IMX_TRUSTY_OS is not set
# CONFIG_SYS_ARM_CACHE_WRITEALLOC is not set
CONFIG_IDENT_STRING=""
# CONFIG_PRE_CONSOLE_BUFFER is not set
CONFIG_VIDEO=y

#
# ARM debug
#
# CONFIG_DEBUG_LL is not set
CONFIG_DEFAULT_DEVICE_TREE="imx6ull-14x14-evk-gpmi-weim"
CONFIG_SMBIOS_PRODUCT_NAME="mx6ullevk"
# CONFIG_AHCI is not set

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
# CONFIG_XEN is not set
# CONFIG_DISTRO_DEFAULTS is not set
CONFIG_SYS_MALLOC_F=y
CONFIG_EXPERT=y
CONFIG_SYS_MALLOC_CLEAR_ON_INIT=y
# CONFIG_TOOLS_DEBUG is not set
# CONFIG_PHYS_64BIT is not set

#
# Boot images
#
# CONFIG_FIT is not set
# CONFIG_OF_BOARD_SETUP is not set
# CONFIG_OF_SYSTEM_SETUP is not set
# CONFIG_OF_STDOUT_VIA_ALIAS is not set
CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/freescale/mx6ullevk/imximage.cfg"
CONFIG_ARCH_FIXUP_FDT_MEMORY=y

#
# API
#
# CONFIG_API is not set

#
# Boot timing
#
# CONFIG_BOOTSTAGE is not set
CONFIG_BOOTSTAGE_USER_COUNT=20
CONFIG_BOOTSTAGE_STASH_ADDR=0
CONFIG_BOOTSTAGE_STASH_SIZE=4096

#
# Boot media
#
CONFIG_NAND_BOOT=y
# CONFIG_ONENAND_BOOT is not set
# CONFIG_QSPI_BOOT is not set
# CONFIG_SATA_BOOT is not set
# CONFIG_SD_BOOT is not set
# CONFIG_SPI_BOOT is not set
CONFIG_BOOTDELAY=3

#
# Console
#
# CONFIG_CONSOLE_RECORD is not set
# CONFIG_SILENT_CONSOLE is not set
CONFIG_CONSOLE_MUX=y
CONFIG_SYS_CONSOLE_IS_IN_ENV=y
# CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE is not set
# CONFIG_SYS_CONSOLE_ENV_OVERWRITE is not set
# CONFIG_SYS_CONSOLE_INFO_QUIET is not set
# CONFIG_SYS_STDIO_DEREGISTER is not set
CONFIG_DEFAULT_FDT_FILE=""
# CONFIG_VERSION_VARIABLE is not set
CONFIG_BOARD_LATE_INIT=y
CONFIG_DISPLAY_CPUINFO=y
CONFIG_DISPLAY_BOARDINFO=y

#
# Start-up hooks
#
# CONFIG_ARCH_EARLY_INIT_R is not set
# CONFIG_ARCH_MISC_INIT is not set
CONFIG_BOARD_EARLY_INIT_F=y

#
# SPL / TPL
#

#
# Command line interface
#
CONFIG_CMDLINE=y
CONFIG_HUSH_PARSER=y
CONFIG_SYS_PROMPT="=> "

#
# Autoboot options
#
CONFIG_AUTOBOOT=y
# CONFIG_AUTOBOOT_KEYED is not set

#
# FASTBOOT
#
# CONFIG_FASTBOOT is not set

#
# Commands
#

#
# Info commands
#
CONFIG_CMD_BDI=y
# CONFIG_CMD_CONFIG is not set
CONFIG_CMD_CONSOLE=y
# CONFIG_CMD_CPU is not set
# CONFIG_CMD_LICENSE is not set

#
# Boot commands
#
CONFIG_CMD_BOOTD=y
CONFIG_CMD_BOOTM=y
CONFIG_CMD_BOOTZ=y
CONFIG_CMD_BOOTEFI=y
CONFIG_CMD_BOOTEFI_HELLO_COMPILE=y
# CONFIG_CMD_BOOTEFI_HELLO is not set
# CONFIG_CMD_BOOTMENU is not set
CONFIG_CMD_ELF=y
CONFIG_CMD_FDT=y
CONFIG_CMD_GO=y
CONFIG_CMD_RUN=y
CONFIG_CMD_IMI=y
# CONFIG_CMD_IMLS is not set
CONFIG_CMD_XIMG=y

#
# Environment commands
#
# CONFIG_CMD_ASKENV is not set
CONFIG_CMD_EXPORTENV=y
CONFIG_CMD_IMPORTENV=y
CONFIG_CMD_EDITENV=y
# CONFIG_CMD_GREPENV is not set
CONFIG_CMD_SAVEENV=y
CONFIG_CMD_ENV_EXISTS=y

#
# Memory commands
#
CONFIG_CMD_MEMORY=y
CONFIG_CMD_CRC32=y
# CONFIG_LOOPW is not set
CONFIG_CMD_MEMTEST=y
# CONFIG_CMD_MX_CYCLIC is not set
# CONFIG_CMD_MEMINFO is not set
# CONFIG_CMD_UNZIP is not set
# CONFIG_CMD_ZIP is not set

#
# Device access commands
#
CONFIG_CMD_DM=y
# CONFIG_CMD_DEMO is not set
CONFIG_CMD_LOADB=y
CONFIG_CMD_LOADS=y
CONFIG_CMD_FLASH=y
# CONFIG_CMD_GPT is not set
# CONFIG_CMD_ARMFLASH is not set
# CONFIG_CMD_MMC is not set
CONFIG_CMD_NAND=y
# CONFIG_CMD_PART is not set
# CONFIG_CMD_SF is not set
# CONFIG_CMD_SPI is not set
CONFIG_CMD_I2C=y
CONFIG_CMD_USB=y
# CONFIG_CMD_DFU is not set
# CONFIG_CMD_USB_SDP is not set
# CONFIG_CMD_USB_MASS_STORAGE is not set
CONFIG_CMD_FPGA=y
CONFIG_CMD_GPIO=y

#
# Shell scripting commands
#
CONFIG_CMD_ECHO=y
CONFIG_CMD_ITEST=y
CONFIG_CMD_SOURCE=y
CONFIG_CMD_SETEXPR=y

#
# Network commands
#
CONFIG_CMD_NET=y
# CONFIG_CMD_TFTPPUT is not set
# CONFIG_CMD_TFTPSRV is not set
# CONFIG_CMD_RARP is not set
CONFIG_CMD_DHCP=y
# CONFIG_CMD_PXE is not set
CONFIG_CMD_NFS=y
# CONFIG_CMD_MII is not set
CONFIG_CMD_PING=y
# CONFIG_CMD_CDP is not set
# CONFIG_CMD_SNTP is not set
# CONFIG_CMD_DNS is not set
# CONFIG_CMD_LINK_LOCAL is not set

#
# Misc commands
#
CONFIG_CMD_CACHE=y
# CONFIG_CMD_TIME is not set
CONFIG_CMD_MISC=y
# CONFIG_CMD_TIMER is not set
# CONFIG_CMD_QFW is not set

#
# Power commands
#
# CONFIG_CMD_REGULATOR is not set

#
# Security commands
#

#
# Firmware commands
#

#
# Filesystem commands
#
CONFIG_CMD_EXT2=y
CONFIG_CMD_EXT4=y
CONFIG_CMD_EXT4_WRITE=y
CONFIG_CMD_FAT=y
CONFIG_CMD_FS_GENERIC=y
CONFIG_CMD_UBI=y

#
# Partition Types
#
CONFIG_PARTITIONS=y
# CONFIG_MAC_PARTITION is not set
CONFIG_DOS_PARTITION=y
# CONFIG_ISO_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_PARTITION_UUIDS is not set
CONFIG_SUPPORT_OF_CONTROL=y

#
# Device Tree Control
#
CONFIG_OF_CONTROL=y
CONFIG_OF_SEPARATE=y
# CONFIG_OF_EMBED is not set
CONFIG_NET=y
# CONFIG_NET_RANDOM_ETHADDR is not set
# CONFIG_NETCONSOLE is not set
CONFIG_NET_TFTP_VARS=y
CONFIG_BOOTP_PXE_CLIENTARCH=0x15
CONFIG_BOOTP_VCI_STRING="U-Boot.armv7"

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_DM=y
CONFIG_DM_WARN=y
CONFIG_DM_DEVICE_REMOVE=y
CONFIG_DM_STDIO=y
CONFIG_DM_SEQ_ALIAS=y
# CONFIG_SPL_DM_SEQ_ALIAS is not set
# CONFIG_REGMAP is not set
# CONFIG_SPL_REGMAP is not set
CONFIG_DEVRES=y
# CONFIG_DEBUG_DEVRES is not set
CONFIG_SIMPLE_BUS=y
CONFIG_OF_TRANSLATE=y
# CONFIG_ADC is not set
# CONFIG_ADC_EXYNOS is not set
# CONFIG_ADC_SANDBOX is not set
# CONFIG_BLK is not set
# CONFIG_BLOCK_CACHE is not set

#
# SATA/SCSI device support
#

#
# Clock
#
# CONFIG_CLK is not set
# CONFIG_CPU is not set

#
# Hardware crypto devices
#
# CONFIG_FSL_CAAM is not set
CONFIG_SYS_FSL_SEC_COMPAT_4=y
# CONFIG_SYS_FSL_SEC_BE is not set
CONFIG_SYS_FSL_SEC_LE=y

#
# Demo for driver model
#
# CONFIG_DM_DEMO is not set
# CONFIG_IMX8M_DRAM is not set
# CONFIG_IMX8M_LPDDR4 is not set
# CONFIG_IMX8M_DDR4 is not set
CONFIG_SAVED_DRAM_TIMING_BASE=0x180000

#
# DFU support
#

#
# DMA Support
#
# CONFIG_DMA is not set
# CONFIG_TI_EDMA3 is not set

#
# FPGA support
#
# CONFIG_FPGA_ALTERA is not set
# CONFIG_FPGA_XILINX is not set

#
# GPIO Support
#
CONFIG_DM_GPIO=y
# CONFIG_ALTERA_PIO is not set
# CONFIG_DWAPB_GPIO is not set
# CONFIG_ATMEL_PIO4 is not set
# CONFIG_INTEL_BROADWELL_GPIO is not set
# CONFIG_IMX_RGPIO2P is not set
# CONFIG_LPC32XX_GPIO is not set
# CONFIG_MSM_GPIO is not set
# CONFIG_PCF8575_GPIO is not set
# CONFIG_ROCKCHIP_GPIO is not set
# CONFIG_TEGRA_GPIO is not set
# CONFIG_TEGRA186_GPIO is not set
# CONFIG_VYBRID_GPIO is not set
CONFIG_DM_74X164=y
# CONFIG_DM_PCA953X is not set
# CONFIG_MPC85XX_GPIO is not set

#
# I2C support
#
CONFIG_DM_I2C=y
# CONFIG_DM_I2C_COMPAT is not set
# CONFIG_DM_I2C_GPIO is not set
# CONFIG_SYS_I2C_FSL is not set
# CONFIG_SYS_I2C_DW is not set
# CONFIG_SYS_I2C_INTEL is not set
# CONFIG_SYS_I2C_MXC is not set
# CONFIG_SYS_I2C_ROCKCHIP is not set
# CONFIG_SYS_I2C_MVTWSI is not set
# CONFIG_I2C_MUX is not set
# CONFIG_DM_KEYBOARD is not set
# CONFIG_CROS_EC_KEYB is not set

#
# LED Support
#
# CONFIG_LED is not set
# CONFIG_LED_STATUS is not set

#
# Mailbox Controller Support
#
# CONFIG_DM_MAILBOX is not set

#
# Memory Controller drivers
#

#
# Multifunction device drivers
#
# CONFIG_MISC is not set
# CONFIG_CROS_EC is not set
# CONFIG_FSL_SEC_MON is not set
# CONFIG_MXC_OCOTP is not set
# CONFIG_NUVOTON_NCT6102D is not set
# CONFIG_PWRSEQ is not set
# CONFIG_PCA9551_LED is not set
# CONFIG_WINBOND_W83627 is not set

#
# MMC Host controller Support
#
CONFIG_MMC=y
CONFIG_GENERIC_MMC=y
CONFIG_DM_MMC=y
# CONFIG_DM_MMC_OPS is not set
# CONFIG_SPL_MMC_TINY is not set
# CONFIG_MMC_DW is not set
# CONFIG_MMC_MXC is not set
# CONFIG_MMC_MXS is not set
# CONFIG_MMC_OMAP_HS is not set
# CONFIG_MMC_SDHCI is not set

#
# MTD Support
#
CONFIG_MTD=y
# CONFIG_MTD_NOR_FLASH is not set
# CONFIG_CFI_FLASH is not set
# CONFIG_ALTERA_QSPI is not set

#
# NAND Device Support
#
# CONFIG_NAND_DENALI is not set
# CONFIG_NAND_VF610_NFC is not set
# CONFIG_NAND_PXA3XX is not set
# CONFIG_NAND_ARASAN is not set
# CONFIG_NAND_MXS is not set
# CONFIG_NAND_ZYNQ is not set

#
# Generic NAND options
#

#
# SPI Flash Support
#
# CONFIG_DM_SPI_FLASH is not set
# CONFIG_SPI_FLASH is not set

#
# UBI support
#
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_BITBANGMII is not set
# CONFIG_MV88E6352_SWITCH is not set
# CONFIG_PHYLIB is not set
CONFIG_DM_ETH=y
CONFIG_NETDEVICES=y
# CONFIG_ALTERA_TSE is not set
# CONFIG_DWC_ETH_QOS is not set
# CONFIG_E1000 is not set
# CONFIG_ETH_DESIGNWARE is not set
# CONFIG_ETHOC is not set
# CONFIG_FEC_MXC is not set
# CONFIG_MACB is not set
# CONFIG_RTL8139 is not set
# CONFIG_RTL8169 is not set
# CONFIG_SUN8I_EMAC is not set
# CONFIG_PCI is not set
# CONFIG_MVEBU_COMPHY_SUPPORT is not set

#
# Pin controllers
#
CONFIG_PINCTRL=y
CONFIG_PINCTRL_FULL=y
CONFIG_PINCTRL_GENERIC=y
CONFIG_PINMUX=y
# CONFIG_PINCONF is not set
# CONFIG_ROCKCHIP_RK3036_PINCTRL is not set
# CONFIG_ROCKCHIP_RK3288_PINCTRL is not set
# CONFIG_PINCTRL_AT91PIO4 is not set
# CONFIG_ROCKCHIP_RK3399_PINCTRL is not set
CONFIG_PINCTRL_IMX=y
CONFIG_PINCTRL_IMX6=y

#
# Power
#

#
# Power Domain Support
#
# CONFIG_POWER_DOMAIN is not set
# CONFIG_DM_PMIC is not set
# CONFIG_POWER_MC34VR500 is not set
CONFIG_DM_REGULATOR=y
# CONFIG_SPL_DM_REGULATOR is not set
# CONFIG_REGULATOR_PWM is not set
CONFIG_DM_REGULATOR_FIXED=y
CONFIG_DM_REGULATOR_GPIO=y
# CONFIG_DM_PWM is not set
# CONFIG_RAM is not set

#
# Remote Processor drivers
#

#
# Reset Controller Support
#
# CONFIG_DM_RESET is not set

#
# Real Time Clock
#
# CONFIG_DM_RTC is not set

#
# Serial drivers
#
# CONFIG_DM_SERIAL is not set
# CONFIG_DEBUG_UART is not set
# CONFIG_DEBUG_UART_SKIP_INIT is not set
# CONFIG_ATMEL_USART is not set
# CONFIG_FSL_LPUART is not set
# CONFIG_MVEBU_A3700_UART is not set
# CONFIG_MXC_UART is not set
# CONFIG_SYS_NS16550 is not set
# CONFIG_PXA_SERIAL is not set

#
# Sound support
#
# CONFIG_SOUND is not set

#
# SPI Support
#
CONFIG_DM_SPI=y
# CONFIG_ALTERA_SPI is not set
# CONFIG_CADENCE_QSPI is not set
# CONFIG_DESIGNWARE_SPI is not set
# CONFIG_EXYNOS_SPI is not set
# CONFIG_FSL_DSPI is not set
# CONFIG_ICH_SPI is not set
# CONFIG_MVEBU_A3700_SPI is not set
# CONFIG_ROCKCHIP_SPI is not set
# CONFIG_TEGRA114_SPI is not set
# CONFIG_TEGRA20_SFLASH is not set
# CONFIG_TEGRA20_SLINK is not set
# CONFIG_TEGRA210_QSPI is not set
# CONFIG_XILINX_SPI is not set
# CONFIG_OMAP3_SPI is not set
# CONFIG_SOFT_SPI is not set
# CONFIG_FSL_ESPI is not set
# CONFIG_FSL_FSPI is not set
# CONFIG_FSL_QSPI is not set
# CONFIG_TI_QSPI is not set

#
# SPMI support
#
# CONFIG_SPMI is not set

#
# System reset device drivers
#
# CONFIG_SYSRESET is not set
CONFIG_DM_THERMAL=y
# CONFIG_IMX_THERMAL is not set

#
# Timer Support
#
# CONFIG_TIMER is not set

#
# TPM support
#
CONFIG_USB=y
CONFIG_DM_USB=y

#
# USB Host Controller Drivers
#
CONFIG_USB_HOST=y
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI=y
CONFIG_USB_EHCI_MX6=y
# CONFIG_MXC_USB_OTG_HACTIVE is not set
# CONFIG_USB_EHCI_MSM is not set
# CONFIG_USB_EHCI_GENERIC is not set
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_UHCI_HCD is not set

#
# MUSB Controller Driver
#
# CONFIG_USB_MUSB_HOST is not set
# CONFIG_USB_MUSB_GADGET is not set
# CONFIG_USB_MUSB_TI is not set

#
# ULPI drivers
#

#
# USB peripherals
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_KEYBOARD is not set
# CONFIG_USB_GADGET is not set

#
# Graphics support
#
# CONFIG_DM_VIDEO is not set

#
# TrueType Fonts
#
# CONFIG_VIDEO_VESA is not set
# CONFIG_VIDEO_LCD_ANX9804 is not set
# CONFIG_VIDEO_LCD_SSD2828 is not set
# CONFIG_VIDEO_LCD_HITACHI_TX18D42VM is not set
# CONFIG_VIDEO_MVEBU is not set
# CONFIG_I2C_EDID is not set
# CONFIG_DISPLAY is not set
# CONFIG_VIDEO_TEGRA20 is not set
# CONFIG_VIDEO_BRIDGE is not set
# CONFIG_VIDEO_IPUV3 is not set
CONFIG_CFB_CONSOLE=y
# CONFIG_CFB_CONSOLE_ANSI is not set
CONFIG_VGA_AS_SINGLE_DEVICE=y
CONFIG_VIDEO_SW_CURSOR=y
# CONFIG_CONSOLE_EXTRA_INFO is not set
CONFIG_CONSOLE_SCROLL_LINES=1
# CONFIG_VIDEO_CT69000 is not set
CONFIG_SYS_CONSOLE_BG_COL=0x00
CONFIG_SYS_CONSOLE_FG_COL=0xa0
# CONFIG_LCD is not set

#
# WATCHDOG support
#
# CONFIG_ULP_WATCHDOG is not set
# CONFIG_PHYS_TO_BUS is not set

#
# File systems
#

#
# Library routines
#
# CONFIG_CC_OPTIMIZE_LIBS_FOR_SPEED is not set
CONFIG_HAVE_PRIVATE_LIBGCC=y
CONFIG_USE_PRIVATE_LIBGCC=y
CONFIG_SYS_HZ=1000
# CONFIG_USE_TINY_PRINTF is not set
CONFIG_REGEX=y
# CONFIG_LIB_RAND is not set
# CONFIG_AVB_ATX is not set
# CONFIG_DUAL_BOOTLOADER is not set
# CONFIG_CMD_DHRYSTONE is not set
# CONFIG_RSA is not set
# CONFIG_TPM is not set

#
# Hashing Support
#
# CONFIG_SHA1 is not set
# CONFIG_SHA256 is not set
# CONFIG_SHA_HW_ACCEL is not set

#
# Compression Support
#
# CONFIG_LZ4 is not set
# CONFIG_ERRNO_STR is not set
CONFIG_OF_LIBFDT=y
# CONFIG_LOAD_FDT_FROM_PART is not set
# CONFIG_OF_LIBFDT_OVERLAY is not set
# CONFIG_SPL_OF_LIBFDT is not set
# CONFIG_FDT_FIXUP_PARTITIONS is not set

#
# System tables
#
CONFIG_GENERATE_SMBIOS_TABLE=y
CONFIG_SMBIOS_MANUFACTURER="freescale"
CONFIG_EFI_LOADER=y
# CONFIG_UNIT_TEST is not set

Thank you.

- jh


Re: Support UBI u-boot

JH
 

Hi Andy,

On 2/6/20, Andy Pont <andy.pont@...> wrote:
JH wrote...


I added NAND and UBIFS support to my Yocto layer machine config file:

UBOOT_CONFIG = "nand"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
UBOOT_CONFIG[nand] += "ubi"
UBOOT_CONFIG[nand] += "ubifs"

But my u-boot.imx-nand still could not support ubi:

=> ubi part rootfs
Unknown command 'ubi' - try ‘help’
You need to start to read through the various sources to figure out for
yourself what is going on!

Starting from the bottom, in U-Boot 2017.03 all of the command sources
are in the “cmd” directory. The “ubi …” command are all in ubi.c.
Reading cmd/Makefile shows that file gets added into the build if
CONFIG_CMD_UBI is enabled.
You are right, that CONFIG_CMD_UBI is not enabled, but I could not
find any conf or bb files I could change or enable CONFIG_CMD_UBI in
meta-freescale layer.

Desperately, I hacked to run "make menuconfig" at U-Boot 2017.03 build
directory, selected and enabled CONFIG_CMD_UBI and saved to .config
file in that build directory, but then to run bitbake to build u-boot
again, the .config was removed and replaced by an old one disabled
CONFIG_CMD_UBI again.

Other people recommended to build u-boot in a standalone environment
out of OE / Yocto build system. Since I have set up everything in OE /
Yocto environment, I thought it could be easier if I could modify one
line of u-boot config file in a recipe.

Any idea where is the recipe in meta-freescale to allow me to change /
enable CONFIG_CMD_UBI?

Am I the only one unable to change u-boot config file in OE / Yoctu
build? That makes me very sad :-(.


The next place to look is whether or not that is set in your defconfig
for U-Boot or overwritten somewhere in a recipe in your Yocto build
environment.
Yeah, I'll been searched all day, could not find a recipe Yocto build
environment, I was told OE / Yocto does not have that stack and
mechanism to set and change u-boot config, is it true?

Thank you very much.

Kind regards,

- jh


Re: [yocto] Support UBI u-boot

JH
 

Hi Gabriele,

On 2/6/20, Gabriele Zampieri <gabbla.malist@...> wrote:
As far as I know uboot (usually virtual/bootloader) does not have a task to
run menuconfig directly from bitbake.
I usually have a local clone of uboot and I simply run `make [...]
menuconfig|savedefconfig` , then I create a patch
to add my defconfig (custom_defconfig) to configs/ and specify
UBOOT_MACHINE = "custom_defconfig"
Are there any document to use cross compiler tools to build u-boot-imx
on Ubuntu 18 host machine? It seems that build environment will not be
the same as the Yocto build environment I am currently running on
Ubuntu 18 host.

Thank you Gabriele for great helps.

Kind regards,

- jh


Re: [yocto] Support UBI u-boot

Gabriele <gabbla.malist@...>
 

Hi,

On Thu, Feb 6, 2020 at 11:07 AM JH <jupiter.hce@...> wrote:
Thanks Gabriele and Andy,

On 2/6/20, Gabriele Zampieri <gabbla.malist@...> wrote:
> Hi JH,
>
> have you tried what we suggested you in your last thread? More specifically
> adding your defconfig and tweaking it through menuconfig. and then specify
> the UBOOT_MACHINE.

Yes, as I posted in another thread, the MTD, UBI are all set in my
Linux kernel defconfig, I have also added UBOOT_CONFIG = "nand" in my
layer machine config.
What I missed is u-boot overlay, as you and Andy alluded. I added
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config", but strange
enough, that mx6ull_14x14_evk_nand_config, did not set CONFIG_CMD_UBI
in its config.

Sorry, I never tried that approach. 

I think I need to add an appended recipes-bsp to my layer just like I
added the recipes-kernel to my layer to overwrite kernel defconfig, I
need to overwrite u-boot defconfig.

In kernel, to overwrite defconfig, I run bitbake -c menuconfig
virtual/kernel, how can I generate u-boot defconfig, to run bitbake -c
menuconfig u-boot?
 
As far as I know uboot (usually virtual/bootloader) does not have a task to run menuconfig directly from bitbake.
I usually have a local clone of uboot and I simply run `make [...] menuconfig|savedefconfig` , then I create a patch
to add my defconfig (custom_defconfig) to configs/ and specify UBOOT_MACHINE = "custom_defconfig"

Thank you.

Kind regards,

- jh

Gabriele


Re: [yocto] Support UBI u-boot

JH
 

On 2/6/20, JH <jupiter.hce@...> wrote:
I think I need to add an appended recipes-bsp to my layer just like I
added the recipes-kernel to my layer to overwrite kernel defconfig, I
need to overwrite u-boot defconfig.

In kernel, to overwrite defconfig, I run bitbake -c menuconfig
virtual/kernel, how can I generate u-boot defconfig, to run bitbake -c
menuconfig u-boot?
Hmm, more complicated than I thought, it does not have defconfig in
u-boot like kernel does, how do you overwrite u-boot config in Yocto?


Re: [yocto] Support UBI u-boot

JH
 

Thanks Gabriele and Andy,

On 2/6/20, Gabriele Zampieri <gabbla.malist@...> wrote:
Hi JH,

have you tried what we suggested you in your last thread? More specifically
adding your defconfig and tweaking it through menuconfig. and then specify
the UBOOT_MACHINE.
Yes, as I posted in another thread, the MTD, UBI are all set in my
Linux kernel defconfig, I have also added UBOOT_CONFIG = "nand" in my
layer machine config.

What I missed is u-boot overlay, as you and Andy alluded. I added
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config", but strange
enough, that mx6ull_14x14_evk_nand_config, did not set CONFIG_CMD_UBI
in its config.

I think I need to add an appended recipes-bsp to my layer just like I
added the recipes-kernel to my layer to overwrite kernel defconfig, I
need to overwrite u-boot defconfig.

In kernel, to overwrite defconfig, I run bitbake -c menuconfig
virtual/kernel, how can I generate u-boot defconfig, to run bitbake -c
menuconfig u-boot?

Thank you.

Kind regards,

- jh


gstreamer allocation error on imx6dl-sabresd

Mauro Ziliani
 

Hi all.

I'm working on a imx6dl-sabresd derived board, gstreamer, uvcvideo webcam, Yocto Freescale i.MX Release Distro 4.1.15-2.0.1 FXMZ /dev/ttymxc0

the pipeline is

gst-launch-1.0 \
        imxv4l2src device=/dev/video1 \
        ! capsfilter caps="video/x-raw, width=640, height=480" \
        ! imxvideoconvert_g2d rotation=4 \
        ! imxv4l2sink overlay-width=800 overlay-height=600 overlay-left=235 overlay-top=65 enable-last-sample=true name=sink


Sometime the webcam freeze. After the first freeze the video stream is black and gstream GST_DEBUG=1 show the following message

WARN    default gstallocatorphymem.c:259:gst_buffer_is_phymem: physical address in memory block is invalid


There is some explanation/patch for this behavior?


gstreamer 1.8.1

gstreamer-plugin-imx 0.12.2


Thanks for your help

MZ


Re: [yocto] Support UBI u-boot

Gabriele <gabbla.malist@...>
 

Hi JH,

have you tried what we suggested you in your last thread? More specifically adding your defconfig and tweaking it through menuconfig. and then specify the UBOOT_MACHINE.

However you should be able to create and apply patches for external repo without any problem and the needs to push your changes to public repos (unless them are useful for others).

BR
Gabriele


On Thu, Feb 6, 2020 at 7:35 AM JH <jupiter.hce@...> wrote:
Hi,

Sorry for cross-posting, I have been asking for helping solving the
issue many days ago, but could not get those work.

(1) UBI support

I added NAND and UBIFS support to my Yocto layer machine config file:

UBOOT_CONFIG = "nand"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
UBOOT_CONFIG[nand] += "ubi"
UBOOT_CONFIG[nand] += "ubifs"

But my u-boot.imx-nand still could not support ubi:

=> ubi part rootfs
Unknown command 'ubi' - try 'help'

What I could be missing here?


(2) Patch u-boot parameters

I am not clear how you do to change u-boot parameters, it seems to me
I have to create my own u-boot-imx_2017.03.bbappend and patch files to
 mx6ullevk.h, to change u-boot parameters of mtdparts, NAND_ROOT_UBI,
bootcmd, etc based on my configuration.

But Yocto won't allow the patch running unless that the patch is
committed to the git repository in
https://source.codeaurora.org/external/imx/uboot-imx.git.

Ideally, I thought all u-boot parameters can be changed in a bbappend
file, could you advise if it is possible to do that way or not? If so,
how to do it?

If not, what is the policy for making parches and commit to the git
repository https://source.codeaurora.org/external/imx/uboot-imx.git?

Thank you.

Kind regards,

- jh


Support UBI u-boot

JH
 

Hi,

Sorry for cross-posting, I have been asking for helping solving the
issue many days ago, but could not get those work.

(1) UBI support

I added NAND and UBIFS support to my Yocto layer machine config file:

UBOOT_CONFIG = "nand"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
UBOOT_CONFIG[nand] += "ubi"
UBOOT_CONFIG[nand] += "ubifs"

But my u-boot.imx-nand still could not support ubi:

=> ubi part rootfs
Unknown command 'ubi' - try 'help'

What I could be missing here?


(2) Patch u-boot parameters

I am not clear how you do to change u-boot parameters, it seems to me
I have to create my own u-boot-imx_2017.03.bbappend and patch files to
mx6ullevk.h, to change u-boot parameters of mtdparts, NAND_ROOT_UBI,
bootcmd, etc based on my configuration.

But Yocto won't allow the patch running unless that the patch is
committed to the git repository in
https://source.codeaurora.org/external/imx/uboot-imx.git.

Ideally, I thought all u-boot parameters can be changed in a bbappend
file, could you advise if it is possible to do that way or not? If so,
how to do it?

If not, what is the policy for making parches and commit to the git
repository https://source.codeaurora.org/external/imx/uboot-imx.git?

Thank you.

Kind regards,

- jh


Support UBI and make patch to mx6ullevk.h

JH
 

Hi,

Sorry I am new to the uboot imx, appreciate your kind help for my
following questions:

(1) UBI support

I added NAND and UBIFS support to my Yocto layer machine config file:

UBOOT_CONFIG = "nand"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_config"
UBOOT_CONFIG[nand] += "mx6ull_14x14_evk_nand_config"
UBOOT_CONFIG[nand] += "ubi"
UBOOT_CONFIG[nand] += "ubifs"

But my u-boot.imx-nand still could support ubi:

=> ubi part rootfs
Unknown command 'ubi' - try 'help'

What I could be missing here?


(2) Patch u-boot parameters

I am not clear how you do to change u-boot parameters, it seems to me
I have to create my own u-boot-imx_2017.03.bbappend and patch files to
mx6ullevk.h, to change u-boot parameters of mtdparts, NAND_ROOT_UBI,
bootcmd, etc based on my configuration.

But Yocto won't allow the patch running unless that the patch is
committed to the git repository in
https://source.codeaurora.org/external/imx/uboot-imx.git.

Ideally, I thought all u-boot parameters can be changed in a bbappend
file, could you advise if it is possible to do that way or not? If so,
how to do it?

If not, what is the policy for making parches and commit to the git
repository https://source.codeaurora.org/external/imx/uboot-imx.git?

Thank you.

Kind regards,

- jh


Re: [meta-xilinx] addressing security in Yocto

Mark Hatle <mark.hatle@...>
 

Security requires a holistic approach. This can be divided into design and
defect response.

The design aspect of this is left to the implementer of the device. However, as
a project we need to do a better job at defining defaults, and looking for items
like SCAP that can be used to help people design/implement more secure devices.

On the defect (security) response side, work is in progress on this.

Currently there is a script that will pull down CVE information and attempt to
determine if a recipe may be affected based on specific CPE information. But in
the end, this is a reactive approach that relies on other people to do initial
triage and assign the CPEs (and other information).

This means we really need more proactive, response approach. The tooling for
this is nearly ready to go. We have the security response tool (which is part
of the Yocto Project) designed to help us perform triage, and a small group of
us has been working on a process around to perform the triage.

In the near future, I will be trying to post to the yocto-security list triage
status and other issues we find. When I begin posting, I will be inviting
people to help contribute to our triage, and response process. (Currently we're
running proof of concept triage behavior with a small group of people.)

--Mark

On 1/13/20 11:13 AM, Minelik, Ben [US] (MS) wrote:
Good Morning,

 

I was wondering if there is a more holistic way we can address security in Yocto
where we don’t have to create scripts for each vulnerability?  Is there anything
in Yocto meta-security and buck-security that can assist with the hardening of
Yocto?

 

 

 

Thank you,

 

Ben

Cybersecurity Engineer

720-975-5665




Re: imx8mn evk

Andrey Zhizhikin
 

Hello Richard,

On Tue, Jan 28, 2020 at 10:39 AM Richard Röjfors
<richard.rojfors@...> wrote:

Hi,

Thanks,!
Right now its a bit of head ache to switch to master, but I reviewed the files;
What is the particular problem of switching to [master] branch do you have?

I hear this from a lot of people, but never had it myself... I
actually was building [master] from the Day 1 and recently brought
patches which solves (partially I have to admit) python2/3 migration.
The only thing I've realized today the there are few recipes in
-distro layer which should be adapted, but in general it builds OK.

Can you please share what you have, I might have a look if this could
be solved relatively easy?

It basically looks like my private patches, except I'm using a slightly older older firmware-imx,
so it looks promising!

BR
Richard

Den tors 9 jan. 2020 kl 09:27 skrev Andrey Zhizhikin <andrey.z@...>:

Hello Richard,

On Thu, Dec 12, 2019 at 11:00 AM Andrey Zhizhikin <andrey.z@...> wrote:

On Thu, Dec 12, 2019 at 10:50 AM Richard Röjfors
<richard.rojfors@...> wrote:


Anyone knowing if NXP's has a upstream schedule for the nano EVK?
Would be interested in that info as well, since EVK is already available.
i.MX8M Nano EVK support has been merged into the meta-freescale layer,
you can try to build it off the master branch now.

--
Regards,
Andrey.


--
Regards,
Andrey.


Re: imx8mn evk

Richard Röjfors <richard.rojfors@...>
 

Hi,

Thanks,! 
Right now its a bit of head ache to switch to master, but I reviewed the files;
It basically looks like my private patches, except I'm using a slightly older older firmware-imx,
so it looks promising!

BR
Richard

Den tors 9 jan. 2020 kl 09:27 skrev Andrey Zhizhikin <andrey.z@...>:

Hello Richard,

On Thu, Dec 12, 2019 at 11:00 AM Andrey Zhizhikin <andrey.z@...> wrote:
>
> On Thu, Dec 12, 2019 at 10:50 AM Richard Röjfors
> <richard.rojfors@...> wrote:
> >
> >
> > Anyone knowing if NXP's has a upstream schedule for the nano EVK?
>
> Would be interested in that info as well, since EVK is already available.
>

i.MX8M Nano EVK support has been merged into the meta-freescale layer,
you can try to build it off the master branch now.

--
Regards,
Andrey.


Cannot bind OpenGlES 3.2 on IMX6D

Federico Giovanardi
 

Hello,
I'm running an IMX6D board with yocto-zeus and linux-imx 4.14 but I'm unable to bind the opengl api at version 3.2.
driver is vivante V6.2.4.p4.190076 Vivante GC2000 and the changelog attached to the commit says that
opengl es 3.2 should be fully supported on driver 6.x

https://source.codeaurora.org/external/imx/imx-manifest/tree/GraphicsChangeLogv6?h=imx-linux-warrior

In successfully able to bind the 3.0 api but not the 3.1 and neither the 3.2.  The application is compiled with -DLINUX -DEGL_API_FB -D_REENTRANT
and   -lGAL -lEGL -lGLESv2 because I haven't found any libGLESv3 in the receipe (only the headers).

Regards
Federico

601 - 620 of 24851