[Xenomai-help] at91sam9263 and user-space support compile fails

[Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

Hello,

im trying to compile the user-space with following instructions:

cd xenobuild
../xenomai-2.4.3/configure --build=i686-pc-linux-gnu --host=arm-elf --enable-arm-mach=at91sam926x
make

Here is the output that make generate:
_____________________________________________________________________________
Making all in src
make[1]: Entering directory `/home/paradoxxa/xenobuild/src'
Making all in include
make[2]: Entering directory `/home/paradoxxa/xenobuild/src/include'
make  all-am
make[3]: Entering directory `/home/paradoxxa/xenobuild/src/include'
make[3]: Für das Ziel »all-am« ist nichts zu tun.
make[3]: Leaving directory `/home/paradoxxa/xenobuild/src/include'
make[2]: Leaving directory `/home/paradoxxa/xenobuild/src/include'
Making all in rtdk
make[2]: Entering directory `/home/paradoxxa/xenobuild/src/rtdk'
/bin/sh ../../libtool --tag=CC   --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../../src/include -I../../../xenomai-2.4.3/src/rtdk  -O2 -D_GNU_SOURCE -D_REENTRANT -Wall -pipe -march=armv5 -D__XENO__ -D__IN_XENO__ -Wstrict-prototypes -I../../../xenomai-2.4.3/include    -MT librtdk_la-rt_print.lo -MD -MP -MF .deps/librtdk_la-rt_print.Tpo -c -o librtdk_la-rt_print.lo `test -f 'rt_print.c' || echo '../../../xenomai-2.4.3/src/rtdk/'`rt_print.c
 arm-elf-gcc -DHAVE_CONFIG_H -I. -I../../src/include -I../../../xenomai-2.4.3/src/rtdk -O2 -D_GNU_SOURCE -D_REENTRANT -Wall -pipe -march=armv5 -D__XENO__ -D__IN_XENO__ -Wstrict-prototypes -I../../../xenomai-2.4.3/include -MT librtdk_la-rt_print.lo -MD -MP -MF .deps/librtdk_la-rt_print.Tpo -c ../../../xenomai-2.4.3/src/rtdk/rt_print.c -o librtdk_la-rt_print.o
In file included from ../../src/include/asm/xenomai/system.h:134,
                 from ../../../xenomai-2.4.3/src/rtdk/rt_print.c:30:
../../../xenomai-2.4.3/include/nucleus/system.h:23:20: error: memory.h: No such file or directory
../../../xenomai-2.4.3/include/nucleus/system.h:25:23: error: asm/param.h: No such file or directory
In file included from ../../src/include/asm/xenomai/atomic.h:77,
                 from ../../../xenomai-2.4.3/include/nucleus/system.h:26,
                 from ../../src/include/asm/xenomai/system.h:134,
                 from ../../../xenomai-2.4.3/src/rtdk/rt_print.c:30:
../../src/include/asm/xenomai/syscall.h:229:22: error: sys/mman.h: No such file or directory
In file included from ../../../xenomai-2.4.3/src/rtdk/rt_print.c:30:
../../src/include/asm/xenomai/system.h:135:28: error: bits/local_lim.h: No such file or directory
../../../xenomai-2.4.3/src/rtdk/rt_print.c:68: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__buffer_lock'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:69: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__buffer_key'
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'rt_vfprintf':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:78: warning: implicit declaration of function 'pthread_getspecific'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:78: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:78: error: (Each undeclared identifier is reported only once
../../../xenomai-2.4.3/src/rtdk/rt_print.c:78: error: for each function it appears in.)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:78: warning: initialization makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c:95: warning: assignment makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'set_buffer_name':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:206: warning: implicit declaration of function 'pthread_self'
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'rt_print_init':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:216: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:216: warning: initialization makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c:253: warning: implicit declaration of function 'pthread_mutex_lock'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:253: error: '__buffer_lock' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:260: warning: implicit declaration of function 'pthread_mutex_unlock'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:262: warning: implicit declaration of function 'pthread_setspecific'
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'rt_print_cleanup':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:274: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:274: warning: passing argument 1 of 'cleanup_buffer' makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'rt_print_buffer_name':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:279: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:279: warning: initialization makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c:290: warning: assignment makes pointer from integer without a cast
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'cleanup_buffer':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:303: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:305: error: '__buffer_lock' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function 'printer_thread':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:387: warning: implicit declaration of function 'nanosleep'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:389: error: '__buffer_lock' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c: In function '__rt_print_init':
../../../xenomai-2.4.3/src/rtdk/rt_print.c:399: error: 'pthread_t' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:399: error: expected ';' before 'thread'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:400: error: 'pthread_attr_t' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:400: error: expected ';' before 'thattr'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:432: warning: implicit declaration of function 'pthread_mutex_init'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:432: error: '__buffer_lock' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:433: warning: implicit declaration of function 'pthread_key_create'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:433: error: '__buffer_key' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:435: warning: implicit declaration of function 'pthread_attr_init'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:435: error: 'thattr' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:436: warning: implicit declaration of function 'pthread_attr_setstacksize'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:436: error: 'PTHREAD_STACK_MIN' undeclared (first use in this function)
../../../xenomai-2.4.3/src/rtdk/rt_print.c:437: warning: implicit declaration of function 'pthread_create'
../../../xenomai-2.4.3/src/rtdk/rt_print.c:437: error: 'thread' undeclared (first use in this function)
make[2]: *** [librtdk_la-rt_print.lo] Fehler 1
make[2]: Leaving directory `/home/paradoxxa/xenobuild/src/rtdk'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/paradoxxa/xenobuild/src'
make: *** [all-recursive] Fehler 1
_____________________________________________________________________________

It says me that the files memory.h and asm/param.h couldn't be found. 
Im wondering why? I also tried it like the example in the README.INSTALL 2.6 Building for ARM
but with the same result. Do anyone know how to fix this?

Regards,
Thomas





_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Thu, May 15, 2008 at 10:36 AM,  <Paradoxxa2001@domain.hid> wrote:
> It says me that the files memory.h and asm/param.h couldn't be found.
> Im wondering why? I also tried it like the example in the README.INSTALL 2.6 Building for ARM
> but with the same result. Do anyone know how to fix this?

It looks like a toolchain issue. Are you sure your toolchain is
properly installed ? Is there a memory.h or sys/mman.h in the
toolchain include dir ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Thu, May 15, 2008 at 11:21 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Thu, May 15, 2008 at 10:36 AM,  <Paradoxxa2001@domain.hid> wrote:
>> It says me that the files memory.h and asm/param.h couldn't be found.
>> Im wondering why? I also tried it like the example in the README.INSTALL 2.6 Building for ARM
>> but with the same result. Do anyone know how to fix this?
>
> It looks like a toolchain issue. Are you sure your toolchain is
> properly installed ? Is there a memory.h or sys/mman.h in the
> toolchain include dir ?

I routinely compile Xenomai with the two following toolchains for ARM:
- Snapgear 2005 toolchain:
http://ftp.snapgear.org/pub/snapgear/tools/arm-linux/arm-linux-tools-20051123.tar.gz
- CodeSourcery 2007q3 toolchain (no longer available, the current
toolchain is 2008q1):
http://www.codesourcery.com/gnu_toolchains/arm/download.html

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

With the CodeSourcery 2007q3 toolchain it works.
Thanks a lot!

Thomas

-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 15.05.08 11:48:43
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Thu, May 15, 2008 at 11:21 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Thu, May 15, 2008 at 10:36 AM,  <Paradoxxa2001@domain.hid> wrote:
>> It says me that the files memory.h and asm/param.h couldn't be found.
>> Im wondering why? I also tried it like the example in the README.INSTALL 2.6 Building for ARM
>> but with the same result. Do anyone know how to fix this?
>
> It looks like a toolchain issue. Are you sure your toolchain is
> properly installed ? Is there a memory.h or sys/mman.h in the
> toolchain include dir ?

I routinely compile Xenomai with the two following toolchains for ARM:
- Snapgear 2005 toolchain:
http://ftp.snapgear.org/pub/snapgear/tools/arm-linux/arm-linux-tools-20051123.tar.gz
- CodeSourcery 2007q3 toolchain (no longer available, the current
toolchain is 2008q1):
http://www.codesourcery.com/gnu_toolchains/arm/download.html

-- 
 Gilles

_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help



_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

Hi,

actual i working with the CodeSourcery 2008q1 toolchain. When im building the 
user-space support it seem to work fine. Then im also compiled the kernel with this
toolchain. The Image file which i get is about 4,7MB big. My System provide just 
less then 4MB space for the Kernel Image. With my first compiler i got kernel images
with the size of 1,6MB. I also checked the Optimization Level, but that isn't the cause.
What do you think about that?

Thomas

-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 15.05.08 11:48:43
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Thu, May 15, 2008 at 11:21 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Thu, May 15, 2008 at 10:36 AM,  <Paradoxxa2001@domain.hid> wrote:
>> It says me that the files memory.h and asm/param.h couldn't be found.
>> Im wondering why? I also tried it like the example in the README.INSTALL 2.6 Building for ARM
>> but with the same result. Do anyone know how to fix this?
>
> It looks like a toolchain issue. Are you sure your toolchain is
> properly installed ? Is there a memory.h or sys/mman.h in the
> toolchain include dir ?

I routinely compile Xenomai with the two following toolchains for ARM:
- Snapgear 2005 toolchain:
http://ftp.snapgear.org/pub/snapgear/tools/arm-linux/arm-linux-tools-20051123.tar.gz
- CodeSourcery 2007q3 toolchain (no longer available, the current
toolchain is 2008q1):
http://www.codesourcery.com/gnu_toolchains/arm/download.html

-- 
 Gilles

_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help



_______________________________________________________________________
EINE FÜR ALLE: die kostenlose WEB.DE-Plattform für Freunde und Deine
Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/?kid=kid@domain.hid

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 10:15 AM,  <Paradoxxa2001@domain.hid> wrote:
> Hi,
>
> actual i working with the CodeSourcery 2008q1 toolchain. When im building the
> user-space support it seem to work fine. Then im also compiled the kernel with this
> toolchain. The Image file which i get is about 4,7MB big. My System provide just
> less then 4MB space for the Kernel Image. With my first compiler i got kernel images
> with the size of 1,6MB. I also checked the Optimization Level, but that isn't the cause.
> What do you think about that?

This is a known issue. Use a more recent kernel, or patch the arch
Makefile as indicated here:
http://lists.arm.linux.org.uk/lurker/message/20080508.101225.d54f8f71.en.html

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

I checked the linux-2.6.24/arch/arm/Makefile file.
OBJCOPYFLAGS is like these in the referenced Patch.

Thomas

-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 10:45:01
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 10:15 AM,  <Paradoxxa2001@domain.hid> wrote:
> Hi,
>
> actual i working with the CodeSourcery 2008q1 toolchain. When im building the
> user-space support it seem to work fine. Then im also compiled the kernel with this
> toolchain. The Image file which i get is about 4,7MB big. My System provide just
> less then 4MB space for the Kernel Image. With my first compiler i got kernel images
> with the size of 1,6MB. I also checked the Optimization Level, but that isn't the cause.
> What do you think about that?

This is a known issue. Use a more recent kernel, or patch the arch
Makefile as indicated here:
http://lists.arm.linux.org.uk/lurker/message/20080508.101225.d54f8f71.en.html

-- 
 Gilles



_____________________________________________________________________
Unbegrenzter Speicherplatz für Ihr E-Mail Postfach? Jetzt aktivieren!
http://freemail.web.de/club/landingpage.htm/?mc=025555

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 11:10 AM,  <Paradoxxa2001@domain.hid> wrote:
> I checked the linux-2.6.24/arch/arm/Makefile file.
> OBJCOPYFLAGS is like these in the referenced Patch.

How large is vmlinux ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

-rwxr-xr-x 1 paradoxxa paradoxxa 35M 16. Mai 11:20 vmlinux


-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 11:19:09
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 11:10 AM,  <Paradoxxa2001@domain.hid> wrote:
> I checked the linux-2.6.24/arch/arm/Makefile file.
> OBJCOPYFLAGS is like these in the referenced Patch.

How large is vmlinux ?

-- 
 Gilles



_______________________________________________________________
Schon gehört? Der neue WEB.DE MultiMessenger kann`s mit allen: 
http://www.produkte.web.de/messenger/?did=3016

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 11:24 AM,  <Paradoxxa2001@domain.hid> wrote:
>
> -rwxr-xr-x 1 paradoxxa paradoxxa 35M 16. Mai 11:20 vmlinux

You have a problem, my vmlinux is 4MB large. Could you run
readelf --sections vmlinux
?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

Sure,
the Output of "readelf --sections vmlinux" is:

--------------------------------------------------------------------------------------
There are 29 section headers, starting at offset 0x2132b94:

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
  [ 0]                   NULL            00000000 000000 000000 00      0   0  0
  [ 1] .note.gnu.build-i NOTE            00000000 008000 000024 00   A  0   0  4
  [ 2] .text.head        PROGBITS        c0008000 010000 000240 00  AX  0   0 32
  [ 3] .init             PROGBITS        c0008240 010240 019dc0 00 WAX  0   0 32
  [ 4] .text             PROGBITS        c0022000 02a000 307cb8 00  AX  0   0 1024
  [ 5] __ksymtab         PROGBITS        c032a000 332000 005548 00   A  0   0  4
  [ 6] __ksymtab_gpl     PROGBITS        c032f548 337548 0016a0 00   A  0   0  4
  [ 7] __ksymtab_gpl_fut PROGBITS        c0330be8 338be8 000018 00   A  0   0  4
  [ 8] __kcrctab         PROGBITS        c0330c00 338c00 002aa4 00   A  0   0  4
  [ 9] __kcrctab_gpl     PROGBITS        c03336a4 33b6a4 000b50 00   A  0   0  4
  [10] __kcrctab_gpl_fut PROGBITS        c03341f4 33c1f4 00000c 00   A  0   0  4
  [11] __ksymtab_strings PROGBITS        c0334200 33c200 00e968 00   A  0   0  1
  [12] __param           PROGBITS        c0342b68 34ab68 0006b8 00   A  0   0  4
  [13] .data             PROGBITS        c0344000 34c000 022658 00  WA  0   0 32
  [14] .bss              NOBITS          c0366660 36e658 03ed40 00  WA  0   0 32
  [15] .comment          PROGBITS        00000000 36e658 007b4a 00      0   0  1
  [16] .ARM.attributes   ARM_ATTRIBUTES  00000000 3761a2 000027 00      0   0  1
  [17] .debug_line       PROGBITS        00000000 3761c9 175a4c 00      0   0  1
  [18] .debug_info       PROGBITS        00000000 4ebc15 1753949 00      0   0  1
  [19] .debug_abbrev     PROGBITS        00000000 1c3f55e 0ca742 00      0   0  1
  [20] .debug_aranges    PROGBITS        00000000 1d09ca0 0072b0 00      0   0  8
  [21] .debug_pubnames   PROGBITS        00000000 1d10f50 024da2 00      0   0  1
  [22] .debug_str        PROGBITS        00000000 1d35cf2 0cc8d1 01  MS  0   0  1
  [23] .debug_frame      PROGBITS        00000000 1e025c4 06c354 00      0   0  4
  [24] .debug_loc        PROGBITS        00000000 1e6e918 24e506 00      0   0  1
  [25] .debug_ranges     PROGBITS        00000000 20bce20 075c20 00      0   0  8
  [26] .shstrtab         STRTAB          00000000 2132a40 000153 00      0   0  1
  [27] .symtab           SYMTAB          00000000 213301c 0b87a0 10     28 36997  4
  [28] .strtab           STRTAB          00000000 21eb7bc 09dabd 00      0   0  1
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings)
  I (info), L (link order), G (group), x (unknown)
  O (extra OS processing required) o (OS specific), p (processor specific)
