headers
Philip Levis | 1 Nov 2005 03:37
Picon

Re: Dynamic memory allocation - Function pointers in nesC

On Oct 29, 2005, at 11:32 PM, MANJUNATH wrote:

>
> Dear All,
>
>     Just I wanted to understand about exact reasons for not to include
>     dynamic memory allocation and function pointers in nesC.
>
>     One reason:  Usage of function pointers makes deadcode elimination
>              difficult.
>
>     I am not able to get any other reasons......
>
>     I would request you to please give me some pointers/details about
>     the same...
>
>     I went through the paper "An holistic approach.."

Short answer: it leads to more reliable code.

Long answer:

Here's a pointer (haha!):

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005- 
February/007712.html

There's a difference between malloc() and dynamic allocation. nesC  
does not forbid dynamic memory allocation: there's nothing stopping  
you from writing a component that allocates a pool of memory and has
(Continue reading)

Permalink | Reply | 0 comments |
headers
A.K. | 1 Nov 2005 11:08
Picon
Favicon

redhat linux 9 problems



Guys,

i am doing a sensornet project with tinyoson mica2.

plz reply if you could help:
i installed rhl9(redhat linux 9) with kernel version 2.4.20-8. i am facing following problems:

1. screen does not expands to monitor size but a small window.
2. doesnt recognize USB drive.the /etc/mnt directory doesnt have anything to mount for USB.
3. fail to configure eth0, that interface card.

i would try to figure out what rpms i need. but if you could give me quick response that would be great.

thanks.


 

Yahoo! FareChase - Search multiple travel sites in one click. 
<div>
<div>
<br><br>Guys,</div>
<p>i am doing a sensornet project with tinyoson mica2.</p>
<p>plz reply if you could help:<br>i installed rhl9(redhat linux 9) with kernel version 2.4.20-8. i am facing following problems:</p>
<p>1. screen does not expands to monitor size but a small window.<br>2. doesnt recognize USB drive.the /etc/mnt directory doesnt have anything to mount for USB.<br>3. fail to configure eth0, that interface card.</p>
<p>i would try to figure out what rpms i need. but if you could give me quick response that would be great.</p>
<p>thanks.</p>
<p><br>&nbsp;</p>
<blockquote class="replbq"></blockquote>
<p>
		</p>
<a href="http://us.lrd.yahoo.com/_ylc=X3oDMTFqODRtdXQ4BF9TAzMyOTc1MDIEX3MDOTY2ODgxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--/SIG=110oav78o/**http%3a//farechase.yahoo.com/">Yahoo! FareChase - Search multiple travel sites in one click.</a>
</div>
Permalink | Reply | 0 comments |
headers
Andrea Pacini | 1 Nov 2005 14:03
Picon
Favicon

tmote sky multiplier

I 've seen that in msp430 assembler doesn't exist the
mul src,dst instruction.
I don't understand if exist the memory mapped
multiplier. If not exist how can I make a
multiplication ?



----
Email.it, the professional e-mail, gratis per te:clicca qui

Sponsor:
25% di sconto su TV Color LCD di Dell, clicca qui
Clicca qui

<div>
<div>I 've seen that in msp430 assembler doesn't exist 
the</div>
<div>mul src,dst instruction.</div>
<div>I don't understand if exist the memory 
mapped</div>
<div>multiplier. If not exist how can I make a 
</div>
<div>multiplication ?</div>
<br><br><br><p>----<br>
Email.it, the professional e-mail, gratis per te:<a href="http://www.email.it/cgi-bin/start?sid=3" target="_blank">clicca qui</a><br><br>
Sponsor:<br>
25% di sconto su TV Color LCD di Dell, clicca qui<br><a href="http://adv.email.it/cgi-bin/foclick.cgi?mid=4104&amp;d=1-11" target="_blank">Clicca qui</a><br><br></p>
</div>
Permalink | Reply | 0 comments |
headers
Kristin Wright | 1 Nov 2005 20:17
Picon

TinyOS 2.0.0 PreRelease2

On behalf of the entire TinyOS 2.0 Working Group, I am pleased to
announce TinyOS 2.0 PreRelease2. PreRelease2 features two new
platforms, TelosB/TmoteSky and MicaZ, plus microcontroller power
management interfaces, and other extensive work on ADC support and
serial communication.

Please see the announcement on tinyos.net for more details and
information on how to install
2.x:
http://www.tinyos.net/scoop/story/2005/11/1/11215/8473

