Jamie Lokier wrote:
> On uClinux with no MMU, you have to use FLT format (all architectures
> support this I think) or FDPIC-ELF (just a few architectures support
> this, the advantage is proper shared libraries and loadable modules).
FRV does not support FLAT format, only FDPIC-ELF.
David
Dear Greg:
>
> It is not extracted, it is mounted and used "in-place"
> using the MTD uclinux.c map driver. It is a RAM based
> MTD setup.
I can duplicate the result on skyeye as you do and I can see my
console output finally.
Thanks everyone's kind help in the past week :-)
right I am trying to
Hi Loody,
loody wrote:
11. cp .
Dear Greg:
Everything seems fine before step 11.
I am trying to find where or how to generate the conf.
Here is what I use:
cpu: arm7tdmi
mach: at91
mem_bank: map=M, type=RW, addr=0x, size=0x4000
mem_bank: map=M, type=RW, addr=0x0100,
> 11. cp .
Dear Greg:
Everything seems fine before step 11.
I am trying to find where or how to generate the conf.
BTW, I previously hand made root file system and pass it to the kernel
which I configured as supporting initramfs. But after seeing what
uclinux done for me, I feel my method is pret
loody wrote:
What target did you use as your base for this?
(What I really want to know is what is set in the
config.arch file).
Regards
Greg
Dear Greg:
I use GDB/armulator.
attach the config and config.arch for your reference.
Thanks for your help,
Here is what I did:
1. downloaded uClinux
> What target did you use as your base for this?
> (What I really want to know is what is set in the
> config.arch file).
>
> Regards
> Greg
Dear Greg:
I use GDB/armulator.
attach the config and config.arch for your reference.
Thanks for your help,
miloody
.config
Description: Binary data
confi
> On Thu, Jan 29, 2009 at 06:12:15AM +, Jamie Lokier wrote:
>> I wouldn't be surprised if the Codesourcery tools (especially
>> pre-built libs) are targetting later ARM chips only, since people
>> using later ARM chips are probably paying Codesourcery for the work.
>
> Our tools support all (po
Hi Loody,
loody wrote:
2009/1/29 Greg Ungerer :
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, yo
Daniel Jacobowitz wrote:
> On Thu, Jan 29, 2009 at 06:12:15AM +, Jamie Lokier wrote:
> > I wouldn't be surprised if the Codesourcery tools (especially
> > pre-built libs) are targetting later ARM chips only, since people
> > using later ARM chips are probably paying Codesourcery for the work.
>
> make[2]: Entering directory `/home/cc/Desktop/temp/uClinux-dist/user/busybox'
> LINKbusybox_unstripped^M
> Trying libraries: crypt m^M
> Failed: -Wl,--start-group -lcrypt -lm -Wl,--end-group
> Output of:
> ucfront-gcc arm-linux-gcc -Os -g -pipe -msoft-float -fno-common -fno-builtin
> -Wall
loody wrote:
> 2009/1/29 Jamie Lokier :
> > loody wrote:
> >>e1a0e00fmov lr, pc
> >>e12fff13bx r3
>
> Actually my cpu get exception when executing this instruction not bx r3.
> But lr is the destination for cpu to write, I have checked the arm
> reference and it doe
2009/1/29 Jamie Lokier :
> loody wrote:
>>e1a0e00fmov lr, pc
>>e12fff13bx r3
>
>> What is the specialty of the instruction, "mov lr,pc", which let
>> arm cpu fail?
>
> Both of those instructions can put the CPU into Thumb mode. If it
> doesn't support Thumb, y
2009/1/29 Greg Ungerer :
> 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
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 f
loody wrote:
>e1a0e00fmov lr, pc
>e12fff13bx r3
> What is the specialty of the instruction, "mov lr,pc", which let
> arm cpu fail?
Both of those instructions can put the CPU into Thumb mode. If it
doesn't support Thumb, you get an instruction fault.
"mov lr
loody wrote:
> When I use "-Wl,-elf2flt,-s32768" to compile my hellow.c.
It should say "-wL,-elf2flt=-s32768". Note the "=" (equal sign).
> b.
> When I use "-Wl,-elf2flt" to compile my hellow.c.
> it will say:
> arm-linux-uclibcgnueabi/bin/ld.real: error: no memory region specified
> for loadabl
> 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-
Quoth loody:
> At beginning, I use the combination you suggest, but uclinux makes me
> cry when I find that the only executable file format that can run on
> uclinux is FLAT.
This is because the other file formats rely on the VMM being able to make
code/data appear at specific addresses.
Without
Hi Loody,
loody wrote:
You are really making things difficult for yourself to start out.
My suggestion, get the uClinux-dist, use the arm-linux compiler
linked from uclinux.org. I specifically use the GDB/ARMulator
target. Build it "as is" and run it on the Skyeye emulator.
Use that as a starti
> You are really making things difficult for yourself to start out.
>
> My suggestion, get the uClinux-dist, use the arm-linux compiler
> linked from uclinux.org. I specifically use the GDB/ARMulator
> target. Build it "as is" and run it on the Skyeye emulator.
> Use that as a starting point.
>
> R
Hi Loody,
loody wrote:
I try 2 another cross-toolchains today.
1. buildroot,
2. arm-uclinux, download from Codesourcery.
The transformation of elf to FLAT of them is quite different.
I get help from buildroot maintainer, so I can build buildroot with
elf2flt successfully.
a.
When I use "-Wl,
2009/1/28 Jamie Lokier :
> loody wrote:
>> "File is not an object file"
>> so, it seems I have to make a object relocation file to let this tool,
>> arm-linux-elf2flt, work.
>> but how?
>
> Don't use the tool directly, use it with GCC as you found:
>
>> 2. I use "-Wl,-elf2flt=-s1024" with arm-linux
loody wrote:
> "File is not an object file"
> so, it seems I have to make a object relocation file to let this tool,
> arm-linux-elf2flt, work.
> but how?
Don't use the tool directly, use it with GCC as you found:
> 2. I use "-Wl,-elf2flt=-s1024" with arm-linux-gcc and it says:
>
> /media/sda6/u
2009/1/27 Jamie Lokier :
> loody wrote:
>> BTW, I also find that if I want uclinux kernel to support ELF binary
>> file, I also have to enable the mmu option.
>> But the format of cross-compiled binary file like busybox is only ELF,
>> if there is option I can add to let busybox and other binary f
loody wrote:
> BTW, I also find that if I want uclinux kernel to support ELF binary
> file, I also have to enable the mmu option.
> But the format of cross-compiled binary file like busybox is only ELF,
> if there is option I can add to let busybox and other binary files
> compiled in different fo
But the format of cross-compiled binary file like busybox is only ELF,
Why do you think so. I do use busybox in a non-MMU arch (NIOS). It is
cross-compiled on a PC using the appropriate "uClinux-distr" tool chain.
The format of the executable file "busybox" is flt.
OTOH I do have another
2009/1/26 Greg Ungerer :
>
> Hi Miloody,
>
> loody wrote:
>>
>> I try to compile kernel with support binfmt_aout.c, CONFIG_BINFMT_AOUT.
>> but it says "fs/binfmt_aout.c:438: error: `TASK_SIZE_26' undeclared
>> (first use in this function)", and I check in asm/memory.h, it only
>> support TASK_SIZE_
Hi Miloody,
loody wrote:
I try to compile kernel with support binfmt_aout.c, CONFIG_BINFMT_AOUT.
but it says "fs/binfmt_aout.c:438: error: `TASK_SIZE_26' undeclared
(first use in this function)", and I check in asm/memory.h, it only
support TASK_SIZE_26 when kernel with mmu support.
Does that m
28 matches
Mail list logo
