On Fri, Feb 10, 2012 at 1:53 AM, dwaraka nath <[email protected]>wrote: > > > my hardware connections are following TelosB architecture.. >
So what does that mean? What is the TelosB architecture? > what does working fine mean? What program? Have you compiled NULL. >>> Have you compiled Blink. Does Blink work? >>> >> > Yes i tried Null and Blink. working fine mean the hardware is working... > Okay. Good. >> (I found the error message that Blip 2.0 is for Linux). >>> >> >> What error message? >> > > when i tried to configure Blip in windows it showed error that Blip works > in Linux > Okay. Not sure what that means. But okay. > > >> >>> in which i'm able to install latest version of Blip. here I made a new >>> platform for "mymote" which is same as I tried in TinyOS-2.0.2. I succeeded >>> in compiling the code in command line. But when I port the ihex file on to >>> the processor through 'bsl', I'm unable to program using bsl. >>> >> >> It would be helpful if you say what went wrong. Just saying it doesn't >> work doesn't help. >> > > when i tried to "install" the program my hardware is not responding for > bsl programming > BSL requires certain pins on the process to be wiggled in a particular way. On the TelosB this is done via the USB/Serial interface and a state machine that does the reset properly. This then puts the cpu into BSL mode and things work for downloading. If you want your h/w to work via BSL you have to figure out how to get this working. It isn't something that belong on tinyos-help. Beyond the scope. That said, it is kind of moot because you have the JTAG working. You can program and single step your board using mspdebug? If that is the case you can ignore the bsl stuff. > I found alternative to program "mymote" using "mspdebug" tool and now I'm >>> able to program the device (Using FET-UIF). But I couldnt run the program >>> on the hardware. >>> >> >> Again, what went wrong. >> > > the hardware is not responding ( Leds are not glowing, Node to Node > communication is not happening) > Okay so you now have to debug the board using mspdebug. This is something you are going to have to learn. I'm not sure where to point you for an introduction to this kind of debugging. I use msp430-gdb and mspdebug to debug my stuff. There is a learning curve. It is also beyond the scope of tinyos-help. Too steep and it requires as far as I'm concerned a certain base level of skill. ie. do you know GDB? do you know how to work with a remote GDB server? etc. > Think through what kind of information you would want from someone if you >> were trying to help them. >> > > > >> >> Yet something isn't working. So ruling out this directory because >> "you've made sufficient changes to work for the cc2520" isn't a reasonable >> conclusion. Because it isn't working. >> > > the same changes worked in TinyOS-2.0.2 for my hardware. > I find that hard to believe. TinyOS-2.0.2 doesn't have any support for the 2618 processor. So how could your "same changes" possibly work? So what changes are you talking about. > >> >> Why are you building a new mote? >> >> Our hardware was designed to support Zigbee Stack.. and now we are moving >> to TinyOS. >> >>> >>> >>> >>> -- >>> Tulasi Dwarakanath.V >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> >> >> >> -- >> Eric B. Decker >> Senior (over 50 :-) Researcher >> >> >> > > > -- > Tulasi Dwarakanath.V > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
