Hikey board, ARM 32/64 debian toolchain on ubuntu 16.04

[Anand Gudimanchi]

Dear Experts

We have hikey boards and we building the ARM 64 and 32 debian toolchain on ububtu 16.0.4 pc. Please can you help me if I can get help getting the relevant toolchain to build the same.

 

Thank you in advance

Protocoder

[Igor]

43 minutes ago, Anand Gudimanchi said:

Dear Experts

 We have hikey boards and we building the ARM 64 and 32 debian toolchain on ububtu 16.0.4 pc. Please can you help me if I can get help getting the relevant toolchain to build the same.

 

Our build system downloads most used compilers but to tell you which exactly is appropriate for Hikey board u-boot/kernel sources ... no idea. You can try to play around this way:
1. Define a board config https://github.com/armbian/build/tree/development/config/boards

2. Define a source config https://github.com/armbian/build/tree/development/config/sources

 

Check this example for RK3328 ... https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L32-L43

default branch, kernel 4.4.y need to have a version higher or equal than 6.3  KERNEL_USE_GCC='> 6.3'  while kernel dev branch 4.17.y needs KERNEL_USE_GCC='> 7.0' ... u-boot and atf have their own settings. We know that This board is aarch64 (https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L1) and this way systems knows which compiler to choose. 

Sometimes trial and error is the fastest way.  We use those:

Spoiler

# download external Linaro compiler and missing special dependencies since they are needed for certain sources
	local toolchains=(
		"https://dl.armbian.com/_toolchains/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabi.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-6.4.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz"
		"https://dl.armbian.com/_toolchains/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz"
		)

	for toolchain in ${toolchains[@]}; do
		download_toolchain "$toolchain"
	done

 

I hope you will find those hints useful.

[Anand Gudimanchi]

Thank you Igor

I will give it a try, the requirement is to create Image with least minimum packages only meant for gcc, gdb, glibc and binutils.

 

Thanks a lot

[Igor]

29 minutes ago, Anand Gudimanchi said:

Thank you Igor

I will give it a try, the requirement is to create Image with least minimum packages only meant for gcc, gdb, glibc and binutils.

 

Thanks a lot

 

You have to boot the board first. Usually, it's not just kernel and u-boot, but up to few other (pre)loaders. Packages optimization is a fairly simple task. If our default package base is a too much, use PACKAGE_LIST_RM parameter when building an image to remove what you might not need.
https://github.com/armbian/build/blob/development/lib/configuration.sh#L219-L222