[Tinyos-help] about 6lowpan in tinyos-2.x

2009-04-08 Thread Kye-Myung Jung
I know that tinyos-2.x has the 6lowpan id 
 
I've seen the follows in CC2420.h file 
 
/**
 * The 6LowPAN NALP ID for a TinyOS network is 63 (TEP 125).
 */
#ifndef TINYOS_6LOWPAN_NETWORK_ID
#define TINYOS_6LOWPAN_NETWORK_ID 0x3f
#endif
 
I wonder 0x3f is specified in RFC or draft. 
If I implement 6lowpan in tinyos-2.x, should I use this id? 
 
thank you in advance. 
 
 
---
iBIT Technologies, Inc.
Research Engineer  Kye-Myung Jung
Tel : 82-31-478-0678  Fax : 82-31-478-0677
Mobile : 82-10-2736-8334
E-mail : jgm2...@ibitworld.com
---
 
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Problem with __attribute__((C))

2009-04-08 Thread Rannouna Rania


Hi,

I have a library already linked with my application when I compile withmake pc 
I have no problem, but when I compile using make telosb the compiler don't 
recognize functions called from the library and I obtain this error:

$ make telosb
mkdir -p build/telosb
compiling Miller to a telosb binary
ncc -o build/telosb/main.exe -O -I. -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnes
c-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -I%T/lib/Deluge -Wl
,--section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DIDENT_PROGRAM_NA
ME=\"Miller\" -DIDENT_USER_ID=\"rania\" -DIDENT_HOSTNAME=\"your-01199f19b2\" -DI
DENT_USER_HASH=0x23006c1eL -DIDENT_UNIX_TIME=0x49dc6ac8L -DIDENT_UID_HASH=0xee2d
ba53L -mdisable-hwmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio Miller.nc -lm -L. -l
miracl
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x140): In function `m
ain':
app.c:undefined reference to `mirsys'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x14e):app.c: undefine
d reference to `mirvar_mem'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x160):app.c: undefine
d reference to `epoint_init_mem'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x172):app.c: undefine
d reference to `epoint_init_mem'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x184):app.c: undefine
d reference to `epoint_init_mem'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x198):app.c: undefine
d reference to `epoint_init_mem'
/cygdrive/c/DOCUME~1/rania/LOCALS~1/Temp/ccxBD1vb.o(.text+0x1ac):app.c: undefine
d reference to `ecurve2_add'
make: *** [exe0] Error 1

I guess the solution is to use the __attribute__((C)) after each undefined 
function but the problem when I compile after adding the  __attribute__((C))  I 
obtain this:

$ gcc -c -m32 -O2 mrec2m.c
In file included from mrec2m.c:29:
miracl.h:791: warning: `C' attribute directive ignored
miracl.h:821: warning: `C' attribute directive ignored
miracl.h:1048: warning: `C' attribute directive ignored

The problem that the C attribute is ignored.

Have you please any idea about this problem ?? 

Ragards,
Rania 


  ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] BlockWrite BlockRead(telosb)

2009-04-08 Thread giorgio
I'am new of tinyos and I'am writing a program test to write and read on memory 
flash of telosb(msp430).I have understand the general idea of volume and so I 
have create a xml file for the volume and I use printf to see what I write and 
what I read .I use kubuntu 8.10 with eclipse with plugin yeti 2 .My problem is 
that I have alway writeDone and readDone success but when show what I read 
doesn't match with I would write.
I must use a minum packet size ? for address I start from 0 and for each write 
I add addr with addr = addr + len with len the number of byte write.
I write an array of uint16_t [480] and I populate this with numbers 
1..first write then for the second write I populate with ...:I can 
write with BlockWrite number on the flash or I must use esadecimal format or 
other ?When I write I must before erase the block where I want to write or not 
?As you see I have many questions :I have try on the forum but for the moment 
I haven't found .
Every information is appreciate.
Thanks a lot

Giorgio
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Unstable compilation

2009-04-08 Thread Nouha Baccour
Hi all,
I am working on CTP and particularly on link estimation. I added some
fields in the structure of packet header, neighbor table entry,
routing table entryin order to evaluate my contribution.

When I compile my application (make micaz sim) , sometimes I get
"Successfully built micaz TOSSIM library" and sometime I get a series
of errors!!!

As follow an extract of these errors:

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: In function
`SubReceive.receive':
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1133: implicit
declaration of function `dbg'

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1136: warning: passing argument

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1136: warning: passing argument
1 of `Packet.getPayload' from incompatible pointer type

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1137: warning: passing argument
1 of `Packet.payloadLength' from incompatible pointer type

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1137: warning: passing argument
1 of `Receive.receive' from incompatible pointer type

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1137: warning: return
from incompatible pointer type

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: At top level:
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1140: conflicting
types for `Packet.clear'
...
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: In function `Packet.clear':
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1141: warning: passing argument
1 of `SubPacket.clear' from incompatible pointer type

/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: At top level:
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1146: conflicting
types for `Packet.payloadLength'

