From: "Mynampati, Venkata S." <MynamVS@nsc-msg01.network.com>
To: "'Gary Thomas'" <gthomas@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Unable to load srec files via serial port
Date: Tue, 24 Jul 2001 16:21:00 -0000 [thread overview]
Message-ID: <A7E1C26945C8D211ADBF0008C709661A035F2AF8@nsc-msg02.network.com> (raw)
On 24-Jul-2001 Mynampati, Venkata S. wrote:
> >> >
> >> > i use this command "load -m ymodem -r -b 0xa1000000".
> >> > Is there any size limitation for x/y modem upload?
> >>
> >> If this is a Motorola S-record file, you probably do not want "-r"
> >>
> >> If it fails for large files, perhaps you are running out of memory.
i stopped using '-r' while uploading for SREC files, but still
after about 1147K, the transfer stops. Windows's Hyper terminal's
'send file' window displays 'no response from remote system'.
The interesting thing is, i used visionclick's probe to peep into
RAM areas. What i found is like this:
ram locations starting from 0xa0308000 to 0xa037138A are good,
i.e they correspond to vmlinux.srec file's contents, but location
0xa037138b onwards it is zero.
Also, RedBoot hangs after this upload fails, but if i cancel upload,
RedBoot works.
I think, the upload process uses some RAM locations which i am
overwriting.is this true ? have you seen this behaviour? what is
happening here and how to over come it? or is there anything i
missed.
Your help is appreciated.
Regards
Venkat
next reply other threads:[~2001-07-24 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 16:21 Mynampati, Venkata S. [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-24 9:45 Mynampati, Venkata S.
2001-07-24 10:01 ` Gary Thomas
2001-07-24 7:36 Mynampati, Venkata S.
2001-07-24 7:48 ` Gary Thomas
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=A7E1C26945C8D211ADBF0008C709661A035F2AF8@nsc-msg02.network.com \
--to=mynamvs@nsc-msg01.network.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).