From: Alan Modra <alan@linuxcare.com.au>
To: russell@webaxs.net
Cc: binutils@sourceware.cygnus.com
Subject: Re: What won't this objcopy split work?
Date: Fri, 21 Jul 2000 20:49:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0007221302020.30258-100000@front.linuxcare.com.au> (raw)
In-Reply-To: <200007211744.KAA03363@elmo.cygnus.com>
On Fri, 21 Jul 2000, Nick Clifton wrote:
> Hi Russel,
>
> : I'm producing code for a 16-bit h8/300h cpu, and want to
> : generate an srec file for all the even bytes, and an srec
> : file for all the odd bytes, using objcopy:
> :
> : h8300-hms-objcopy --output-target=srec --interleave=2
> : --byte=1 flash.coff flodd.srec
> :
> : However, it responds with flodd.srec: illegal operation
> :
> : What can be wrong?
>
> I am not sure. I was able to run the same command (admittedly with a
> different input file) on my test machine and it gave me no problems.
> Also when I searched through the sources I could not find the 'illegal
> operation' error message anywhere!
Sounds like the message is coming from the operating system then.
Russell, you said you're running Linux, but what platform, and what
version of libc? Also, what type of filesystem is flodd.srec on?
If it's NFS, try doing the objcopy on a local filesytem instead.
Alan Modra
--
Linuxcare. Support for the Revolution.
next prev parent reply other threads:[~2000-07-21 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 10:44 Nick Clifton
2000-07-21 20:49 ` Alan Modra [this message]
2000-07-22 23:23 ` Where can i find asm operand constraints? Russ.Shaw
2000-07-24 10:06 ` Michael Meissner
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 1:05 What won't this objcopy split work? Russ.Shaw
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=Pine.LNX.4.21.0007221302020.30258-100000@front.linuxcare.com.au \
--to=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=russell@webaxs.net \
/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).