From: dony <dony.he@huawei.com.cn>
To: Jeff Millar <jeff@wa1hco.mv.com>,
linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Please help me...
Date: Sat, 01 Jan 2000 16:46:40 +0800 [thread overview]
Message-ID: <386DBEF0.FEFBCEC5@huawei.com.cn> (raw)
In-Reply-To: 001801bf50e1$6d3ad8a0$0201a8c0@home
> When you say the download doesn't work, what do you mean?
When I try to download the "zImage" from TFTP Server to my RAM 0x00200000 on
board,
the download process will stop . That is to say, it cannot download the whole
"zImage" file
but just a part of the "zImage " file. But it I download the "zImage" to my RAM
0x00100000 on
board, it will succeed to download and show a message "starting at
0x00100000..." and halt.
>
>
> How much RAM do you have?
32M.
Notes that I want to download the "zImage" from remote TFTP Server via EHERNET
instead of from local flash .
I have downloaded the FADSROM and 8xxROM packages and researched them.
They all seem to download the "zImage" from local flash disk, not from remote
TFTP server via ETHERNET. I think the latter is easy to debug applications,
right?
Do you think it will make any difference between these two cases?
When I download the "zImage" from remote TFTP server via ethernet to RAM
0x00200000 board , how can I dispose the "zImage" at other address , and when
jumping there it will boot the kernel?
Any ideas?
> Downloading zImage to 2MB should work. You might
> try downloading to 3 or 4MB. You need to download the relocatable kernel
> image (zImage) so that entirely fits in RAM, low enough that the top end of
> zImage and any attached initrd doesn't over flow the top of RAM. The
> bootloader will copy the kernel low using 0x0 and up for its data structures
> and executable. The zImage must not conflict with the kernel executable or
> data structures. Putting the zImage at 0x00100000 is too low. During the
> boot load process, the kernel builds data structures upward in memory
> depending on the size of the kernel and number of options.
>
> Copying the image to flash depends on the hardware and flash ROM chips. You
> will have to write
> a flash ROM erase and writing program. Assuming your board has flash, find
> the data sheet and read up on the write programming algorithm. The zImage
> and initrd can load into ROM and the boot
> loader can execute fromm flash rom.
Sorry, I still don't understand your meaning.
When you say "copy image to flash", what does the image contain?
bootrom codes+kernel+RootFileSystems or kernel+RootFileSystems? If so, in what
file format can I write it into flash?
Best regards,
dony
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-01 8:46 UTC|newest]
Thread overview: 26+ 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
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 [this message]
1999-12-31 8:40 ` dony
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=386DBEF0.FEFBCEC5@huawei.com.cn \
--to=dony.he@huawei.com.cn \
--cc=jeff@wa1hco.mv.com \
--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).