/opt/tinyos-2.x/tos/interfaces/Packet.nc:67: previous declaration of
`Packet.payloadLength'
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: In function
`Packet.payloadLenth':
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1149: warning: passing argument
1 of `SubPacket.payloadLength' from incompatible pointer type
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: At top level:
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1156: conflicting types for `Pa
ket.setPayloadLength'
/opt/tinyos-2.x/tos/interfaces/Packet.nc:83: previous declaration of `Packet.set
ayloadLength'
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: In function `Packet.setPayload
ength':
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1162: warning: passing argument
1 of `SubPacket.setPayloadLength' from incompatible pointer type
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: At top level:
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1170: conflicting types for `Pa
ket.getPayload'
/opt/tinyos-2.x/tos/interfaces/Packet.nc:115: previous declaration of `Packet.ge
Payload'
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc: In function `Packet.getPayload
:
/opt/tinyos-2.x/tos/lib/net/le/LinkEstimatorP.nc:1171: warning: passing argument
1 of `SubPacket.getPayload' from incompatible pointer type
In file included from /opt/tinyos-2.x/tos/system/AMSenderC.nc:49,
 from /opt/tinyos-2.x/tos/lib/net/ctp/CtpP.nc:136,
 from /opt/tinyos-2.x/tos/lib/net/ctp/CollectionC.nc:69,
 from SimulStudyAppC.nc:6:
In component `AMQueueEntryP':
/opt/tinyos-2.x/tos/system/AMQueueEntryP.nc: At top level:
/opt/tinyos-2.x/tos/system/AMQueueEntryP.nc:47: conflicting types for `AMSend.se
d'
/opt/tinyos-2.x/tos/interfaces/AMSend.nc:69: previous declaration of `AMSend.sen
'
/opt/tinyos-2.x/tos/system/AMQueueEntryP.nc: In function `AMSend.send':
/opt/tinyos-2.x/tos/system/AMQueueEntryP.nc:48: warning: passing argument 1 of `
MPacket.setDestination' from incompatible pointer type
/opt/tinyos-2.x/tos/system/AMQueueEntryP.nc:49: warning: passing argument 1 of `
...
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `Init.init':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:219: warning: passing argum
nt 1 of `BeaconSend.getPayload' from incompatible pointer type
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:221: implicit declaration o
 function `dbg'
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `StdControl.st
rt':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:232: implicit declaration o
 function `dbg'
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `StdControl.st
p':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:239: implicit declaration o
 function `dbg'
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `RadioControl.
tartDone':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:245: implicit declaration o
 function `dbg'
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `RadioControl.
topDone':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc:256: implicit declaration o
 function `dbg'
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutingEngineP.nc: In function `updateRouteTa
k.runTask':
/opt/tinyos-2.x/tos/lib/net/ctp/CtpRoutin

[Tinyos-help] bug of ftsp?

2009-04-08 Thread Jiangjie He
Hi, all
Recently I am reading the code of ftsp. I've noticed a problem in
/tinyos-2.1.0/tos/lib/ftsp/TimeSyncP.nc. At line 402, is it a mistype
of "TS_USER_MODE", which should be "TS_TIMER_MODE". In description of
interface TimeSyncMode, it said the timer is stopped when mode is set
to TS_USER_MODE. so is it a bug or just my misunderstanding?

TIA

Regards,
JIE
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] reg. the receiving a msg over the radio

2009-04-08 Thread Siva Sankar Gupta
Hello,

I have a doubt regarding the reception of a msg over the radio...
can a node receive the msg which it has sent over the radio(self receiving)?

If the question is wrong please excuse me

with regards
-- 
Siva Sankar Gupta Guggilum
Schubertstraße 19
Klagenfurt,9020
Austria
Ph:- 0043 6606871071
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Error using TOSSIM

2009-04-08 Thread Abhishek Phadnis
hey everyone,

have a problem running the test program with TOSSIM..


x...@ubuntu:~/tinyos/apps$ make telosb sim
mkdir -p simbuild/telosb
  placing object files in simbuild/telosb
  writing XML schema to app.xml
  compiling BlinkAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/telosb/sim.o -g -O0 -O -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate
-fnesc-nido-motenumber=sim_node\(\)   -mdisable-hwmul -Wall -Wshadow
-Wnesc-all -target=telosb -fnesc-cfile=simbuild/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"xiii\" -DIDENT_HOSTNAME=\"ubuntu\"
-DIDENT_USERHASH=0xa6363f6eL -DIDENT_TIMESTAMP=0x49dcaf93L
-DIDENT_UIDHASH=0x15f1f732L -Wno-nesc-data-race BlinkAppC.nc
-fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants
-fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags
-fnesc-dumpfile=app.xml
Unknown target telosb
Known targets for TinyOS directory /opt/tinyos-2.1.0/tos
and the specified include directories are:
  shimmer eyesIFXv1 eyesIFXv2 tinynode mica2dot null mica2 telosa intelmote2
micaz telosb iris
make: *** [sim-exe] Error 2


is there a problem in the installation?or do i have to upgrade any package
in ubuntu?


thanks
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] MAC protocols used in TinyOS 2.x?

2009-04-08 Thread Gary Lee
Hi,

I am wondering what is the default MAC protocol used in TinyOS 2.x? if it is
B-MAC, which file actually implements B-MAC?

Thanks,

Gary
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] To get the messurements in actual unit in MoteView using MDA300

2009-04-08 Thread Jijo P T
hi,

I need to interface some sensors (LVDT, Strain guage etc..) to crossbow's
MDA300 DAQ board (Radio module: IRIS). I am able to get the sensor
parameters in millivolt in moteview (in server message column). But we need
to get it converted to engineering unit (mm, micro strain...). is there any
possibility to get the same in moteview or mote explorer ..? for that i
configured MDA300 in configuration tab using polynomial conversion in mote
view, and i expect result in front page but its not coming


anybody know how to resolve these problem, please let me know and
any related comment highly appreciated

Thanks in advance
-- 
With Regards,
 JIJO P T
 STARMASS ARABIA
 RIYADH, KSA. ptj...@gmail.com
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] reg. the receiving a msg over the radio

2009-04-08 Thread Michael Schippling
nope. the radio is single duplex and either in recv or send mode, or off...
MS


Siva Sankar Gupta wrote:
> Hello,
> 
> I have a doubt regarding the reception of a msg over the radio...
> can a node receive the msg which it has sent over the radio(self receiving)?
> 
> If the question is wrong please excuse me
> 
> with regards
> -- 
> Siva Sankar Gupta Guggilum
> Schubertstraße 19
> Klagenfurt,9020
> Austria
> Ph:- 0043 6606871071
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


Re: [Tinyos-help] Compilation error - component not found

2009-04-08 Thread Michael Schippling
If you're getting the wrong version of an interface file
you may be in for more trouble than you like because the
code you want to use may not be written for the platform
you are on... But you can go look in the various platform
specific directories for a ".platform" file, e.g.:
 tos/platform/mica2/.platform
(on T1, T2 changed the names some...)
and see what order this define shows:
 @commonplatforms = ("mica128", "mica", "avrmote");
and you can also experiment with including the directory
containing the file you really want in the CFLAGS and PFLAGS.

Adding a "-v" to the PFLAGS will also list all the include
paths during the compile.

MS

Kim Noble wrote:
> Thanks Michael,
> That has made a difference - however the compiler reports errors within
> TimeSyncM as it is picking up the wrong version of Timer.  How can I
> force the compiler to use the correct Timer interface?   
> TIA
> Kim
> 
> -Original Message-
> From: Michael Schippling [mailto:sc...@santafe.edu] 
> Sent: 07 April 2009 17:58
> To: Kim Noble
> Cc: tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] Compilation error - component not found
> 
> Try putting that directory in your makefile with:
> 
> PFLAGS += -IC:/Crossbow...
> 
> (or it might be CFLAGS)
> 
> I believe forward slashes '/' are the kind to use.
> 
> MS
> 
> 
> Kim Noble wrote:
>> Apologies if this has been asked before, but I cannot find it on FAQ.
> 
>> Why when I include Crossbow's TimeSyncService component, do I get the 
>> 'component not found error', when it is installed at
>>
>> C:\Crossbow\cygwin\opt\MoteWorks\tos\lib\TimeSync
>>
>> TIA
>>
>> Kim  
>>
>>  
>>
>>  
>>
>>
>> This email has been scanned for all known viruses by the MessageLabs 
>> Email Security System.
>>
>> Systems Engineering & Assessment Ltd - Beckington Castle, 17 Castle 
>> Corner, Beckington, Frome, Somerset, BA11 6TA, UK
>> is registered in England and Wales with the company number 2430846.
>>
>> The contents of this email (including any attachments) are
> confidential 
>> and may be legally privileged.
>>
>> If you are not the intended recipient of this email any disclosure, 
>> copying, distribution or use of its contents is strictly prohibited.
> You 
>> should notify the sender immediately and then delete it (including any
> 
>> attachments) from your system.
>>
>> Please help out the environment by only printing this e-mail if 
>> absolutely necessary - Thank You.
>>
>>
>>
> 
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 
> This email has been scanned for all known viruses by the MessageLabs
> Email Security System.
> 
> Please help out the environment by only printing this e-mail if
> absolutely necessary - Thank You.
> 
> This email has been scanned for all known viruses by the MessageLabs Email 
> Security System.
> 
> Systems Engineering & Assessment Ltd - Beckington Castle, 17 Castle Corner, 
> Beckington, Frome, Somerset, BA11 6TA, UK 
> is registered in England and Wales with the company number 2430846.
> 
> The contents of this email (including any attachments) are confidential and 
> may be legally privileged. 
> 
> If you are not the intended recipient of this email any disclosure, copying, 
> distribution or use of its contents is strictly prohibited.  You should 
> notify the sender immediately and then delete it (including any attachments) 
> from your system.
> 
> Please help out the environment by only printing this e-mail if absolutely 
> necessary - Thank You.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] TestSerial Issue

2009-04-08 Thread MOHSIN MURAD

hello,

i am using Ubuntu 8.10 - the Intrepid and have installed the tinyos-2.1.0 using 
the synaptic package manager.  
when i write u...@ubuntu:/opt/tinyos-2.1.0/apps/tests/TestSerial$ make telosb 
,it returns the following errors

mkdir -p build/telosb
javac -target 1.4 -source 1.4 *.java
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Message.java:84: cannot 
find symbol
symbol  : class SerialPacket
location: class net.tinyos.message.Message
  private SerialPacket serialPacket;
  ^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Message.java:676: cannot 
find symbol
symbol  : class SerialPacket
location: class net.tinyos.message.Message
  public SerialPacket getSerialPacket() {
:
:
:

/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:345: 
possible loss of precision
found   : int
required: byte
escaped[escapePtr++] = ESCAPE_BYTE;
   ^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:353: 
possible loss of precision
found   : int
required: byte
  escaped[escapePtr++] = SYNC_BYTE;
 ^
22 errors
make: *** [TestSerial.class] Error 1

can someone help me out with this?


Regards,
Mohsin Murad



_
Drag n’ drop—Get easy photo sharing with Windows Live™ Photos.

http://www.microsoft.com/windows/windowslive/products/photos.aspx___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TinyOS 2.1 Tools - Mac OS X 10.5.6

2009-04-08 Thread samualef
Hi all,
I recently bought a MacBook Pro, and I installed TinyOS 2.1 following the guide 
on the TinyOS web site.
Everything seems to work (I can compile my TinyOS applications with "make 
telosb"), except the java jni libraries.
Every time I run the serialforwarder or others java serial applications, I get 
the message:
"The toscomm JNI library was not found.
Check that your tinyos-tools package is installed and try
rerunning tos-install-jni.
Aborting."

I run several times the tos-install-jni, and my jni libraries are correctly 
placed in /Library/java/Extensions.
I tried to add to the TOSCommLibraryLoader.java some debug print, and this is 
the result:
java.lang.UnsatisfiedLinkError: /Library/Java/Extensions/libtoscomm.jnilib: 
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1822)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1739)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1030)
at 
net.tinyos.comm.TOSCommLibraryLoader.load(TOSCommLibraryLoader.java:33)
at net.tinyos.comm.TOSCommJNI.(TOSCommJNI.java:14)
at net.tinyos.comm.NativeSerial.getTOSCommMap(NativeSerial.java:207)
at net.tinyos.comm.TOSSerial.(TOSSerial.java:282)
at 
net.tinyos.packet.SerialByteSource.openStreams(SerialByteSource.java:56)
at net.tinyos.packet.StreamByteSource.open(StreamByteSource.java:51)
at net.tinyos.packet.Packetizer.openSource(Packetizer.java:139)
at net.tinyos.packet.AbstractSource.open(AbstractSource.java:69)
at net.tinyos.packet.Packetizer.open(Packetizer.java:132)
at net.tinyos.packet.PhoenixSource.run(PhoenixSource.java:167)
/Library/Java/Extensions/libtoscomm.jnilib: 
The toscomm JNI library was not found.
Check that your tinyos-tools package is installed and try
rerunning tos-install-jni.
Aborting.

My java version is:
$ java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06-153)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_07-b06-57, mixed mode)


Thank you for any help or suggestions.

Regards,
Samuele.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS 2.1 Tools - Mac OS X 10.5.6

2009-04-08 Thread Greg Hackmann
On 4/8/09 3:43 PM, samua...@alice.it wrote:
> My java version is:
> $ java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06-153)
> Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_07-b06-57, mixed mode)
>
>
> Thank you for any help or suggestions.
>
> Regards,
> Samuele.

You're using Java 6, which is 64-bit on OS X.  When you built 
libtoscomm.jnilib, it was almost certainly built as a 32-bit library. 
You can confirm this by running "file 
/Library/Java/Extensions/libtoscomm.jnilib" (if it says "Mach-O bundle 
i386", it's 32-bit).  You can't use 32-bit JNI libraries with a 64-bit 
Java VM, so Java is completely ignoring it.

The simplest fix is to make the 32-bit J2SE 5.0 VM the default by 
running Java Preferences and dragging it to the top of the list.

Or, you could try to compile libtoscomm.jnilib as a 64-bit library.  I'm 
not sure how to do that, though.

Greg Hackmann
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] XMeshBase with one_hop_broadcast

2009-04-08 Thread Yong Sheng Low
Dear Sirs/Mdms,

I've programmed a Xmesh-based network which is working in the  
following manner:

I have Member Motes which mainly form the spine of the network and  
forwards data sent by other motes to the base (automatically  
implemented by Xmesh). It also periodically sends back information  
about itself back to the base.

I have Leaf Motes which sends information to the Member Motes via one- 
hop-broadcast, from which the Member Motes encapsulates the  
information and sends it back to base.

The problem is now this: The Leaf motes are able to send back to base  
via the Member Motes fine, but when the Leaf mote is within range of  
the base, somehow the base is unable to register the one-hop-broadcast  
messages. Is Xmeshbase unable to register such messages?

My messages sent from the Leaf motes are coded as such:

call Send.send(TOS_BCAST_ADDR,MODE_ONE_HOP_BROADCAST,msg_radio,  
sizeof(XDataMsg))

May i know if there's any way to let the base see such messages?

Yongsheng
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


[Tinyos-help] Sentilla JCreate support

2009-04-08 Thread Chris Custine
Hi All,
Has anyone had any luck loading TinyOS 2.1 apps onto the Sentilla JCreate
motes?  I have been working at it for a few days with no luck.  Using the
included tos-bsl I get:
$ make telosb install bsl,/dev/tty.usbserial-M4ASU2X7
mkdir -p build/telosb
compiling BlinkAppC to a telosb binary
ncc -o build/telosb/main.exe  -Os -O -mdisable-hwmul -Wall -Wshadow
-Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"ccustine\" -DIDENT_HOSTNAME=\"cgcmac1.home.cu\"
-DIDENT_USERHASH=0xd159fcfdL -DIDENT_TIMESTAMP=0x49dd9a6cL
-DIDENT_UIDHASH=0x709a81c4L  BlinkAppC.nc -lm
compiled BlinkAppC to build/telosb/main.exe
2650 bytes in ROM
  55 bytes in RAM
msp430-objcopy --output-target=ihex build/telosb/main.exe
build/telosb/main.ihex
writing TOS image
cp build/telosb/main.ihex build/telosb/main.ihex.out
installing telosb binary using bsl
tos-bsl --telosb -c /dev/tty.usbserial-M4ASU2X7 -r -e -I -p
build/telosb/main.ihex.out
MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass Erase...

An error occoured:
Timeout
make: *** [program] Error 1

With the tmote-bsl from the Sentilla distro I get the following result:

$ make telosb install bsl,M4ASU2X7
mkdir -p build/telosb
compiling BlinkAppC to a telosb binary
ncc -o build/telosb/main.exe  -Os -O -mdisable-hwmul -Wall -Wshadow
-Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"ccustine\" -DIDENT_HOSTNAME=\"cgcmac1.home.cu\"
-DIDENT_USERHASH=0xd159fcfdL -DIDENT_TIMESTAMP=0x49dd9ac8L
-DIDENT_UIDHASH=0x7637a681L  BlinkAppC.nc -lm
compiled BlinkAppC to build/telosb/main.exe
2650 bytes in ROM
  55 bytes in RAM
msp430-objcopy --output-target=ihex build/telosb/main.exe
build/telosb/main.ihex
writing TOS image
cp build/telosb/main.ihex build/telosb/main.ihex.out
installing telosb binary using bsl
/opt/SentillaWork-1.1.01//SentillaWork/plugins/com.sentilla.work_1.1.1/tmote-bsl
-bsl=mini -c M4ASU2X7 -r -e -I -p build/telosb/main.ihex.out
devlist: 1
Error, FT_OpenEx, device not opened
make: *** [program] Error 1

Anyone have any experience or suggestions on this?

Thanks,
Chris

--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help