--------------------------------------------------------------------------------------


Thomas
-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 11:27:41
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 11:24 AM,  <Paradoxxa2001@domain.hid> wrote:
>
> -rwxr-xr-x 1 paradoxxa paradoxxa 35M 16. Mai 11:20 vmlinux

You have a problem, my vmlinux is 4MB large. Could you run
readelf --sections vmlinux
?

-- 
 Gilles



______________________________________________________
Bis 50 MB Dateianhänge? Kein Problem!
http://freemail.web.de/club/landingpage.htm/?mc=025556

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 11:34 AM,  <Paradoxxa2001@domain.hid> wrote:
> Sure,
> the Output of "readelf --sections vmlinux" is:

vmlinux is large because of debug infos, your .text section is 3MB
large, which looks normal. Follow the various steps in making the
zImage to find what is wrong.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 11:45 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Fri, May 16, 2008 at 11:34 AM,  <Paradoxxa2001@domain.hid> wrote:
>> Sure,
>> the Output of "readelf --sections vmlinux" is:
>
> vmlinux is large because of debug infos, your .text section is 3MB
> large, which looks normal. Follow the various steps in making the
> zImage to find what is wrong.

The vmlinux that really matters is arch/arm/boot/compressed/vmlinux

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

I have found some debug flags.
Now the vmlinux is smaller but still to big

-rwxr-xr-x 1 paradoxxa paradoxxa 4,8M 16. Mai 12:36 vmlinux
-rwxr-xr-x 1 paradoxxa paradoxxa 1,7M 16. Mai 12:36 arch/arm/boot/compressed/vmlinux



-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 11:58:24
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails



The vmlinux that really matters is arch/arm/boot/compressed/vmlinux

-- 
 Gilles

_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help



_____________________________________________________________________
Unbegrenzter Speicherplatz für Ihr E-Mail Postfach? Jetzt aktivieren!
http://freemail.web.de/club/landingpage.htm/?mc=025555

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 1:07 PM,  <Paradoxxa2001@domain.hid> wrote:
> I have found some debug flags.
> Now the vmlinux is smaller but still to big
>
> -rwxr-xr-x 1 paradoxxa paradoxxa 4,8M 16. Mai 12:36 vmlinux
> -rwxr-xr-x 1 paradoxxa paradoxxa 1,7M 16. Mai 12:36 arch/arm/boot/compressed/vmlinux

A 1.7M vmlinux is Ok. I do not understand what you mean.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

The manual of my starterkit says i should do this with the vmlinux:

arm-elf-objcopy -O binary -S vmImage vmlinux.bin
gzip -f9 vmlinux.bin
mkimage -A arm -O linux -T kernel -C gzip -a 0x20008000 -e 0x20008000 -n "Linux Kernel Image" -d vmlinux.bin.gz vmImage

When im take the ./arch/arm/boot/compressed/vmlinux it won't work.
If i take the ./vmlinux it is to big.




-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 14:18:30
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 1:07 PM,  <Paradoxxa2001@domain.hid> wrote:
> I have found some debug flags.
> Now the vmlinux is smaller but still to big
>
> -rwxr-xr-x 1 paradoxxa paradoxxa 4,8M 16. Mai 12:36 vmlinux
> -rwxr-xr-x 1 paradoxxa paradoxxa 1,7M 16. Mai 12:36 arch/arm/boot/compressed/vmlinux

A 1.7M vmlinux is Ok. I do not understand what you mean.

-- 
 Gilles



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 2:40 PM,  <Paradoxxa2001@domain.hid> wrote:
> The manual of my starterkit says i should do this with the vmlinux:
>
> arm-elf-objcopy -O binary -S vmImage vmlinux.bin

This step is the same as the one made by the Linux kernel Makefile.
So, of course, if you do not use the Linux kernel Makefiles, you
should use the same flags as the ones it uses.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

Finally i got it. Thanks a lot.
I flashed this Image to the target and booted it.
After the Message "Starting kernel" it seems like the system hung up.
Nothing more happens.

----------------------------------------------------------------
LCD init done, video memory at 0x70000000
In:    serial
Out:   serial
Err:   serial
AT91 Ethernet PHY: DP83848 (1)
operating at 100M full duplex mode
End of Autonegociation
MAC: 02:00:11:53:d0:85
Hit any key to stop autoboot:  0
## Booting image at 10050000 ...
   Image Name:   Xenomai Linux Kernel 
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1682870 Bytes =  1.6 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...
----------------------------------------------------------------

Thomas

_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 3:53 PM,  <Paradoxxa2001@domain.hid> wrote:
> Finally i got it. Thanks a lot.
> I flashed this Image to the target and booted it.
> After the Message "Starting kernel" it seems like the system hung up.
> Nothing more happens.

See first tip in the "Tips and tricks" section of the following page:
http://www.xenomai.org/index.php/I-pipe:ArmPorting

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 3:53 PM,  <Paradoxxa2001@domain.hid> wrote:
> Finally i got it. Thanks a lot.
> I flashed this Image to the target and booted it.
> After the Message "Starting kernel" it seems like the system hung up.
> Nothing more happens.
>
> ----------------------------------------------------------------
> LCD init done, video memory at 0x70000000
> In:    serial
> Out:   serial
> Err:   serial
> AT91 Ethernet PHY: DP83848 (1)
> operating at 100M full duplex mode
> End of Autonegociation
> MAC: 02:00:11:53:d0:85
> Hit any key to stop autoboot:  0
> ## Booting image at 10050000 ...
>   Image Name:   Xenomai Linux Kernel
>   Image Type:   ARM Linux Kernel Image (gzip compressed)
>   Data Size:    1682870 Bytes =  1.6 MB
>   Load Address: 20008000
>   Entry Point:  20008000
>   Verifying Checksum ... OK
>   Uncompressing Kernel Image ... OK
>
> Starting kernel ...

By the way, if your boot loader is uboot, the Linux kernel makefiles
have a uImage target which produces an image which u-boot can use.


-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

OK, i will include the printascii function.
Thank you for your patience. I appreciate you.

Thomas

-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 16:13:04
An: Paradoxxa2001@domain.hid
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 4:07 PM,  <Paradoxxa2001@domain.hid> wrote:
> Well, when im building it with the other Compiler which comes
> with the Module (AT91SAM9263) the kernel starts and the system
> is coming up. With the Compiler which Gills suggested (CodeSourcery)
> it doesn't work. I don't think the ArmPorting guide helps me here.

The ArmPorting guide explains you how to proceed when your kernel does
not boot and does not display anything. It is the first tip in the
"Tips and tricks" section.

-- 
 Gilles



_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Fri, May 16, 2008 at 4:34 PM,  <Paradoxxa2001@domain.hid> wrote:
> OK, i will include the printascii function.
> Thank you for your patience. I appreciate you.

You are welcome. Have you tried "make uImage" ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa2001]

God Morning,

I tried "make uImage" already.
I got the messages like:

uncompressing kernel---
crc error
--System halted

I saw that the scripts uses zImage to make the uImage. And the uImage is built
from the arch/arm/boot/compressed/vmlinux. The difference what i saw is that no 
compression is used to build the uImage by the scripts.


The Kernel with the printascii Function begin to start. 
Here are the logs:
----------------------------------------------------------------------------------------------
Starting kernel ...

