Hi all, I am trying to debug my nesC codes using GDB (for TinyOS1.x using
Mica2Dot and Mica2). Bunch of naive questions, so I think you know this for
sure: 1) avr-gdb and gdb are used for .exe (srec?) symbols reading. For the
Mica2Dot ATMega128L do I necessarily need to use the 1st one? Or the latter one
can also be used? What would be their difference by the way? 2) Why can I read
these symbols only by compiling with the debug command (make mica2dot install
debug mib520,com3)? 3) For on-chip debugging i need necessarily the JTAG
interface to be connected with the MIB520 programming board. Avarice will carry
out the interconnection of the JTAG-ICE interface (which is connected to the
programming board+Mica2/Mica2Dot of course) and the avr-gdb through the serial
port. So that means is 100% certain that I can do step-by-step on-chip
debugging using avr-gdb (or even using the WinAvr Insight graphical GUI). Can I
also see the assembly code and the correspondant nesC code side-by-side on that
Insight GUI? Has anyone have this sort of experience? Is Avarice also
compatible with JTAG-ISP or just with the JTAG-ICE?
Didn't really want to waste my money.... Thanks guys,Edgar Charry
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
