Standalone build for u-boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Standalone build for u-boot

Jump to solution
2,734 Views
rans
Senior Contributor I

Hello,

In "i.mx Linux user's guide" it is said that for standalone u-boot and kernel, we can clone the source from git, and just make <>_defconfig, and make for build.

In "i.mx Yocto project user's guide" it is said that u-boot builds for sd by default and in order to change it it should be done by writing to local.conf , for example for qspi1:

 echo "UBOOT_CONFIG = \"qspi1\"" >> conf/ local.conf

In case we are doing a standalone build, how do I configure u-boot to build for the specific storage media (as done in yocto local.conf) ?

If I understand correctly no more configuration are required in source- code , (we are using evaluation board and using the correct defconfig file for the evaluation board) , Right ?

Regards,

Ran

1 Solution
2,064 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello  Ran Shalit,

The UBOOT_CONFIG as qspi1 option references a specific defconfig file that configures the make instruction for compiling u-boot.

For example, this boot option for the i.MX6UL EVK calls the mx6ul_14x14_evk_qspi1_defconfig file which defines:

CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/freescale/mx6ul_14x14_evk/imximage.cfg,MX6UL,SYS_BOOT_QSPI"

CONFIG_ARM=y

CONFIG_TARGET_MX6UL_14X14_EVK=y

CONFIG_DM=y

CONFIG_DM_THERMAL=y

The easiest option then would be looking for the actual existing file for your board, since it’s already available.

There is no easy straightforward way to do this but you may look for references to this setting on the sources directory and look which defconfig is used for your board, for example with the command below:

$ grep -rnw '/<BSP_RELEASE_PATH>/sources/' -e "qspi1"

Then you would need to look for this file on the <BSP>/tmp/work directory.

I hope this helps!

Regards,

View solution in original post

2 Replies
2,065 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello  Ran Shalit,

The UBOOT_CONFIG as qspi1 option references a specific defconfig file that configures the make instruction for compiling u-boot.

For example, this boot option for the i.MX6UL EVK calls the mx6ul_14x14_evk_qspi1_defconfig file which defines:

CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/freescale/mx6ul_14x14_evk/imximage.cfg,MX6UL,SYS_BOOT_QSPI"

CONFIG_ARM=y

CONFIG_TARGET_MX6UL_14X14_EVK=y

CONFIG_DM=y

CONFIG_DM_THERMAL=y

The easiest option then would be looking for the actual existing file for your board, since it’s already available.

There is no easy straightforward way to do this but you may look for references to this setting on the sources directory and look which defconfig is used for your board, for example with the command below:

$ grep -rnw '/<BSP_RELEASE_PATH>/sources/' -e "qspi1"

Then you would need to look for this file on the <BSP>/tmp/work directory.

I hope this helps!

Regards,

2,064 Views
rans
Senior Contributor I

Hi gusarambula,

Yes, that's really helpful.

I please would also like to ask this: If the board has multiple storage device (we are using sabe solox, which has both qspi and sd),  and in config we give SD as the required boot storage device, in CONFIG_SYS_EXTRA_OPTIONS.

Does it mean that in linux we shall see only the partitions of sd (/dev/sdX) , or should we see also qspi partitions ?  If we shall see both - how can we know which is who ?

I also assume that on trying to boot from qspi, I can just change in the config from sd to qspi in CONFIG_SYS_EXTRA_OPTIONS and build u-boot, Right ?

Thank you very much.

Ran

0 Kudos
Reply