AVR32 & JTAGICE standalone questions

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

Just getting started so some of these might be stupid questions. I'm using the AVR32 studio from the atmel website with a JTAGICE mk2 connected via USB. I'm running Windows 2000 under parallels on a MAC.

The avr32gdbproxy situation is confusing to me. It seems that in order to download the program to flash it can't be running, but has to be running in order to debug. In the GDB setup you have to tell it the TCP port to connect to avr32gdbproxy but if you let AVR32 studio automatically start avr32gdbproxy it will open a socket on whatever the next socket is so no connection. The only way I got it to work was to let it fail this step and then manually start it using a batch file and then start debugging again (without loading the code). I tried adding "-a :4242" (assuming 4242 is the port defined for gdb) to the avr32gdbproxy command elsewhere in the IDE but then it says it can't launch it, even though it has. What am I doing wrong?

Peeves:
The memory dump only shows question marks when I try to dump the contents of internal SRAM.

The register display doesn't show the status register (SR).

There doesn't appear to be a way to manually change the address being dis-assembled.

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

Hi,

please upgrade to the 1.0 RC which was just released to http://www.atmel.no/beta_ware. It fixes issues with the avr32gdbproxy communication. Basically you should leave AVR32 Studio to start its own instance of avr32gdbproxy as needed, so unless you have conflicting services on the ports which Studio defaults to, there shouldn't be a need to change anything.

Make sure you get the latest GNU Toolchain while you're at it: get the big installer which contain both Studio and the toolchain.

The memory view appears to fail because it attempts to fetch memory beyond what's in the viewport. For me it fails when I get near the end of the internal SRAM. You can probably work around this issue by using the Expressions view where you can type in addresses to watch.

You can find the status register in the AVR32 Registers view under System Registers.

The disassembly view is limited to displaying the current function. This view is part of the Eclipse CDT project. We haven't prioritized making a more flexible disassembly view so far.

Tore

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

tolsen2 wrote:
It fixes issues with the avr32gdbproxy communication.

Yes, that fixes that, thanks.
Quote:
The memory view appears to fail because it attempts to fetch memory beyond what's in the viewport.

That seems to be the case. It seems kind of silly that it puts in question marks for the addresses that are actually valid.
Quote:
You can find the status register in the AVR32 Registers view under System Registers.

Thanks for the tip!
Quote:
The disassembly view is limited to displaying the current function. This view is part of the Eclipse CDT project. We haven't prioritized making a more flexible disassembly view so far.

I was thinking it would be nice to be able to check out what the startup code (and other library code) actually is.

Thanks Tore

No if I can keep UART1 from shutting down when it receives a character using the PDC....