<5>Linux version 2.6.24-paradoxxa-pm9263 (support@domain.hid) (gcc version 4.2.3 (Sourcery G++ Lite 2
008q1-126)) #7 Mon May 19 08:01:12 CEST 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Ronetix PM9263/BB9263
<4>Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 16384
<7>  DMA zone: 128 pages used for memmap
<7>  DMA zone: 0 pages reserved
<7>  DMA zone: 16256 pages, LIFO batch:3
<7>  Normal zone: 0 pages used for memmap
<7>  Movable zone: 0 pages used for memmap
Clocks: CPU 199 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
<5>Kernel command line: root=/dev/mtdblock4 rootfstype=jffs2 fbcon=rotate:3 mtdparts=physmap-flash.0
:256k(u-boot)ro,64k(u-boot-env)ro,1408k(kernel),-(rootfs);nand:-(nand) ip=10.0.0.17:10.0.0.20:10.0.0
.20:255.255.255.0:PM9263:eth0:off
<6>AT91: 160 gpio irqs in 5 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
<6>I-pipe 1.9-01: pipeline enabled.
Console: colour dummy device 80x30
<6>console [tty0] enabled
<6>console [ttyS0] enabled
Linux version 2.6.24-paradoxxa-pm9263 (support@domain.hid) (gcc version 4.2.3 (Sourcery G++ Lite 2008
q1-126)) #7 Mon May 19 08:01:12 CEST 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Ronetix PM9263/BB9263
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 199 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: root=/dev/mtdblock4 rootfstype=jffs2 fbcon=rotate:3 mtdparts=physmap-flash.0:25
6k(u-boot)ro,64k(u-boot-env)ro,1408k(kernel),-(rootfs);nand:-(nand) ip=10.0.0.17:10.0.0.20:10.0.0.20
:255.255.255.0:PM9263:eth0:off
AT91: 160 gpio irqs in 5 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
I-pipe 1.9-01: pipeline enabled.
Console: colour dummy device 80x30
console [tty0] enabled
console [ttyS0] enabled
<6>Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>Memory:Memory: 64MB 64MB = 64MB total
 = 64MB total
<5>Memory: 61184KB available (3220K code, 388K data, 108K init)
Memory: 61184KB available (3220K code, 388K data, 108K init)
<7>Calibrating delay loop... 99.12 BogoMIPS (lpj=495616)
Mount-cache hash table entries: 512
Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: CPU: Testing write buffer coherency: ok
ok
<6>net_namespace: 64 bytes
net_namespace: 64 bytes
<6>NET: Registered protocol family 16
NET: Registered protocol family 16
<6>usbcore: registered new interface driver usbfs
usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
usbcore: registered new device driver usb
<6>NET: Registered protocol family 2
NET: Registered protocol family 2
<6>Time: at91_tc0 clocksource has been installed.
Time: at91_tc0 clocksource has been installed.
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
<6>TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP: Hash tables configured (established 2048 bind 2048)
TCP: Hash tables configured (established 2048 bind 2048)
<6>TCP reno registered
TCP reno registered
<4>NetWinder Floating Point Emulator V0.97 (double precision)
NetWinder Floating Point Emulator V0.97 (double precision)
<6>I-pipe: Domain Xenomai registered.
I-pipe: Domain Xenomai registered.
<6>Xenomai: hal/arm started.
Xenomai: hal/arm started.
<6>Xenomai: real-time nucleus v2.4.3 (Back to Shalla-Bal) loaded.
Xenomai: real-time nucleus v2.4.3 (Back to Shalla-Bal) loaded.
<6>Xenomai: starting native API services.
Xenomai: starting native API services.
<6>Xenomai: starting POSIX services.
Xenomai: starting POSIX services.
<6>Xenomai: starting RTDM services.
Xenomai: starting RTDM services.
<6>JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
io scheduler noop registered
<6>io scheduler anticipatory registered (default)
io scheduler anticipatory registered (default)
<6>atmel_lcdfb atmel_lcdfb.0: 4096KiB frame buffer at 70000000 (mapped at c5000000)
atmel_lcdfb atmel_lcdfb.0: 4096KiB frame buffer at 70000000 (mapped at c5000000)
Console: switching to colour frame buffer device 40x30
Console: switching to colour frame buffer device 40x30
<6>atmel_lcdfb atmel_lcdfb.0: fb0: Atmel LCDC at 0x00700000 (mapped at c4850000), irq 26
atmel_lcdfb atmel_lcdfb.0: fb0: Atmel LCDC at 0x00700000 (mapped at c4850000), irq 26
<6>atmel_usart.0: ttyS0 at MMIO 0xfeffee00 (irq = 1) is a ATMEL_SERIAL
atmel_usart.0: ttyS0 at MMIO 0xfeffee00 (irq = 1) is a ATMEL_SERIAL
<6>atmel_usart.1: ttyS1 at MMIO 0xfff8c000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfff8c000 (irq = 7) is a ATMEL_SERIAL
<6>MACB_mii_bus: probed
MACB_mii_bus: probed
<6>eth0: Atmel MACB at 0xfffbc000 irq 21 (02:00:11:53:d0:85)
eth0: Atmel MACB at 0xfffbc000 irq 21 (02:00:11:53:d0:85)
<6>eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
<6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
<6>ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
<5>physmap platform flash device: 04000000 at 10000000
physmap platform flash device: 04000000 at 10000000
<6>physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
<7>physmap-flash.0: Found an alias at 0x400000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x800000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0xc00000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x1000000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x1400000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x1800000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x1c00000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x2000000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x2400000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x2800000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x2c00000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x3000000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x3400000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x3800000 for the chip at 0x0
<7>physmap-flash.0: Found an alias at 0x3c00000 for the chip at 0x0
 Amd/Fujitsu Extended Query Table at 0x0040
 Amd/Fujitsu Extended Query Table at 0x0040
<5>number of CFI chips: 1
number of CFI chips: 1
<5>cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
<5>4 cmdlinepart partitions found on MTD device physmap-flash.0
4 cmdlinepart partitions found on MTD device physmap-flash.0
<5>Creating 4 MTD partitions on "physmap-flash.0":
Creating 4 MTD partitions on "physmap-flash.0":
<5>0x00000000-0x00040000 : "u-boot"
0x00000000-0x00040000 : "u-boot"
<5>0x00040000-0x00050000 : "u-boot-env"
0x00040000-0x00050000 : "u-boot-env"
<5>0x00050000-0x001b0000 : "kernel"
0x00050000-0x001b0000 : "kernel"
<5>0x001b0000-0x00400000 : "rootfs"
0x001b0000-0x00400000 : "rootfs"
<6>NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
<6>AT91 NAND: 8-bit, Software ECC
AT91 NAND: 8-bit, Software ECC
<6>Scanning device for bad blocks
Scanning device for bad blocks
<5>Creating 1 MTD partitions on "at91_nand":
Creating 1 MTD partitions on "at91_nand":
<5>0x00000000-0x10000000 : "nand"
0x00000000-0x10000000 : "nand"
<6>atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffa4000 (irq 14)
atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffa4000 (irq 14)
<6>mtd_dataflash spi0.0: AT45DB321x (4224 KBytes)
mtd_dataflash spi0.0: AT45DB321x (4224 KBytes)
<6>atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffa8000 (irq 15)
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffa8000 (irq 15)
<6>at91_cf: irqs det #62, io #56
at91_cf: irqs det #62, io #56
<7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
<6>at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: AT91 OHCI
<6>at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
<6>at91_ohci at91_ohci: irq 29, io mem 0x00a00000
at91_ohci at91_ohci: irq 29, io mem 0x00a00000
<6>usb usb1: configuration #1 chosen from 1 choice
usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: 2 ports detected
<6>mice: PS/2 mouse device common for all mice
mice: PS/2 mouse device common for all mice
<6>ads7846 spi1.0: touchscreen, irq 31
ads7846 spi1.0: touchscreen, irq 31
<6>input: ADS784x Touchscreen as /class/input/input0
input: ADS784x Touchscreen as /class/input/input0
<6>rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
<6>Driver for 1-wire Dallas network protocol.
Driver for 1-wire Dallas network protocol.
<6>pm926x_w1, gpio pin 95
pm926x_w1, gpio pin 95
<6>Registered led device: led0
Registered led device: led0
<6>Registered led device: led1
Registered led device: led1
<6>usbcore: registered new interface driver usbhid
usbcore: registered new interface driver usbhid
<6>drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
<6>Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
<6>ALSA sound/arm/at91-ac97.c:564: ALSA sound/arm/at91-ac97.c:564: AC97C regs = FFFA0000
AC97C regs = FFFA0000
<6>ALSA sound/arm/at91-ac97.c:565: ALSA sound/arm/at91-ac97.c:565: AC97C irq  = 18
AC97C irq  = 18
<4>ALSA sound/arm/at91-ac97.c:493: ALSA sound/arm/at91-ac97.c:493: at91-ac97: codec read timeout 1
at91-ac97: codec read timeout 1
<4>ALSA sound/arm/at91-ac97.c:493: <4>ALSA sound/arm/at91-ac97.c:493: at91-ac97: codec read timeout
1
at91-ac97: codec read timeout 1
<4>ALSA sound/arm/at91-ac97.c:493: <4>ALSA sound/arm/at91-ac97.c:493: at91-ac97: codec read timeout
1
at91-ac97: codec read timeout 1
<4>ALSA sound/arm/at91-ac97.c:493: <4>ALSA sound/arm/at91-ac97.c:493: at91-ac97: codec read timeout
1
at91-ac97: codec read timeout 1
<6>ASoC version 0.13.1
<6>ASoC version 0.13.1
<6>ALSA device list:
ALSA device list:
<6>  #0: Atmel AC97 Controller at 0xfffa0000, irq 18
  #0: Atmel AC97 Controller at 0xfffa0000, irq 18
<6>TCP cubic registered
TCP cubic registered
<6>NET: Registered protocol family 1
NET: Registered protocol family 1
<6>NET: Registered protocol family 17
NET: Registered protocol family 17
<6>RPC: Registered udp transport module.
RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
RPC: Registered tcp transport module.
<6>rtc-at91sam9 at91_rtt.0: setting system clock to 2008-05-19 08:15:34 UTC (1211184934)
rtc-at91sam9 at91_rtt.0: setting system clock to 2008-05-19 08:15:34 UTC (1211184934)
IP-Config: Complete:IP-Config: Complete:
      device=eth0
      device=eth0, addr=10.0.0.17, addr=10.0.0.17, mask=255.255.255.0, mask=255.255.255.0, gw=10.0.0
.20, gw=10.0.0.20,
     host=PM9263, domain=, nis-domain=(none),
     host=PM9263, domain=, nis-domain=(none),
     bootserver=10.0.0.20,
     bootserver=10.0.0.20, rootserver=10.0.0.20, rootserver=10.0.0.20, rootpath=, rootpath=

<1>Unable to handle kernel NULL pointer dereference at virtual address 00000001
Unable to handle kernel NULL pointer dereference at virtual address 00000001
<1>pgd = c0004000
pgd = c0004000
<1>[00000001] *pgd=00000000[00000001] *pgd=00000000

