Dear Nelly Chen In this example explain this task:
http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-1.x/contrib/SharedUSART/apps/TestUSART/ Jorge http://isi.upc.es/ > > Message: 8 > Date: Mon, 6 Apr 2009 10:51:14 -0400 > From: Nelly Chen <[email protected]> > Subject: [Tinyos-help] [Help] How to transmit 4 byte > messages to UART0 > on telosb > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; > delsp=yes > > Hi, > > I am just starting to learn TinyOS and also not very > familiar with > coding in mcu. I've searched through the archive but still > not > understand how to transmit a 4 byte package to UART0 (pin > 23) on Telosb? > > The package is sent to a motor controller connected to the > pin 4 on > the 10-pin extension. > > I used HplMsp430Usart interface, modified the baudrate, and > send the 4 > byte signal when timer is fired. Is it right? > > Any feedback or big picture of the structure is > appreciated. > > Thanks. > > > ------------------------------ > > Message: 9 > Date: Mon, 6 Apr 2009 16:25:50 +0100 > From: Frank Smith <[email protected]> > Subject: [Tinyos-help] Error making docs > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Folks, > > I'm new to TOS and have started to work my way through the > tutorials. On > Cygwin, I've managed to successfully execute: > > /opt/tinyos-2.x/apps/Blink $ make micaz sim > ... > ... > ... > *** Successfully built micaz TOSSIM library. > > > Now I'm trying to generate docs and am getting the > following: > > /opt/tinyos-2.x/apps/Blink $ make micaz docs > Making documentation for BlinkAppC on micaz > nesdoc -o /opt/tinyos-2.x/doc/nesdoc > -finline-limit=100000 -Wall -Wshadow > -Wnes > c-all -target=micaz -fnesc-cfile=build/micaz/app.c > -board=micasb > -DIDENT_PROGRAM > _NAME=\"BlinkAppC\" -DIDENT_USER_ID=\"FrankSmith\" > -DIDENT_HOSTNAME=\"London\ > " -DIDENT_USER_HASH=0xf946e71eL > -DIDENT_UNIX_TIME=0x49da1daaL > -DIDENT_UID_HASH=0 > xc5b3ec8fL BlinkAppC.nc > Couldn't execute avr-gcc > nesdoc failed: no valid input > make: *** [docs_] Error 2 > > > Should I be installing avr tools? If so, from where and > which versions? In > case, ncc etc. versions are: > > /opt/tinyos-2.x/apps/Blink $ ncc --version > ncc: 1.2.4 > nescc: 1.2.8a > gcc: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd > 0.125) > Copyright (C) 2004 Free Software Foundation, Inc. > This is free software; see the source for copying > conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > > Many thanks in advance, > > Frank > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20090406/e794024f/attachment-0001.htm > > > ------------------------------ > > Message: 10 > Date: Mon, 6 Apr 2009 10:46:50 -0500 > From: Janos Sallai <[email protected]> > Subject: Re: [Tinyos-help] Error making docs > To: Frank Smith <[email protected]> > Cc: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > > Should I be installing avr tools? If so, from where > and which versions? > It depends on what docs you need. Obviously, the set of > components > that get compiled into a micaz application will be vastly > different > from the ones compiled into a telosb application. To get > the docs, you > will need the proper c compiler for the platform. > > The latest avr toolchain is available from > http://docs.tinyos.net/index.php/Installing_TinyOS_2.1 > > Janos > > On Mon, Apr 6, 2009 at 10:25 AM, Frank Smith > <[email protected]> > wrote: > > Folks, > > > > I'm new to TOS and have started to work my way through > the tutorials. On > > Cygwin, I've managed to successfully execute: > > > > /opt/tinyos-2.x/apps/Blink $ make micaz sim > > ... > > ... > > ... > > *** Successfully built micaz TOSSIM library. > > > > > > Now I'm trying to generate docs and am getting the > following: > > > > /opt/tinyos-2.x/apps/Blink $ make micaz docs > > ??? Making documentation for BlinkAppC on micaz > > nesdoc -o /opt/tinyos-2.x/doc/nesdoc? > -finline-limit=100000 -Wall -Wshadow > > -Wnes > > c-all -target=micaz -fnesc-cfile=build/micaz/app.c > -board=micasb > > -DIDENT_PROGRAM > > _NAME=\"BlinkAppC\" -DIDENT_USER_ID=\"FrankSmith\" > > -DIDENT_HOSTNAME=\"London\ > > " -DIDENT_USER_HASH=0xf946e71eL > -DIDENT_UNIX_TIME=0x49da1daaL > > -DIDENT_UID_HASH=0 > > xc5b3ec8fL BlinkAppC.nc > > Couldn't execute avr-gcc > > nesdoc failed: no valid input > > make: *** [docs_] Error 2 > > > > > > Should I be installing avr tools? If so, from where > and which versions? In > > case, ncc etc. versions are: > > > > /opt/tinyos-2.x/apps/Blink $ ncc --version > > ncc: 1.2.4 > > nescc: 1.2.8a > > gcc: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using > dmd 0.125) > > Copyright (C) 2004 Free Software Foundation, Inc. > > This is free software; see the source for copying > conditions.? There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR > A PARTICULAR PURPOSE. > > > > > > Many thanks in advance, > > > > Frank > > > > > > _______________________________________________ > > Tinyos-help mailing list > > [email protected] > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > > ------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > End of Tinyos-help Digest, Vol 72, Issue 18 > ******************************************* > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
