Debugging two processors simultaneously (longish)?

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

I have two AVR32's talking to each other using a fairly complex protocol. The basic protocol is simple, but there are tens of different messages. I need to develop one program that builds and sends these messages and another program on another processor, that receives and parses these messages. It would be really helpful if I could debug both sides simultaneously.

Currently, I'm using AVR32 Studio. As noted elsewhere, I experience 2..3 x delays in about every operation with Studio5, so I don't want to use that - but I could, if I must. I have tried running two instances of AVR32 Studio, each with their own workspace, connected to two JTAGICE mkII's. This does not really work, as there is some kind of intermediate layer between the Studio and the JTAG (the jtagserver.exe process), and there are only one of these. It gets confused if there are two debuggers running. It does work if one side is in run state and the other is in debug state, but I'd like to be able to break, look variables etc on both sides.

The trivial solution is to buy another computer and make room on my desktop for another set of monitor, keyboard and mouse.

Assuming I don't want to do this, what are my other options? Please share you experiences and internal know-how if you have it, before I start spending serious money to experiments! Right now, I only have one JTAGICE mkII (I had one on loan for a while), and I don't want to buy another unless I know it will work. So, is there a way to make this work with two JTAGICE mkII's? What if the other debugger is a Dragon or JTAGICE3? Two instances of Studio5? One Studio5 and one AVR32 Studio?

Please, if you have a setup where you are able to debug two processors concurrently, could you share the details of your setup?

Thank you!

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

One solution that should (at least theoretically) keep things separated is to use a virtual machine for the second debugger (with only xp, avr32, debugger installed).

-Pantelis

Professor of Applied Murphology, University of W.T.F.Justhappened.

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

If you are debugging the protocol then the basic structure should be working well enough not to need jtag control to stop the processor and examine memory.

Use serial debug printfs in side by side terminal windows, with time stamps to correlate the outputs. Here's a nifty perl script that stamps, displays, and logs to a file http://contiki.git.sourceforge.net/git/gitweb.cgi?p=contiki/contiki;a=blob_plain;f=tools/serial-log.pl