Internal error: Oops: 5 [#1]
Internal error: Oops: 5 [#1]
Modules linked in:Modules linked in:

CPU: 0    Not tainted  (2.6.24-paradoxxa-pm9263 #7)
CPU: 0    Not tainted  (2.6.24-paradoxxa-pm9263 #7)
PC is at name_to_dev_t+0x160/0x28c
PC is at name_to_dev_t+0x160/0x28c
LR is at name_to_dev_t+0x13c/0x28c
LR is at name_to_dev_t+0x13c/0x28c
pc : [<c0023810>]    lr : [<c00237ec>]    psr: 20000013
sp : c3c17f2c  ip : c3c17f2c  fp : c3c17f78
pc : [<c0023810>]    lr : [<c00237ec>]    psr: 20000013
sp : c3c17f2c  ip : c3c17f2c  fp : c3c17f78
r10: 00000000  r9 : 00000000  r8 : c3c16000
r10: 00000000  r9 : 00000000  r8 : c3c16000
r7 : 00000000  r6 : 00000000  r5 : c001d871  r4 : c3c17f30
r7 : 00000000  r6 : 00000000  r5 : c001d871  r4 : c3c17f30
r3 : 00000001  r2 : 00000001  r1 : 0000006d  r0 : 00001730
r3 : 00000001  r2 : 00000001  r1 : 0000006d  r0 : 00001730
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 0005317f  Table: 20004000  DAC: 00000017
Control: 0005317f  Table: 20004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc3c16258)
Process swapper (pid: 1, stack limit = 0xc3c16258)
Stack: (0xc3c17f2c to 0xc3c18000)
Stack: (0xc3c17f2c to 0xc3c18000)
7f20: 7f20:                                                       00000000 00000000 6264746d 6264746
d 6b636f6c 6b636f6c c3c10034 c3c10034 c3c17f48 c3c17f48

7f40: 7f40: c004b3fc c004b3fc c006185c c006185c 00000003 00000003 00000000 00000000 00000000 0000000
0 00000000 00000000 00000001 00000001 c001d86c c001d86c

7f60: 7f60: c001d85c c001d85c 00000000 00000000 c001c070 c001c070 c3c17f94 c3c17f94 c3c17f7c c3c17f7
c c0009328 c0009328 c00236c0 c00236c0 c3c17f88 c3c17f88

7f80: 7f80: c036a4e0 c036a4e0 00000000 00000000 c3c17ff4 c3c17ff4 c3c17f98 c3c17f98 c0008a98 c0008a9
8 c00092a4 c00092a4 00000000 00000000 00000000 00000000

7fa0: 7fa0: 00000000 00000000 c3c17fb0 c3c17fb0 c0024060 c0024060 c0037720 c0037720 00000000 0000000
0 00000000 00000000 c0008868 c0008868 c003ddbc c003ddbc

7fc0: 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000
0 00000000 00000000 00000000 00000000 00000000 00000000

7fe0: 7fe0: 00000000 00000000 00000000 00000000 00000000 00000000 c3c17ff8 c3c17ff8 c003ddbc c003ddb
c c0008878 c0008878 0f73fc8c 0f73fc8c 1f13ac4e 1f13ac4e

Backtrace: Backtrace:

[<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c) (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
 [<c0009328>] (prepare_namespace+0x94/0x16c)
(prepare_namespace+0x94/0x16c)
 r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c r5:c001d85c r4:c001d86c r4:c001d86c

[<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c) (prepare_namespace+0x0/0x16c) from [<c0008a9
8>] from [<c0008a98>] (kernel_init+0x230/0x290)
(kernel_init+0x230/0x290)
 r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0

[<c0008868>] [<c0008868>] (kernel_init+0x0/0x290) (kernel_init+0x0/0x290) from [<c003ddbc>] from [<c
003ddbc>] (do_exit+0x0/0x790)
(do_exit+0x0/0x790)
Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020 e51b2020 e51b2020 (e5d21000) (e5d2
1000)

<4>---[ end trace aae4ab6fc1a48acc ]---
---[ end trace aae4ab6fc1a48acc ]---
<0>Kernel panic - not syncing: Attempted to kill init!
Kernel panic - not syncing: Attempted to kill init!
<6>eth0: link up (100/Full)
eth0: link up (100/Full)


----------------------------------------------------------------------------------------------

Thomas


-----Ursprüngliche Nachricht-----
Von: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
Gesendet: 16.05.08 17:28:23
An: Paradoxxa2001@domain.hid
CC: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] at91sam9263 and user-space support compile fails

On Fri, May 16, 2008 at 4:34 PM,  <Paradoxxa2001@domain.hid> wrote:
> OK, i will include the printascii function.
> Thank you for your patience. I appreciate you.

You are welcome. Have you tried "make uImage" ?

-- 
 Gilles

_______________________________________________
Xenomai-help mailing list
Xenomai-help@domain.hid
https://mail.gna.org/listinfo/xenomai-help



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Mon, May 19, 2008 at 8:26 AM,  <Paradoxxa2001@domain.hid> wrote:
> God Morning,
>
> I tried "make uImage" already.
> I got the messages like:
>
> uncompressing kernel---
> crc error
> --System halted

Yes, uImage is compressed, but contains the decompression code, it is
not supposed to be decompressed by uboot. Maybe what you want is "make
Image".

> [<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c) (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
>  [<c0009328>] (prepare_namespace+0x94/0x16c)
> (prepare_namespace+0x94/0x16c)
>  r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c r5:c001d85c r4:c001d86c r4:c001d86c
>
> [<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c) (prepare_namespace+0x0/0x16c) from [<c0008a9
> 8>] from [<c0008a98>] (kernel_init+0x230/0x290)
> (kernel_init+0x230/0x290)
>  r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0
>
> [<c0008868>] [<c0008868>] (kernel_init+0x0/0x290) (kernel_init+0x0/0x290) from [<c003ddbc>] from [<c
> 003ddbc>] (do_exit+0x0/0x790)
> (do_exit+0x0/0x790)
> Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020 e51b2020 e51b2020 (e5d21000) (e5d2
> 1000)

This does not seem to be related to Xenomai or the compiler. Maybe you
selected a wrong kernel option ? Have you tried compiling with the
defconfig for your board ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 8:26 AM,  <Paradoxxa2001@domain.hid> wrote:
>   
>> God Morning,
>>
>> I tried "make uImage" already.
>> I got the messages like:
>>
>> uncompressing kernel---
>> crc error
>> --System halted
>>     
>
> Yes, uImage is compressed, but contains the decompression code, it is
> not supposed to be decompressed by uboot. Maybe what you want is "make
> Image".
>
>   
I will check this.
>> [<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c) (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
>>  [<c0009328>] (prepare_namespace+0x94/0x16c)
>> (prepare_namespace+0x94/0x16c)
>>  r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c r5:c001d85c r4:c001d86c r4:c001d86c
>>
>> [<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c) (prepare_namespace+0x0/0x16c) from [<c0008a9
>> 8>] from [<c0008a98>] (kernel_init+0x230/0x290)
>> (kernel_init+0x230/0x290)
>>  r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0
>>
>> [<c0008868>] [<c0008868>] (kernel_init+0x0/0x290) (kernel_init+0x0/0x290) from [<c003ddbc>] from [<c
>> 003ddbc>] (do_exit+0x0/0x790)
>> (do_exit+0x0/0x790)
>> Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020 e51b2020 e51b2020 (e5d21000) (e5d2
>> 1000)
>>     
>
> This does not seem to be related to Xenomai or the compiler. Maybe you
> selected a wrong kernel option ? Have you tried compiling with the
> defconfig for your board ?
>
>   

I used all the time the defconfig for my board. Without the ipipe patch 
the kernel works. If i use the vendor compiler and the ipipe patched
kernel i can boot it, too!

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Mon, May 19, 2008 at 1:20 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> On Mon, May 19, 2008 at 8:26 AM,  <Paradoxxa2001@domain.hid> wrote:
>>
>>>
>>> God Morning,
>>>
>>> I tried "make uImage" already.
>>> I got the messages like:
>>>
>>> uncompressing kernel---
>>> crc error
>>> --System halted
>>>
>>
>> Yes, uImage is compressed, but contains the decompression code, it is
>> not supposed to be decompressed by uboot. Maybe what you want is "make
>> Image".
>>
>>
>
> I will check this.
>>>
>>> [<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c)
>>> (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
>>>  [<c0009328>] (prepare_namespace+0x94/0x16c)
>>> (prepare_namespace+0x94/0x16c)
>>>  r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c r5:c001d85c
>>> r4:c001d86c r4:c001d86c
>>>
>>> [<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c)
>>> (prepare_namespace+0x0/0x16c) from [<c0008a9
>>> 8>] from [<c0008a98>] (kernel_init+0x230/0x290)
>>> (kernel_init+0x230/0x290)
>>>  r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0
>>>
>>> [<c0008868>] [<c0008868>] (kernel_init+0x0/0x290) (kernel_init+0x0/0x290)
>>> from [<c003ddbc>] from [<c
>>> 003ddbc>] (do_exit+0x0/0x790)
>>> (do_exit+0x0/0x790)
>>> Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020
>>> e51b2020 e51b2020 (e5d21000) (e5d2
>>> 1000)
>>>
>>
>> This does not seem to be related to Xenomai or the compiler. Maybe you
>> selected a wrong kernel option ? Have you tried compiling with the
>> defconfig for your board ?
>>
>>
>
> I used all the time the defconfig for my board. Without the ipipe patch the
> kernel works. If i use the vendor compiler and the ipipe patched
> kernel i can boot it, too!

No, you are not using the defconfig since you have CONFIG_DEBUG_INFO
enabled and it is not enabled in the defconfigs. So, you made at least
one change.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 1:20 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>   
>> Gilles Chanteperdrix schrieb:
>>     
>>> On Mon, May 19, 2008 at 8:26 AM,  <Paradoxxa2001@domain.hid> wrote:
>>>
>>>       
>>>> God Morning,
>>>>
>>>> I tried "make uImage" already.
>>>> I got the messages like:
>>>>
>>>> uncompressing kernel---
>>>> crc error
>>>> --System halted
>>>>
>>>>         
>>> Yes, uImage is compressed, but contains the decompression code, it is
>>> not supposed to be decompressed by uboot. Maybe what you want is "make
>>> Image".
>>>
>>>
>>>       
>> I will check this.
>>     
>>>> [<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c)
>>>> (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
>>>>  [<c0009328>] (prepare_namespace+0x94/0x16c)
>>>> (prepare_namespace+0x94/0x16c)
>>>>  r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c r5:c001d85c
>>>> r4:c001d86c r4:c001d86c
>>>>
>>>> [<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c)
>>>> (prepare_namespace+0x0/0x16c) from [<c0008a9
>>>> 8>] from [<c0008a98>] (kernel_init+0x230/0x290)
>>>> (kernel_init+0x230/0x290)
>>>>  r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0
>>>>
>>>> [<c0008868>] [<c0008868>] (kernel_init+0x0/0x290) (kernel_init+0x0/0x290)
>>>> from [<c003ddbc>] from [<c
>>>> 003ddbc>] (do_exit+0x0/0x790)
>>>> (do_exit+0x0/0x790)
>>>> Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020
>>>> e51b2020 e51b2020 (e5d21000) (e5d2
>>>> 1000)
>>>>
>>>>         
>>> This does not seem to be related to Xenomai or the compiler. Maybe you
>>> selected a wrong kernel option ? Have you tried compiling with the
>>> defconfig for your board ?
>>>
>>>
>>>       
>> I used all the time the defconfig for my board. Without the ipipe patch the
>> kernel works. If i use the vendor compiler and the ipipe patched
>> kernel i can boot it, too!
>>     
>
> No, you are not using the defconfig since you have CONFIG_DEBUG_INFO
> enabled and it is not enabled in the defconfigs. So, you made at least
> one change.
>
>   
Thats  all what i changed!  Without it, nothing happens.

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> On Mon, May 19, 2008 at 1:20 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>
>>>
>>> Gilles Chanteperdrix schrieb:
>>>
>>>>
>>>> On Mon, May 19, 2008 at 8:26 AM,  <Paradoxxa2001@domain.hid> wrote:
>>>>
>>>>
>>>>>
>>>>> God Morning,
>>>>>
>>>>> I tried "make uImage" already.
>>>>> I got the messages like:
>>>>>
>>>>> uncompressing kernel---
>>>>> crc error
>>>>> --System halted
>>>>>
>>>>>
>>>>
>>>> Yes, uImage is compressed, but contains the decompression code, it is
>>>> not supposed to be decompressed by uboot. Maybe what you want is "make
>>>> Image".
>>>>
>>>>
>>>>
>>>
>>> I will check this.
>>>
>>>>>
>>>>> [<c00236b0>] [<c00236b0>] (name_to_dev_t+0x0/0x28c)
>>>>> (name_to_dev_t+0x0/0x28c) from [<c0009328>] from
>>>>>  [<c0009328>] (prepare_namespace+0x94/0x16c)
>>>>> (prepare_namespace+0x94/0x16c)
>>>>>  r7:c001c070 r7:c001c070 r6:00000000 r6:00000000 r5:c001d85c
>>>>> r5:c001d85c
>>>>> r4:c001d86c r4:c001d86c
>>>>>
>>>>> [<c0009294>] [<c0009294>] (prepare_namespace+0x0/0x16c)
>>>>> (prepare_namespace+0x0/0x16c) from [<c0008a9
>>>>> 8>] from [<c0008a98>] (kernel_init+0x230/0x290)
>>>>> (kernel_init+0x230/0x290)
>>>>>  r5:00000000 r5:00000000 r4:c036a4e0 r4:c036a4e0
>>>>>
>>>>> [<c0008868>] [<c0008868>] (kernel_init+0x0/0x290)
>>>>> (kernel_init+0x0/0x290)
>>>>> from [<c003ddbc>] from [<c
>>>>> 003ddbc>] (do_exit+0x0/0x790)
>>>>> (do_exit+0x0/0x790)
>>>>> Code: Code: 20000220 20000220 e2833001 e2833001 e50b3020 e50b3020
>>>>> e51b2020 e51b2020 (e5d21000) (e5d2
>>>>> 1000)
>>>>>
>>>>>
>>>>
>>>> This does not seem to be related to Xenomai or the compiler. Maybe you
>>>> selected a wrong kernel option ? Have you tried compiling with the
>>>> defconfig for your board ?
>>>>
>>>>
>>>>
>>>
>>> I used all the time the defconfig for my board. Without the ipipe patch
>>> the
>>> kernel works. If i use the vendor compiler and the ipipe patched
>>> kernel i can boot it, too!
>>>
>>
>> No, you are not using the defconfig since you have CONFIG_DEBUG_INFO
>> enabled and it is not enabled in the defconfigs. So, you made at least
>> one change.
>>
>>
>
> Thats  all what i changed!  Without it, nothing happens.

No, you are talking about CONFIG_DEBUG_LL, I am talking about
CONFIG_DEBUG_INFO. These are two different options. So, this make at
least two options that you changed. Could you check if a kernel with
an unmodified defconfig boots ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>   
>
>
> No, you are talking about CONFIG_DEBUG_LL, I am talking about
> CONFIG_DEBUG_INFO. These are two different options. So, this make at
> least two options that you changed. Could you check if a kernel with
> an unmodified defconfig boots ?
>
>   
The CONFIG_DEBUG_INFO is already set in the defconfig. The 
CONFIG_DEBUG_LL i set manually.
As well I had to changed the  AT91 Master Clock Frequency.

Here are the logs of a unmodified defconfig boot:
----------------------------------------------------------------------------------------------------------
Starting kernel ...

Linux version 2.6.24-dienetho-pm9263 (support@domain.hid) (gcc version 
4.1.1) #1 Mon May 19 14:48:33
 CEST 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Ronetix PM9263/BB9263
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 199 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: root=/dev/mtdblock4 rootfstype=jffs2 fbcon=rotate:3 
mtdparts=physmap-flash.0:25
6k(u-boot)ro,64k(u-boot-env)ro,1408k(kernel),-(rootfs);nand:-(nand) 
ip=10.0.0.17:10.0.0.20:10.0.0.20
:255.255.255.0:PM9263:eth0:off
AT91: 160 gpio irqs in 5 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
I-pipe 1.9-01: pipeline enabled.
Console: colour dummy device 80x30
console [tty0] enabled
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Kernel panic - not syncing: AT91 clock rate incorrectly set.
Please recompile with IPIPE_AT91_MCK set to 99532800 Hz.

----------------------------------------------------------------------------------------------------------

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>
>>
>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>> least two options that you changed. Could you check if a kernel with
>> an unmodified defconfig boots ?
>>
>>
>
> The CONFIG_DEBUG_INFO is already set in the defconfig. The CONFIG_DEBUG_LL i
> set manually.
> As well I had to changed the  AT91 Master Clock Frequency.
>
> Here are the logs of a unmodified defconfig boot:

Ok. But this is a boot with your old compiler. Could you try a
defconfig build (with I-pipe AT91 master clock frequency modified)
with CodeSourcery compiler ?

If you can not get CodeSourcery compiler to compile correctly a Linux
kernel, I can send you the 2007q3 compiler, or you could try to
compile the kernel with your old compiler, and to compile user-space
with CodeSourcery compiler.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>   
>> Gilles Chanteperdrix schrieb:
>>     
>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>
>>>
>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>>> least two options that you changed. Could you check if a kernel with
>>> an unmodified defconfig boots ?
>>>
>>>
>>>       
>> The CONFIG_DEBUG_INFO is already set in the defconfig. The CONFIG_DEBUG_LL i
>> set manually.
>> As well I had to changed the  AT91 Master Clock Frequency.
>>
>> Here are the logs of a unmodified defconfig boot:
>>     
>
> Ok. But this is a boot with your old compiler. Could you try a
> defconfig build (with I-pipe AT91 master clock frequency modified)
> with CodeSourcery compiler ?
>   
The  output what i get is "Starting Kernel ..."! That was it.

> If you can not get CodeSourcery compiler to compile correctly a Linux
> kernel, I can send you the 2007q3 compiler, or you could try to
> compile the kernel with your old compiler, and to compile user-space
> with CodeSourcery compiler.
>   
I tried it with the both compiler. When i execute 
/usr/xenomai/bin/latency i get the message "sh: 
/usr/xenomai/bin/latency: not found"

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>   
>> Gilles Chanteperdrix schrieb:
>>     
>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>
>>>
>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>>> least two options that you changed. Could you check if a kernel with
>>> an unmodified defconfig boots ?
>>>
>>>
>>>       
>> The CONFIG_DEBUG_INFO is already set in the defconfig. The CONFIG_DEBUG_LL i
>> set manually.
>> As well I had to changed the  AT91 Master Clock Frequency.
>>
>> Here are the logs of a unmodified defconfig boot:
>>     
>
> Ok. But this is a boot with your old compiler. Could you try a
> defconfig build (with I-pipe AT91 master clock frequency modified)
> with CodeSourcery compiler ?
>   
> If you can not get CodeSourcery compiler to compile correctly a Linux
> kernel, I can send you the 2007q3 compiler, or you could try to
> compile the kernel with your old compiler, and to compile user-space
> with CodeSourcery compiler.
>   
By the way, how i can figure out if the binary or the compiler is a 
oabi/eabi file/compiler?

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>
>>>
>>> Gilles Chanteperdrix schrieb:
>>>
>>>>
>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>>
>>>>
>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>>>> least two options that you changed. Could you check if a kernel with
>>>> an unmodified defconfig boots ?
>>>>
>>>>
>>>>
>>>
>>> The CONFIG_DEBUG_INFO is already set in the defconfig. The
>>> CONFIG_DEBUG_LL i
>>> set manually.
>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>
>>> Here are the logs of a unmodified defconfig boot:
>>>
>>
>> Ok. But this is a boot with your old compiler. Could you try a
>> defconfig build (with I-pipe AT91 master clock frequency modified)
>> with CodeSourcery compiler ?
>>  If you can not get CodeSourcery compiler to compile correctly a Linux
>> kernel, I can send you the 2007q3 compiler, or you could try to
>> compile the kernel with your old compiler, and to compile user-space
>> with CodeSourcery compiler.
>>
>
> I tried it with the both compiler. When i execute /usr/xenomai/bin/latency i
> get the message "sh: /usr/xenomai/bin/latency: not found"

Have you tried running file, ldd, or readelf on the binary to see what
it is made of ?

>
>
> By the way, how i can figure out if the binary or the compiler is a
> oabi/eabi file/compiler?

codesourcery compiles for eabi by default. So, you have to enable eabi
in kernel configuration to be able to run binaries generated by
codesourcery compiler.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[paradoxxa]

Gilles Chanteperdrix schrieb:
> On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>   
>> Gilles Chanteperdrix schrieb:
>>     
>>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>
>>>       
>>>> Gilles Chanteperdrix schrieb:
>>>>
>>>>         
>>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>>>
>>>>>
>>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>>>>> least two options that you changed. Could you check if a kernel with
>>>>> an unmodified defconfig boots ?
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> The CONFIG_DEBUG_INFO is already set in the defconfig. The
>>>> CONFIG_DEBUG_LL i
>>>> set manually.
>>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>
>>>> Here are the logs of a unmodified defconfig boot:
>>>>
>>>>         
>>> Ok. But this is a boot with your old compiler. Could you try a
>>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>> with CodeSourcery compiler ?
>>>  If you can not get CodeSourcery compiler to compile correctly a Linux
>>> kernel, I can send you the 2007q3 compiler, or you could try to
>>> compile the kernel with your old compiler, and to compile user-space
>>> with CodeSourcery compiler.
>>>
>>>       
>> I tried it with the both compiler. When i execute /usr/xenomai/bin/latency i
>> get the message "sh: /usr/xenomai/bin/latency: not found"
>>     
>
> Have you tried running file, ldd, or readelf on the binary to see what
> it is made of ?
>
>   
>> By the way, how i can figure out if the binary or the compiler is a
>> oabi/eabi file/compiler?
>>     
>
> codesourcery compiles for eabi by default. So, you have to enable eabi
> in kernel configuration to be able to run binaries generated by
> codesourcery compiler.
>
>   
The eabi was disabled in the kernel configuration. But to enable it make 
no changes.


$ file usr/xenomai/bin/latency
usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1 
(SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not 
stripped


$ ldd usr/xenomai/bin/latency
    not a dynamic executable

$ readelf --sections /usr/xenomai/bin/latency
There are 30 section headers, starting at offset 0x42f0:

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg 
Lk Inf Al
  [ 0]                   NULL            00000000 000000 000000 00      
0   0  0
  [ 1] .interp           PROGBITS        08048174 000174 000013 00   A  
0   0  1
  [ 2] .note.ABI-tag     NOTE            08048188 000188 000020 00   A  
0   0  4
  [ 3] .hash             HASH            080481a8 0001a8 000168 04   A  
5   0  4
  [ 4] .gnu.hash         GNU_HASH        08048310 000310 000048 04   A  
5   0  4
  [ 5] .dynsym           DYNSYM          08048358 000358 000330 10   A  
6   1  4
  [ 6] .dynstr           STRTAB          08048688 000688 000266 00   A  
0   0  1
  [ 7] .gnu.version      VERSYM          080488ee 0008ee 000066 02   A  
5   0  2
  [ 8] .gnu.version_r    VERNEED         08048954 000954 000060 00   A  
6   3  4
  [ 9] .rel.dyn          REL             080489b4 0009b4 000020 08   A  
5   0  4
  [10] .rel.plt          REL             080489d4 0009d4 000140 08   A  
5  12  4
  [11] .init             PROGBITS        08048b14 000b14 000017 00  AX  
0   0  4
  [12] .plt              PROGBITS        08048b2c 000b2c 000290 04  AX  
0   0  4
  [13] .text             PROGBITS        08048dc0 000dc0 0018a4 00  AX  
0   0 16
  [14] .fini             PROGBITS        0804a664 002664 00001c 00  AX  
0   0  4
  [15] .rodata           PROGBITS        0804a680 002680 000a54 00   A  
0   0  4
  [16] .eh_frame_hdr     PROGBITS        0804b0d4 0030d4 000014 00   A  
0   0  4
  [17] .eh_frame         PROGBITS        0804b0e8 0030e8 00003c 00   A  
0   0  4
  [18] .ctors            PROGBITS        0804cedc 003edc 000008 00  WA  
0   0  4
  [19] .dtors            PROGBITS        0804cee4 003ee4 000008 00  WA  
0   0  4
  [20] .jcr              PROGBITS        0804ceec 003eec 000004 00  WA  
0   0  4
  [21] .dynamic          DYNAMIC         0804cef0 003ef0 000100 08  WA  
6   0  4
  [22] .got              PROGBITS        0804cff0 003ff0 000004 04  WA  
0   0  4
  [23] .got.plt          PROGBITS        0804cff4 003ff4 0000ac 04  WA  
0   0  4
  [24] .data             PROGBITS        0804d0a0 0040a0 000034 00  WA  
0   0  4
  [25] .bss              NOBITS          0804d0e0 0040d4 0000a0 00  WA  
0   0 32
  [26] .comment          PROGBITS        00000000 0040d4 000130 00      
0   0  1
  [27] .shstrtab         STRTAB          00000000 004204 0000e9 00      
0   0  1
  [28] .symtab           SYMTAB          00000000 0047a0 000910 10     
29  46  4
  [29] .strtab           STRTAB          00000000 0050b0 000645 00      
0   0  1
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings)
  I (info), L (link order), G (group), x (unknown)
  O (extra OS processing required) o (OS specific), p (processor specific)

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

paradoxxa wrote:
 > Gilles Chanteperdrix schrieb:
 > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
 > >   
 > >> Gilles Chanteperdrix schrieb:
 > >>     
 > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
 > >>>
 > >>>       
 > >>>> Gilles Chanteperdrix schrieb:
 > >>>>
 > >>>>         
 > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
 > >>>>>
 > >>>>>
 > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
 > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
 > >>>>> least two options that you changed. Could you check if a kernel with
 > >>>>> an unmodified defconfig boots ?
 > >>>>>
 > >>>>>
 > >>>>>
 > >>>>>           
 > >>>> The CONFIG_DEBUG_INFO is already set in the defconfig. The
 > >>>> CONFIG_DEBUG_LL i
 > >>>> set manually.
 > >>>> As well I had to changed the  AT91 Master Clock Frequency.
 > >>>>
 > >>>> Here are the logs of a unmodified defconfig boot:
 > >>>>
 > >>>>         
 > >>> Ok. But this is a boot with your old compiler. Could you try a
 > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
 > >>> with CodeSourcery compiler ?
 > >>>  If you can not get CodeSourcery compiler to compile correctly a Linux
 > >>> kernel, I can send you the 2007q3 compiler, or you could try to
 > >>> compile the kernel with your old compiler, and to compile user-space
 > >>> with CodeSourcery compiler.
 > >>>
 > >>>       
 > >> I tried it with the both compiler. When i execute /usr/xenomai/bin/latency i
 > >> get the message "sh: /usr/xenomai/bin/latency: not found"
 > >>     
 > >
 > > Have you tried running file, ldd, or readelf on the binary to see what
 > > it is made of ?
 > >
 > >   
 > >> By the way, how i can figure out if the binary or the compiler is a
 > >> oabi/eabi file/compiler?
 > >>     
 > >
 > > codesourcery compiles for eabi by default. So, you have to enable eabi
 > > in kernel configuration to be able to run binaries generated by
 > > codesourcery compiler.
 > >
 > >   
 > The eabi was disabled in the kernel configuration. But to enable it make 
 > no changes.
 > 
 > 
 > $ file usr/xenomai/bin/latency
 > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1 
 > (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not 
 > stripped
 > 
 > 
 > $ ldd usr/xenomai/bin/latency
 >     not a dynamic executable

This is wrong. ldd should be run on the target, not on the host. Also
check that /usr/xenomai/lib is in the ld.so.conf on your target (and
that you have run ldconfig) or use LD_LIBRARY_PATH

 > 
 > $ readelf --sections /usr/xenomai/bin/latency

I was rather thinking about readelf -d /usr/xenomai/bin/latency

-- 


					    Gilles.

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa]

Gilles Chanteperdrix schrieb:
> paradoxxa wrote:
>  > Gilles Chanteperdrix schrieb:
>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>  > >   
>  > >> Gilles Chanteperdrix schrieb:
>  > >>     
>  > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>  > >>>
>  > >>>       
>  > >>>> Gilles Chanteperdrix schrieb:
>  > >>>>
>  > >>>>         
>  > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa <paradoxxa2001@domain.hid> wrote:
>  > >>>>>
>  > >>>>>
>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make at
>  > >>>>> least two options that you changed. Could you check if a kernel with
>  > >>>>> an unmodified defconfig boots ?
>  > >>>>>
>  > >>>>>
>  > >>>>>
>  > >>>>>           
>  > >>>> The CONFIG_DEBUG_INFO is already set in the defconfig. The
>  > >>>> CONFIG_DEBUG_LL i
>  > >>>> set manually.
>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>  > >>>>
>  > >>>> Here are the logs of a unmodified defconfig boot:
>  > >>>>
>  > >>>>         
>  > >>> Ok. But this is a boot with your old compiler. Could you try a
>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>  > >>> with CodeSourcery compiler ?
>  > >>>  If you can not get CodeSourcery compiler to compile correctly a Linux
>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>  > >>> compile the kernel with your old compiler, and to compile user-space
>  > >>> with CodeSourcery compiler.
>  > >>>
>  > >>>       
>  > >> I tried it with the both compiler. When i execute /usr/xenomai/bin/latency i
>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>  > >>     
>  > >
>  > > Have you tried running file, ldd, or readelf on the binary to see what
>  > > it is made of ?
>  > >
>  > >   
>  > >> By the way, how i can figure out if the binary or the compiler is a
>  > >> oabi/eabi file/compiler?
>  > >>     
>  > >
>  > > codesourcery compiles for eabi by default. So, you have to enable eabi
>  > > in kernel configuration to be able to run binaries generated by
>  > > codesourcery compiler.
>  > >
>  > >   
>  > The eabi was disabled in the kernel configuration. But to enable it make 
>  > no changes.
>  > 
>  > 
>  > $ file usr/xenomai/bin/latency
>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1 
>  > (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not 
>  > stripped
>  > 
>  > 
>  > $ ldd usr/xenomai/bin/latency
>  >     not a dynamic executable
>
> This is wrong. ldd should be run on the target, not on the host. Also
> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
> that you have run ldconfig) or use LD_LIBRARY_PATH
>
>  > 
>  > $ readelf --sections /usr/xenomai/bin/latency
>
> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>
>   
I actuall don't have ldd and readelf on the target. I did a ldconfig -p. 
The Xenomai Libraries were listed there.

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> paradoxxa wrote:
>>  > Gilles Chanteperdrix schrieb:
>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>> wrote:
>>  > >    > >> Gilles Chanteperdrix schrieb:
>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>> <paradoxxa2001@domain.hid> wrote:
>>  > >>>
>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>  > >>>>
>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>> <paradoxxa2001@domain.hid> wrote:
>>  > >>>>>
>>  > >>>>>
>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>> at
>>  > >>>>> least two options that you changed. Could you check if a kernel
>> with
>>  > >>>>> an unmodified defconfig boots ?
>>  > >>>>>
>>  > >>>>>
>>  > >>>>>
>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>> defconfig. The
>>  > >>>> CONFIG_DEBUG_LL i
>>  > >>>> set manually.
>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>  > >>>>
>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>  > >>>>
>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>> Could you try a
>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>  > >>> with CodeSourcery compiler ?
>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>> Linux
>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>  > >>> compile the kernel with your old compiler, and to compile
>> user-space
>>  > >>> with CodeSourcery compiler.
>>  > >>>
>>  > >>>        > >> I tried it with the both compiler. When i execute
>> /usr/xenomai/bin/latency i
>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>  > >>      > >
>>  > > Have you tried running file, ldd, or readelf on the binary to see
>> what
>>  > > it is made of ?
>>  > >
>>  > >    > >> By the way, how i can figure out if the binary or the
>> compiler is a
>>  > >> oabi/eabi file/compiler?
>>  > >>      > >
>>  > > codesourcery compiles for eabi by default. So, you have to enable
>> eabi
>>  > > in kernel configuration to be able to run binaries generated by
>>  > > codesourcery compiler.
>>  > >
>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>> it make  > no changes.
>>  >  >  > $ file usr/xenomai/bin/latency
>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>> stripped
>>  >  >  > $ ldd usr/xenomai/bin/latency
>>  >     not a dynamic executable
>>
>> This is wrong. ldd should be run on the target, not on the host. Also
>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>
>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>
>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>
>>
>
> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
> Xenomai Libraries were listed there.

readelf can work on the host. But ldd on the target is the best way to
know if the installation worked correctly. If you are looking for ldd,
it is compiled as part of the glibc. You may even found it in the
toolchain files.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
>> Gilles Chanteperdrix schrieb:
>>>
>>> paradoxxa wrote:
>>>  > Gilles Chanteperdrix schrieb:
>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>> wrote:
>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>> <paradoxxa2001@domain.hid> wrote:
>>>  > >>>
>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>  > >>>>
>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>> <paradoxxa2001@domain.hid> wrote:
>>>  > >>>>>
>>>  > >>>>>
>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>>> at
>>>  > >>>>> least two options that you changed. Could you check if a kernel
>>> with
>>>  > >>>>> an unmodified defconfig boots ?
>>>  > >>>>>
>>>  > >>>>>
>>>  > >>>>>
>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>> defconfig. The
>>>  > >>>> CONFIG_DEBUG_LL i
>>>  > >>>> set manually.
>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>  > >>>>
>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>  > >>>>
>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>> Could you try a
>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>>  > >>> with CodeSourcery compiler ?
>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>>> Linux
>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>  > >>> compile the kernel with your old compiler, and to compile
>>> user-space
>>>  > >>> with CodeSourcery compiler.
>>>  > >>>
>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>> /usr/xenomai/bin/latency i
>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>  > >>      > >
>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>> what
>>>  > > it is made of ?
>>>  > >
>>>  > >    > >> By the way, how i can figure out if the binary or the
>>> compiler is a
>>>  > >> oabi/eabi file/compiler?
>>>  > >>      > >
>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>> eabi
>>>  > > in kernel configuration to be able to run binaries generated by
>>>  > > codesourcery compiler.
>>>  > >
>>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>>> it make  > no changes.
>>>  >  >  > $ file usr/xenomai/bin/latency
>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>>> stripped
>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>  >     not a dynamic executable
>>>
>>> This is wrong. ldd should be run on the target, not on the host. Also
>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>
>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>
>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>
>>>
>>
>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
>> Xenomai Libraries were listed there.
>
> readelf can work on the host. But ldd on the target is the best way to
> know if the installation worked correctly. If you are looking for ldd,
> it is compiled as part of the glibc. You may even found it in the
> toolchain files.

Actually ldd is a script, it is not compiled.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org> wrote:
>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
>>> Gilles Chanteperdrix schrieb:
>>>>
>>>> paradoxxa wrote:
>>>>  > Gilles Chanteperdrix schrieb:
>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>> wrote:
>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>> <paradoxxa2001@domain.hid> wrote:
>>>>  > >>>
>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>  > >>>>
>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>> <paradoxxa2001@domain.hid> wrote:
>>>>  > >>>>>
>>>>  > >>>>>
>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>>>> at
>>>>  > >>>>> least two options that you changed. Could you check if a kernel
>>>> with
>>>>  > >>>>> an unmodified defconfig boots ?
>>>>  > >>>>>
>>>>  > >>>>>
>>>>  > >>>>>
>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>> defconfig. The
>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>  > >>>> set manually.
>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>  > >>>>
>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>  > >>>>
>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>> Could you try a
>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>>>  > >>> with CodeSourcery compiler ?
>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>>>> Linux
>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>> user-space
>>>>  > >>> with CodeSourcery compiler.
>>>>  > >>>
>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>> /usr/xenomai/bin/latency i
>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>  > >>      > >
>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>> what
>>>>  > > it is made of ?
>>>>  > >
>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>> compiler is a
>>>>  > >> oabi/eabi file/compiler?
>>>>  > >>      > >
>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>> eabi
>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>  > > codesourcery compiler.
>>>>  > >
>>>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>>>> it make  > no changes.
>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>>>> stripped
>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>  >     not a dynamic executable
>>>>
>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>
>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>
>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>
>>>>
>>>
>>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
>>> Xenomai Libraries were listed there.
>>
>> readelf can work on the host. But ldd on the target is the best way to
>> know if the installation worked correctly. If you are looking for ldd,
>> it is compiled as part of the glibc. You may even found it in the
>> toolchain files.
>
> Actually ldd is a script, it is not compiled.

All what it does is launching

LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency

So, you do not even need the script.

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa]

Gilles Chanteperdrix schrieb:
> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org> wrote:
>   
>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>     
>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>       
>>>> Gilles Chanteperdrix schrieb:
>>>>         
>>>>> paradoxxa wrote:
>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>> wrote:
>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>
>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>  > >>>>
>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>>>>> at
>>>>>  > >>>>> least two options that you changed. Could you check if a kernel
>>>>> with
>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>> defconfig. The
>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>  > >>>> set manually.
>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>  > >>>>
>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>  > >>>>
>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>> Could you try a
>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>>>>  > >>> with CodeSourcery compiler ?
>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>>>>> Linux
>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>> user-space
>>>>>  > >>> with CodeSourcery compiler.
>>>>>  > >>>
>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>> /usr/xenomai/bin/latency i
>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>  > >>      > >
>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>> what
>>>>>  > > it is made of ?
>>>>>  > >
>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>> compiler is a
>>>>>  > >> oabi/eabi file/compiler?
>>>>>  > >>      > >
>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>> eabi
>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>  > > codesourcery compiler.
>>>>>  > >
>>>>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>>>>> it make  > no changes.
>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>>>>> stripped
>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>  >     not a dynamic executable
>>>>>
>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>
>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>
>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>
>>>>>
>>>>>           
>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
>>>> Xenomai Libraries were listed there.
>>>>         
>>> readelf can work on the host. But ldd on the target is the best way to
>>> know if the installation worked correctly. If you are looking for ldd,
>>> it is compiled as part of the glibc. You may even found it in the
>>> toolchain files.
>>>       
>> Actually ldd is a script, it is not compiled.
>>     
>
> All what it does is launching
>
> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>
> So, you do not even need the script.
>
>   

> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org> wrote:
>   
>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>     
>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>       
>>>> Gilles Chanteperdrix schrieb:
>>>>         
>>>>> paradoxxa wrote:
>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>> wrote:
>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>
>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>  > >>>>
>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>>>>> at
>>>>>  > >>>>> least two options that you changed. Could you check if a kernel
>>>>> with
>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>> defconfig. The
>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>  > >>>> set manually.
>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>  > >>>>
>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>  > >>>>
>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>> Could you try a
>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>>>>  > >>> with CodeSourcery compiler ?
>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>>>>> Linux
>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>> user-space
>>>>>  > >>> with CodeSourcery compiler.
>>>>>  > >>>
>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>> /usr/xenomai/bin/latency i
>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>  > >>      > >
>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>> what
>>>>>  > > it is made of ?
>>>>>  > >
>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>> compiler is a
>>>>>  > >> oabi/eabi file/compiler?
>>>>>  > >>      > >
>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>> eabi
>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>  > > codesourcery compiler.
>>>>>  > >
>>>>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>>>>> it make  > no changes.
>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>>>>> stripped
>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>  >     not a dynamic executable
>>>>>
>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>
>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>
>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>
>>>>>
>>>>>           
>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
>>>> Xenomai Libraries were listed there.
>>>>         
>>> readelf can work on the host. But ldd on the target is the best way to
>>> know if the installation worked correctly. If you are looking for ldd,
>>> it is compiled as part of the glibc. You may even found it in the
>>> toolchain files.
>>>       
>> Actually ldd is a script, it is not compiled.
>>     
>
> All what it does is launching
>
> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>
> So, you do not even need the script.
>
>   

> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org> wrote:
>   
>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>     
>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
>>>       
>>>> Gilles Chanteperdrix schrieb:
>>>>         
>>>>> paradoxxa wrote:
>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>> wrote:
>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>
>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>  > >>>>
>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make
>>>>> at
>>>>>  > >>>>> least two options that you changed. Could you check if a kernel
>>>>> with
>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>
>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>> defconfig. The
>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>  > >>>> set manually.
>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>  > >>>>
>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>  > >>>>
>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>> Could you try a
>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency modified)
>>>>>  > >>> with CodeSourcery compiler ?
>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly a
>>>>> Linux
>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>> user-space
>>>>>  > >>> with CodeSourcery compiler.
>>>>>  > >>>
>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>> /usr/xenomai/bin/latency i
>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>  > >>      > >
>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>> what
>>>>>  > > it is made of ?
>>>>>  > >
>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>> compiler is a
>>>>>  > >> oabi/eabi file/compiler?
>>>>>  > >>      > >
>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>> eabi
>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>  > > codesourcery compiler.
>>>>>  > >
>>>>>  > >    > The eabi was disabled in the kernel configuration. But to enable
>>>>> it make  > no changes.
>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1  >
>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not  >
>>>>> stripped
>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>  >     not a dynamic executable
>>>>>
>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>
>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>
>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>
>>>>>
>>>>>           
>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The
>>>> Xenomai Libraries were listed there.
>>>>         
>>> readelf can work on the host. But ldd on the target is the best way to
>>> know if the installation worked correctly. If you are looking for ldd,
>>> it is compiled as part of the glibc. You may even found it in the
>>> toolchain files.
>>>       
>> Actually ldd is a script, it is not compiled.
>>     
>
> All what it does is launching
>
> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>
> So, you do not even need the script.
>
>   
I think that doesn't look good:

root@domain.hid:~# LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
-sh: /usr/xenomai/bin/latency: not found



root@domain.hid -d /usr/xenomai/bin/latency

Dynamic section at offset 0x48a0 contains 29 entries:
  Tag        Type                         Name/Value
 0x00000001 (NEEDED)                     Shared library: [libnative.so.1]
 0x00000001 (NEEDED)                     Shared library: [librtdm.so.1]
 0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
 0x00000001 (NEEDED)                     Shared library: [libm.so.6]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x0000000f (RPATH)                      Library rpath: [/usr/xenomai/lib]
 0x0000000c (INIT)                       0x8bbc
 0x0000000d (FINI)                       0xbdc8
 0x00000019 (INIT_ARRAY)                 0x14894
 0x0000001b (INIT_ARRAYSZ)               4 (bytes)
 0x0000001a (FINI_ARRAY)                 0x14898
 0x0000001c (FINI_ARRAYSZ)               4 (bytes)
 0x00000004 (HASH)                       0x8168
 0x00000005 (STRTAB)                     0x86b4
 0x00000006 (SYMTAB)                     0x82f4
 0x0000000a (STRSZ)                      703 (bytes)
 0x0000000b (SYMENT)                     16 (bytes)
 0x00000015 (DEBUG)                      0x0
 0x00000003 (PLTGOT)                     0x149b0
 0x00000002 (PLTRELSZ)                   336 (bytes)
 0x00000014 (PLTREL)                     REL
 0x00000017 (JMPREL)                     0x8a6c
 0x00000011 (REL)                        0x8a4c
 0x00000012 (RELSZ)                      32 (bytes)
 0x00000013 (RELENT)                     8 (bytes)
 0x6ffffffe (VERNEED)                    0x89ec
 0x6fffffff (VERNEEDNUM)                 3
 0x6ffffff0 (VERSYM)                     0x8974
 0x00000000 (NULL)                       0x0

Thomas

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

On Tue, May 20, 2008 at 2:43 PM, Paradoxxa <paradoxxa2001@domain.hid> wrote:
> Gilles Chanteperdrix schrieb:
>>
>> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>
>>>
>>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>
>>>>
>>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid>
>>>> wrote:
>>>>
>>>>>
>>>>> Gilles Chanteperdrix schrieb:
>>>>>
>>>>>>
>>>>>> paradoxxa wrote:
>>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>>> wrote:
>>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>
>>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this
>>>>>> make
>>>>>> at
>>>>>>  > >>>>> least two options that you changed. Could you check if a
>>>>>> kernel
>>>>>> with
>>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>>> defconfig. The
>>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>>  > >>>> set manually.
>>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>>  > >>>>
>>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>>> Could you try a
>>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency
>>>>>> modified)
>>>>>>  > >>> with CodeSourcery compiler ?
>>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly
>>>>>> a
>>>>>> Linux
>>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>>> user-space
>>>>>>  > >>> with CodeSourcery compiler.
>>>>>>  > >>>
>>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>>> /usr/xenomai/bin/latency i
>>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>>  > >>      > >
>>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>>> what
>>>>>>  > > it is made of ?
>>>>>>  > >
>>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>>> compiler is a
>>>>>>  > >> oabi/eabi file/compiler?
>>>>>>  > >>      > >
>>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>>> eabi
>>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>>  > > codesourcery compiler.
>>>>>>  > >
>>>>>>  > >    > The eabi was disabled in the kernel configuration. But to
>>>>>> enable
>>>>>> it make  > no changes.
>>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1
>>>>>>  >
>>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs),
>>>>>> not  >
>>>>>> stripped
>>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>>  >     not a dynamic executable
>>>>>>
>>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>>
>>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>>
>>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig
>>>>> -p. The
>>>>> Xenomai Libraries were listed there.
>>>>>
>>>>
>>>> readelf can work on the host. But ldd on the target is the best way to
>>>> know if the installation worked correctly. If you are looking for ldd,
>>>> it is compiled as part of the glibc. You may even found it in the
>>>> toolchain files.
>>>>
>>>
>>> Actually ldd is a script, it is not compiled.
>>>
>>
>> All what it does is launching
>>
>> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>>
>> So, you do not even need the script.
>>
>>
>
>> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>
>>>
>>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>
>>>>
>>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid>
>>>> wrote:
>>>>
>>>>>
>>>>> Gilles Chanteperdrix schrieb:
>>>>>
>>>>>>
>>>>>> paradoxxa wrote:
>>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>>> wrote:
>>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>
>>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this
>>>>>> make
>>>>>> at
>>>>>>  > >>>>> least two options that you changed. Could you check if a
>>>>>> kernel
>>>>>> with
>>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>>> defconfig. The
>>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>>  > >>>> set manually.
>>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>>  > >>>>
>>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>>> Could you try a
>>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency
>>>>>> modified)
>>>>>>  > >>> with CodeSourcery compiler ?
>>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly
>>>>>> a
>>>>>> Linux
>>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>>> user-space
>>>>>>  > >>> with CodeSourcery compiler.
>>>>>>  > >>>
>>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>>> /usr/xenomai/bin/latency i
>>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>>  > >>      > >
>>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>>> what
>>>>>>  > > it is made of ?
>>>>>>  > >
>>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>>> compiler is a
>>>>>>  > >> oabi/eabi file/compiler?
>>>>>>  > >>      > >
>>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>>> eabi
>>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>>  > > codesourcery compiler.
>>>>>>  > >
>>>>>>  > >    > The eabi was disabled in the kernel configuration. But to
>>>>>> enable
>>>>>> it make  > no changes.
>>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1
>>>>>>  >
>>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs),
>>>>>> not  >
>>>>>> stripped
>>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>>  >     not a dynamic executable
>>>>>>
>>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>>
>>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>>
>>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig
>>>>> -p. The
>>>>> Xenomai Libraries were listed there.
>>>>>
>>>>
>>>> readelf can work on the host. But ldd on the target is the best way to
>>>> know if the installation worked correctly. If you are looking for ldd,
>>>> it is compiled as part of the glibc. You may even found it in the
>>>> toolchain files.
>>>>
>>>
>>> Actually ldd is a script, it is not compiled.
>>>
>>
>> All what it does is launching
>>
>> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>>
>> So, you do not even need the script.
>>
>>
>
>> On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix
>> <gilles.chanteperdrix@xenomai.org> wrote:
>>
>>>
>>> On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>
>>>>
>>>> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <paradoxxa2001@domain.hid>
>>>> wrote:
>>>>
>>>>>
>>>>> Gilles Chanteperdrix schrieb:
>>>>>
>>>>>>
>>>>>> paradoxxa wrote:
>>>>>>  > Gilles Chanteperdrix schrieb:
>>>>>>  > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <paradoxxa2001@domain.hid>
>>>>>> wrote:
>>>>>>  > >    > >> Gilles Chanteperdrix schrieb:
>>>>>>  > >>      > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>
>>>>>>  > >>>        > >>>> Gilles Chanteperdrix schrieb:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa
>>>>>> <paradoxxa2001@domain.hid> wrote:
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about
>>>>>>  > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this
>>>>>> make
>>>>>> at
>>>>>>  > >>>>> least two options that you changed. Could you check if a
>>>>>> kernel
>>>>>> with
>>>>>>  > >>>>> an unmodified defconfig boots ?
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>
>>>>>>  > >>>>>            > >>>> The CONFIG_DEBUG_INFO is already set in the
>>>>>> defconfig. The
>>>>>>  > >>>> CONFIG_DEBUG_LL i
>>>>>>  > >>>> set manually.
>>>>>>  > >>>> As well I had to changed the  AT91 Master Clock Frequency.
>>>>>>  > >>>>
>>>>>>  > >>>> Here are the logs of a unmodified defconfig boot:
>>>>>>  > >>>>
>>>>>>  > >>>>          > >>> Ok. But this is a boot with your old compiler.
>>>>>> Could you try a
>>>>>>  > >>> defconfig build (with I-pipe AT91 master clock frequency
>>>>>> modified)
>>>>>>  > >>> with CodeSourcery compiler ?
>>>>>>  > >>>  If you can not get CodeSourcery compiler to compile correctly
>>>>>> a
>>>>>> Linux
>>>>>>  > >>> kernel, I can send you the 2007q3 compiler, or you could try to
>>>>>>  > >>> compile the kernel with your old compiler, and to compile
>>>>>> user-space
>>>>>>  > >>> with CodeSourcery compiler.
>>>>>>  > >>>
>>>>>>  > >>>        > >> I tried it with the both compiler. When i execute
>>>>>> /usr/xenomai/bin/latency i
>>>>>>  > >> get the message "sh: /usr/xenomai/bin/latency: not found"
>>>>>>  > >>      > >
>>>>>>  > > Have you tried running file, ldd, or readelf on the binary to see
>>>>>> what
>>>>>>  > > it is made of ?
>>>>>>  > >
>>>>>>  > >    > >> By the way, how i can figure out if the binary or the
>>>>>> compiler is a
>>>>>>  > >> oabi/eabi file/compiler?
>>>>>>  > >>      > >
>>>>>>  > > codesourcery compiles for eabi by default. So, you have to enable
>>>>>> eabi
>>>>>>  > > in kernel configuration to be able to run binaries generated by
>>>>>>  > > codesourcery compiler.
>>>>>>  > >
>>>>>>  > >    > The eabi was disabled in the kernel configuration. But to
>>>>>> enable
>>>>>> it make  > no changes.
>>>>>>  >  >  > $ file usr/xenomai/bin/latency
>>>>>>  > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1
>>>>>>  >
>>>>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs),
>>>>>> not  >
>>>>>> stripped
>>>>>>  >  >  > $ ldd usr/xenomai/bin/latency
>>>>>>  >     not a dynamic executable
>>>>>>
>>>>>> This is wrong. ldd should be run on the target, not on the host. Also
>>>>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and
>>>>>> that you have run ldconfig) or use LD_LIBRARY_PATH
>>>>>>
>>>>>>  >  > $ readelf --sections /usr/xenomai/bin/latency
>>>>>>
>>>>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I actuall don't have ldd and readelf on the target. I did a ldconfig
>>>>> -p. The
>>>>> Xenomai Libraries were listed there.
>>>>>
>>>>
>>>> readelf can work on the host. But ldd on the target is the best way to
>>>> know if the installation worked correctly. If you are looking for ldd,
>>>> it is compiled as part of the glibc. You may even found it in the
>>>> toolchain files.
>>>>
>>>
>>> Actually ldd is a script, it is not compiled.
>>>
>>
>> All what it does is launching
>>
>> LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
>>
>> So, you do not even need the script.
>>
>>
>
> I think that doesn't look good:
>
> root@domain.hid:~# LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency
> -sh: /usr/xenomai/bin/latency: not found

