Thanks! And glad to hear my code was of use :) We're pretty committed to 868 MHz (better propagation and less interference than 2.4 GHz, plus these are expected to work with our existing networks), and 32K is plenty for our "leaf nodes", so we've been planning on using the CC430 for a while now.
Cheers, Michiel From: Antonio Linan [mailto:[email protected]] Sent: Tuesday, November 19, 2013 22:49 To: Eric Decker Cc: Michiel Konstapel; [email protected] Subject: Re: [Tinyos-help] CC430 I have been using the msp430 x5xxx implementation from tp-master and had no problem, the I2C/SPI works great but I have not looked the ADC implementation. I've ported the CC1120 from the Gnode's CC1101 driver (thanks Michiel bttw!) with CC1190 support for operation in compliance with FCC/CEPT/ARIB regulations, so far no problems have arised. The CC430 was quickly discarded due to size constrains, I'm running an application pretty close to the 16Kb RAM and 80Kb flash, with a 2Mbit STM25P. About the x2xxx status in tp-master I have overlooked it as we are currently working with the msp430f5438a in a project, and for the Z1 mote we mostly support what is already in tinyos main, but there was room for improvements and there was a something-breakfast-called implementation in tinyprod that looked promising but haven't got the time to test. The cc2538 is looking great, there's a port and plenty of work done already by the Contiki folks, taking a peak might be worthwhile if anyone wishes to port it to TinyOS. My two cents about it. Cheers! --Antonio On Tue, Nov 19, 2013 at 8:49 PM, Eric Decker <[email protected]<mailto:[email protected]>> wrote: On Tue, Nov 19, 2013 at 3:36 AM, Michiel Konstapel <[email protected]<mailto:[email protected]>> wrote: What would be the best jumping off point for our CC430F5137 based platform? First the choice of the CC430f5137 isn't great. It doesn't have much code space and it has very little RAM. 32K code and 4K RAM. But if that works for you great. If you can handle switching to 2.4GHz, the CC2538 looks very interesting. Its an ARM Cortex-M3 core coupled to a 2520 radio. But I'd recommend, using the 5438 coupled to a 2520/2591 (with range extender). I've just finished rewriting the 2520 driver. I'd also strongly recommend that you have somekind of non-vol storage that you can put core dumps into for failure analysis. tp-master has a Panic facility that I use for paranoid code. The mainline has a simple_panic which works well for debugging (put a single breakpoint in the panic code). But my main tag has a SD card with tons of storage and I put core dumps into that. If you are deploying in anykiind of reasonable fashion, things will go wrong. And figure that out will be the lion's share of time involved in making this stuff real. I write my code with that in mind. Eric, since I know you've done a lot of work on the 5xx series, I've taken the liberty of CCing you personally. No problem. As far as I can tell, tinyos-main (https://github.com/tinyos/tinyos-main) has no 5xx support. that is correct. There are lots of differences between tp-master and tinyos-main(master). However, tp-master tracks tinyos-main as its upstream. I need to do a pull here shortly. tinyprod (https://github.com/tinyprod/prod ) does, but I don't know what branch I would want to start from; master, mm-core or tp-master? I'm working my way through the commit logs and code, but I could use some guidance. You want to port your changes over to a branch off tp-master. But you want to make sure it is a branch and then tp-master will be your upstream. The surf platform is based on the same chip, but it has not been updated recently. You should be able to start from the surf platform. It has bitrotted but shouldn't be too bad. Once you get your platform going and stable, I'd like you to put the simple part of your platform code into tp-master and I'll deprecate the surf code. But only if schematics are available for your platform. Otherwise I'll just keep the surf code as the example cc430 code. Are there known issues with it, or the x5xx support in general? Any gotchas I should look out for? the 5438 code is solid and the subset of that which is also cc430 code should also be good. But there is no one actively wacking on cc430 code (the processors are too constrained). So your mileage will vary. But you should be okay. Kind regards, Michiel Konstapel -- Eric B. Decker Senior (over 50 :-) Researcher _______________________________________________ Tinyos-help mailing list [email protected]<mailto:[email protected]> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- -- Antonio Liñán Colina R+D Engineer @: [email protected]<mailto:[email protected]> @: [email protected]<mailto:[email protected]> ------------------------------ Advancare Ph.: +34 935 511 403 http://www.advancare.com<http://www.advancare.com/> http://www.zolertia.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
