From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: binutils-2.9 objcopy fails (fwd)
Date: Tue, 14 Apr 1998 12:49:00 -0000
Message-id: <Pine.BSF.3.96.980414142247.1247Q-100000@vespucci.advicom.net>
X-SW-Source: 1998/msg00120.html

A failure in m68k-rtems objcopy.

--joel


---------- Forwarded message ----------
Date: Tue, 14 Apr 98 13:20:47 -0600
From: Eric Norum <eric@skatter.USask.Ca>
To: rtems-snapshots@oarcorp.com
Subject: binutils-2.9 objcopy fails

I downloaded and installed the latest binutils.  Now I can't  
generate prom images any more.

Background:
I've got two types of 68360 systems here.  One uses a single 8-bit  
bootstrap prom and the other uses 4 8-bit bootstrap proms as a 32-bit  
prom.  I use a script to generate the S-record images for my prom  
burner.

Here are the salient lines from the script:

m68k-rtems-objcopy --output-target=srec prom.exe prom.hex

for byte in 0 1 2 3
do
        m68k-rtems-objcopy --interleave=4 --byte=$byte  
--output-target=srec prom.exe prom$byte.hex
done


Problem:
The first objcopy works fine to build the 8-bit bootstrap prom  
image, but when I try to split the executable into the 4 images for  
the 32-bit prom, I get:

+ m68k-rtems-objcopy --output-target=srec prom.exe prom.hex
+ m68k-rtems-objcopy --interleave=4 --byte=0 --output-target=srec  
prom.exe prom0.hex
m68k-rtems-objcopy: prom0.hex: Invalid operation


Any ideas?
---
Eric Norum                                 eric@skatter.usask.ca
Saskatchewan Accelerator Laboratory        Phone: (306) 966-6308
University of Saskatchewan                 FAX:   (306) 966-6058
Saskatoon, Canada.