Hi,

 

I'm looking for the simplest way to provide a custom uboot configuration to the Armbian build system.

 

I have read (I think I did not miss something obvious) the documentation pages how to customize Armbian build, but the doc is mostly focused on specifying alternate source version or applying custom patches, while I only need a way to specify an already existing uboot config (generated with make menuconfig from the existing, installed Armbian sources).

 

What would be the best way to tell Armbian to use an alternate uboot configuration?

 

Thanks,

Emmanuel.

 

Did you try the same way as for kernel?

Hi Igor,]

 

You mean something like https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-kernel-config ?

 

No, I'm not even sure to understand how to name the files for uboot, nor where to look to get this info :-(

6 hours ago, eblot said:

You mean something like https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-kernel-config ?

 

No, I'm not even sure to understand how to name the files for uboot, nor where to look to get this info :-(

Yes.

 

What do you want to achieve with this?

 

10 hours ago, eblot said:

I only need a way to specify an already existing uboot config

You add changes to the basic config with a patch. Like this one:
https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/add-a20-optional-eMMC.patch
 

> What do you want to achieve with this?

 

I want the most minimalistic uboot bianry to boot from SPI flash, then boot from bootp/tftp and save the environment in the SPI flash.

For now, uboot takes many seconds to enumerate the (for me useless) USB EHCIs, and I cannot save the u-boot environment to the SPI dataflash, so the OrangePiZero device cannot boot w/o MMC or command sent to the serial port.

 

> You add changes to the basic config with a patch.

Ok. It is only possible through a patch.

It seems need to skim all the MMC/USB/... off the default config, and add the SPI write feature for the u-boot environment. 

The patch should be generated against the .config file that can be found in the u-boot source directory after an initial build, shouldn't it?

 

Thanks for your help,

Emmanuel.

I still fail to find how I should name the patch and where I should store it:

  * userpatches/linux-$KERNELFAMILY-$KERNELBRANCH.config is for kernel

  * userpatches/sources/$LINUXFAMILY.conf with LINUXFAMILY=sunxi does not seem to address uboot

 

Should I use your example (build/patch/u-boot/u-boot-sunxi/add-a20-optional-eMMC.patch) and replace build/patch with build/userpatches, e.g. build/userpatches/u-boot/u-boot-sunxi/my-custom-conf.patch? Sorry, I'm still confused about how to address u-boot config from https://docs.armbian.com/Developer-Guide_User-Configurations/.

 

Thanks.