-kw
Permalink | Reply | 1 comment |
headers
Jeff Thorn | 1 Nov 2005 21:56

SurgeTelos and TOSSIM

I cannot seem to get /beta/TOSSIM-CC2420 to work properly with SurgeTelos.
If I run:

	make pc sim,telos

I get TONS of errors. Below is a small example of the build errors I get. Is
there something else I need to do? Does anyone know how to get SurgeTelos to
work with TOSSIM?

Thanks, 
Jeff
	
Sample build errors:
----------------------------------------
$ cd apps/SurgeTelos
$ make pc sim,telos
mkdir -p build/pc
    compiling Surge to a pc binary
ncc -o build/pc/main.exe -g -O0 -I%T/../contrib/ucb/tos/lib/MultiHopLQI
-DSEND_QUEUE_SIZE=8 -DMHOP_LEDS -pthread -fnesc-nido-tosnodes=1000 -
fnesc-simulate -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc
-fnesc-cfile=build/pc/app.c -board=micasb -I%T/lib/Deluge -I%T/l
ib/Flash -I%T/lib/Flash/STM25P -DDEFAULT_EEPROM_SIZE=0x100000
-DIDENT_PROGRAM_NAME=\"Surge\" -DIDENT_USER_ID=\"jthorn\"
-DIDENT_HOSTNAME=\"L
ATITUDE-D800\" -DIDENT_USER_HASH=0xdb10e625L -DIDENT_UNIX_TIME=0x4367d3ddL
-DIDENT_UID_HASH=0xbf170c33L -I/opt/tinyos-1.x/tos/../beta/TOSSIM
-CC2420 -I/opt/tinyos-1.x/tos/lib/CC2420Radio
-I/opt/tinyos-1.x/tos/../beta/TOSSIM-CC2420/telosa Surge.nc -lm
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc: In
function `flushRXFIFO':
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:120:
`CC2420_RXFIFO' undeclared (first use in this function)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:120:
(Each undeclared identifier is reported only once
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:120: for
each function it appears in.)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:121:
`CC2420_SFLUSHRX' undeclared (first use in this function)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc: In
function `sendPacket':
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:291:
`CC2420_STXONCCA' undeclared (first use in this function)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:292:
`CC2420_SNOP' undeclared (first use in this function)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:293:
`CC2420_TX_ACTIVE' undeclared (first use in this function)
C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:300:
`CC2420_SYMBOL_UNIT' undeclared (first use in this function)
etc.
etc.
Permalink | Reply | 0 comments |
headers
Omprakash Gnawali | 1 Nov 2005 22:01
Picon
Favicon

compile problem with HPLTimer1M.nc / where to find outw ?


When I am trying to use a component that uses
tos/platform/micaz/HPLTimer1M.nc, I get the following error:

tos/platform/micaz/HPLTimer1M.nc: In function `Timer1.setInterval':
tos/platform/micaz/HPLTimer1M.nc:77: implicit declaration of function `outw'

It seems there was a discussion about implicit declaration of __outw a
while back, but I didn't see anything about outw not being found. I
downloaded previous versions of avr-libc and it appears that
avr-libc-1.0.5 was the last version before outw was phased out.

Is there a way to fix this problem short of going back to
avr-libc-1.0.5 ? Can going back to this version cause other problems ?

Thanks.

- om_p
Permalink | Reply | 1 comment |
headers
Philip Levis | 1 Nov 2005 22:17
Picon

Re: [Tinyos-2.0wg] TinyOS 2.0.0 PreRelease2

On Tue, 2005-11-01 at 12:17 -0700, Kristin Wright wrote:
> On behalf of the entire TinyOS 2.0 Working Group, I am pleased to
> announce TinyOS 2.0 PreRelease2. PreRelease2 features two new
> platforms, TelosB/TmoteSky and MicaZ, plus microcontroller power
> management interfaces, and other extensive work on ADC support and
> serial communication.
> 
> Please see the announcement on tinyos.net for more details and
> information on how to install
> 2.x:
> http://www.tinyos.net/scoop/story/2005/11/1/11215/8473

For those attending SenSys, the 2.x WG has a poster/demonstration in the
Wednesday night session. We'll be happy to answer questions and talk
about the 2.x roadmap with anyone who's interested.

Phil
Permalink | Reply | 0 comments |
headers
David Gay | 1 Nov 2005 22:59
Picon