I would say there is something wrong with your installation: your
toolchain links with some library which are not present on your target
system (for instance you have ld-linux.so.2 on your target whereas the
binaries generated by your toolchain links to ld-linux.so.3). To know
if this is the case, could you try to compile a simple "hello world"
program using the same toolchain as the one you use to compile Xenomai
user-space libraries ?

-- 
 Gilles

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Paradoxxa]

Am Dienstag, den 20.05.2008, 17:16 +0200 schrieb Gilles Chanteperdrix:

> 
> I would say there is something wrong with your installation: your
> toolchain links with some library which are not present on your target
> system (for instance you have ld-linux.so.2 on your target whereas the
> binaries generated by your toolchain links to ld-linux.so.3). To know
> if this is the case, could you try to compile a simple "hello world"
> program using the same toolchain as the one you use to compile Xenomai
> user-space libraries ?
> 
I built the helloworld. The readelf output is:
--------------------------------------------------
Dynamic section at offset 0x9f8 contains 27 entries:
  Tag        Type                         Name/Value
0x00000001 (NEEDED)                     Shared library: [libstdc++.so.6]
0x00000001 (NEEDED)                     Shared library: [libm.so.6]
0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
0x00000001 (NEEDED)                     Shared library: [libc.so.6]
0x0000000c (INIT)                       0x84bc
0x0000000d (FINI)                       0x8940
0x00000019 (INIT_ARRAY)                 0x109e8
0x0000001b (INIT_ARRAYSZ)               8 (bytes)
0x0000001a (FINI_ARRAY)                 0x109f0
0x0000001c (FINI_ARRAYSZ)               4 (bytes)
0x00000004 (HASH)                       0x8168
0x00000005 (STRTAB)                     0x8294
0x00000006 (SYMTAB)                     0x81b4
0x0000000a (STRSZ)                      339 (bytes)
0x0000000b (SYMENT)                     16 (bytes)
0x00000015 (DEBUG)                      0x0
0x00000003 (PLTGOT)                     0x10af8
0x00000002 (PLTRELSZ)                   72 (bytes)
0x00000014 (PLTREL)                     REL
0x00000017 (JMPREL)                     0x8474
0x00000011 (REL)                        0x8464
0x00000012 (RELSZ)                      16 (bytes)
0x00000013 (RELENT)                     8 (bytes)
0x6ffffffe (VERNEED)                    0x8404
0x6fffffff (VERNEEDNUM)                 3
0x6ffffff0 (VERSYM)                     0x83e8
0x00000000 (NULL)                       0x0
--------------------------------------------------

Additionly i searched for the ld-linux.so*. On the Target is
ld-slinux-so.2 and on the host is ld-linux.so.3 (Sourcery Toolchain).
The rootfs is also distributed from the vendor. I think i should build a
own one. What do you use for building a rootfs?
I built also a own Toolchain with crossdev (ld-linux.so.2) and with it i
seems to work. I can build the kernel and the user-space support an both
of them run on the target.  

Thomas

Re: [Xenomai-help] at91sam9263 and user-space support compile fails

[Gilles Chanteperdrix]

Paradoxxa wrote:
 > 
 > Am Dienstag, den 20.05.2008, 17:16 +0200 schrieb Gilles Chanteperdrix:
 > 
 > > 
 > > I would say there is something wrong with your installation: your
 > > toolchain links with some library which are not present on your target
 > > system (for instance you have ld-linux.so.2 on your target whereas the
 > > binaries generated by your toolchain links to ld-linux.so.3). To know
 > > if this is the case, could you try to compile a simple "hello world"
 > > program using the same toolchain as the one you use to compile Xenomai
 > > user-space libraries ?
 > > 
 > I built the helloworld. The readelf output is:
 > --------------------------------------------------
 > Dynamic section at offset 0x9f8 contains 27 entries:
 >   Tag        Type                         Name/Value
 > 0x00000001 (NEEDED)                     Shared library: [libstdc++.so.6]
 > 0x00000001 (NEEDED)                     Shared library: [libm.so.6]
 > 0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
 > 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 > 0x0000000c (INIT)                       0x84bc
 > 0x0000000d (FINI)                       0x8940
 > 0x00000019 (INIT_ARRAY)                 0x109e8
 > 0x0000001b (INIT_ARRAYSZ)               8 (bytes)
 > 0x0000001a (FINI_ARRAY)                 0x109f0
 > 0x0000001c (FINI_ARRAYSZ)               4 (bytes)
 > 0x00000004 (HASH)                       0x8168
 > 0x00000005 (STRTAB)                     0x8294
 > 0x00000006 (SYMTAB)                     0x81b4
 > 0x0000000a (STRSZ)                      339 (bytes)
 > 0x0000000b (SYMENT)                     16 (bytes)
 > 0x00000015 (DEBUG)                      0x0
 > 0x00000003 (PLTGOT)                     0x10af8
 > 0x00000002 (PLTRELSZ)                   72 (bytes)
 > 0x00000014 (PLTREL)                     REL
 > 0x00000017 (JMPREL)                     0x8474
 > 0x00000011 (REL)                        0x8464
 > 0x00000012 (RELSZ)                      16 (bytes)
 > 0x00000013 (RELENT)                     8 (bytes)
 > 0x6ffffffe (VERNEED)                    0x8404
 > 0x6fffffff (VERNEEDNUM)                 3
 > 0x6ffffff0 (VERSYM)                     0x83e8
 > 0x00000000 (NULL)                       0x0
 > --------------------------------------------------
 > 
 > Additionly i searched for the ld-linux.so*. On the Target is
 > ld-slinux-so.2 and on the host is ld-linux.so.3 (Sourcery Toolchain).
 > The rootfs is also distributed from the vendor. I think i should build a
 > own one. What do you use for building a rootfs?
 > I built also a own Toolchain with crossdev (ld-linux.so.2) and with it i
 > seems to work. I can build the kernel and the user-space support an both
 > of them run on the target.  

I am afraid these questions are completely out of the scope of Xenomai
mailing lists. Personally, I make my rootfs on an NFS shared directory
by copying the libc files from the toolchain, just adding a few other
programs such as busybox, gdbserver, strace, tcpdump, etc... This is
suitable for a test rootfs, but probably not realistic for serious use.

-- 


					    Gilles.