AVR Studio 6, unresolved aliases... wtf

Log in or register to post comments
Go To Last Post
2 posts / 0 new
Author
Message
gibbon
gibbon's picture
Level: Wannabe
Joined: Thu. Oct 7, 2004
Posts: 75 View posts
#1
Posted by gibbon: Tue. Jan 15, 2013 - 11:08 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm newish to AVR Studio 6. For a long time I've been compiling my code under WinAVR + Codelite and debugging with AVR Studio 4. Now I'm trying to use VS6 and JtagIce3. But continuing to use CodeLite for Editing/Building.

I've noticed one thing I dislike enough to mention. Other that the version I first installed would give me, an error 'can't create project'. The newer version appears to workish.

When I start debugging I get the File Alias Pane (which can't be re-sized WTF? Seriously?), but it has unresolved files this in it.

When using the the tool chain that comes with VS6, I get stuff like this.

C:\home\tools\hudson\workspace\avr8-gnu-toolchain\build-win32_x86\avr-gcc-full\gcc\fp-bit.c

When Using the last version of WinAVR I got a bunch of unresolved files like below.

C:\Program Files (0x86)\Atmel\Atmel Studio 6.0\cli\cli_user.h

Where cli\cli_user.h us one of my source files.

Any idea why this happens?

Tags:

Tools, Atmel Studio (AVR-related)
Top
Gold Markclawson
clawson's picture
Level: Moderator
Joined: Mon. Jul 18, 2005
Posts: 100675 View posts
Location: (using avr-gcc in) Finchingfield, Essex, England
Posted by clawson: Wed. Jan 16, 2013 - 09:03 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well the first one is a build error on Atmel's part. They mistakenly built library code with -g and then did not use avr-strip -g at the end to remove it. The way source level debugging works is that it does not include actual C code in the object file but instead just the name of the file and a line number. That works fine on your own machine with the code you build as the debugger just finds and opens the file and reads the line. But you don't have the fp-bit.c file used for their library code. The solution is to locate the .a library file where fp-bit.o is located and use avr-strip -g on it.

As for the .h issue, I'm afraid that's just a limit of DWARF2, you won't get source annotation for static inline code from .h files.

Top