On Monday 01 December 2014 16:32:21 Shawn Guo wrote:
> Is it a valid or supported use case to build LSK 3.14 kernel with
> android-toolchain? I can build a LSK 3.14 kernel with Linux toolchain
> gcc-linaro-arm-none-eabi-4.9-2014.09, which boots fine on my board.
> When I build the same kernel with
> android-toolchain-eabi-4.9-2014.09-x86, the kernel can be built out
> successfully, but it fails to boot on the board at very early stage
> with only uncompressing message shown up like below.
>
> Uncompressing Linux... done, booting the kernel.
>
> And it's not a LSK 3.14 specific problem, I tried to build mainline
> 3.10, 3.14 and 3.18-rc4 with the android-toolchain, and they all
> failed to boot.
>
> I need some help to understand if it's a valid use case at all, before
> I try to looking into the problem.
I would expect it to work, it's probably a good idea to find out
why it doesn't. For all I know 'arm-none-eabi' is actually /not/
supported for building the kernel, since that doesn't use the Linux
Linux variant of eabi, while 'arm-*-linux-gnueabi' or
'arm-*-linux-gnueabihf' is the default for Linux these days and
'arm-*-linux-android' should be compatible with that. What is the
exact target triplet you use in those two cases?
A few things you could try:
- boot it in qemu using the vexpress or virt platform code, see if
the symptom is the same. If it is, attach gdb to the qemu gdbstub
to look at the contents of the _log_buf.
- Maybe debug_ll crashes, try disabling that
- Maybe debug_ll is disabled already, try enabling it to see if you
get more output.
Arnd
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
