Vlasios thanks for the two cents. Good to hear WinAVR is looking pretty
good.
I've been wondering whether I should be using the more generally available
'C' tools and use the output or some modified version of app.c
I haven't investigated the switches on the avr-gcc to see what they support.
I was on a conference call this morning were someone was praising the
CodeWarrior environment for its capabilities in being able to get going with
a Freescale version of a wireless network - but of course its 'C' and the
productivity comes with a high $$$ I hear.
Of course many thanks to all the highly motivated developers who have put so
much work into the avr-gcc and nesC - it is truly amazing what has been
done.
As ever, though it is trying to figure how to make it better.
regards
Neil Hancock
-----Original Message-----
From: Vlasios Tsiatsis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 29, 2005 12:39 PM
To: Neil Hancock
Cc: Raghu Ganti; [email protected]
Subject: RE: [Tinyos-users] Debugging
I will share my experience with AVR Studio and non-TinyOS programs.
I have used a non-TinyOS C program, converted to EXT-COFF using WinAVR and
then loaded it to AVR-Studio. You can step through C statements if you
follow this procedure (C code -> EXT COFF by WinAVR -> Import to AVR
Studio). By the way the same non-TinyOS program could run on the mica2
mote. I used the AVR studio to measure executation time in terms of clock
cycles for some pieces of code. AVR Studio can produce cycle counts which
are close to the real executation cycle counts.
The bad news is that the TinyOS avr-gcc distribution doesn't support the
EXT-COFF output file. In theory you could take the build/<tgt>/app.c file
and follow the above procedure to debug a TinyOS program or measure it but
i have never tried it. Plus you would have to be familiar with the TInyOS
code so that you can understand what nesC statements correspond to what C
statements. It's not difficult but it's time consuming.
That's my 2 cents.
vlassis
On Mon, 28 Mar 2005, Neil Hancock wrote:
> Raghu
>
> I think you need to be a bit more explicit on the errors in "make pc" to
get
> any help.
>
> I'm also thinking about the same issue - how to do path level code
coverage
> on the motes in a reasonably productive manner, and then integrate it into
> and debug on mote2dot.
>
> Its been fairly hair-raising.
>
> I have my own hardware daughter board, and have first developed an in situ
> debug monitor to be able to debug with the mote2dot.
> Now that I have my own hardware it seems I have to customize it to fit the
> "make pc" environment to be able to do path level testing on the PC.
> This could work, but it would be nice to try and find a GUI interface to
its
> commands and single step through
>
> As far as I've found
> - Avr-insight is possibly the most productive tool with visual source
level
> debugger. It is a GUI interface to gdb. I was over the moon when I found
it.
> However it seems to only interface to an JTAG-ICE and this seems like it
is
> the AVR JTAG. From what I've found the AVR JTAG mk II that is available
has
> been upgraded and currently isn't compatible with gdb.
>
> - It seems like gdb with a GUI should be available to work with the
> build/<tgt>/app.c that is created, but I haven't managed to track down how
> this would work in the nesC tool chain.
>
> - Atmel AVR studio looks attractive, but only seems to deal with
assembler.
>
> - Avrora is a simulator, but again doesn't seem to deal with 'nesC' level
> source code.
>
> Be interersted in any insights from the experts
>
> Chow
> Neil
>
> -----Original Message-----
> From: Raghu Ganti [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 26, 2005 8:40 PM
> To: [email protected]
> Subject: [Tinyos-users] Debugging
>
>
> Hi
> I am facing a major problem in debugging the motes! First, to start
> with my module does not compile for TOSSIM, so if I give "make pc" it
> will not compile whereas on "make micaz" it will compile well!
> Is there any method by which I can debug the code running on micaz?
> (other than by looking at the Leds).
> If anyone can point me to a good source, it will be of great help.
>
> Thanks
> Raghu
_______________________________________________
Tinyos-users mailing list
[email protected]
http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
