Debugging with XMega TWI

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

I have the impression that during a debug session (GCC debugger active and MK-II connected to PDI) TWI clock is reduced.
Using a logic state analyser I see that during normal operation the clock is 100 kHz, while during debug speed lowers to 3,12 kHz (that is 1/32 of normal speed).
I suppose this is normally not a problem, after all slaves adapt their speed to master clock. In my case this is a problem because I have to synchronise certain actions with SCL.

Apart from this: did you experience the same problem?
Before contacting Atmel support I would share your opinion.

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

I have only ever used JTAG with an Xmega.

With Studio the trick is to 'run until' or have very few breakpoints. The Xmega should run at full speed up to the breakpoint. You then have a long pause while Studio reads all the registers, memory etc.

You hint that you are using avr-gdb. That is your choice. I would guess that the behaviour should be similar.

David.

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

Actually I did not think that debugging under PDI with the xmega WAS supported by avarice (which you must use to debug with gdb).