[Tinyos-help] (no subject)
km.musta...@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] /home/tiny1/tinyos-1.x/contrib/handhelds/apps/BioMOBIUS/Reconfigurable does not compile
Hi Mike, That Reconfigurable code is old and unsupported, and there are much much better examples in shimmer's tos2 contrib folder. But that said, the problem with compiling the code is down to changes made to the shimmer platforms in tinyos-1.x a long time ago. The shimmer and shimmer2 have the same accelerometer chip on them, the freescale mma7260, but the shimmer2r has a different one, specifically the freescale mma7361. As a result the shimmers accel interface was generalised to allow the same applications to be compiled for both chips. What this means to you is that you need to perform the following changes to get the code to compile: - in Reconfigurable.nc change all references to "MMA7260_AccelM" to "AccelC" - in ReconfigurableM.nc change the two references to "MMA7260_Accel" to "MMA_Accel" After those changes the code will at least compile, but as to how well it will work for your intended application is a different story. I would strongly recommend that you instead start with the JustFatLogging (or HostTimeLogging) application in the tinyos-2.x-contrib/shimmer/apps directory, and add Bluetooth functionality to it (but remember that having the BT active while saving to the microSD card will have a fairly large battery life penalty). Take a look at tinyos-2.x-contrib/shimmer/swtest/Bluetooth for a simple BT example app. Or instead if you are looking to keep the "reconfigurable" nature of the app, start with the BoilerPlate app (in tinyos-2.x-contrib/shimmer/apps) and add JustFatLogging's functionality, but this might be a more difficult route to go down to begin with. Mike On Sun, Apr 17, 2011 at 5:03 PM, Mike wrote: > Hi there, > > I'm having some trouble trying to use the firmware "Reconfigurable" from > /home/tiny1/tinyos-1.x/contrib/handhelds/apps/BioMOBIUS/Reconfigurable > on my Shimmer 2r device. I'm using the VMware player virtual linux > environment that came with the SHIMMER devices to try and program them > and have successfully installed the Blink app and also the > BioMOBIUS/AccelGyro app. However, for the functionality that I need > (Connect via bluetooth to start storing data to SD simultaneously from a > number of SHIMMER devices) the firmware "Reconfigurable" seems to be > able to do all this. However, when I repeat the same command used to > successfully program other firmware (make shimmer2r install > bsl,/dev/ttyUSB0) I get the following error: > > In the component `Reconfigurable': > Reconfigurable.nc:74: no match > make: *** [exe0] Error 1 > > I've googled this and found nothing that seems to indicate my problem > (except maybe that I have a drive that is inaccessible?) and I can't > seem to find anyone else that has used the Reconfigurable firmware. Line > 74 of Reconfigurable.nc is: > > ReconfigurableM.Accel-> MMA7260_AccelM; > > I am not experienced in Tinyos, NESC or linux and so am unsure what this > means and how to continue, any help would be greatly appreciated! In > ReconfigurableM.nc the only reference to the above line that I can see is: > > includes MMA7260_Accel; > > and: > > interface MMA7260_Accel as Accel; > > I'm also wondering if theres an easier work around to get a number of > SHIMMER devices to start recording to SD simultaneously? > > Many thanks for any help or advice, > > Mike > ___ > 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
[Tinyos-help] Routing protocols in tossim
Hello, I am looking at the routing protocols available in TOSSIM. I have come across TYMO in their tutorial. I am looking at it. but it is a reactive protocols. are their any other protocols that are available. A protocol that we can have more control of. Regards, shamali ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Installing Tinyos 2.1.0 on a Ubuntu 10.10 system
Hello to everyone. It's the first time i write to this forum. I was working with Tinyos 2.1.0 on a Ubuntu 32 bit system installed in vmware, and it worked ok. Now i'm trying to make it work in a Ubuntu 64 bit, 10.10. I can compile and install programs into MICAZ motes. FINE. But i can't get Serial readings. I get the following messages from Tinyos: TOS-CHECK-ENV output: t*os-check-env completed with errors: * *--> WARNING: The JAVA version found first by tos-check-env may not be version 1.4 or version 1.5one of which is required by TOS. Please ensure that the located Java version is 1.4 or 1.5* *--> WARNING: The graphviz (dot) version found by tos-check-env is not 1.10. Please update your graphviz version if you'd like to use the nescdoc documentation generator.* TOS-INSTALL-JNI output: *jx@x-Inspiron-1750:~$ sudo tos-install-jni* *[sudo] password for juan: * *[: 31: =: unexpected operator* *Installing 64-bit Java JNI code in /usr/lib/jvm/java-6-sun/jre/lib/amd64 ... * *done.* I have been searching for solutions to this problem around the web, but anything that i have seen has helped to me. I tried to uninstall JAVA6, and installing JAVA5 later, but it didn't work. Now I have reinstalled JAVA6. I would be grateful if anyone of you have a solution to this problem, would help me. Thanks very much. Greetings ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Installing Tinyos 2.1.0 on a Ubuntu 10.10 system
Hi Juan,
I'm developing in Cygwin environment but also had some trouble with
versions when I installed TinyOS. I can therefore already help you a
bit but not on what directly concerns Ubuntu 64 bits.
Regarding tos-check-env, I think you can simply ignore the "errors".
These are simple warnings which check for old versions of
Java/graphviz which are hardcoded in the tos-check-env script. As far
as I know, Java 1.6 is supported and should not cause trouble as well
as older graphviz/dot versions. I could generate nesdoc with newer
graphviz at least.
If you want to get rid of tos-check-env warnings, you can open the
tos-check-env.sh script and change following lines:
in sub chk_java() function, replace
if ($_ =~ /version \"1\.[45]/) {
by
if ($_ =~ /version \"1\.[456]/) {
This will tell the script that 1.6 is also OK
in sub chk_graphviz function you can simply drop the test on the
version number. If you have dot installed on Ubuntu, it will for sure
be higher than 1.10 ! for this, replace
$versionok = 1 if /1\.10/;
by
$versionok = 1
With these 2 changes, tos_check_env should be happy.
Regarding the tos-install-jni problem, could you post your
tos-install-jni.sh script ? It would help people on the list to
understand what produced the error at line 31.
By the way did you check in /usr/lib/jvm/java-6-sun/jre/lib/amd64 if
TinyOS libraries were installed ? Perhaps the script terminates with
an error but nevertheless copied the library files. You should have
libgetenv.so and libtoscomm.so files there if everything went smooth.
Regards,
Romain
On Mon, Apr 18, 2011 at 12:54 PM, Juan Garrido Castellano
wrote:
> Hello to everyone.
>
> It's the first time i write to this forum.
>
> I was working with Tinyos 2.1.0 on a Ubuntu 32 bit system installed in
> vmware, and it worked ok.
>
> Now i'm trying to make it work in a Ubuntu 64 bit, 10.10. I can compile and
> install programs into MICAZ motes. FINE.
>
> But i can't get Serial readings. I get the following messages from Tinyos:
>
>
> TOS-CHECK-ENV output:
>
> tos-check-env completed with errors:
>
> --> WARNING: The JAVA version found first by tos-check-env may not be
> version 1.4 or version 1.5one of which is required by TOS. Please ensure
> that the located Java version is 1.4 or 1.5
> --> WARNING: The graphviz (dot) version found by tos-check-env is not 1.10.
> Please update your graphviz version if you'd like to use the nescdoc
> documentation generator.
>
> TOS-INSTALL-JNI output:
>
> jx@x-Inspiron-1750:~$ sudo tos-install-jni
> [sudo] password for juan:
> [: 31: =: unexpected operator
> Installing 64-bit Java JNI code in /usr/lib/jvm/java-6-sun/jre/lib/amd64 ...
> done.
>
> I have been searching for solutions to this problem around the web, but
> anything that i have seen has helped to me. I tried to uninstall JAVA6, and
> installing JAVA5 later, but it didn't work. Now I have reinstalled JAVA6.
>
> I would be grateful if anyone of you have a solution to this problem, would
> help me.
>
> Thanks very much.
>
> Greetings
>
>
>
>
> ___
> 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
[Tinyos-help] d.mat...@gmail.com
d.mat...@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] rfxlink for new byte radio
Hi Romain! On Mon, Apr 18, 2011 at 8:28 AM, Romain Bornet wrote: > Hi Miklos, > > Thanks for the quick and precise answer ! I think I have all pieces of > information I need to go on for now. > >>> Everything else is practically ready (I can write for you a packet layout >>> layer that is compatible with CC1000 and uses fewer bytes than 802.15.4). > If it doesn't take you much time I would really appreciate. It would > give me an additional reference to base my stuff on. Ok, I will do that. Question for you: how do you want ACKs? Currently, it is packet oriented, that is the ACK is a separate (very small) packet. If I know correctly, then on the CC1000 the ACK is really just a pulse of energy. So what do you plan to do? What chipset are we talking about? >>> Unfortunately there is no current documentation, other than emails. I plan >>> to write it up soon, but found no time to do it yet. > Once I will have dived deep into rfxlink and understood its features > and details, I'm ready to help you and write part of the > documentation. In which format do you plan to write it ? As a TEP? > Something similar to the CC2420 TEP126 > (http://www.tinyos.net/tinyos-2.1.0/doc/html/tep126.html) or Packet > Link Layer TEP127 > (http://www.tinyos.net/tinyos-2.1.0/doc/html/tep127.html) or would you > prefer a separate documentation ? A TEP would be fine. Miklos > > Best regards, > Romain > > On Fri, Apr 15, 2011 at 5:23 PM, Miklos Maroti > wrote: >> Ho Romain, >> >> On Fri, Apr 15, 2011 at 3:27 PM, Romain Bornet wrote: >>> Hi TinyOS gurus, >>> >>> I'm currently porting TOS to a new CPU architecture (low-power SoC >>> with integrated radio) and will start soon with the writing of the >>> radio driver/stack for this chip. >>> The radio peripheral does not support advanced features in hardware >>> (no FIFOs, no hardware address recognition, no 802.15.4 features...) >>> and can only send/receive single bytes. By looking at the different >>> radios supported by TOS, I found that the CC1000 seems to provide >>> rather similar features and that it is also a "byte radio". >>> >>> The current CC1000 implementation is not based on rfxlink and I wonder >>> if it could be supported by rfxlink or not ? Or in other words: is >>> there any strong dependence on 802.15.4 in rfxlink that would prevent >>> its use with simpler Sub-1GHz byte radios ? >> >> You can use the rfxlink library to support non 802.15.4 radios. In >> fact we have an SI443x based mote and plan to use rfxlink for the >> driver. I would suggest you to use rfxlink as it is actively >> maintained, supports other chips and you get improvements will >> automatically (e.g BLIP support, LPL improvements). >> >>> And a second question... Is there some detailed documententation on >>> rfxlink, its architecture, its configuration options,... ? I can for >>> sure walk through the code and figure it out myself but if it's >>> already summarized somewhere I would probably jump in more quickly :-) >> >> Unfortunately there is no current documentation, other than emails. I >> plan to write it up soon, but found no time to do it yet. Here is some >> info I have copied from an older mail. I have updated stuff to match >> what is currently in the mainline: >> >> 1) Everything is in lib/rfxlink. The layers and util subdirectories >> are chip independent. All rf230 specific code is in the chips/rf230 >> directory. The RF230RadioC connects all components. On top of that are >> the RF230ActiveMessageC, RF230Ieee154MessageC and >> RF230TimeSyncMessageC. You want to look at RF230RadioC. >> >> 2) The RF230RadioC radio stack is a vertical layer of components. The >> components come from the layer directory. Most components need some >> configuration interface (to adopt it to the particular radio chip), >> which are implemented in RF230RadioP. There is very little >> interconnection between layers, so you can mix and match it. >> >> 3) The lowest layer is the RF230DriverLayerC, an important middle >> layer is the MessageBufferLayerC, and finally comes the >> ActiveMessageLayer and/or Ieee154MessageLayerC on top. Every >> communication between the RF230DriverLayerC and the >> MessageBufferLayerC is happening in interrupt context via the >> RadioSend/RadioReceive and RadioState interfaces. Everything above the >> MessageBuffer is in task context and communication is via BareSend and >> BareReceive (almost the same as Send and Receive). This is important, >> since we want fast software ACKs but only want to send it if we can >> surely deliver it (have some buffer space), so all of this is done in >> interrupt context, while the rest of the processing is done from >> tasks. >> >> 4) You can configure to run the interrupt context code in task context >> with a simple define (TASKLET_IS_TASK) or keep it in interrupt >> context. These tasklets are funny. When run in interrupt context you >> still do not need atomic sections (the whole RF230 driver contains a >> couple 2-3 line atomic se
[Tinyos-help] using 6lowpan on telosb tprca2400ca trp2410ca
hi all, i'm new in using tinyos and nesc, i would like to know what i have to do to use 6lowpan on telosb, i mean i have to give the ability to the devices to communicate with ipv6 packet by 6lowpan and rpl. Regards, Daniele. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Help: HplAtm128TimerCtrl16 and Hpl128Compare
Hi Gerald, Please see my answers below. On Sun, Apr 17, 2011 at 3:45 PM, Gerald Stanje wrote: > Hello, > > I use the interfaces HplAtm128TimerCtrl16 and Hpl128Compare. > > At the beginning I set: > Atm128TimerCtrlCompare_t compare; > Atm128TimerCtrlCapture_t capture; > > compare.bits.comA = 1; // OC3A toggle on compare match > compare.bits.comB = 1; // OC3B toggle on compare match > capture.bits.wgm32 = 1;// what is this? This is to configure waveform generation. There's a huge table that helps you set the correct value of the WGMn2 bit in the data sheet. The correct value pretty much depends on what you want to do. > capture.bits.cs = 1; // == clocksource of what? This sets the clock source of the timer. The table with the possible values and their meanings are in the data sheet. I don't think you would want to change whatever this bit is set to, otherwise you risk breaking things in TinyOS. > call TimerCtrl.setCtrlCompare(compare); > call TimerCtrl.setCtrlCapture(capture); > > call CompareB.set(6); > call CompareA.set(1000); > > at what time does the timer start to run? They are started at boot time by the initialization code, before tasks start running. > how could i reset the timer to zero? You can write 0 to the corresponding timer/counter register. However, it is not recommended for timers/counters that are used elsewhere in the system, because that could potentially break things. What you should do instead is "remembering" a reference time value, wait for the caputure event, and subtract the the reference time value from the captured one to figure out how much time had passed in between. > why does the interrupt of CompareA.fired still come after I called > CompareA.stop()? It should not come, because CompareA.stop() clears the interrupt flag. Are you sure that that the interrupt flag does not get gets reasserted somewhere else in your code? Janos ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] rfxlink for Telos
Hey Markus, The reason why I have only checked in the micaz version of the cc2420x stack is that the telos timer subsystem must be reconfigured "significantly" in order for the microsecond timestamping to work. Specifically, we have to make sure two things: a) the SPI bus is fast enough to download from/upload to the FIFO in real time, and b) that the SFD is captured by the microsecond counter (vs. the asynchronous 32khz counter). I have the code for this in tinyos-2.x-contrib/vu. Specifically, the code that configures the timer subsystem in is tos/msp430, and the altered timer map is in platforms/telosa. RADIO_ALARM_MICROSEC can safely be set to 1, since the mote runs close to 4MHz, which when prescaled by 4 will give a microsecond timer (and alarm, therefore). For the same reason, RADIO_ALARM_MILLI_EXP should be set to 10. Janos On Fri, Apr 15, 2011 at 5:04 AM, Markus Becker wrote: > Hello, > > I was checking out rfxlink and whether it works on TelosB nodes. I didn't see > support in the repository nor someone working on it on the mailing list. > > So I got started with it and wired things together for TelosB: > http://www.comnets.uni-bremen.de/gitweb/?p=mab-tinyos- > main.git;a=commit;h=3df542e639efcaea007127b28691d45c99768bf9 > > rfxlink/TestTransmit compiles for telosb now at least. > > I don't know how to calculate the values for RADIO_ALARM_MICROSEC and > RADIO_ALARM_MILLI_EXP , though. Would someone advise me please? > > BR, > mab > > > | Dipl.-Ing. Markus Becker > | Communication Networks > | Mobile Research Center > | TZI - Center for Computing Technologies > | University Bremen > | Germany > > ___ > 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] using 6lowpan on telosb tprca2400ca trp2410ca
Hi Daniele, you can start with the Blip tutorial, and learn how to setup a 6lowpan/ipv6 subnet in tinyos. You find the tutorial at http://docs.tinyos.net/index.php/BLIP_Tutorial Regards pietro 2011/4/18 daniele mattiacci > hi all, > i'm new in using tinyos and nesc, i would like to know what i have to do to > use 6lowpan on telosb, i mean i have to give the ability to the devices to > communicate with ipv6 packet by 6lowpan and rpl. > Regards, > Daniele. > > ___ > 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] using 6lowpan on telosb tprca2400ca trp2410ca
molte grazie pietro, lo spulcerò fino alla fine ;) Thanks pietro, i'll read it at all ;) 2011/4/18 PIETRO GONIZZI > Hi Daniele, > > you can start with the Blip tutorial, and learn how to setup a 6lowpan/ipv6 > subnet in tinyos. > You find the tutorial at > http://docs.tinyos.net/index.php/BLIP_Tutorial > > Regards > pietro > > 2011/4/18 daniele mattiacci > >> hi all, >> i'm new in using tinyos and nesc, i would like to know what i have to do >> to use 6lowpan on telosb, i mean i have to give the ability to the devices >> to communicate with ipv6 packet by 6lowpan and rpl. >> Regards, >> Daniele. >> >> ___ >> 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] Routing between two computers using IPBaseStation with blip
Also, When I manually add a route to it:
ip -6 route add fec0::65 dev tun0
and ping6 fec0::65
I get From fec0::64 icmp_seq=3 Time exceeded: Hop limit
Thanks,
Aaron
On Mon, Apr 18, 2011 at 1:00 PM, Aaron Rosen wrote:
> Hi Pietro,
>
> Thanks for your reply. So now I'm running two laptops with the
> IPBaseStation and then having one mote in the middle running UDPEcho.
>
> Right now I have my laptop with a mote plugged into it with address
> fec0::64 and that is able to ping the mote in the middle running the UDPEcho
> (fec0::1). On the other laptop I have IPBaseStation also running with
> address fec0:65. Though I'm unable to ping that node and the node plugged
> into my computer does not see a route to it.
>
> Any ideas how to fix this ("add: add a persistent link between
> n1 and n2" I'm not sure what that does)? Running wireshark on tun0 on the
> opposite edge routers does not show any packets from the other.
>
> Thanks,
>
> Aaron
>
>
> On Mon, Apr 18, 2011 at 3:55 AM, PIETRO GONIZZI <
> pietro.goni...@studenti.unipr.it> wrote:
>
>> Hi Aaron,
>>
>> do you want to create a route between the two laptops, each of them acting
>> as router for the same ipv6 subnet? In this case, I am not sure you can do
>> it with blip. You can try to deploy a host in the middle (e.g a mote with
>> the UdpEcho application installed for instance), and see what you get. You
>> should see from each laptop the configured mote address.
>> You can also deploy wireshark or some packet sniffer to monitor the
>> traffic from/to the laptop.
>>
>> pietro
>>
>> 2011/4/18 Aaron Rosen
>>
>>> Hello,
>>>
>>> I'm trying to create a route between two laptops using the IPBaseStation
>>> app with each laptop having a mote plugged into it. In serial_tun.conf I
>>> have the following:
>>>
>>> addr fec0::64 # addr fec0::65 for the other laptop
>>> proxy lo
>>> channel 15
>>>
>>> Now I install the IPBaseStation app on each mote and that goes
>>> successfully. Then I run ./ip-driver -c ../serial_tun.conf /dev/ttyUSB0
>>> telosb, after doing this the tun interface is created successfully. The
>>> problem I'm having though is the nodes do not seem to see each other
>>> therefore I can not create the connection between the two machines. Any
>>> ideas where I could be going wrong?
>>>
>>> blip:ke-desktop> ^C2011-04-17T19:40:59.142EST: INFO: driver shutting
>>> down
>>> arosen@ke-desktop:~/tinyos-2.1.1/support/sdk/c/blip/driver$ sudo
>>> ./ip-driver -c ../serial_tun.conf /dev/ttyUSB0 telosb
>>> 2011-04-17T19:41:48.688EST: INFO: Read config from '../serial_tun.conf'
>>> 2011-04-17T19:41:48.688EST: INFO: Using channel 15
>>> 2011-04-17T19:41:48.688EST: INFO: Retries: 5
>>> 2011-04-17T19:41:48.688EST: INFO: telnet console server running on port
>>> 6106
>>> 2011-04-17T19:41:48.692EST: INFO: created tun device: tun0
>>> 2011-04-17T19:41:48.970EST: INFO: interface device successfully
>>> initialized
>>> 2011-04-17T19:41:48.970EST: INFO: starting radvd on device tun0
>>>
>>> blip:ke-desktop> links
>>> 0x65[C]: dist: Inf
>>>
>>> blip:ke-desktop> routes
>>> 0x65:
>>>
>>> Thanks!
>>>
>>>
>>> --
>>> Aaron O. Rosen
>>> Masters Student - Network Communication
>>> 306B Fluor Daniel
>>> 843.425.9777
>>>
>>>
>>> ___
>>> Tinyos-help mailing list
>>> Tinyos-help@millennium.berkeley.edu
>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>>
>>
>>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> 843.425.9777
>
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
843.425.9777
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] rfxlink for Telos
On Mon, Apr 18, 2011 at 8:27 AM, Janos Sallai wrote: > Hey Markus, > > The reason why I have only checked in the micaz version of the cc2420x > stack is that the telos timer subsystem must be reconfigured > "significantly" in order for the microsecond timestamping to work. > If you are using standard interfaces that may be true. But the TelosB h/w timer is actually ticking at 1uis (binary microsecond ticks).The main mis (binary millisecond) timer is being clocked off a 32KiHz clock. The main clocks are shut down when the cpu goes to sleep. > Specifically, we have to make sure two things: a) the SPI bus is fast > enough to download from/upload to the FIFO in real time, and b) that > the SFD is captured by the microsecond counter (vs. the asynchronous > 32khz counter). > > I have the code for this in tinyos-2.x-contrib/vu. Specifically, the > code that configures the timer subsystem in is tos/msp430, and the > altered timer map is in platforms/telosa. > > RADIO_ALARM_MICROSEC can safely be set to 1, since the mote runs close > to 4MHz, which when prescaled by 4 will give a microsecond timer (and > alarm, therefore). For the same reason, RADIO_ALARM_MILLI_EXP should > be set to 10. > > Janos > > > On Fri, Apr 15, 2011 at 5:04 AM, Markus Becker > wrote: > > Hello, > > > > I was checking out rfxlink and whether it works on TelosB nodes. I didn't > see > > support in the repository nor someone working on it on the mailing list. > > > > So I got started with it and wired things together for TelosB: > > http://www.comnets.uni-bremen.de/gitweb/?p=mab-tinyos- > > main.git;a=commit;h=3df542e639efcaea007127b28691d45c99768bf9 > > > > rfxlink/TestTransmit compiles for telosb now at least. > > > > I don't know how to calculate the values for RADIO_ALARM_MICROSEC and > > RADIO_ALARM_MILLI_EXP , though. Would someone advise me please? > > > > BR, > > mab > > > > > > | Dipl.-Ing. Markus Becker > > | Communication Networks > > | Mobile Research Center > > | TZI - Center for Computing Technologies > > | University Bremen > > | Germany > > > > ___ > > 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 > -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Installing Tinyos 2.1.0 on a Ubuntu 10.10 system
Hi Romain,
Thank you for your quicky answer.
Ok, if those warnings doesn't crash the system to work, i don't mind
annoying them.
I've checked the folder /usr/lib/jvm/java-6-sun/jre/lib/amd64, and of
course, I can see the following libs, among others:
*libgetenv.so
libtoscomm.so*
So it seems to be ok.
The content of the tos-install-jni.sh file is:
#!/bin/sh
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
tinyoslibdir=$libdir/tinyos
jni=`tos-locate-jre --jni`
if [ $? -ne 0 ]; then
echo "Java not found, not installing JNI code"
exit 1
fi
if [ cygpath -w / >/dev/null 2>/dev/null ] || [ `uname` = "Darwin" ]; then
echo "Installing Java JNI code in $jni ... "
for lib in $tinyoslibdir/*.so; do
install $lib "$jni" || exit 1
done
else
java=`tos-locate-jre --java`
bits=32
if [ $? -ne 0 ]; then
echo "java command not found - assuming 32 bits"
elif file -L $java/java | grep -q 64-bit; then
bits=64
fi
echo "Installing $bits-bit Java JNI code in $jni ... "
for lib in $tinyoslibdir/*-$bits.so; do
realname=`basename $lib | sed -e s/-$bits\.so/.so/`
install $lib "$jni/$realname" || exit 1
done
fi
echo "done."
I have marked in red the line 31 in the script. Is the previous to the last
one. I think it doesn't say anything..
Regards,
Juan
2011/4/18 Romain Bornet
> Hi Juan,
>
> I'm developing in Cygwin environment but also had some trouble with
> versions when I installed TinyOS. I can therefore already help you a
> bit but not on what directly concerns Ubuntu 64 bits.
>
> Regarding tos-check-env, I think you can simply ignore the "errors".
> These are simple warnings which check for old versions of
> Java/graphviz which are hardcoded in the tos-check-env script. As far
> as I know, Java 1.6 is supported and should not cause trouble as well
> as older graphviz/dot versions. I could generate nesdoc with newer
> graphviz at least.
>
> If you want to get rid of tos-check-env warnings, you can open the
> tos-check-env.sh script and change following lines:
>
> in sub chk_java() function, replace
> if ($_ =~ /version \"1\.[45]/) {
> by
> if ($_ =~ /version \"1\.[456]/) {
>
> This will tell the script that 1.6 is also OK
>
> in sub chk_graphviz function you can simply drop the test on the
> version number. If you have dot installed on Ubuntu, it will for sure
> be higher than 1.10 ! for this, replace
>
> $versionok = 1 if /1\.10/;
> by
> $versionok = 1
>
> With these 2 changes, tos_check_env should be happy.
>
> Regarding the tos-install-jni problem, could you post your
> tos-install-jni.sh script ? It would help people on the list to
> understand what produced the error at line 31.
>
> By the way did you check in /usr/lib/jvm/java-6-sun/jre/lib/amd64 if
> TinyOS libraries were installed ? Perhaps the script terminates with
> an error but nevertheless copied the library files. You should have
> libgetenv.so and libtoscomm.so files there if everything went smooth.
>
> Regards,
>Romain
>
> On Mon, Apr 18, 2011 at 12:54 PM, Juan Garrido Castellano
> wrote:
> > Hello to everyone.
> >
> > It's the first time i write to this forum.
> >
> > I was working with Tinyos 2.1.0 on a Ubuntu 32 bit system installed in
> > vmware, and it worked ok.
> >
> > Now i'm trying to make it work in a Ubuntu 64 bit, 10.10. I can compile
> and
> > install programs into MICAZ motes. FINE.
> >
> > But i can't get Serial readings. I get the following messages from
> Tinyos:
> >
> >
> > TOS-CHECK-ENV output:
> >
> > tos-check-env completed with errors:
> >
> > --> WARNING: The JAVA version found first by tos-check-env may not be
> > version 1.4 or version 1.5one of which is required by TOS. Please ensure
> > that the located Java version is 1.4 or 1.5
> > --> WARNING: The graphviz (dot) version found by tos-check-env is not
> 1.10.
> > Please update your graphviz version if you'd like to use the nescdoc
> > documentation generator.
> >
> > TOS-INSTALL-JNI output:
> >
> > jx@x-Inspiron-1750:~$ sudo tos-install-jni
> > [sudo] password for juan:
> > [: 31: =: unexpected operator
> > Installing 64-bit Java JNI code in /usr/lib/jvm/java-6-sun/jre/lib/amd64
> ...
> > done.
> >
> > I have been searching for solutions to this problem around the web, but
> > anything that i have seen has helped to me. I tried to uninstall JAVA6,
> and
> > installing JAVA5 later, but it didn't work. Now I have reinstalled JAVA6.
> >
> > I would be grateful if anyone of you have a solution to this problem,
> would
> > help me.
> >
> > Thanks very much.
> >
> > Greetings
> >
> >
> >
> >
> > ___
> > 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] rfxlink for Telos
Eric, This actually has nothing to do with the standard interfaces. In fact, this reconfiguration is absolutely under the hood. Here it is, explained a bit more in detail: Currently, the DCO is used as a clock source for MCLK, and MCLK/4 is the source for SMCLK. TimerA is driven by SMCLK without prescaling. The SPI clock is SMCLK/2, which is 500kHz. By reprogramming the clock subsystem such that MCLK without prescaling is used for SMCLK, and using a prescaler of 4 to drive the 1uis clock (SMCLK/4), the SPI clock speed will jump to 2MHz. This way, the radio stack (and other SPI-limited operations) will be _much_ faster. The SFD pin of the CC2420 is connected to pin on the MSP430 that can capture timer/counter B but not timer/counter A. Therefore, to be able to timestamp with the microsecond clock, timer B must be clocked at 1uis, and timer A should be programmed as the 32kHz clock. (Currently, timer A is running at 1uis, and timer B at 32kHz.) I'd really appreciate if you could comment on this. Can you think of a particular reason why SMCLK was set to MCLK/4? Would it break anything if the clocks were set up as described above? We did use this setup in a live deployment, a fairly complex application that used the SPI bus, serial, I2C, had multihop routing, periodic timers, allowing the mcu to sleep, etc. One potential difference from the original clock setup is that in this case we are left with only 3 timer compare interfaces for the 32khz/1mis clocks, versus 7 in the original case. But since the 1mis clock is virtualized, this should not be a limitation. Janos On Mon, Apr 18, 2011 at 1:42 PM, Eric Decker wrote: > > > On Mon, Apr 18, 2011 at 8:27 AM, Janos Sallai > wrote: >> >> Hey Markus, >> >> The reason why I have only checked in the micaz version of the cc2420x >> stack is that the telos timer subsystem must be reconfigured >> "significantly" in order for the microsecond timestamping to work. > > If you are using standard interfaces that may be true. But the TelosB h/w > timer is actually ticking at 1uis (binary microsecond ticks). The main > mis > (binary millisecond) timer is being clocked off a 32KiHz clock. The main > clocks are shut down when the cpu goes to sleep. > >> >> Specifically, we have to make sure two things: a) the SPI bus is fast >> enough to download from/upload to the FIFO in real time, and b) that >> the SFD is captured by the microsecond counter (vs. the asynchronous >> 32khz counter). >> >> I have the code for this in tinyos-2.x-contrib/vu. Specifically, the >> code that configures the timer subsystem in is tos/msp430, and the >> altered timer map is in platforms/telosa. >> >> RADIO_ALARM_MICROSEC can safely be set to 1, since the mote runs close >> to 4MHz, which when prescaled by 4 will give a microsecond timer (and >> alarm, therefore). For the same reason, RADIO_ALARM_MILLI_EXP should >> be set to 10. >> >> Janos >> >> >> On Fri, Apr 15, 2011 at 5:04 AM, Markus Becker >> wrote: >> > Hello, >> > >> > I was checking out rfxlink and whether it works on TelosB nodes. I >> > didn't see >> > support in the repository nor someone working on it on the mailing list. >> > >> > So I got started with it and wired things together for TelosB: >> > http://www.comnets.uni-bremen.de/gitweb/?p=mab-tinyos- >> > main.git;a=commit;h=3df542e639efcaea007127b28691d45c99768bf9 >> > >> > rfxlink/TestTransmit compiles for telosb now at least. >> > >> > I don't know how to calculate the values for RADIO_ALARM_MICROSEC and >> > RADIO_ALARM_MILLI_EXP , though. Would someone advise me please? >> > >> > BR, >> > mab >> > >> > >> > | Dipl.-Ing. Markus Becker >> > | Communication Networks >> > | Mobile Research Center >> > | TZI - Center for Computing Technologies >> > | University Bremen >> > | Germany >> > >> > ___ >> > 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 > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] rfxlink for Telos
On Mon, Apr 18, 2011 at 1:04 PM, Janos Sallai wrote: > Eric, > > This actually has nothing to do with the standard interfaces. In fact, > this reconfiguration is absolutely under the hood. Here it is, > explained a bit more in detail: > I thought an interface might be involved because you were talking about timestamping. ie. Obtaining some kind of officially maintained time... that could be used. I timestamp stuff all the time when debugging in the guts of my code. But I do it by just nabbing TAR which is ticking at 1uis. Currently, the DCO is used as a clock source for MCLK, and MCLK/4 is > the source for SMCLK. TimerA is driven by SMCLK without prescaling. > The SPI clock is SMCLK/2, which is 500kHz. By reprogramming the clock > subsystem such that MCLK without prescaling is used for SMCLK, and > using a prescaler of 4 to drive the 1uis clock (SMCLK/4), the SPI > clock speed will jump to 2MHz. This way, the radio stack (and other > SPI-limited operations) will be _much_ faster. > That is a good. thing. On the mm4 mote (2618 based) I have a SD card that is driven off of an SPI and I want it to run as fast as possible so I did something similar. All the peripherals are run off SMCLK. In general the SMCLK should be run as fast as possible. It is unclear why the original choice of SMCLK = DCO/4 was chosen. Maybe Vlado can comment, I'm pretty sure he was there. > The SFD pin of the CC2420 is connected to pin on the MSP430 that can > capture timer/counter B but not timer/counter A. Therefore, to be able > to timestamp with the microsecond clock, timer B must be clocked at > 1uis, and timer A should be programmed as the 32kHz clock. (Currently, > timer A is running at 1uis, and timer B at 32kHz.) > okay now I understand. What exactly are you doing with SFD? Why the need for 1uis granularity? > > I'd really appreciate if you could comment on this. Can you think of a > particular reason why SMCLK was set to MCLK/4?. > I've been through the code pretty extensively and don't think that would break anything. Anyother msp430 folks see a problem? With Timer B clocked off the 32KiHz clock the minimum capture granularity is 30.5us. Do you really need uis precision? Is this something that the core msp430 code should support by default because of the telosb platform?This is clearly a platform dependancy. Abstractly, a msp430 platform needs to provide a uis tick source and a low power mis tick source for long term time. But the application you are discussing requires additional capture symantics. If the implementation details of the 1st two timing sources is hidden then it shouldn't be a problem moving things around to accomodate the capture issue. Would it break anything > if the clocks were set up as described above? I don't beleive so. But this is a platform thing should initially show up in platform overrides when building the image. Are you perhaps thinking that this should propagate into the core files above platform? We are currently refactoring the core msp430 files with the intent of supporting the different TI families. Current support families defined are x1 (msp430f149, msp430f1611), x2 (msp430f2616-2619), and x5 (cc430f5137, msp430f5438). One of the issues that has yet to be addressed is how to deal with timers and basic clocking. What basic clocks are required by a platform? And other things. What is a reasonable abstraction boundary that for example will allow one to deal with the problem you are describing. So if you want to take a crack at defining this that would be most helpful. I can help but am busy bringing in the x5 support. > We did use this setup in > a live deployment, a fairly complex application that used the SPI bus, > serial, I2C, had multihop routing, periodic timers, allowing the mcu > to sleep, etc. > Sound good to me. What did you use for the i2c driver? what kind of chip did you talk to? > > One potential difference from the original clock setup is that in this > case we are left with only 3 timer compare interfaces for the > 32khz/1mis clocks, versus 7 in the original case. Actually, putting the 1mis clock on TimerA gives 3 CCRs and the 1uis clock on TimerB gives 7 CCRs for the uis clock. But since the 1mis > clock is virtualized, this should not be a limitation. > In practice the additonal compare capture registers aren't utilized. If they do get used it is a special app that needs to handle the situation itself. > > Janos > > > On Mon, Apr 18, 2011 at 1:42 PM, Eric Decker wrote: > > > > > > On Mon, Apr 18, 2011 at 8:27 AM, Janos Sallai < > sal...@isis.vanderbilt.edu> > > wrote: > >> > >> Hey Markus, > >> > >> The reason why I have only checked in the micaz version of the cc2420x > >> stack is that the telos timer subsystem must be reconfigured > >> "significantly" in order for the microsecond timestamping to work. > > > > If you are using standard interfaces that may be true. But the TelosB > h/w > > timer is act
Re: [Tinyos-help] rfxlink for Telos
Eric: >> Currently, the DCO is used as a clock source for MCLK, and MCLK/4 is >> the source for SMCLK. TimerA is driven by SMCLK without prescaling. >> The SPI clock is SMCLK/2, which is 500kHz. By reprogramming the clock >> subsystem such that MCLK without prescaling is used for SMCLK, and >> using a prescaler of 4 to drive the 1uis clock (SMCLK/4), the SPI >> clock speed will jump to 2MHz. This way, the radio stack (and other >> SPI-limited operations) will be _much_ faster. > > That is a good. thing. On the mm4 mote (2618 based) I have a SD card that > is > driven off of an SPI and I want it to run as fast as possible so I did > something > similar. All the peripherals are run off SMCLK. In general the SMCLK > should > be run as fast as possible. It is unclear why the original choice of SMCLK > = DCO/4 > was chosen. Maybe Vlado can comment, I'm pretty sure he was there. Interestingly, the msp430x also uses DCO/4 for SMCLK. Any rational for that? >> The SFD pin of the CC2420 is connected to pin on the MSP430 that can >> capture timer/counter B but not timer/counter A. Therefore, to be able >> to timestamp with the microsecond clock, timer B must be clocked at >> 1uis, and timer A should be programmed as the 32kHz clock. (Currently, >> timer A is running at 1uis, and timer B at 32kHz.) > > okay now I understand. What exactly are you doing with SFD? Why the need > for 1uis granularity? The SFD pin is asserted when the SFD byte (after the preamble but before the payload) are received or transmitted. This is the best possible synchronization point between two motes. >> I'd really appreciate if you could comment on this. Can you think of a >> particular reason why SMCLK was set to MCLK/4?. > > I've been through the code pretty extensively and don't think that would > break anything. Anyother msp430 folks see a problem? > > With Timer B clocked off the 32KiHz clock the minimum capture granularity > is 30.5us. Do you really need uis precision? Microsecond precision timestamping is goal #1. Fast SPI is goal #2. > Is this something that the core msp430 code should support by default > because > of the telosb platform? This is clearly a platform dependancy. If you're referring to the fast SPI, than this applies to both msp430 and msp430x. If you're referring to the microsecond timestamping on the telos, then it is obviously telos specific. > Abstractly, a msp430 platform needs to provide a uis tick source and a low > power > mis tick source for long term time. But the application you are discussing > requires > additional capture symantics. What I'm describing is TEP132 and TEP133 compliance. > If the implementation details of the 1st two timing sources is hidden then > it shouldn't > be a problem moving things around to accomodate the capture issue. > >> Would it break anything >> if the clocks were set up as described above? > > I don't beleive so. But this is a platform thing should initially show up > in > platform overrides when building the image. Yes. It should go to platforms/telosb. > Sound good to me. What did you use for the i2c driver? what kind of chip > did you talk > to? A Xilinx Spartan 3 FPGA. Janos ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] toscomm.dll for 64bit Systems
Hi everyone, I have a problem. I did a java application using TinyOS stuff on my 32bit laptop. I ran that application on several 32bit Windows machines with no TinyOS installed just copying the toscomm.dll with the app. Now, I would like to make the application run on a 64bit Windows machine, but the problem is that the toscomm library is compiled for 32 bit systems. Can anyone give me the 64bit dll? Is it available somewhere? Thanks so much for your attention, Kind Regards, Antonio Guerrieri ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] About pogram error 57 in usip when trying to program a mote with cywin: Problem solved
I have the error57 problem. My OS is win7. use cygcheck -s, i got DLL version: 1.5.24. i hope this problem can be solved very soon. 2010/11/15 barbaran > > > Hi Michael, > > Yes, I remember you answered to my question, and I followed the topic on > the forum and I sae about 4 or 5 persons complaining about this issue, that > is not too much, and I'm not sure if it happens in every Windows. > > As you suggested, I ran cygcheck -s and the version of the DLL is 1.7.7, I > don't know which one was the older one, but I guess it could be the one you > put in your email. I agree with you, it would be a nice idea that everybody > that has experienced this error could post the DLL version so we can know > if it is a general error. > > Our experience here in Málagais that people that tries to install it and > find any problem move on to VMWare installation, probably that is why not > too many people has post the problem. > > Regards and thank you for the quick answer, > > Javier. > > > On Sun, 14 Nov 2010 11:30:39 -0700, Michael Schippling > wrote: > > I suppose it's too late to look at your old install, > > but can you run this in your new cygwin shell: > > > > cygcheck -s > > > > It will dump out a lot of info about paths and version > > numbers, one of which should be the base dll ID, like: > > > > Cygwin DLL version info: > > DLL version: 1.5.18 > > > > AFAIK, this is as close as one can get to a cygwin version ID. > > > > Perhaps others who have "error 57" problems can do the same > > and we may be able to get some traction on this. I haven't > > followed carefully, but I seem to remember the error being > > intermittent for some people. Is/was that true? > > > > MS > > > > > > barbaran wrote: > >> Hi all, > >> > >> Around March of this year I posted a problem when trying to program a > >> mote > >> using TinyOS installed over cygwin, and I got error 57 when using uisp. > >> Other folks told me that they had the same problem even in Windows XP > or > >> 7, > >> but no one solution came up, so in that days a take the option of > >> installing VMware, but now I dont want to use it anymore, so I searched > >> into avr forums, and it seems that installing a new version of cygwin > >> everything would be all right. > >> > >> Yesterday I tried again, using Windows 7, so... firstly, I installed > >> tinyos using cygwin and rpms available, from the tinyos website, I got > >> the > >> error 57 problem when trying to test Blink application into a micaZ. > >> Then, > >> without uninstalling anything, I downloaded a new version cygwin and > >> installed it over the other one, after a while installing (as the > >> installation program download every cygwin's package separately) I > didn't > >> notice any difference with cygwin and neither with tinyos as all the > >> packages were still installed, and when I tried to program, everything > >> works fine!! > >> > >> So, this e-mail it is only for those who get the error 57 when trying > to > >> program a sensor, so they only need to update the cygwin, I think the > >> reason is that some windows update is creating some problem with the > >> tinyos > >> website cygwin version, so yu only need to update it to the latest. > >> > >> I would also propose to the tinyos website administrator to change the > >> cygwin installer reference, or at least put a comment about this, > because > >> this problem could be causing some people that want to use TinyOS into > >> Windows to use other o.s. or have a mess trying to install vmware or > even > >> installing a Linux. > >> > >> Regards, > >> > >> Javier Barbarán > >> barba...@lcc.uma.es > >> ___ > >> 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 > ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Reg:MDA 100CB in Micaz mote
Hey! I have the same problem, only in my case I use a Iris mote!There seems to be a problem somewhere with the MoteView application picking up my raw sensor data and turning it into data that can be visualized. I have MoteView configured to acquire live data locally via MIB520 (COM4, Baud > rate: 57600) using XMDA100 as my application type. I can't see any data in visualization tab and in topology the notes are not linked togheter. Instead in server data, data looks like this: *Query: INSERT into xbw_da100_results *>*(result_time,nodeid,parent,voltage,temp,light,adc2,adc3,adc4,adc5,adc6) *>* values (now(),1,0,434,480,925,738,583,401,284,224) * and in Error Message: *System.NullReferenceException: Object reference not set to an instance of an object. at XBow.Plugin.Histogram.guiHistogram.FillNode(DataSet dSet, MoteInfo moteInfo, String sensor, Double[]& xData, Double[]& yData, Double[]& threshold, Double[]& num_crossing, Double[]& rate_crossing)* Could you send me the tutorial with the steps so I can be able to fix the problem? ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] radiochip status
Hello, I am using low power listening and the blip stack on CC2420 (TelosB) and I'm trying to measure how long the radiochip stays in OFF, Sleep, Idle, RX and TX mode. The target is to understand how much the density of the network influence the power consumption due to the radiochip usage. As first attempt I tried using a timer in order to measure the time between CC2420.startVRegDone() and CC2420.startOssilatorDone(). As from the datasheet I can see approximately 1msec. Unlikely, starting a timer from an async event is not a great idea. I get a warning (of course) and from the oscilloscope I see that the active period become few milliseconds larger than usual (I think this is the effect of the warning). Can you suggest me how to measure the time duration of each state where the radiochip might be? (not the transition time). Is there any component that I haven't seen? Many thanks Davide Pusceddu Embedded Systems Software Researcher NIMBUS CENTRE for Embedded Systems Research http://nimbus.cit.ie Department of Electronic Engineering - Cork Institute of Technology - Ireland ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] rfxlink for Telos
On Mon, Apr 18, 2011 at 23:18, Eric Decker wrote: > That is a good. thing. On the mm4 mote (2618 based) I have a SD card that > is > driven off of an SPI and I want it to run as fast as possible so I did > something > similar. All the peripherals are run off SMCLK. In general the SMCLK > should > be run as fast as possible. It is unclear why the original choice of SMCLK > = DCO/4 > was chosen. Maybe Vlado can comment, I'm pretty sure he was there. > I guess there are several reasons for the SMCLK=1MHz decision. First this config has long tradition in the general msp430 community and TI example code) and was considered a safe choice for the set of peripheral chips that we had to support at that time. For example, 500 kHz SPI bus clock is pushing the limits of the TDA5250 radio on eyesIFX. >> >> The SFD pin of the CC2420 is connected to pin on the MSP430 that can >> capture timer/counter B but not timer/counter A. Therefore, to be able >> to timestamp with the microsecond clock, timer B must be clocked at >> 1uis, and timer A should be programmed as the 32kHz clock. (Currently, >> timer A is running at 1uis, and timer B at 32kHz.) > >> >> One potential difference from the original clock setup is that in this >> case we are left with only 3 timer compare interfaces for the >> 32khz/1mis clocks, versus 7 in the original case. > > Actually, putting the 1mis clock on TimerA gives 3 CCRs and the 1uis clock > on TimerB gives 7 CCRs for the uis clock. > >> But since the 1mis >> clock is virtualized, this should not be a limitation. > > In practice the additonal compare capture registers aren't utilized. If > they do get > used it is a special app that needs to handle the situation itself. There are many platform-specific telosB applications out there that use more than three jiffy alarms, so I would be very careful with going down this road only because of the way the CC2420 SFD is wired or not wired to the MCU on a given platform. Vlado ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Installing Tinyos 2.1.0 on a Ubuntu 10.10 system
Hi Juan,
If you have the libs in the correct directory, I think it should be
OK. By the way, I found an interesting blog entry relating the same
problem with "[: 31: =: unexpected operator".
It is not a problem at line 31 but it's due to Ubuntu not using bash
but dash as default shell. The error can be removed by changing
#!/bin/sh by #!/bin/bash at the beginning of the script.Blog post is
here:
http://amrra.net/2010/11/09/solved-tinyos-error-tos-install-jni-31-unexpected-operator/
When having installed with these tricks, your environment should be
OK. If you still have problems reading messages over serial port, try
to verify/debug your serial port settings. Perhaps you simply do not
listen on the right port or not at the correct baudrate.
You can also find solutions to common issues with serial communication
in Tutorial 4:
http://docs.tinyos.net/index.php/Mote-PC_serial_communication_and_SerialForwarder#Troubleshooting_Serial_Comm_Issues
Regards
Romain
On Mon, Apr 18, 2011 at 10:03 PM, Juan G C wrote:
>
> Hi Romain,
>
> Thank you for your quicky answer.
>
> Ok, if those warnings doesn't crash the system to work, i don't mind
> annoying them.
>
> I've checked the folder /usr/lib/jvm/java-6-sun/jre/lib/amd64, and of
> course, I can see the following libs, among others:
>
> libgetenv.so
> libtoscomm.so
>
> So it seems to be ok.
>
> The content of the tos-install-jni.sh file is:
>
>
> #!/bin/sh
> prefix=/usr
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> tinyoslibdir=$libdir/tinyos
>
> jni=`tos-locate-jre --jni`
> if [ $? -ne 0 ]; then
> echo "Java not found, not installing JNI code"
> exit 1
> fi
>
> if [ cygpath -w / >/dev/null 2>/dev/null ] || [ `uname` = "Darwin" ]; then
> echo "Installing Java JNI code in $jni ... "
> for lib in $tinyoslibdir/*.so; do
> install $lib "$jni" || exit 1
> done
> else
> java=`tos-locate-jre --java`
> bits=32
> if [ $? -ne 0 ]; then
> echo "java command not found - assuming 32 bits"
> elif file -L $java/java | grep -q 64-bit; then
> bits=64
> fi
> echo "Installing $bits-bit Java JNI code in $jni ... "
> for lib in $tinyoslibdir/*-$bits.so; do
> realname=`basename $lib | sed -e s/-$bits\.so/.so/`
> install $lib "$jni/$realname" || exit 1
> done
> fi
> echo "done."
>
> I have marked in red the line 31 in the script. Is the previous to the last
> one. I think it doesn't say anything..
>
>
> Regards,
> Juan
>
>
> 2011/4/18 Romain Bornet
>>
>> Hi Juan,
>>
>> I'm developing in Cygwin environment but also had some trouble with
>> versions when I installed TinyOS. I can therefore already help you a
>> bit but not on what directly concerns Ubuntu 64 bits.
>>
>> Regarding tos-check-env, I think you can simply ignore the "errors".
>> These are simple warnings which check for old versions of
>> Java/graphviz which are hardcoded in the tos-check-env script. As far
>> as I know, Java 1.6 is supported and should not cause trouble as well
>> as older graphviz/dot versions. I could generate nesdoc with newer
>> graphviz at least.
>>
>> If you want to get rid of tos-check-env warnings, you can open the
>> tos-check-env.sh script and change following lines:
>>
>> in sub chk_java() function, replace
>> if ($_ =~ /version \"1\.[45]/) {
>> by
>> if ($_ =~ /version \"1\.[456]/) {
>>
>> This will tell the script that 1.6 is also OK
>>
>> in sub chk_graphviz function you can simply drop the test on the
>> version number. If you have dot installed on Ubuntu, it will for sure
>> be higher than 1.10 ! for this, replace
>>
>> $versionok = 1 if /1\.10/;
>> by
>> $versionok = 1
>>
>> With these 2 changes, tos_check_env should be happy.
>>
>> Regarding the tos-install-jni problem, could you post your
>> tos-install-jni.sh script ? It would help people on the list to
>> understand what produced the error at line 31.
>>
>> By the way did you check in /usr/lib/jvm/java-6-sun/jre/lib/amd64 if
>> TinyOS libraries were installed ? Perhaps the script terminates with
>> an error but nevertheless copied the library files. You should have
>> libgetenv.so and libtoscomm.so files there if everything went smooth.
>>
>> Regards,
>> Romain
>>
>> On Mon, Apr 18, 2011 at 12:54 PM, Juan Garrido Castellano
>> wrote:
>> > Hello to everyone.
>> >
>> > It's the first time i write to this forum.
>> >
>> > I was working with Tinyos 2.1.0 on a Ubuntu 32 bit system installed in
>> > vmware, and it worked ok.
>> >
>> > Now i'm trying to make it work in a Ubuntu 64 bit, 10.10. I can compile
>> > and
>> > install programs into MICAZ motes. FINE.
>> >
>> > But i can't get Serial readings. I get the following messages from
>> > Tinyos:
>> >
>> >
>> > TOS-CHECK-ENV output:
>> >
>> > tos-check-env completed with errors:
>> >
>> > --> WARNING: The JAVA version found first by tos-check-env may not be
>> > version 1.4 or version 1.5one of which is required by TOS. Please ensure
>> > that the located Java version is 1.4 or 1.5
>> > --> WARNING: The graphviz (dot) version
[Tinyos-help] How to convert RAW data to degree Celsius for Telos B
Hello, I would like to know how to convert RAW data to degree Celsius for Telos B mote which uses Sensirion Sht11 as temperature and humidity sensor. I've checked the Sht11 data sheet, and it seems that the conversion formula depends on the voltage value of Sht11 (Page 9, top right). So I'd like to know is it possible to get the voltage value of Sht11 sensor on my Telos B mote ? Or it's just a constant ? Best regards. p.s. Sensirion Sht11 data sheet : http://www.sensirion.com/en/pdf/product_information/Datasheet-humidity-sensor-SHT1x.pdf ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
