From: Wolfgang Denk <wd@denx.de>
To: "Kwansuk Kim" <kskim@neowave.co.kr>
Cc: "jinoung kim" <jinoung@mail.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: omitted kernel sections
Date: Mon, 26 Jun 2000 10:08:59 +0200 [thread overview]
Message-ID: <200006260808.KAA23698@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 26 Jun 2000 15:43:35 +0900." <NEBBKFENMLEDKDHMEHPJKEMECAAA.kskim@neowave.co.kr>
In message <NEBBKFENMLEDKDHMEHPJKEMECAAA.kskim@neowave.co.kr> Kwansuk
Kim wrote:
>
> when I was following the procedure : initialize console on SMC2, memory allocation for kernel and ramdisk...
> there was a problem. The compressed kernel image wasn't loaded. So the procedure stopped on gunzip process.
Which version of Linux are you using?
> I use AMC BDM port, and I speculate the messages.
>
> It's the message when kernel is loaded.
>
> ---------------------------------------
> > LOAD 'c:\860source\zvmlinux.initrd'
> Warning: symbols deleted - check use in macros etc.
> Loading section '.text' located at 0x00400000..0x004046E4
> Loading section '.rodata' located at 0x004046F0..0x00404B90
> Loading section '.data' located at 0x00405000..0x0040530C
> Loading section '.bss' located at 0x00406000..0x0040B1F0
> Warning:
> 'main' function not found in file: c:\860source\zvmlinux.initrd
> Note: in startup routine. Enter STEP to go to High-level module.
It seems your debugger loads only the boot loader code, but neither
the kernel nor the initrd.
> This is the section map through the command 'objdump -h zvmlinux.initrd'
>
> --------------------
> zvmlinux.initrd: file format elf32-big
>
> Sections:
> Idx Name Size VMA LMA File off Algn
> 0 .text 000046e4 00400000 00400000 00010000 2**2
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 1 .rodata 000004a0 004046f0 004046f0 000146f0 2**4
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 2 .data 0000030c 00405000 00405000 00015000 2**2
> CONTENTS, ALLOC, LOAD, DATA
> 3 .bss 000051f0 00406000 00406000 00016000 2**2
> ALLOC
> 4 .image 00064605 00000000 00000000 00016000 2**0
> CONTENTS, READONLY
> 5 .initrd 00201d19 00000000 00000000 0007a605 2**0
> CONTENTS, READONLY
>
> Why weren't .image, .initrd section loaded? Because they aren't elf format file?
Most probably because your debugger loads only such sections that
have the "LOAD" flag set.
> What can I do? I haven't any idea.
There are several solutions; for instance, use objcopy to set the
"LOAD" flag on the '.image' and '.initrd' sections, too.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
If programming was easy, they wouldn't need something as complicated
as a human being to do it, now would they?
- L. Wall & R. L. Schwartz, _Programming Perl_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-26 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 0:53 I am looking for 8xxrom with ethernet(TFTP) jinoung kim
2000-06-26 6:43 ` omitted kernel sections Kwansuk Kim
2000-06-26 8:08 ` Wolfgang Denk [this message]
2000-06-26 12:48 ` Jerry Van Baren
2000-06-26 14:40 ` Murray Jensen
2000-06-26 15:18 ` Steven Tarr
2000-06-26 15:46 ` Jerry Van Baren
2000-06-26 16:04 ` Wolfgang Denk
2000-06-26 16:40 ` Jerry Van Baren
2000-06-26 21:57 ` Dan Malek
2000-06-27 13:42 ` Frank Przybylski
2000-06-26 8:18 ` Matt Porter
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=200006260808.KAA23698@denx.local.net \
--to=wd@denx.de \
--cc=jinoung@mail.com \
--cc=kskim@neowave.co.kr \
--cc=linuxppc-embedded@lists.linuxppc.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).