From: "Swiger, Dan" <Dan.Swiger@drs-ss.com>
To: "'binutils@sourceware.org'" <binutils@sourceware.org>
Subject: nios-elf-objcopy S-record length
Date: Thu, 24 Feb 2005 05:41:00 -0000 [thread overview]
Message-ID: <2C52593826C4D611A69F00508B60303F0281CF31@aego_exch1.sigp.net> (raw)
I am currently working with a GNU tool chain obtained from Altera for
the NIOS processor. Here is the version information obtained from a
'nios-elf-objcopy -V' command:
<start>
GNU objcopy 2.9-nios-010801-20030722
Copyright 1997, 1998, 1999 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
<end>
I am currently having a problem of objcopy making S-Records with 21 data
bytes in them and am looking for a solution (21 bytes will be *very*
inconvenient when I go to use these to FLASH a 16-bit device). On a
redirect from someone, I have been browsing the archives of this mailing
list and found an apparent patch for objcopy that would fix my problem.
Here are the references to the messages I found:
http://sourceware.org/ml/binutils/2000-09/msg00321.html
http://sourceware.org/ml/binutils/2000-03/msg00346.html
http://sourceware.org/ml/binutils/2000-03/msg00416.html
http://sourceware.org/ml/binutils/2000-03/msg00427.html
Can someone please tell me if/how I can apply this patch to my version
of objcopy so that I may get 16-byte S-Records generated and ease my
life considerably? Or is there just a switch I need to activate that is
not documented in 'nios-elf-objcopy -h' that I can use already?
Thanks,
Dan
next reply other threads:[~2005-02-23 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 5:41 Swiger, Dan [this message]
2005-02-25 15:58 ` Nick Clifton
[not found] <1109267032.5342.ezmlm@sources.redhat.com>
2005-02-24 19:38 ` E. Weddington
2005-02-24 20:06 Swiger, Dan
2005-02-24 20:06 ` E. Weddington
2005-02-24 20:36 Swiger, Dan
2005-02-24 21:05 ` Daniel Jacobowitz
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=2C52593826C4D611A69F00508B60303F0281CF31@aego_exch1.sigp.net \
--to=dan.swiger@drs-ss.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).