All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Lewis <jlewis@mvista.com>
To: LiuTao <tliu@ict.ac.cn>
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
	"linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problem with gunzip()
Date: Mon, 10 Jan 2000 09:25:26 -0600	[thread overview]
Message-ID: <3879F9E6.EF018D4E@mvista.com> (raw)
In-Reply-To: 38799BA3.269E8869@ict.ac.cn


Hi,

I have had a problem such as yours that was caused by corruption in the
compressed s-record image once it was on the target. I had thought that
Gunzip would catch this, but it did not. How is your image being
transmitted to the target? Is it over a serial link? In my case, the
S-record loader was not checking checksums and occasionally, a serial
transmission error went undetected. Gunzip did not complain, but the
uncompressed image would end up being skewed by a few bytes.
Hope this helps.


LiuTao wrote:

> Hi
>
> When I ported linux to a board with MPC860, 16M RAM and 2M Flash,
> I met a problem.
> After the program gunzip()(misc.c) the vmlinux image to address 0x0,
> the contents from 0x0 to IMAGE_SIZE should be as same as that in
> linux/vmlinux, right? I found that they are not same. Only from 0x0
> to about 0xb500, they are same.
> I don't think gunzip() has any problem.
> Do you have any suggestions?
> Thanks!
>
> LiuTao

--
Jim Lewis
Sr. Field Applications Engineer
MontaVista Software, Inc.
(817)261-9088 http://www.mvista.com


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-10 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-10  8:43 problem with gunzip() LiuTao
2000-01-10 15:25 ` Jim Lewis [this message]
2000-01-11  0:37   ` LiuTao

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=3879F9E6.EF018D4E@mvista.com \
    --to=jlewis@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=tliu@ict.ac.cn \
    /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.