Error loading object file (Dragon)

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am getting this error when trying to open an .elf file with AVR Studio 4.18 build 700. After opening, I see the green bar growing while "loading program in memory".

After this I can retry to open and send again with no luck.

I can program the .elf file directly with the connection dialog but only after restarting AVR Studio, because the connection dialog keeps coming back after "loading program in memory".

My elf is compiled using avr gcc 4.3.4 on debian. I am trying to migrate from Arduino via command line compiling to debugging with AVR studio.
[edit] cpu=atmega32

Can anybody shine a light on these issues?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

My elf is compiled using avr gcc 4.3.4 on debian.

Did you get the .deb here:

www.wrightflyer.co.uk/avr-gcc/

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

Did you get the .deb here:

www.wrightflyer.co.uk/avr-gcc/

I think not, my avr-gcc is in /usr/bin/avr-gcc. I probably used a debian repository. I'll take your question as an advice and see what happens when I use that package.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

uhm...
After installing gcc-avr 4.3.4 my system now wants a glibc-2.11-1. This means upgrading a whole lot of other packages as well. I am running Debian and try to keep it stable (with an occasional package from testing if needed). Is this the preferred way to go or should I downgrade to a lower revision of avr-gcc?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Drop back to one of the earlier versions on that page. In fact I think there was one built "static" that should have no external library requirements.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

the gcc 4.3.3 dated 25 feb 2010 does compile into an elf that AVR studio will read. Because my elf and sources lie on a samba server I than have to go through 18 slow dialogs to change drive mappings for libraries etc.
I think I will have to consider moving the whole stuff over to Windows.

Thanks for the helpfull hints anyway.