2009/1/29 Greg Ungerer <g...@snapgear.com>: > Hi Loody, > > loody wrote: >>> >>> Why is only supporting FLAT a problem for you? >>> (It is not entirely true to say uClinux only supports FLAT, >>> some uClinux architectures support fdelf-pic). >> >> Sorry for using the word, ONLY. Tears will make the screen blur, you >> know. :-(.... >> >>> >>>> I don't know how to make a flat with the arm-linux compiler linked >>>> from uclinux.org. You can see it in the previous letter. >>> >>> That is why I said to get the uClinux-dist. >>> It builds applications with that compiler against its >>> own uClibc. They work. I specifically test it for the >>> GDB/ARMulator target before uClinux-dist releases. >>> >> >> According all your suggestions, I stop trying to use different >> cross-toolchains except >> 1. arm-linux-tools-20061213.tar.gz >> 2. arm-linux-tools-20070808.tar.gz >> >> And I try to use both of them to compile applications at user. >> 2 can get the FLAT I need but 1 will fail while calling the linker and it >> says >> ld.real: address 0x22380 of busybox_unstripped.gdb section .text is >> not within region flatmem > > Please give details. > How exactly did you try to build these? > Standalone or in the uClinux-dist framework? > What where the compile lines? > More details please?
In the uClinux-dist framework, please see the attach file,
arm-linux-gcc_2006_link_error.log.
>> So I wipe my tears out and recompile the kernel with 2 happily :)
>> but tears full fill my eyes again when my platform get
>> unknown-instruction-exception, while executing below instructions:
>>
>> e1a0e00f mov lr, pc
>> e12fff13 bx r3
>>
>> :-(~~~
>
> Details?
> Is part of the kernel, or app?
Is part of kernel:
80008b74 <start_kernel>:
80008b74: e1a0c00d mov ip, sp
80008b78: e92dd870 stmdb sp!, {r4, r5, r6, fp, ip, lr, pc}
80008b7c: e24cb004 sub fp, ip, #4 ; 0x4
80008b80: e24dd008 sub sp, sp, #8 ; 0x8
80008b84: e59f0414 ldr r0, [pc, #1044] ; 80008fa0 <.init+0xc00>
80008b88: eb003ddc bl 80018300 <printk>
80008b8c: e59f3410 ldr r3, [pc, #1040] ; 80008fa4 <.init+0xc04>
80008b90: e1a0e00f mov lr, pc
---------------> here it is
80008b94: e12fff13 bx r3
80008b98: e59f0408 ldr r0, [pc, #1032] ; 80008fa8 <.init+0xc08>
80008b9c: eb003dd7 bl 80018300 <printk>
80008ba0: e59f0404 ldr r0, [pc, #1028] ; 80008fac <.init+0xc0c>
80008ba4: eb003dd5 bl 80018300 <printk>
80008ba8: e59f0400 ldr r0, [pc, #1024] ; 80008fb0 <.init+0xc10>
80008bac: eb003dd3 bl 80018300 <printk>
80008bb0: e59f03fc ldr r0, [pc, #1020] ; 80008fb4 <.init+0xc14>
80008bb4: eb003dd1 bl 80018300 <printk>
80008bb8: e10f3000 mrs r3, CPSR
80008bbc: e3833080 orr r3, r3, #128 ; 0x80
Thanks for your help,
miloody
arm-linux-gcc_2006_link_error.log
Description: Binary data
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
