> >>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? >
Hi, 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. You should be able to figure out exactly which u-boot recipe you are using by running: bitbake -e <image name> | grep ^PREFERRED_PROVIDER_virtual/bootloader Not sure if this is the recommended way to go, but that’s how I solved it. //Pelle
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48293): https://lists.yoctoproject.org/g/yocto/message/48293 Mute This Topic: https://lists.yoctoproject.org/mt/71016973/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
