Hi,
We just added TARGET_CPU_VARIANT:= generic in device /linaro/iMX53/BoardConfig.mk file.
Then we got error saying no uboot diectory, as of now uboot was not required as we already have uboot image for imx53.
So commented below line in "device/linaro/common/tasks/kernel.mk" file
#BOOTLOADER_DEP := $(PRODUCT_OUT)/u-boot.bin
So JellyBean 4.3 code got compiled successfully for imx53 with no other errors,
But Out target(out/target/product/imx53) directory doesn't contain
"userdata.tar.bz2 ,system.tar.bz2, boot.tar.bz2 " any of these tarball .
Command used for compilation:
make -j4 TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro/bin/arm-linux-androideabi- TARGET_PRODUCT=iMX53 systemtarball userdatatarball boottarball
Regards,
Sowmya
-----Original Message-----
From: Bernhard Rosenkränzer <bernhard.rosenkranzer@linaro.org>
To: sowmya.ls@calsoftlabs.com
Cc: linaro-android <linaro-android@lists.linaro.org>
Subject: Re: Jelly Bean Compilation error for imx53
Date: Mon, 5 Aug 2013 23:32:04 +0200
On 5 August 2013 07:56, sowmya <sowmya.ls@calsoftlabs.com> wrote:
While trying to compile linaro4.3 SDK for imx53QSB using below command,throws an error :
command:
bionic/libc/Android.mk:425: TARGET_CPU_VARIANT is not defined
bionic/libc/arch-arm/arm.mk:32: *** "TARGET_CPU_VARIANT not set or set to an unknown value. Possible values are cortex-a9, cortex-a15, krait. Use generic for devices that do not have a CPU similar to any of the supported cpu variants.". Stop.
I've just committed a (completely untested) fix for this.
http://review.android.git.linaro.org/#/c/4342/
Later added TARGET_CPU_VARIANT variable as cortex-a8 in in device/linaro/iMX53/BoardConfig.mk file.
But cortex-a8 folder is not there in "bionic/libc/arch-arm/ " path.
There is no support for cortex-a8 in 4.3 (no current device uses A8 anymore), and 4.2 didn't have CPU specific optimization bits. So the correct variant for cortex-a8 in 4.3 (unless you want to go an extra step and push optimized functions for A8) is "generic".
I've pushed a patch that should fix this, but it is completely untested, while it should fix this problem, you might run into another one. If you want to be on the safe side, try building the 4.2 branch (that has been done successfully before - nobody else has tried building 4.3 for imx53 before).
ttyl
bero