Project stops building after upgrade to Studio 2.6

Log in or register to post comments
Go To Last Post
6 posts / 0 new
Author
Message
mjbcswitzerland
mjbcswitzerland's picture
Level: Hangaround
Joined: Fri. May 1, 2009
Posts: 155 View posts
Location: Switzerland
#1
Posted by mjbcswitzerland: Sat. Oct 16, 2010 - 10:42 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi All

After some fiddling I managed to get a project building with AVR32 studio 2.5 (see https://www.avrfreaks.net/index.p...).

After upgrading to AVR32 studio 2.6 the same project has stopped building (it builds with the same GCC binaries when called from a make file) but it looks as though the compiler (!) encounters an error when the build is controlled by studio:

avr32-gcc -D_HW_AVR32 -D_GNU -Iproject -O0 -march=ucr2 -Wall -Wstrict-prototypes -g -c -Os -mpart=uc3a0512 -oHardware\AVR32\AVR32.o ..\Hardware\AVR32\AVR32.c
..\Hardware\AVR32\AVR32.c: In function 'fnConfigSCI':
..\Hardware\AVR32\AVR32.c:1280: error: insn does not satisfy its constraints:
(insn 56 366 57 14 ..\Hardware\AVR32\AVR32.c:1146 (set (mem:SI (reg:SI 7 r8) [7 S4 A32])
(ior:SI (mem:SI (reg:SI 7 r8) [7 S4 A32])
(const_int 256 [0x100]))) 98 {iorsi3} (nil))
..\Hardware\AVR32\AVR32.c:1280: internal compiler error: in reload_cse_simplify_operands, at postreload.c:395

There have been no configuration changes - the same project builds when commanded from V2.5 but fails with V2.6 (the same error is encountered in various files and the project does build if optimisation is disabled).

What I would really like to know is how the IDE can cause a build to fail when the same GCC binaries work fine otherwise. It must somehow be manipulating the GCC commands but I don't actually see any difference in the command in the Console view.

Does anyone know how to simply force studio to work with an external make file???

Regards

Mark

Tags:

Tools, In-System Debuggers and Programmers
Top
hce
hce's picture
Level: Raving Lunatic
Joined: Tue. Jan 7, 2003
Posts: 4581 View posts
Location: Oslo, Norway
Posted by hce: Sun. Oct 17, 2010 - 12:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When upgrading to AVR32 Studio 2.6, you also installed a new toolchain in the same go... This has already been reported in a thread, weird you didn't find it when you searched this forum ;)

Hans-Christian

Top
mjbcswitzerland
mjbcswitzerland's picture
Level: Hangaround
Joined: Fri. May 1, 2009
Posts: 155 View posts
Location: Switzerland
Posted by mjbcswitzerland: Sun. Oct 17, 2010 - 03:19 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi

Thanks. I added an avr32-gcc -v command as pre-build step to display the GCC version being used.

V2.5 is using the chain in the original folder (outside of the AVR32 studio installation folders) [gcc version 4.3.2. (atmel-1.2.0-(mingw32_special))] and V2.6 is using a chain stored in one of the plug-in folders (inside its installation folders [gcc version 4.3.3 (AVR Toolchain_3.0_123].

This means that the new gcc version is failing to build some c-files.

I am sorry but I didn't find the original report of this fact and I have just spent some time searching for various reports and reading through posts but still haven't been able to locate it - could you give a link to this other thread containing the info?

Furthermore is there any way to get Studio to use the old tool chain? I have been playing around in the tool chain settings but it looks as though it doesn't allow it to be changed (maybe it needs the old chain as a plug-in?). If not I suppose one must downgrade until the compile bug is solved(?)

Regards

Mark

Top
torkildr
torkildr's picture
Level: Hangaround
Joined: Mon. Aug 7, 2006
Posts: 300 View posts
Location: Trondheim, Norway
Posted by torkildr: Tue. Oct 19, 2010 - 08:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

mjbcswitzerland wrote:

Furthermore is there any way to get Studio to use the old tool chain? I have been playing around in the tool chain settings but it looks as though it doesn't allow it to be changed (maybe it needs the old chain as a plug-in?). If not I suppose one must downgrade until the compile bug is solved(?)

Sure. That's a topic in the release notes.

Top
mjbcswitzerland
mjbcswitzerland's picture
Level: Hangaround
Joined: Fri. May 1, 2009
Posts: 155 View posts
Location: Switzerland
Posted by mjbcswitzerland: Sat. Oct 23, 2010 - 08:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi

The release notes explain about the toolchain being integrated and that it needs to be uninstalled if a different one is to be used.

It also instructs where this is done. However in the "AVR Studio Installation Details" the "AVR Toolchains" entry can be selected but only the "Properties" button becomes active. The "Uninstall.." button remains inactive and so the Uninstall can not be started.(This is true for all plugins - also the "Upgrade.." button is inactive (grayed out)).

Is this a problem with my installation or generally with V2.6?

Are there any other ways of uninstalling?

Regards

Mark

Top
mjbcswitzerland
mjbcswitzerland's picture
Level: Hangaround
Joined: Fri. May 1, 2009
Posts: 155 View posts
Location: Switzerland
Posted by mjbcswitzerland: Sat. Jan 1, 2011 - 11:29 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi All

OK, it took about 2 months but it was finally possible to uninstall the new tool chain (thanks for the tip from Uwe in Germany) from a Windows 7 PC.

When starting AVR32 studio it is necessary to start it as administrator (click on the AVR32 symbol and then right click to get the context menu - then issue the command to start as administrator). Then the uninstall buttons are no longer greyed out and the tool chain and utilities can be uninstalled.

After this it was possible to compile the project with optimisation enabled with the older tool chain without the compiler crashing - the crash has been reported to the GCC developers.

Regards

Mark

Top