[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep117.html,1.7,1.8
Phil Levis
scipio at users.sourceforge.net
Wed May 30 23:24:53 PDT 2007
Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv30785/html
Modified Files:
tep117.html
Log Message:
Finalized.
Index: tep117.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep117.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep117.html 21 Apr 2007 07:04:39 -0000 1.7
--- tep117.html 31 May 2007 06:24:51 -0000 1.8
***************
*** 4,8 ****
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
! <meta name="generator" content="Docutils 0.3.6: http://docutils.sourceforge.net/" />
<title>Low-Level I/O</title>
<meta name="author" content="Phil Buonadonna, Jonathan Hui" />
--- 4,8 ----
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
! <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
<title>Low-Level I/O</title>
<meta name="author" content="Phil Buonadonna, Jonathan Hui" />
***************
*** 284,287 ****
--- 284,288 ----
</head>
<body>
+ <div class="document" id="low-level-i-o">
<h1 class="title">Low-Level I/O</h1>
<table class="docinfo" frame="void" rules="none">
***************
*** 296,315 ****
</tr>
<tr><th class="docinfo-name">Status:</th>
! <td>Draft</td></tr>
<tr class="field"><th class="docinfo-name">TinyOS-Version:</th><td class="field-body">2.x</td>
</tr>
<tr><th class="docinfo-name">Author:</th>
<td>Phil Buonadonna, Jonathan Hui</td></tr>
- <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">23-Jan-2006</td>
- </tr>
- <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.5</td>
- </tr>
- <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-12-12</td>
- </tr>
- <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
- </tr>
</tbody>
</table>
- <div class="document" id="low-level-i-o">
<div class="note">
<p class="first admonition-title">Note</p>
--- 297,307 ----
</tr>
<tr><th class="docinfo-name">Status:</th>
! <td>Final</td></tr>
<tr class="field"><th class="docinfo-name">TinyOS-Version:</th><td class="field-body">2.x</td>
</tr>
<tr><th class="docinfo-name">Author:</th>
<td>Phil Buonadonna, Jonathan Hui</td></tr>
</tbody>
</table>
<div class="note">
<p class="first admonition-title">Note</p>
***************
*** 319,329 ****
TEP 1.</p>
</div>
! <div class="section" id="abstract">
! <h1><a name="abstract">Abstract</a></h1>
<p>The memo documents the TinyOS 2.x interfaces used for controlling
digital IO functionality and digital interfaces.</p>
</div>
! <div class="section" id="introduction">
! <h1><a name="introduction">1. Introduction</a></h1>
<p>The canonical TinyOS device is likely to have a variety of digital
interfaces. These interfaces may be divided into two broad
--- 311,321 ----
TEP 1.</p>
</div>
! <div class="section">
! <h1><a id="abstract" name="abstract">Abstract</a></h1>
<p>The memo documents the TinyOS 2.x interfaces used for controlling
digital IO functionality and digital interfaces.</p>
</div>
! <div class="section">
! <h1><a id="introduction" name="introduction">1. Introduction</a></h1>
<p>The canonical TinyOS device is likely to have a variety of digital
interfaces. These interfaces may be divided into two broad
***************
*** 339,344 ****
<p>This memo documents the interfaces used for pins and the three buses.</p>
</div>
! <div class="section" id="pins">
! <h1><a name="pins">2. Pins</a></h1>
<p>General Purpose I/O (GPIO) pins are single, versatile digital I/O
signals individually controllable on a particular chip or
--- 331,336 ----
<p>This memo documents the interfaces used for pins and the three buses.</p>
</div>
! <div class="section">
! <h1><a id="pins" name="pins">2. Pins</a></h1>
<p>General Purpose I/O (GPIO) pins are single, versatile digital I/O
signals individually controllable on a particular chip or
***************
*** 381,386 ****
</ul>
</blockquote>
! <div class="section" id="generalio">
! <h2><a name="generalio">2.1 GeneralIO</a></h2>
<p>The GeneralIO HIL interface is the fundamental mechanism for controlling a
GPIO pin. The interface provides a mechanism for setting the pin mode
--- 373,378 ----
</ul>
</blockquote>
! <div class="section">
! <h2><a id="generalio" name="generalio">2.1 GeneralIO</a></h2>
<p>The GeneralIO HIL interface is the fundamental mechanism for controlling a
GPIO pin. The interface provides a mechanism for setting the pin mode
***************
*** 404,409 ****
</pre>
</div>
! <div class="section" id="gpiointerrupt">
! <h2><a name="gpiointerrupt">2.2 GpioInterrupt</a></h2>
<p>The GPIO Interrupt HIL interface provides baseline event control for a
GPIO pin. It provides a mechanism to detect a rising edge OR a falling
--- 396,401 ----
</pre>
</div>
! <div class="section">
! <h2><a id="gpiointerrupt" name="gpiointerrupt">2.2 GpioInterrupt</a></h2>
<p>The GPIO Interrupt HIL interface provides baseline event control for a
GPIO pin. It provides a mechanism to detect a rising edge OR a falling
***************
*** 425,430 ****
</pre>
</div>
! <div class="section" id="gpiocapture">
! <h2><a name="gpiocapture">2.3 GpioCapture</a></h2>
<p>The GpioCapture interface provides a means of associating a timestamp
with a GPIO event. Platforms MAY provide this interface.</p>
--- 417,422 ----
</pre>
</div>
! <div class="section">
! <h2><a id="gpiocapture" name="gpiocapture">2.3 GpioCapture</a></h2>
<p>The GpioCapture interface provides a means of associating a timestamp
with a GPIO event. Platforms MAY provide this interface.</p>
***************
*** 448,459 ****
</div>
</div>
! <div class="section" id="buses">
! <h1><a name="buses">3. Buses</a></h1>
<p>Bus operations may be divided into two categories: data and
control. The control operations of a particular bus controller are
platform specific and not covered here. Instead, we focus on the data
interfaces at the HIL level that are expected to be provided.</p>
! <div class="section" id="serial-peripheral-interface">
! <h2><a name="serial-peripheral-interface">3.1 Serial Peripheral Interface</a></h2>
<p>The Serial Peripheral Interface (SPI) is part of a larger class of
Synchronous Serial Protocols. The term SPI typically refers to the
--- 440,451 ----
</div>
</div>
! <div class="section">
! <h1><a id="buses" name="buses">3. Buses</a></h1>
<p>Bus operations may be divided into two categories: data and
control. The control operations of a particular bus controller are
platform specific and not covered here. Instead, we focus on the data
interfaces at the HIL level that are expected to be provided.</p>
! <div class="section">
! <h2><a id="serial-peripheral-interface" name="serial-peripheral-interface">3.1 Serial Peripheral Interface</a></h2>
<p>The Serial Peripheral Interface (SPI) is part of a larger class of
Synchronous Serial Protocols. The term SPI typically refers to the
***************
*** 485,490 ****
</pre>
</div>
! <div class="section" id="i2c">
! <h2><a name="i2c">3.2 I2C</a></h2>
<p>The Inter-Integrated Circuit (I2C) interface is another type of
digital bus that is often used for chip-to-chip communication. It is
--- 477,482 ----
</pre>
</div>
! <div class="section">
! <h2><a id="i2c" name="i2c">3.2 I2C</a></h2>
<p>The Inter-Integrated Circuit (I2C) interface is another type of
digital bus that is often used for chip-to-chip communication. It is
***************
*** 507,511 ****
underlying implementation supports. Valid type values are below.</p>
<pre class="literal-block">
! TI2CExtdAddr - Interfaces uses the extended (10-bit) addressing mode.
TI2CBasicAddr - Interfaces uses the basic (7-bit) addressing mode.
</pre>
--- 499,503 ----
underlying implementation supports. Valid type values are below.</p>
<pre class="literal-block">
! TI2CExtdAddr - Interfaces uses the extended (10-bit) addressing mode.
TI2CBasicAddr - Interfaces uses the basic (7-bit) addressing mode.
</pre>
***************
*** 517,526 ****
I2C_STOP - Transmit an I2C STOP at the end of the operation. Cannot be used
with the I2C_ACK_END flag.
! I2C_ACK_END - ACK the last byte sent from the buffer. This flags is only valid
a write operation. Cannot be used with the I2C_STOP flag.
</pre>
</div>
! <div class="section" id="uart">
! <h2><a name="uart">3.3 UART</a></h2>
<p>The Universal Asynchronous Receiver/Transmitter (UART) interface is a
type of serial interconnect. The interface is "asynchronous" since it
--- 509,518 ----
I2C_STOP - Transmit an I2C STOP at the end of the operation. Cannot be used
with the I2C_ACK_END flag.
! I2C_ACK_END - ACK the last byte sent from the buffer. This flags is only valid
a write operation. Cannot be used with the I2C_STOP flag.
</pre>
</div>
! <div class="section">
! <h2><a id="uart" name="uart">3.3 UART</a></h2>
<p>The Universal Asynchronous Receiver/Transmitter (UART) interface is a
type of serial interconnect. The interface is "asynchronous" since it
***************
*** 540,548 ****
async command error_t send( uint8_t* buf, uint16_t len );
async event void sendDone( uint8_t* buf, uint16_t len, error_t error );
!
async command error_t enableReceiveInterrupt();
async command error_t disableReceiveInterrupt();
async event void receivedByte( uint8_t byte );
!
async command error_t receive( uint8_t* buf, uint8_t len );
async event void receiveDone( uint8_t* buf, uint16_t len, error_t error );
--- 532,540 ----
async command error_t send( uint8_t* buf, uint16_t len );
async event void sendDone( uint8_t* buf, uint16_t len, error_t error );
!
async command error_t enableReceiveInterrupt();
async command error_t disableReceiveInterrupt();
async event void receivedByte( uint8_t byte );
!
async command error_t receive( uint8_t* buf, uint8_t len );
async event void receiveDone( uint8_t* buf, uint16_t len, error_t error );
***************
*** 564,569 ****
</div>
</div>
! <div class="section" id="implementation">
! <h1><a name="implementation">4. Implementation</a></h1>
<p>Example implementations of the pin interfaces can be found in tos/chips/msp430/pins,
tos/chips/atm128/pins, and tos/chips/pxa27x/gpio.</p>
--- 556,561 ----
</div>
</div>
! <div class="section">
! <h1><a id="implementation" name="implementation">4. Implementation</a></h1>
<p>Example implementations of the pin interfaces can be found in tos/chips/msp430/pins,
tos/chips/atm128/pins, and tos/chips/pxa27x/gpio.</p>
***************
*** 575,580 ****
tos/chips/atm128/uart/ and tos/chips/pxa27x/uart.</p>
</div>
! <div class="section" id="author-s-address">
! <h1><a name="author-s-address">5. Author's Address</a></h1>
<div class="line-block">
<div class="line">Phil Buonadonna</div>
--- 567,572 ----
tos/chips/atm128/uart/ and tos/chips/pxa27x/uart.</p>
</div>
! <div class="section">
! <h1><a id="author-s-address" name="author-s-address">5. Author's Address</a></h1>
<div class="line-block">
<div class="line">Phil Buonadonna</div>
***************
*** 587,591 ****
<div class="line"><br /></div>
<div class="line">Jonathan Hui</div>
! <div class="line">Arched Rock Corporation</div>
<div class="line">657 Mission St. Ste 600</div>
<div class="line">San Francisco, CA 94105-4120</div>
--- 579,583 ----
<div class="line"><br /></div>
<div class="line">Jonathan Hui</div>
! <div class="line">Arch Rock Corporation</div>
<div class="line">657 Mission St. Ste 600</div>
<div class="line">San Francisco, CA 94105-4120</div>
***************
*** 594,599 ****
</div>
</div>
! <div class="section" id="citations">
! <h1><a name="citations">6. Citations</a></h1>
<table class="docutils citation" frame="void" id="tep113" rules="none">
<colgroup><col class="label" /><col /></colgroup>
--- 586,591 ----
</div>
</div>
! <div class="section">
! <h1><a id="citations" name="citations">6. Citations</a></h1>
<table class="docutils citation" frame="void" id="tep113" rules="none">
<colgroup><col class="label" /><col /></colgroup>
More information about the Tinyos-2-commits
mailing list