On Fri, Feb 10, 2012 at 12:15 AM, dwaraka nath <[email protected]>wrote:
> Hi, > I'm working on tinyOS for my academic project.. > > First I tried with TinyOS-2.0.2 in Cygwin. In this I compiled for "mymote > ( MSP430x2618 + cc2520 )" board following telosb hardware configuration. > what does that mean? You started with the telosb platform and then modified it for your new mote yes? Why did you start with the telosb? The Telosb uses the msp430f1611. You are using the 2618 which is very different than the msp430f1611. You would be better off using the Z1 instead of the TelosB. The Z1 is based on the 2617 which is essentially the same as the 2618. The Z1 uses the 2420 radio. > I have used mspgcc-4.4.5 to compile the code. It was working fine on the > hardware. > what does working fine mean? What program? Have you compiled NULL. Have you compiled Blink. Does Blink work? You are bringing a new platform up. It is NOT recommended that you start with a complex program and/or stack. Rather you should start with simpler programs and grow the set of tested programs so you know what works and what doesn't. Starting with a complex program is much more difficult to debug because you don't know what isn't working. Sound familiar? Then I tried to enable Blip on mymote by updating tinyos to tinyOS-2.1.1 > and came to know that the latest version of Blip stack works only in Linux. > Mixing contexts which is very confusing. BLIP is (Berkeley Low-power IP) and refers to the a 6lowpan implementation on the tinyos motes. Not sure what you are talking about when you say the latest version of the BLIP stack only works in Linux. BLIP is a 6lowpan implementation. The Linux side runs ipv6 and communicates with the mote via PPP-IPv6. (I found the error message that Blip 2.0 is for Linux). > What error message? > Now I'm unable to produce the exact error message here.. > > Then I moved to Linux (Ubuntu 11.04 with msp430-gcc-4.5.2) > Where did you get msp430-gcc 4.5.2? The version at Stanford and on TinyProd.net are LTS-20110716 which is based on 4.5.3. > 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. > 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. You have given us a lot of information that doesn't really pertain to the errors you are seeing. And you haven't given us information about what is going wrong. In other words, a bunch of noise. Which makes it hard to help you. Think through what kind of information you would want from someone if you were trying to help them. > I have placed /tos/platforms/mymote/hardware.h file according to my > harware in which LEDs are connectwed to port 5.4, 5.4, 5.6 > (I did it following the steps I did in Windows previously) > > ////////////////////////////////////////////////////////////// > "hardware.h" file is as follows > ////////////////////////////////////////////////////////////// > > #ifndef _H_hardware_h > #define _H_hardware_h > > #include "msp430hardware.h" > > // LEDs > TOSH_ASSIGN_PIN(RED_LED, 5, 4); > TOSH_ASSIGN_PIN(GREEN_LED, 5, 6); > TOSH_ASSIGN_PIN(YELLOW_LED, 5, 5); > > // UART pins > TOSH_ASSIGN_PIN(SOMI0, 3, 2); > TOSH_ASSIGN_PIN(SIMO0, 3, 1); > TOSH_ASSIGN_PIN(UCLK0, 3, 3); > TOSH_ASSIGN_PIN(UTXD0, 3, 4); > TOSH_ASSIGN_PIN(URXD0, 3, 5); > TOSH_ASSIGN_PIN(UTXD1, 3, 6); > TOSH_ASSIGN_PIN(URXD1, 3, 7); > TOSH_ASSIGN_PIN(UCLK1, 5, 3); > TOSH_ASSIGN_PIN(SOMI1, 5, 2); > TOSH_ASSIGN_PIN(SIMO1, 5, 1); > > > #endif // _H_hardware_h > > //////////////////////////////////////////////////////////////// > platform file is as follows.. > //////////////////////////////////////////////////////////////// > > > push( @includes, qw( > %T/platforms/mymote > %T/platforms/mymote/chips/msp430 > %T/platforms/mymote/chips/msp430/adc12 > %T/platforms/mymote/chips/msp430/usci > %T/platforms/mymote/chips/msp430/timer > %T/platforms/mymote/chips/cc2420 > %T/platforms/mymote/chips/sht11 > %T/platforms/mymote/chips/stm25p > %T/chips/cc2520 > %T/chips/cc2520/alarm > %T/chips/cc2520/control > %T/chips/cc2520/csma > %T/chips/cc2520/interfaces > %T/chips/cc2520/link > %T/chips/cc2520/lowpan > %T/chips/cc2520/lpl > %T/chips/cc2520/packet > %T/chips/cc2520/receive > %T/chips/cc2520/spi > %T/chips/cc2520/transmit > %T/chips/cc2520/unique > %T/chips/cc2520/security > %T/chips/msp430 > %T/chips/msp430/adc12 > %T/chips/msp430/dma > %T/chips/msp430/pins > %T/chips/msp430/timer > %T/chips/msp430/sensors > %T/chips/msp430/x2xxx > %T/chips/msp430/x2xxx/usci > %T/chips/stm25p > %T/chips/sht11 > %T/lib/timer > %T/lib/serial > %T/lib/power > ) ); > > @opts = qw( > -gcc=msp430-gcc > -mmcu=msp430x2618 > -fnesc-target=msp430 > -fnesc-no-debug > > -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask > ); > > i'm using %T/platforms/mymote/chips/cc2420 as it makes no difference with > the harware connections on "mymote" and i have made suffient changes to > work for cc2520. > Depends on what is in mymote/chips/cc2420. 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. It is very difficult to debug this kind of thing piecemeal. How much low level embedded programming have you done? Why are you building a new mote? > > > Can any body help..... > > > Thanks in advance.... > > > -- > 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
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
