From: Charles Lepple <clepple@mitre.org>
To: dony <dony.he@huawei.com.cn>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Please help me...
Date: Thu, 30 Dec 1999 08:25:29 -0500 [thread overview]
Message-ID: <386B5D49.DF7A9095@mitre.org> (raw)
In-Reply-To: 386AFFC5.E0134DB8@ctam.com.au
Brendan J Simon wrote:
> > Sections:
> > Idx Name Size VMA LMA File off Algn
> > 0 .text 00004870 ff801000 ff801000 00001000 2**2
> > CONTENTS, ALLOC, LOAD, READONLY, CODE
> > 1 .rodata 00000470 ff805870 ff805870 00005870 2**4
> > CONTENTS, ALLOC, LOAD, READONLY, DATA
> > 2 .data 00000300 ff806000 ff806000 00006000 2**2
> > CONTENTS, ALLOC, LOAD, DATA
> > 3 .bss 0000bbac ff807000 ff807000 00007000 2**2
> > ALLOC
> > 4 image 00061104 ff807000 ff807000 00007000 2**0
> > CONTENTS, ALLOC, LOAD, DATA
^^^^^^^ This section (image) could be your problem if you use a
vxWorks bootloader.
Although the vxWorks loader is written with ELF images in mind,
experience (with a DY4 SVME-177 board) tells me that it ignores ELF
sections that would not be present in a vxWorks executable. I did not
have time to investigate this completely, but the indication that tipped
me off was that the sizes of the sections added up to be much larger
than the sum of the numbers that the boot loader reports. All other test
programs (those without added sections) were loaded correctly.
If the sum of the numbers printed on the screen is significantly less
than the size of the file, then you can assume that anything you need to
load should be in either '.text' or '.data'. If you have the whole
vxWorks toolchain, you can try to find out what other section names are
used in executables loaded by the bootloader (maybe a debugging
section?), or you can work on building a special zImage file.
You can get around this limitation by having the zipped kernel image
inserted directly into the data segment of a wrapper program (see
arch/ppc/chrpboot/, especially piggyback.c).
--
Charles Lepple
clepple@mitre.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-30 13:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-31 2:29 Please help me dony
1999-12-27 8:42 ` Raphael Bossek
2000-01-02 7:23 ` dony
1999-12-30 2:11 ` Brendan J Simon
[not found] ` <38701F3A.FAD6263E@huawei.com.cn>
1999-12-30 4:23 ` Brendan J Simon
[not found] ` <38704D0B.94438516@huawei.com.cn>
1999-12-30 6:46 ` Brendan J Simon
1999-12-30 13:25 ` Charles Lepple [this message]
2000-01-03 11:48 ` Cannot booting the kernel dony
2000-01-04 0:46 ` Brendan J Simon
[not found] ` <38715DAE.B6CBC772@huawei.com.cn>
[not found] ` <3871572F.FA4E7842@ctam.com.au>
[not found] ` <38717C52.ECF1AFFD@huawei.com.cn>
[not found] ` <3871953B.345DDA23@ctam.com.au>
[not found] ` <38754F28.B6B4CE70@huawei.com.cn>
[not found] ` <38754419.20D95C5A@ctam.com.au>
[not found] ` <3876A6E5.3488738B@huawei.com.cn>
[not found] ` <3876C6FD.794BD1BF@ctam.com.au>
[not found] ` <387A87DF.4ED23CA6@huawei.com.cn>
[not found] ` <387A81F3.702B29A2@ctam.com.au>
[not found] ` <387C4D8D.9C058F1C@huawei.com.cn>
[not found] ` <387D3212.A4E9904F@ctam.com.au>
2000-01-13 7:10 ` Cross-compile Applications for 860 on x86 dony
2000-01-13 22:09 ` Brendan J Simon
[not found] ` <387DAFAF.DB0096C7@huawei.com.cn>
[not found] ` <387E460F.B007CE56@ctam.com.au>
[not found] ` <387E7F82.99AF83CE@huawei.com.cn>
[not found] ` <387E7AF5.A92A6122@ctam.com.au>
[not found] ` <387E9927.48689C08@huawei.com.cn>
[not found] ` <387EBEB9.B69B1680@ctam.com.au>
2000-01-14 8:31 ` dony
2000-01-14 11:01 ` Wolfgang Denk
[not found] ` <387F0D81.48F7CABE@iname.com>
2000-01-14 17:13 ` Wolfgang Denk
[not found] ` <38827CD5.D7A44261@huawei.com.cn>
2000-01-17 3:56 ` Jim Lewis
2000-01-17 3:26 ` dony
2000-01-17 4:35 ` Jim Lewis
2000-01-16 2:01 ` Brendan J Simon
[not found] ` <388ABF55.5BD3A031@eng.uct.ac.za>
[not found] ` <388B9C86.8970590A@ctam.com.au>
[not found] ` <388BA902.B41A2E11@huawei.com.cn>
2000-01-24 3:00 ` Cross-compile dynamic apps for mpc860 on ix86 Brendan J Simon
2000-01-24 5:03 ` Wolfgang Denk
2000-01-24 6:46 ` dony
2000-01-24 8:02 ` Wolfgang Denk
[not found] ` <000401bf5016$4757c420$0201a8c0@home>
1999-12-31 8:37 ` Please help me dony
[not found] ` <000c01bf5086$3e358d80$0201a8c0@home>
2000-01-01 1:58 ` dony
[not found] ` <001801bf50e1$6d3ad8a0$0201a8c0@home>
2000-01-01 8:46 ` dony
1999-12-31 8:40 ` dony
2003-09-19 8:55 please " Vijay Angelo
2003-09-19 9:45 ` Arvanitis Kostas
2004-03-30 9:48 Sofia Pujeh
2006-04-24 10:11 Tu Ha
2006-04-24 4:11 ` Frank Kotler
2006-04-24 12:09 ` Tu Ha
[not found] <000101c6734a$573086d0$c41e1ec7@TuThuyHa>
2006-05-09 16:17 ` Frank Kotler
2006-05-10 14:05 ` httu
2006-08-28 12:30 Please " Kumar, Satish B
2006-08-28 14:30 ` Mouhammad Tayseer Alquoatli
2007-01-05 8:01 Debasree Mallick
2007-01-05 8:04 ` Justin Patrin
2007-01-05 8:14 ` Debasree Mallick
2007-01-05 8:43 ` Matthew Palmer
2007-01-05 8:54 ` Marcin Juszkiewicz
2007-01-10 7:13 ` Debasree Mallick
2007-01-11 0:17 ` Justin Patrin
2009-12-21 9:15 please " rajkumar
2009-12-21 10:48 ` Emmanuel Florac
2011-11-26 6:49 Please " shibin k reeny
2014-08-20 15:20 PLEASE HELP ME mrissouf issouf
2014-08-20 15:53 Abdoul Issouf
2014-09-10 12:01 Please Help Me Alina Yukov
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=386B5D49.DF7A9095@mitre.org \
--to=clepple@mitre.org \
--cc=dony.he@huawei.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.