Hi Derek, I'm currently working on integrating the msp430 core code for the three major msp430 families (the x1, x2, and x5).
You are using an x5 part. I'm guessing the cc430f5137 because I beleive you are basing off of the osian/surf board code. When you post question onto tinyos-help (or for that matter anywhere) it would be helpful if you included the specifics of exactly what you are working with so we don't have to guess. That also applies to what flavor of em430 board you are using. TI makes many different eval boards for their processors. For example, I have an eval board for the 5438 that is significantly different from the eval board that the surf folks called the em430. So calling it the em430 doesn't convey alot of information. On Wed, May 18, 2011 at 2:14 AM, Derek Baker < [email protected]> wrote: > Hi, can anybody explain to me the difference between the msp430/usci and > msp430/uart drivers, > The devil is in the details. I think you are talking about tos/chips/msp430/usart vs. tos/chips/msp430/usci. The usart driver (tos/chips/msp430/usart) is the driver for the x1 family peripheral (the USART). On the x2 and x5 family parts there is a different peripheral called the USCI. It is a different beast and has a different driver. There are basically differnt flavors of what these modules do. The USART on the x1 parts only has I2C on port 0 and this is reflected in the code. The USCI situation is also convoluted. The X2 implementation of USCI vs. the x5 implementation has some significant warts. In particular how interrupts are dealt with and where the register are mapped and how they are accessed. > I noticed the /msp430/uart has i2c support. I’m using the em430 mote which > is configured to use the usci but I need the i2c part has anybody developed > the i2c part of the /msp/usci? > Peter who did the initial support for the tinyos cc430f5137 port didn't add the i2c functionality because he didn't have any h/w that used it. The parts will support it. But the driver hasn't been integrated yet. i'm pretty sure that the Z1 folks have a working i2c driver. Keep in mind that all of this code is in flux. The code that is currently in the trunk for the msp430X (tos/chips/msp430X) is being heavily reworked. That said there is a version of the usci drivers in there that worked for the Z1 folks. But it is very ugly and unfinished. A more modern driver is being worked on in the msp430 integration branch. That is also where the merged x5 code is coming in. How soon do you need an i2c driver? > > Regards > > > > Derek > > > > > ------------------------------ > This email message has been delivered safely and archived online by > Mimecast. > A true SaaS solution, Mimecast provides the security, continuity and > archiving for millions of emails, across thousands of customers every day. > For more information please visit http://www.mimecast.co.uk > ------------------------------ > > _______________________________________________ > 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
