objcopy produces "Invalid bfd target" error

support for the ARM toolchain
Post Reply
kleptophobiac
Posts: 2
Joined: Thu Aug 02, 2012 7:42 am

objcopy produces "Invalid bfd target" error

Post by kleptophobiac » Thu Aug 02, 2012 7:46 am

I'm trying to use devkitarm with gnuarm within eclipse on windows. Oddly, the only step which appears to be failing is the part where objcopy prints out section sizes in the binary.

Unfortunately, I have no idea why. I've used this configuration in the past. Admittedly, I had to change a bunch of configuration parameters to reflect the new tuplet (shakes fist), but this doesn't appear to be related.

Any help is much appreciated!

Code: Select all

23:43:27 **** Build of configuration Debug for project pdc ****
make all 
Building file: ../main.c
Invoking: ARM devkitPro Windows GCC C Compiler
arm-none-eabi-gcc -O0 -Wall -Wa,-adhlns="main.o.lst" -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "main.o" "../main.c"
Finished building: ../main.c
 
Building target: pdc.elf
Invoking: ARM devkitPro Windows GCC C++ Linker
arm-none-eabi-g++ -Xlinker --gc-sections -Wl,-Map,pdc.map -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "pdc.elf"  ./main.o   
Finished building target: pdc.elf
 
Invoking: ARM devkitPro Windows GNU Create Flash Image
arm-none-eabi-objcopy -O ihex pdc.elf  "pdc.hex"
Finished building: pdc.hex
 
Invoking: ARM devkitPro Windows GNU Create Listing
arm-none-eabi-objcopy -h -S pdc.elf > "pdc.lst"
Finished building: pdc.lst
 
Invoking: ARM devkitPro Windows GNU Print Size
arm-none-eabi-objcopy  --format=berkeley pdc.elf
c:\devkitPro\devkitARM\bin\arm-none-eabi-objcopy.exe:pdc.elf: Invalid bfd target
make: *** [pdc.siz] Error 1

23:43:27 Build Finished (took 772ms)

kleptophobiac
Posts: 2
Joined: Thu Aug 02, 2012 7:42 am

Re: objcopy produces "Invalid bfd target" error

Post by kleptophobiac » Tue Aug 07, 2012 5:16 pm

In the days since this post, I discovered that the problem only exists in the newest build of devkitarm. If I switch to the immediately previous build everything works great.

Also does anyone know when the gnuarm eclipse plugin might recognize the tuplet change? Editing all of the tool names for every new project is a pain and is driving me to just write my own makefiles. It's not a huge problem but it would make life better.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest