currently, there is a restriction that PlatformSerialC supports only one UART interface.
I met this problem before, then I did a little changes for it: 1. have PlatformSerialC support paramterized UartStrem & UartByte interfaces. 2. have SerialDispatcherC be generalized by UART inteferface parameter. Best regards shan 2008/9/4 <[EMAIL PROTECTED]>: > Send Tinyos-help mailing list submissions to > tinyos-help@millennium.berkeley.edu > > To subscribe or unsubscribe via the World Wide Web, visit > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Tinyos-help digest..." > > > Today's Topics: > > 1. Re: printf problem (Sarfraz Nawaz) > 2. Re: Using SerialActiveMessageC with a different UART (on > TinyOS 2.x) (Sarfraz Nawaz) > 3. Re: Using SerialActiveMessageC with a different UART (on > TinyOS 2.x) (Simgi Dacav) > 4. Re: GPIO lines?? (Javier Almansa Sobrino) > 5. Re: Conversion C to nesC (Simgi Dacav) > 6. Re: [Tinyos-devel] DelugeT2 and MIB600, serialforwarder > (Razvan Musaloiu-E.) > 7. Re: RAM Energy Consumption (for e.g. Tmote Sky) (Steve McKown) > 8. Intercept interface one question (Funofnet funofnet) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 Sep 2008 21:07:40 +1000 > From: "Sarfraz Nawaz" <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] printf problem > To: "Mohamad Moubarak" <[EMAIL PROTECTED]> > Cc: tinyos-help@millennium.berkeley.edu > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > PrintfClient lives under > tinyos-2.x/support/sdk/java/net/tinyos/tools/. A compiled class is > included in the tinyos.jar so you should be able to fire it up with > the command > > java net.tinyos.tools.PrintfClient -comm [EMAIL PROTECTED]:mote > > change the port and mote according to your set up. > > On Fri, Jul 25, 2008 at 5:06 AM, Mohamad Moubarak <[EMAIL PROTECTED]> wrote: >> Hello, >> >> i have downloaded TinyOS 2.0.2 a couple of days ago as an rpm with all >> the required rpms. I have a problem following the printf tutorial at >> >> http://docs.tinyos.net/index.php/The_TinyOS_printf_Library >> >> The problem is that i do have the printf folder under lib,but the java >> tool "PrintfClient" required to receive the messages doesnt exist >> under java/net/tools/ >> nor does the file Printf under apps/tutorials/ >> >> Did i miss a step during installation. I need to use the printf >> library in my project so your help would be much appreciated. >> >> Thank You >> Mohamed Moubarak >> >> _______________________________________________ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > ------------------------------ > > Message: 2 > Date: Thu, 4 Sep 2008 21:17:33 +1000 > From: "Sarfraz Nawaz" <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] Using SerialActiveMessageC with a different > UART (on TinyOS 2.x) > To: "Cian Hughes" <[EMAIL PROTECTED]> > Cc: tinyos-help@millennium.berkeley.edu > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Yes the Uart is specified in PlatformSerialC. Each platform has its > own PlatformSerialC specifying which uart to use. > > On Tue, Aug 5, 2008 at 9:29 AM, Cian Hughes <[EMAIL PROTECTED]> wrote: >> Please excuse me if this question is answered on tinyos.net. I cannot >> seem to access any of the website at the moment (403). >> >> I have successfully set up a Shimmer and am running the TestSerialApp >> on it, communicating with my PC on Uart0, the default platform serial >> port. >> However I would like the application to simultaneously communicate on >> Uart1 also using SerialActiveMessageC. I cannot seem to figure out how >> to reconfigure the Uart used by an instance of SerialActiveMessageC. >> >> I have read both TEP113 & 117 and so I have a rough understanding of >> the stack structure. However it seems to me that the UART is >> ultimately specified in PlatformSerialC. >> >> Many Thanks, >> >> Cian Hughes. >> _______________________________________________ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > ------------------------------ > > Message: 3 > Date: Thu, 4 Sep 2008 14:21:03 +0200 > From: Simgi Dacav <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] Using SerialActiveMessageC with a different > UART (on TinyOS 2.x) > To: tinyos-help@millennium.berkeley.edu > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII > > Hi Cian > > Tue, 5 Aug 2008 00:29:44 +0100; Cian Hughes <[EMAIL PROTECTED]> wrote: >> I have successfully set up a Shimmer and am running the TestSerialApp >> on it, communicating with my PC on Uart0, the default platform serial >> port. >> However I would like the application to simultaneously communicate on >> Uart1 also using SerialActiveMessageC. I cannot seem to figure out how >> to reconfigure the Uart used by an instance of SerialActiveMessageC. >> > > We engaged the same problem some days ago! We are working on a Msp430 > architecture, but I suppose that your problem is quite similar, even if you > haven't specified your architecture... > > However, as you can see here[1], the SerialActiveMessageC is based on the > SerialDispatcherC component[2], that's based on PlatformSerialC[3]. > > The latter is based on Msp430Uart1C, that provides access to the Uart1 > through UartByte and UartStream interfaces. By replacing it witm Msp430Uart0C > you can choose the Uart component. > > Be careful: I've found out that the reference manual isn't complete! You > may need to check your installation directory tree! > > Regards > Giovanni > > > [1] > http://www.tinyos.net/dist-2.0.0/tinyos-2.0.2/doc/nesdoc/telosb/chtml/tos.lib.serial.SerialActiveMessageC.html > [2] > http://www.tinyos.net/dist-2.0.0/tinyos-2.0.2/doc/nesdoc/telosb/chtml/tos.lib.serial.SerialDispatcherC.html > [3] > http://www.tinyos.net/dist-2.0.0/tinyos-2.0.2/doc/nesdoc/telosb/chtml/tos.platforms.telosa.PlatformSerialC.html > > > ------------------------------ > > Message: 4 > Date: Thu, 4 Sep 2008 14:33:55 +0200 > From: Javier Almansa Sobrino <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] GPIO lines?? > To: tinyos-help@millennium.berkeley.edu > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-15 > > Hi everyone. I'm working in an application that needs to read a PIR > sensor and I would like this sensor generate a IRQ when it fires. > > I've readed and understanded TEP9 Appendix A code, but I don't know how > to know wich port number is assigned to each INT pin, so if I wanna > connect my PIR sensor to INT1, for example in a MDA100 board, wich port > sould I select. > > Thanks > -- > Nunca confies en un S.O. del que no tienes c?digo fuente ;-) > > -------------------------------- > Javier Almansa Sobrino. > Ingeniero T?cnico en Inform?tica de Sistemas. > > Grupo de Investigaci?n ARCo. > Escuela Superior de Inform?tica. Ciudad Real > Tel: (+34)926 29 53 00 Ext: 3705 > > > > > ------------------------------ > > Message: 5 > Date: Thu, 4 Sep 2008 14:40:28 +0200 > From: Simgi Dacav <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] Conversion C to nesC > To: tinyos-help@millennium.berkeley.edu > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII > > Hi damon! > > Mon, 14 Jul 2008 20:19:36 +0000; jesus cerezuela zaplana > <[EMAIL PROTECTED]> wrote: >> - All the C variable types are compatible in nesC? I mean, can I use char, >> long, int...etc variables? > > As far as I know you can use the same kind of types provided by the C > standard library's stdint.h (like uint8_t, uin16_t and so on). > > > ------------------------------ > > Message: 6 > Date: Thu, 4 Sep 2008 09:53:47 -0400 (EDT) > From: "Razvan Musaloiu-E." <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] [Tinyos-devel] DelugeT2 and MIB600, > serialforwarder > To: Vincent Borrel <[EMAIL PROTECTED]> > Cc: TinyOS Development <[EMAIL PROTECTED]>, > Tinyos-help <tinyos-help@millennium.berkeley.edu> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII > > Hi! > > Thanks for the patch! There is one thing I would like to warn about: the > serial upload protocol for Deluge T2 doesn't use any user level acks and > the SF TCP protocol doesn't indicate the failure of a failure of a serial > write. I argue for adding support for this as part of this thread: > > https://www.millennium.berkeley.edu/pipermail/tinyos-devel/2008-June/thread.html#3052 > > Because of this limitation I stop trying to made Deluge T2 work using > the SF protocol. > > Note: a good news is that MIG600 is using a serial speed of 57600 which > should make serial writer failure very infrequent. :-) > > -- > Razvan ME > > On Thu, 21 Aug 2008, Vincent Borrel wrote: > >> Hi, >> >> I have been trying to get Deluge T2 to work with an MIB600 programming board. >> >> I finally managed to get it to work using a serialforwarder (on default port >> 9002), and adding two modifications: >> >> in $TOSROOT/tinyos-2.x/support/sdk/python/tos.py, I added the timeout >> parameter to SFClient.write() >> @line 713 >> def write(self, payload, timeout): >> instead of >> def write(self, payload): >> (hoping it doesn't break havoc, which normally shouldn't) >> >> >> the python script tos-deluge has also been modified. Here is the diff: >> >> 402,403c402,403 >> < if sys.argv[2] == 'sf': >> < baudrate = 0 >> --- >>> if sys.argv[2] in BAUDRATES: >>> baudrate = BAUDRATES[sys.argv[2]] >> 405,428c405,417 >> < if sys.argv[2] in BAUDRATES: >> < baudrate = BAUDRATES[sys.argv[2]] >> < else: >> < try: >> < baudrate = int(sys.argv[2]) >> < except: >> < print "ERROR: Wrong baudrate" >> < sys.exit(-1) >> < >> < # Initializes serial or serialforwarder port communication >> < if baudrate == 0: >> < try: >> < s = tos.SFClient(sys.argv[1], 9002) >> < am = tos.AM(s) >> < except: >> < print "ERROR: Unable to initialize network port connection to", >> sys.argv[1] >> < sys.exit(-1) >> < else: >> < try: >> < s = tos.Serial(sys.argv[1], baudrate, flush=True, debug=False) >> < am = tos.AM(s) >> < except: >> < print "ERROR: Unable to initialize serial port connection to", >> sys.argv[1] >> < sys.exit(-1) >> --- >>> try: >>> baudrate = int(sys.argv[2]) >>> except: >>> print "ERROR: Wrong baudrate" >>> sys.exit(-1) >>> >>> # Initializes serial port communication >>> try: >>> s = tos.Serial(sys.argv[1], baudrate, flush=True, debug=False) >>> am = tos.AM(s) >>> except: >>> print "ERROR: Unable to initialize serial port connection to", >>> sys.argv[1] >>> sys.exit(-1) >> >> I hope this can be useful to the community. >> >> Vincent. >> > > > ------------------------------ > > Message: 7 > Date: Thu, 4 Sep 2008 08:02:20 -0600 > From: Steve McKown <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] RAM Energy Consumption (for e.g. Tmote Sky) > To: tinyos-help@millennium.berkeley.edu > Cc: K?derli Philipp <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > On Thursday 28 August 2008 08:07:03 am K?derli Philipp wrote: >> I am interested in how the RAM usage influences (if at all) the energy >> consumption of a sensor node, especially of a Tmote Sky node. I found >> informations about the flash and radio concerning the energy which is >> needed to send respectively store a byte. But I am interested in the >> volatile RAM. Where should I search? > > The RAM used in most sensor nodes is embedded within the microcontroller > package itself. In the case of the TMote Sky, this is the MSP430F1611 part. > Go to www.ti.com/msp430 and find two documents: the Family User's Guide for > MSP430x1xx and the data sheet for the MSP430x15x/MSP430x16x/MSP430x161x > parts. > >> >> Thanks Philipp >> >> _______________________________________________ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > > ------------------------------ > > Message: 8 > Date: Thu, 4 Sep 2008 16:23:52 +0200 > From: "Funofnet funofnet" <[EMAIL PROTECTED]> > Subject: [Tinyos-help] Intercept interface one question > To: <tinyos-help@millennium.berkeley.edu> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Hi all ! > > I will be very thankful if someone explain to me intercept interface. > > As it is mentioned: > > The intercept interface signals that a message has been received, which is > supposed to be forwarded to another destination. > > It returns TRUE if the packet should be forwarded, FALSE else. > > What I understood is : Intercept.forward returns FLASE if a node snoops a > packet being transmitted. > > > > ****** > > To an additional clarification > > "A" sends a message to "B" (which can be a root or "A"'s parent) > > "C" is in the proximity of B or let's say in Tx range of the node A. > > "C" can probably hear the packet being transmitted by "A" and can also snoop > it. > > "C" is not qualified to forward "A" msg, then its Intercept.forward returns > FLASE consequently. > > > > It is true??????? > > > > Thanks > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20080904/b9521e37/attachment.htm > > ------------------------------ > > _______________________________________________ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > End of Tinyos-help Digest, Vol 65, Issue 22 > ******************************************* > _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
