[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with objcopy IEEE-695 support
From: |
Nick Clifton |
Subject: |
Re: problem with objcopy IEEE-695 support |
Date: |
Fri, 02 Mar 2007 07:39:36 +0000 |
User-agent: |
Thunderbird 1.5.0.9 (X11/20061215) |
Hi John,
I have a problem with binutils-2.17 objcopy, and IEEE-695 support.
Have you tried building a set of the binutils from the current head of
the mainline sources of the binutils CVS repository ?
I am trying to use objcopy to convert an ELF file from Tasking VX 2.1r1
toolchain for the Infineon c16x into an IEEE-695 format for use with an
earlier Tasking debugger.
As far as I know we do not currently support the Tasking XV, so
presumably you did not generate the ELF binary using GNU tools, is that
correct ?
Machine: <unknown>: 74
This appears to confirm my hypothesis.
objcopy -I ieee -O ieee myproj_0.abs myproj_1.abs
/binutils-2.17/binutils/objcopy: myproj_0.abs: File format not recognized
Why do you perform the second objcopy ? Why not just run a command like
"objdump -p myproj_0.abs" ?
I suspect this happens with almost any elf->abs->abs conversion.
I tried to reproduce this locally and the objcopy's worked for me (both
of them). I was however using an elf32-littlearm format input file.
Anyway there must be more to this than just a simple conversion to
IEEE-695 format. It is probably due to the nature of the myproj.elf
input file and the generic elf32-little file format.
When I have attached my example files the email has been rejected.
Probably due to size or possible viral load. Did you try putting them
into a compressed tar ball or zip file ? Anyway, the best way to
proceed with this problem is for you to open a new binutils bug report
(at http://www.sourceware.org/bugzilla/). You should be able to upload
the file needed to reproduce the problem there, thus avoiding any email
weirdness.
Cheers
Nick