On Sun, Sep 9, 2012 at 1:40 PM, Antonio Linan <[email protected]> wrote:
> The bigger telosb motes from advanticsys are actually a slightly different > Z1 mote with a similar MCU and one additional sensor, so I can give you > some advise (advertisement free). > That is somewhat confusing. Bigger telosb motes yes for some value of yes.... (the XM1000 is 2618 based and has more code space but less ram space.) A TelosB mote is msp430f1611 based while the Z1 is msp430f2618 based. > You shouldn't have problems working with BLIP other than it was deprecated > in newer 2.1.2 release, so you will have to work with 2.1.1. > > If working with BLIP 2, you can always cut off some fat and reduce the > size stack (both RAM and ROM), see: > > http://zolertia.sourceforge.net/wiki/index.php/Blip_v2.0 > > Normally the size issues were due to memory rather than code size Actually it depends. I've only seen code space problems but I can easily see how it would be possible to run the smaller ram footprint motes out of RAM. It just depends. In particular I've seen code overflow in the telosb. Also depends on what toolchain you are using and what optimization level you are using. I would recommend 4.6.3 and -Os. > (therefore changing from telosb to Advanticsys or Z1 motes would mean > losing 2Kb of ram and gaining more flash size, but 20-bit support to > program the memory to its full size is experimental at the moment), I > haven't tested Ppprouter after 2.1.2 but at the time of the release I > believe everything was working fine. > > € 0.02 > > --Antonio > > On Sun, Sep 9, 2012 at 10:01 PM, Hugo De Haas <[email protected]>wrote: > >> Hi Everybody, >> >> >> >> During compiling of the PppRouter from the TinyOS 2.1.2 I get the error >> that the code size is too large for a TelosB. I know that in the release >> candidate it was within the limit, barely. >> >> But when I compile the same program for epic it finished with a code size >> of 49k bytes. >> >> How is this possible? According to the Epic data sheet it has a 48k rom, >> the same as the TelosB. >> >> >> >> To overcome the code size problem. Would it be wise to invest in a couple >> of Epic motes? Since it the primary target for BLIP (and BLIP2???) as >> stated in the BLIP Tutorial on the TinyOS. >> >> If so which epic version/model? Or is a bigger TelosB also an option? >> >> Advice would be much appreciated. >> >> >> >> BR, >> >> Hugo >> >> >> >> TelosB datasheet: >> >> http: >> //bullseye.xbow.com:81/Products/Product_pdf_files/Wireless_pdf/TelosB_Datasheet.pdf >> >> >> >> Epic datasheet: >> >> http://www.moteware.com/pub-docs/datasheet-epic.pdf >> >> >> >> Bigger TelosB: >> >> http://www.advanticsys.com/shop/asxm1000-p-24.html >> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > > -- > -- > Antonio Liñan Colina > R+D+I Engineer > @: [email protected] > @: [email protected] > ------------------------------ > Advancare > T: +34 93 582 02 70 > http://www.advancare.com > http://www.zolertia.com > http://zolertia.sourceforge.net > http://webshop.zolertia.com > > > _______________________________________________ > 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