Re: compile problem with HPLTimer1M.nc / where to find outw ?

On 11/1/05, Omprakash Gnawali <gnawali <at> usc.edu> wrote:
>
> When I am trying to use a component that uses
> tos/platform/micaz/HPLTimer1M.nc, I get the following error:
>
> tos/platform/micaz/HPLTimer1M.nc: In function `Timer1.setInterval':
> tos/platform/micaz/HPLTimer1M.nc:77: implicit declaration of function `outw'
>
> It seems there was a discussion about implicit declaration of __outw a
> while back, but I didn't see anything about outw not being found. I
> downloaded previous versions of avr-libc and it appears that
> avr-libc-1.0.5 was the last version before outw was phased out.
>
> Is there a way to fix this problem short of going back to
> avr-libc-1.0.5 ? Can going back to this version cause other problems ?

The following diff should fix this:
Index: avrhardware.h
===================================================================
RCS file: /cvsroot/tinyos/tinyos-1.x/tos/platform/avrmote/avrhardware.h,v
retrieving revision 1.17
diff -u -r1.17 avrhardware.h
--- avrhardware.h       23 Jul 2005 21:43:34 -0000      1.17
+++ avrhardware.h       1 Nov 2005 21:57:50 -0000
 <at>  <at>  -66,7 +75,8  <at>  <at> 
 #define inb(port) (port)
 #define outp(value, port) ((port) = (value))
 #define outb(port, value) ((port) = (value))
-#define inw(port) (*(volatile uint16_t *)&port)
+#define inw(port) (*(volatile uint16_t *)&(port))
+#define outw(port, value) ((*(volatile uint16_t *)&(port)) = (value))
 #define PRG_RDB(addr) pgm_read_byte(addr)
 #endif

David Gay
Permalink | Reply | 0 comments |
headers
Elaine Cheong | 2 Nov 2005 01:16
Picon
Favicon

Viptos 5.1-alpha release available

We are announcing the first alpha release of Viptos (Visual Ptolemy and 
TinyOS), an integrated graphical development and simulation environment 
for TinyOS-based wireless sensor networks.

Please visit the website at:
http://ptolemy.eecs.berkeley.edu/viptos

Full abstract:

Viptos (Visual Ptolemy and TinyOS) is an integrated graphical development 
and simulation environment for TinyOS-based wireless sensor networks. 
Viptos allows developers to create block and arrow diagrams to construct 
TinyOS programs from any standard library of nesC/TinyOS components. The 
tool automatically transforms the diagram into a nesC program that can be 
compiled and downloaded from within the graphical environment onto any 
TinyOS-supported target hardware. In particular, Viptos includes the full 
capabilities of VisualSense, which can model communication channels, 
networks, and non-TinyOS nodes. This release of Viptos is compatible with 
nesC 1.2 and includes tools to harvest existing TinyOS components and 
applications and convert them into a format that can be displayed as block 
(and arrow) diagrams and simulated.

Viptos is based on TOSSIM and Ptolemy II. TOSSIM is an interrupt-level 
simulator for TinyOS programs. It runs actual TinyOS code but provides 
software replacements for the simulated hardware and models network 
interaction at the bit or packet level. Ptolemy II is a graphical software 
system for modeling, simulation, and design of concurrent, real-time, 
embedded systems. Ptolemy II focuses on assembly of concurrent components 
with well-defined models of computation that govern the interaction 
between components. VisualSense is a Ptolemy II environment for modeling 
and simulation of wireless sensor networks at the network level.

Viptos provides a bridge between VisualSense and TOSSIM by providing 
interrupt-level simulation of actual TinyOS programs, with packet-level 
simulation of the network, while allowing the developer to use other 
models of computation available in Ptolemy II for modeling various parts 
of the system. While TOSSIM only allows simulation of homogeneous networks 
where each node runs the same program, Viptos supports simulation of 
heterogeneous networks where each node may run a different program. Viptos 
simulations may also include non-TinyOS-based wireless nodes. The 
developer can easily switch to different channel models and change other 
parts of the simulated environment, such as creating models to generate 
simulated traffic on the wireless network.

