Re: [Tinyos-help] how to debug TelosB code at instruction level?
On Thu, Jul 26, 2012 at 9:20 PM, Gary Lee gary.lee1...@gmail.com wrote: TelosB motes have no JTAG interface. Not true. U8 is the jtag header. you can wire that up with a special cable (you will have to figure it out, I don't remember what the connections are) to the TI MSP-FET430UIF, USB JTAG. Documentation is out there that describes what the pin outs look like. Avrora does not support debugging TelosB. So any suggestion about what tools can be used to analyze TelosB TinyOS code at instruction level? Thanks. Gary ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] how to debug TelosB code at instruction level?
TelosB motes have no JTAG interface. Avrora does not support debugging TelosB. So any suggestion about what tools can be used to analyze TelosB TinyOS code at instruction level? Thanks. Gary ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to debug Java code in TinyOS
Hi All I tried to use JDB to debug through the Java code (oscilloscope) in TinyOS. It some how did not stop a the break points. Can debug it via Eclipse? Thanks. Regards, Zhen ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [TinyOS-help]: How to debug nesC code without JTAG in Eclipse
Hi, My question is that whether it is possible to debug nesC code without JTAG. If it is, how? Unfortunately for you it is not possible to debug without a hardware debugger (JTAG, debugWire, SWD,... depending on your target architecture AVR, MSP430). To debug your code on the mote without a hardware debugger, it would be necessary to have a gdbserver or gdb agent running on the mote. Due to the memory and performance constraints of common motes this is not an alternative and JTAG is required. By the way, you can now find really cheap hardware debugger/programmer on eBay or online shops. Hope this helps, Romain On Fri, Jul 15, 2011 at 5:38 AM, Shengkai Zhang shengkai.zh...@gmail.com wrote: Dear all, Yeti 2 of Eclipse is really great. If I could debug nesC code by Eclipse, that's perfect(I have no JTAG). I build an example project, BlinkToRadio, to generate a main.exe file. Then I set Debug Configuration and choose the configuration of GDB proxy to be None. As a result, there is a creating session error whose detail is Cannot run program avr-gdb: Unknown reason. If I choose the configuration of GDB proxy to be Avarice, the error is Could not start GDB Proxy! Command was: avarice --mkI --jtag /dev/avrjtag --jtag-bitrate 1000KHz :4242 --ignore-intr. I apologize if my question is so simple ( I didn't find reasonable answers from Google). My question is that whether it is possible to debug nesC code without JTAG. If it is, how? Thank you very much. I really need your help. -- Shengkai Zhang The Department of Electronics and Information Engineering Huazhong University of Science and Technology Wuhan, Hubei, China ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [TinyOS-help]: How to debug nesC code without JTAG in Eclipse
Dear all, Yeti 2 of Eclipse is really great. If I could debug nesC code by Eclipse, that's perfect(I have no JTAG). I build an example project, BlinkToRadio, to generate a main.exe file. Then I set Debug Configuration and choose the configuration of GDB proxy to be None. As a result, there is a creating session error whose detail is Cannot run program avr-gdb: Unknown reason. If I choose the configuration of GDB proxy to be Avarice, the error is Could not start GDB Proxy! Command was: avarice --mkI --jtag /dev/avrjtag --jtag-bitrate 1000KHz :4242 --ignore-intr. I apologize if my question is so simple ( I didn't find reasonable answers from Google). My question is that whether it is possible to debug nesC code without JTAG. If it is, how? Thank you very much. I really need your help. -- Shengkai Zhang The Department of Electronics and Information Engineering Huazhong University of Science and Technology Wuhan, Hubei, China ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to debug where is wrong when reading from an external sensor under MicaZ?
Hi, I attach an external sensor to the MicaZ mote. After following the tutorial and installing the driver for the sensor, I write a simple application, trying to read values from this sensor. I use Leds to test whether the reading is successful or not. Based on the display of Leds, the reading is not successful. I am wondering how I can further debug to check where is wrong. Is build/micaz/app.c a good start to debug? I am using TinyOS 2.1.0. Any comments are highly appreciated. Gary ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to debug the send message ?
I don't understand the relationship between send() and receive() here
but it's possible that the intermediate put() fails because the UART
is busy. I think put() just starts a uart xmit, and like the radio
send() you need to wait for a done() before successfully posting
another char.
MS
liangjing wrote:
Hi all,
I encountered a problem when debugging the send message. I use the
UART to give me the debugging information. In my application, I start
a timer to send the message repeatly, and when the timer is fired, I
send the message out. Now, I insert two debugging sentences to send
number to UART. My send code is below,
call HPLUART.put(0x06);
call CC1100Control.send( (uint8_t *)cm, CONTROL_MSG_LENGTH+1);
call HPLUART.put(0x07);
I could receive 0x06 and 0x07 on my PC. But I am not sure the
CC1100Control.send is implemented correctly, because in my receive
section, I don't the debugging number I expected. My receive code is
below,
event result_t CC1100Control.receive(uint8_t *t)
{
call HPLUART.put(0x02);
}
I don't get 0x02 on my PC. Is anything wrong ? Any advice is appreciated.
Best Regards
Jing
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to debug the send message ?
Hi all,
I encountered a problem when debugging the send message. I use the
UART to give me the debugging information. In my application, I start
a timer to send the message repeatly, and when the timer is fired, I
send the message out. Now, I insert two debugging sentences to send
number to UART. My send code is below,
call HPLUART.put(0x06);
call CC1100Control.send( (uint8_t *)cm, CONTROL_MSG_LENGTH+1);
call HPLUART.put(0x07);
I could receive 0x06 and 0x07 on my PC. But I am not sure the
CC1100Control.send is implemented correctly, because in my receive
section, I don't the debugging number I expected. My receive code is
below,
event result_t CC1100Control.receive(uint8_t *t)
{
call HPLUART.put(0x02);
}
I don't get 0x02 on my PC. Is anything wrong ? Any advice is appreciated.
Best Regards
Jing
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] how to debug a nesC code.................??
hi everybody, i have developed a simple program in nesC...getting buildfine :D i want to debug it step by step. could anybody suggest me on that.. could anyone tell me more on dbg .. getsome good links regarding nesC:D... tried a lot in net. but nothing materialistic. Regards, Primalfear ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to debug
Hi, I'm using micaz platform and I want to know how to debug nesC code on a mote. I'd be great if someone could give me a clue about how to begin to debug and if it is very difficult or not. Thanks, S. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to debug
The best choice is to use TOSSIM, a simulator for TinyOS applications, please read TOSSIM manual To debug code on the real motes you may make use of LEDS on the mote... I hope this hepls you... Regargds, Manjunath On Fri, 14 Apr 2006, Sara B. wrote: Hi, I'm using micaz platform and I want to know how to debug nesC code on a mote. I'd be great if someone could give me a clue about how to begin to debug and if it is very difficult or not. Thanks, S. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to debug
One added dow'n'dirty technique is to toggle LEDs or other binary outputs and look at them with a scope or logic analyzer. This is useful, as you might expect, for timing and sync relationships... MS ps...thanks for the sparkfun link. looks like some good stuff there. Chuck Kring wrote: I use a combination of JTAG, a sniffer, and UART print statements. First, I use a version of SOdebug to generate a runtime trace of the state machine during execution (UART printing) that can be viewed with Minicomm or Hyperterm. This is very useful for determining that the mote is working correctly and to debug issues issues like missing events (e.g. not receiving a sendDone) or if something returns FAIL. Second, a sniffer answers a very fundamental question: given a missing message, was it dropped on the transmit or the receive end. Finally, JTAG is used for detailed debugging of problems once identified by SOdebug and the sniffer. You can get a cheap but very workable JTAG pod at www.sparkfun.com. The Xbow Xsniffer program is available in Moteworks if you have that. Chuck Kring Finishline Systems At 08:25 AM 4/14/2006, Philip Levis wrote: On Apr 14, 2006, at 7:47 AM, Sara B. wrote: Hi, I'm using micaz platform and I want to know how to debug nesC code on a mote. I'd be great if someone could give me a clue about how to begin to debug and if it is very difficult or not. You need an atmel JTAG adapter. This will let you run gdb that reflects what's going on in a mote. It can be very useful to see the internal state, etc. Setting breakpoints can also be useful, but of course they disrupt what the mote is doing: if you set a breakpoint in a low-level packet interrupt, for example, then you might lose the packet. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
