Can one kill an AT32UC3C0512C with Studio 5?

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

Hi All

I have just bought an AT32UC3C-EK (quite expensive and a shame that it doesn't have Ethernet connected, but the reason was for a CAN project).

Using Studio 5 I loaded some new code to the board and did a bit of debugging - it stepped around in C code and assembler fine for a few minutes.

Then Studio 5 crashed as I manipulated a peripheral register by hand (I was modifying the SCIF UNLOCK register so that I could write a value to another register at the time - the UC3C is a bit more complicated than the UC3A and UC3B types).

Since the crash I can no longer connect to the device either from Studio 5 or from IAR (another board I have on hand with a UC3B on it connects normally).

The message that I get is
"AVR Studio was unable to start your debug session.
Please verify that the debugger is correctly attached to the target and that target power has been switched on. Also verify that the correct device and interface settings have been specified in the project.

Timestamp: 2011-09-03 00:14:39.062
Severity: ERROR
ComponentId: 20100
StatusCode: 0

TCF command: Processes:launch failed: Code:1 ,Service: ,Message from peer:Unexpected JTAG ID 0xffffffff (expected 0x0200003f)"

Also, if I try using avr32program to erase and program I get the following:

"Connected to JTAGICE mkII version 7.13, 7.13 at USB.

Erasing page failed
Error reading memory word from 0xfffe0008.
SAB read from address 0x5fffe0008 failed.
sabRead:
The command was not understood by the JTAGICE mkII unit."

Does this point to the chip having died? Quite disappointing as the board has just come out of the box and the demo was working before debugging the new program. Or could I kill it with an error in the code loaded or did Studio 5 kill it as it crashed???

Any ideas? Looks as though the new project will have to go on hold...;-(

Regards

Mark

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

Hi All

The latest news is that I hit the board (not hard but I tapped around it) and the debugger started working again.

Then I managed to do some more debugging and verified that the first part of the new project runs (including setting up the PLL correctly to 64MHz - from a 16MHz crystal this seems the fastest speed or is there a trick to get 66MHz out of it...?).

I did want to add UART, SD card amnd TFT display options (to verify that the ports have been set up correctly to match - these modules are OK on UC3A and UC3B parts so may work automatically on the new chip if no port setups have gone wrong) but the debugger stopped working again. I tried the trick of hitting the board again but it hasn't worked just yet. The code is running on the processor, so the processor is OK - just the debug interface seems to be the problem.

Maybe a solder joint somewhere...??

Regards

Mark

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

A bad solder joint or failing JTAG cable.

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

Had similar issue with a UC3C0512-EK/AVR One!/AVR32 Studio combo. Had a second board, swapped them and same result. Flattened out the JTag cable and made sure there were no twists and it started working again. I assume it was the cable. Since then I have just made sure there are no twists or stresses on the cable and have had no problem. I guess the cables are kinda fragile. May want to swap that first. You can buy new probes and cables and swap out parts to isolate the problem.

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

Hi All

After experiencing the problem on and off for some time I have now found a workaround:

1) When it happens I have realised that I can move the cable around as much as I want and retry but it just won't work.
2) When this happens I now do the following - from a DOS window issue:
"avr32program program -finternal@0x80000000 -cxtal -F bin -O 2147483648 -e -u -R -r uTaskerV1.4.bin"
This is an attempt to program using avr32program, which always fails with the message:
"Connected to JTAGICE mkII version 7.13, 7.13 at USB.

Erasing page failed
Error reading memory word from 0xfffe0008.
SAB read from address 0x5fffe0008 failed.
sabRead:
The command was not understood by the JTAGICE mkII unit."

Then I return to AVR32 Studo 5 and retry the attempt to load and debug and it works - 100% ...!! ;-)

Every time! Then it can debug perfectly until the problem starts again (which is usually after a good amount of work with several downloads).
When the problem occurs (usually the first time I try to work after starting AVR32 Studio 5) I simply repeat and - as if by magic - it starts working again (no hitting the board or moving cables).

3) It can't be a solder or cable problem in this case.

4) I only have the difficulty with the AT32U3C-EK (presumably the device on it) and not UA or UB devices.

I repeat - this only happens with this board/processor. Since it is 100% consistent (after realising what actually made it start working) it may be an interesting input to the AVR32 Studio 5 developers.

Regards

Mark