EABI broken on arm926t?

View: New views
3 Messages — Rating Filter:   Alert me  

EABI broken on arm926t?

by Hai Zaar-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Good day!
I'm building two weeks old buildroot snapshot for AT91SAM9260 board.

All I do it:
make at91sam9260dfc_defconfig
make menuconfig (select arm926t, EABI and remove games, etc...)
make

Results:
All kernels from 2.6.25 and later finish boot like this:
   VFS: Mounted root (ext2 filesystem).
   Freeing init memory: 128K
   Kernel panic - not syncing: Attempted to kill init!

The only kernel that worked is 2.6.24. After checking the kernel
config, I've found out that CONFIG_AEABI was not set (in spite of EABI
being selected in buildroot's config). Disabling EABI on later
kernels, (or enabling CONFIG_OABI_COMPAT) made them (almost)work.

Currently the situation is as follows:

EABI kernel + EABI rootfs = kernel panic (busibox's linuxrc dies)
EABI kernel + OABI rootfs = kernel panic (busibox's linuxrc dies)
OABI kernel + EABI rootfs = works, but some things like ping and nfs
return 'Illegal instruction'
EABI+OABI_COMPAT kernel + EABI rootfs = works, but some things like
ping and nfs return 'Illegal instruction'
EABI+OABI_COMPAT kernel + OABI rootfs = work correctly
OABI kernel + OABI rootfs = works correctly

1. Is EABI support broken for this platform in buildroot?
2. How can further investigate this issue?

--
Zaar
_______________________________________________
buildroot mailing list
buildroot@...
http://busybox.net/mailman/listinfo/buildroot

Re: EABI broken on arm926t?

by kelvincheung :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have the same problem.
My buildroot version is: buildroot-2009.02
Any one know the solution?

Thanks!

Hai Zaar-2 wrote:
Good day!
I'm building two weeks old buildroot snapshot for AT91SAM9260 board.

All I do it:
make at91sam9260dfc_defconfig
make menuconfig (select arm926t, EABI and remove games, etc...)
make

Results:
All kernels from 2.6.25 and later finish boot like this:
   VFS: Mounted root (ext2 filesystem).
   Freeing init memory: 128K
   Kernel panic - not syncing: Attempted to kill init!

The only kernel that worked is 2.6.24. After checking the kernel
config, I've found out that CONFIG_AEABI was not set (in spite of EABI
being selected in buildroot's config). Disabling EABI on later
kernels, (or enabling CONFIG_OABI_COMPAT) made them (almost)work.

Currently the situation is as follows:

EABI kernel + EABI rootfs = kernel panic (busibox's linuxrc dies)
EABI kernel + OABI rootfs = kernel panic (busibox's linuxrc dies)
OABI kernel + EABI rootfs = works, but some things like ping and nfs
return 'Illegal instruction'
EABI+OABI_COMPAT kernel + EABI rootfs = works, but some things like
ping and nfs return 'Illegal instruction'
EABI+OABI_COMPAT kernel + OABI rootfs = work correctly
OABI kernel + OABI rootfs = works correctly

1. Is EABI support broken for this platform in buildroot?
2. How can further investigate this issue?

--
Zaar
_______________________________________________
buildroot mailing list
buildroot@uclibc.org
http://busybox.net/mailman/listinfo/buildroot

Re: EABI broken on arm926t?

by kelvincheung :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I fond the sulotion:
http://lists.uclibc.org/pipermail/buildroot/2007-June/003189.html

To use EABI for ARM920T in the buildroot, two options are needed to the main buildroot config:
BR2_EXTRA_BINUTILS_CONFIG_OPTIONS="--with-arch=armv4t"
BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-arch=armv4t"
or
BR2_EXTRA_BINUTILS_CONFIG_OPTIONS="--with-cpu=arm920t"
BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-cpu=arm920t"


I have the same problem.
My buildroot version is: buildroot-2009.02
Any one know the solution?

Thanks!

Hai Zaar-2 wrote:
Good day!
I'm building two weeks old buildroot snapshot for AT91SAM9260 board.

All I do it:
make at91sam9260dfc_defconfig
make menuconfig (select arm926t, EABI and remove games, etc...)
make

Results:
All kernels from 2.6.25 and later finish boot like this:
   VFS: Mounted root (ext2 filesystem).
   Freeing init memory: 128K
   Kernel panic - not syncing: Attempted to kill init!

The only kernel that worked is 2.6.24. After checking the kernel
config, I've found out that CONFIG_AEABI was not set (in spite of EABI
being selected in buildroot's config). Disabling EABI on later
kernels, (or enabling CONFIG_OABI_COMPAT) made them (almost)work.

Currently the situation is as follows:

EABI kernel + EABI rootfs = kernel panic (busibox's linuxrc dies)
EABI kernel + OABI rootfs = kernel panic (busibox's linuxrc dies)
OABI kernel + EABI rootfs = works, but some things like ping and nfs
return 'Illegal instruction'
EABI+OABI_COMPAT kernel + EABI rootfs = works, but some things like
ping and nfs return 'Illegal instruction'
EABI+OABI_COMPAT kernel + OABI rootfs = work correctly
OABI kernel + OABI rootfs = works correctly

1. Is EABI support broken for this platform in buildroot?
2. How can further investigate this issue?

--
Zaar
_______________________________________________
buildroot mailing list
buildroot@uclibc.org
http://busybox.net/mailman/listinfo/buildroot