Hi WSL,

Shuanglin Wang wrote:
I'm porting uClinux to our board based on ARM946E-S. Now, I generated an uncompressed uClinux kernel image and romfs (txt+data+romfs) with command like:
cat image.txt image.data romfs > image.bin

And objdumping results like:

===================================================================================
 >arm-elf-objdump -h linux-2.6.x/linux

linux-2.6.x/linux:     file format elf32-littlearm

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
 0 .init         0000c000  00008000  00008000  00008000  2**5
                 CONTENTS, ALLOC, LOAD, CODE
 1 .text         000a5384  00014000  00014000  00014000  2**5
                 CONTENTS, ALLOC, LOAD, READONLY, CODE
 2 .pci_fixup    00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 3 .rio_route    00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 4 __ksymtab     00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 5 __ksymtab_gpl 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 6 __ksymtab_unused 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 7 __ksymtab_unused_gpl 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 8 __ksymtab_gpl_future 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
 9 __kcrctab     00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
10 __kcrctab_gpl 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
11 __kcrctab_unused 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
12 __kcrctab_unused_gpl 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
13 __kcrctab_gpl_future 00000000  000ba000  000ba000  000d7500  2**0
                 CONTENTS
14 __param       00000050  000ba000  000ba000  000ba000  2**2
                 CONTENTS, ALLOC, LOAD, READONLY, DATA
15 .data         0001b500  000bc000  000bc000  000bc000  2**5
                 CONTENTS, ALLOC, LOAD, DATA
16 .bss          0000a2a0  000d7500  000d7500  000d7500  2**5
                 ALLOC
17 .comment      000010f2  00000000  00000000  000d7500  2**0
                 CONTENTS, READONLY
============================================================================

Instead of a standard Linux bootloader. Our board has a simple bootloader, which can

1. Copy image to some place in main memory;
2. Transfer the control to kernel.

My questions are:
  Where should I put the uClinux kernel at 0x00008000 in the main memory?

Yes, this would be consistent with the why the ARMulator sections are
setup and run.


  Do I need to make some changes on our bootloader for booting uClinux?

Probably not. The uClinux startup is pretty simple, typically you
just need to get the kernel into RAM and start executing it.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     [EMAIL PROTECTED]
Secure Computing Corporation                PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com
_______________________________________________
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

Reply via email to