EVK1101 / UC3B0256ES and AVR Studio 2.1.0 compile issue

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

I am trying to compile the 'ControlPanelDemo' using my EVK1101 as the target. The board has a UC3B0256ES on it. I am using the provided example code.

Now, if I set the chip to be a UC3B0256, then it compiles fine but won't download. If I set it as a UC3B0256ES (which is what the JTAGICE mkII reports, as well as the label on the chip), then I get a compile error:

'AVR32_GPIO_LOCAL' undeclared (first use in this function) gpio.h ControlPanelDemo/src/SOFTWARE_FRAMEWORK/DRIVERS/GPIO 493 C/C++ Problem

First obvious swing at this is to find the definition in the 0256' file, insert it into the 0256ES' file.

#define AVR32_GPIO_LOCAL_ADDRESS 0x40000000
#define AVR32_GPIO_LOCAL (*((volatile avr32_gpio_local_t*)AVR32_GPIO_LOCAL_ADDRESS))

Now other other errors occur. Before I start chasing this down the rathole, I thought I would ask. Is this a known problem? Am I going to get this to work, or am I wasting time?

I have just downloaded all new software from the AVR website.

AVR32 Studio
Version: 2.1.0
Build id: R200812171028

avr32program: Found version 3.1.4
avr32gdbproxy: Found version 3.1.5
avr32-gdb: Found version 6.7.1.atmel.1.0.3
avr32-g++: Found version 4.2.2-atmel.1.1.2 (mingw32 special) (mingw32 special)
avr32-gcc: Found version 4.2.2-atmel.1.1.2 (mingw32 special) (mingw32 special)
avr32-as: Found version 2.18.atmel.1.0.1.20070828
avr32-nm: Found version 2.18.atmel.1.0.1.20070828
avrfwupgrade: Found version 1.1.2

You are using the MinGW version of the AVR32 Utilities and AVR32/GNU Toolchain.

I could replace the chip with a UC3B0256 from DigiKey. Any known issues with doing that?

Thanks
Kevin

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

There are two different frameworks. One for the ES version and one for the non-ES version. Try using the ES framework, if you already do not use it.

-drt

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

drt80 wrote:
There are two different frameworks. One for the ES version and one for the non-ES version. Try using the ES framework, if you already do not use it.

-drt

The 2.1.0 version calls out specific frameworks for the ES parts. I believed I am using the ES framework. The header files are different. These are the files that are not working. The non ES version compile fine.