linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: greenlean <jmgomez@atc.ugr.es>
To: linuxppc-embedded@ozlabs.org
Subject: Generated xilinx linux 2.6  image sections
Date: Mon, 21 Jan 2008 05:05:40 -0800 (PST)	[thread overview]
Message-ID: <14997109.post@talk.nabble.com> (raw)


Hi all, 

I'm trying to boot the 2.6 xilinx kernel downloaded from their git server in
the XUPV2P board I'm really having troubles (I can't see anything in the
minicom console terminal). I'm not seeing anything, neither the ucompressing
kernel string nor the prompt with the memory addresses that kernel prompt at
first time, so I have started to distrust of anything. 

When I download the kernel using xmd, I see:

XMD% dow imagen_UART16550_ml300.elf
        section, .text: 0x00400000-0x0040387b
        section, .data: 0x00404000-0x004e6fff
        section, .bss: 0x004e7000-0x004e919f
Downloaded Program imagen_UART16550_ml300.elf
Setting PC with Program Start Address 0x00400000

and when I download some of the TestApp generated by EDK I see:

XMD% dow perif.elf
        section, .vectors: 0xfffe0000-0xfffe20c3
        section, .text: 0x10000000-0x10003b7b
        section, .init: 0x10003b7c-0x10003b9f
        section, .fini: 0x10003ba0-0x10003bbf
        section, .boot0: 0xfffe20c4-0xfffe20d3
        section, .boot: 0xfffffffc-0xffffffff
        section, .rodata: 0x10003bc0-0x10004111
        section, .sdata2: 0x10004114-0x10004113
        section, .sbss2: 0x10004114-0x10004113
        section, .data: 0x10004114-0x10004243
        section, .got: 0x10004244-0x10004243
        section, .got1: 0x10004244-0x10004243
        section, .got2: 0x10004244-0x1000425f
        section, .ctors: 0x10004260-0x10004267
        section, .dtors: 0x10004268-0x1000426f
        section, .fixup: 0x10004270-0x1000426f
        section, .eh_frame: 0x10004270-0x10004277
        section, .jcr: 0x10004278-0x1000427b
        section, .gcc_except_table: 0x1000427c-0x100042
        section, .sdata: 0x1000427c-0x10004293
        section, .sbss: 0x10004294-0x100042a3
        section, .bss: 0x100042a4-0x10004473
        section, .stack: 0x10004474-0x1000647f
        section, .heap: 0x10006480-0x1000847f
Downloaded Program perif.elf
Setting PC with Program Start Address 0xfffffffc

Does anybody know why the kernel elf don't have a boot section like the
TestApp generated by EDK?

I suppossed this is because the image kernel is compressed, but despite
beeing compressed it should have a boot section or something similar ??? 
It's right that the kernel start address is set to the 0x00400000??

Or does the section .text  contains all the kernel code to uncompresse the
code of the kernel??



-- 
View this message in context: http://www.nabble.com/Generated-xilinx-linux-2.6--image-sections-tp14997109p14997109.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

             reply	other threads:[~2008-01-21 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 13:05 greenlean [this message]
2008-01-21 17:16 ` Generated xilinx linux 2.6 image sections Grant Likely
2008-01-21 18:45 ` Stephen Neuendorffer
2008-01-22  9:30   ` greenlean
2008-01-22 13:28     ` greenlean
2008-01-22 17:40       ` Stephen Neuendorffer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14997109.post@talk.nabble.com \
    --to=jmgomez@atc.ugr.es \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).