Viptos inherits the actor-oriented modeling environment of Ptolemy II, 
which allows the developer to use different models of computation at each 
level of simulation. At the lowest level, Viptos uses the discrete-event 
scheduler of TOSSIM to model the interaction between the CPU and TinyOS 
code that runs on it. At the next highest level, Viptos uses the 
discrete-event scheduler of Ptolemy II to model interaction with mote 
hardware, such as the radio and sensors. This level is then embedded 
within VisualSense to allow modeling of the wireless channels to simulate 
packet loss, corruption, delay, etc. The user can also model and simulate 
other aspects of the physical environment including those detected by the 
sensors (e.g., light, temperature, etc.), terrain, etc.

Elaine Cheong
Permalink | Reply | 0 comments |
headers
Janos Sallai | 2 Nov 2005 05:20
Picon
Favicon

TinyDT Eclipse plugin available

We are pleased to announce that TinyDT is now available to the TinyOS

developer community for download from the TinyDT website

(http://www.tinydt.net). TinyDT is a TinyOS 1.x plugin for the Eclipse

platform that implements an IDE for TinyOS/nesC development. As of now,

it has the following features:

 

    * Syntax highlighting of nesC code

    * Code navigation

    * Code completion for interface members

    * Support for multiple target platforms and sensor boards

    * Automatic build support

    * Team development support (through Eclipse-CVS integration)

    * Support for multiple TinyOS source trees

 

The most important feature that distinguishes TinyDT from the existing

TinyOS IDE attempts is that TinyDT's internal parser builds an in-memory

representation of the actual nesC application, which includes component

hierarchy, wirings, interfaces and the JavaDoc style nesC documentation.

The eclipse plugin queries this representation to implement various

features like code navigation, code completion, etc.

 

Please note that TinyDT is still under development and, in some aspects,

has limited functionality. Nevertheless, we encourage everyone to try it

out, report the bugs, and last but not least, to contibute to TinyDT.

 

TinyDT is an open source project, hosted on SourceForge.net, developed

at the Institute of Software Integrated Systems, Vanderbilt University.

 

Janos Sallai

on behalf of the TinyDT team

ISIS, Vanderbilt University

<div>

<div class="Section1">

<p class="MsoNormal"><span>We are pleased to announce that TinyDT is now available to
the TinyOS </span></p>

<p class="MsoNormal"><span>developer community for download from the TinyDT website </span></p>

<p class="MsoNormal"><span>(http://www.tinydt.net). TinyDT is a TinyOS 1.x plugin for
the Eclipse </span></p>

<p class="MsoNormal"><span>platform that implements an IDE for TinyOS/nesC development.
As of now, </span></p>

<p class="MsoNormal"><span>it has the following features:</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Syntax highlighting of nesC code</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Code navigation</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Code completion for interface members</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp; &nbsp;* Support for multiple target platforms
and sensor boards</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Automatic build support</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Team development support (through
Eclipse-CVS integration)</span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; * Support for multiple TinyOS source
trees</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>

<p class="MsoNormal"><span>The most important feature that distinguishes TinyDT from
the existing </span></p>

<p class="MsoNormal"><span>TinyOS IDE attempts is that TinyDT's internal parser builds
an in-memory </span></p>

<p class="MsoNormal"><span>representation of the actual nesC application, which
includes component </span></p>

<p class="MsoNormal"><span>hierarchy, wirings, interfaces and the JavaDoc style nesC
documentation. </span></p>

<p class="MsoNormal"><span>The eclipse plugin queries this representation to implement
various </span></p>

<p class="MsoNormal"><span lang="FR">features like code navigation, code completion, etc.</span></p>

<p class="MsoNormal"><span lang="FR">&nbsp;</span></p>

<p class="MsoNormal"><span>Please note that TinyDT is still under development and, in
some aspects, </span></p>

<p class="MsoNormal"><span>has limited functionality. Nevertheless, we encourage
everyone to try it </span></p>

<p class="MsoNormal"><span>out, report the bugs, and last but not least, to contibute
to TinyDT.</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>

<p class="MsoNormal"><span>TinyDT is an open source project, hosted on SourceForge.net,
developed </span></p>

<p class="MsoNormal"><span>at the </span><span>Institute</span><span> of </span><span>Software</span><span> Integrated
Systems, </span><span>Vanderbilt</span><span> </span><span>University</span><span>.</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>

<p class="MsoNormal"><span>Janos Sallai</span></p>

<p class="MsoNormal"><span>on behalf of the TinyDT team</span></p>

<p class="MsoNormal"><span>ISIS</span><span>, </span><span>Vanderbilt</span><span> </span><span>University</span></p>

</div>

</div>
Permalink | Reply | 0 comments |

Gmane