from:"Erdélyi Ádám \[Edöm\]"

Re: [Tinyos-help] compile ToSSIM

2014-11-05 Thread Erdélyi Ádám [Edöm]


Hi there,

recently I'm not using TinyOS at all, therefore I discontinued updating 
the image file.
Before I answer the other questions, could you please briefly describe 
your programming experience? No offense, but based on your questions I 
have a feeling that it strongly converges to none.


Adam

On 2014.11.05. 17:48, Fahimeh Ashrafy wrote:

Thanks a lot.
The version of that image is about 5th March, 2013. could you please 
give me the link that I can download new version of the image?
I am new in TinyOs. could you please tell me what I should exactly 
do?(Check both lines that are mentioned and correct the type (or 
simply remove the secondary declaration)
As I searched someone else had this problem before, and he just 
mentioned "I have solved the problem, apprently the type def flag that 
I was using was named as "TOSSIM" in my make file, after changing it, 
it now works. I guess it was just confusing the compiler." but 
unfortunately I didnt get a clue.


Best Regards


On Wed, Nov 5, 2014 at 7:59 AM, "Erdélyi Ádám [Edöm]" 
mailto:erdelyiadam.e...@gmail.com>> wrote:


Hi,

this is an image that I uploaded a long time ago. It is now quite
outdated. Unfortunately my account on the wiki page stopped
working, so I couldn't update it and no admin answered my mails
regarding the wiki. I never tested TOSSIM with this image,
therefore it's not guaranteed it'll work at all. I recommend to
make a fresh install with the most up-to-date TinyOS version.
Based on the error message PacketAcknowledgements.wasAcked is
declared multiple times with different types. Check both lines
that are mentioned and correct the type (or simply remove the
secondary declaration).

Cheers,
Adam


On 05/11/14 16:09, Fahimeh Ashrafy wrote:

Hello guys
i really need help
Thanks

On Tue, Nov 4, 2014 at 3:55 AM, Fahimeh Ashrafy
mailto:fahimehashr...@gmail.com>> wrote:

there is no one to help me.
I really need the help to deal with that problem.

On Mon, Nov 3, 2014 at 12:39 AM, Fahimeh Ashrafy
mailto:fahimehashr...@gmail.com>>
wrote:

Hello guys

I've just downloaded the XubunTOS image provided by the TinyOs team 
(

http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_%28with_TinyOS_from_tp-freeforall/prod_repository%29_in_VirtualBox)
and while trying to compile the simple BLINK app with TOSSIM 
support I get
this:

mkdir -p simbuild/micaz
   placing object files in simbuild/micaz
   writing XML schema to app.xml
   compiling BlinkAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 
-fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz 
-fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=10 
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"user\" 
-DIDENT_HOSTNAME=\"XubunTOS\" -DIDENT_USERHASH=0x184e7486L -DIDENT_TIMESTAMP=0x54573467L 
-DIDENT_UIDHASH=0xed24784cL -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
In file included from 
/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/ActiveMessageC.nc:57,
  from 
/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/MainC.nc:72,
  from BlinkAppC.nc:56:
In component `TossimPacketModelC':

/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/TossimPacketModelC.nc:140: 
conflicting types for `PacketAcknowledgements.wasAcked'

/home/user/top/t2_cur/tinyos-2.x/tos/interfaces/PacketAcknowledgements.nc:85: 
previous declaration of `PacketAcknowledgements.wasAcked'
make: *** [sim-exe] Error 1

Could anyone help me?

Thanks a lot





___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu  
<mailto: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] compile ToSSIM

2014-11-05 Thread Erdélyi Ádám [Edöm]


Hi,

this is an image that I uploaded a long time ago. It is now quite 
outdated. Unfortunately my account on the wiki page stopped working, so 
I couldn't update it and no admin answered my mails regarding the wiki. 
I never tested TOSSIM with this image, therefore it's not guaranteed 
it'll work at all. I recommend to make a fresh install with the most 
up-to-date TinyOS version.
Based on the error message PacketAcknowledgements.wasAcked is declared 
multiple times with different types. Check both lines that are mentioned 
and correct the type (or simply remove the secondary declaration).


Cheers,
Adam

On 05/11/14 16:09, Fahimeh Ashrafy wrote:

Hello guys
i really need help
Thanks

On Tue, Nov 4, 2014 at 3:55 AM, Fahimeh Ashrafy 
mailto:fahimehashr...@gmail.com>> wrote:


there is no one to help me.
I really need the help to deal with that problem.

On Mon, Nov 3, 2014 at 12:39 AM, Fahimeh Ashrafy
mailto:fahimehashr...@gmail.com>> wrote:

Hello guys

I've just downloaded the XubunTOS image provided by the TinyOs team (

http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_%28with_TinyOS_from_tp-freeforall/prod_repository%29_in_VirtualBox)
and while trying to compile the simple BLINK app with TOSSIM support I 
get
this:

mkdir -p simbuild/micaz
   placing object files in simbuild/micaz
   writing XML schema to app.xml
   compiling BlinkAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate 
-fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz 
-fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=10 
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"user\" 
-DIDENT_HOSTNAME=\"XubunTOS\" -DIDENT_USERHASH=0x184e7486L -DIDENT_TIMESTAMP=0x54573467L 
-DIDENT_UIDHASH=0xed24784cL -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
In file included from 
/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/ActiveMessageC.nc:57,
  from 
/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/MainC.nc:72,
  from BlinkAppC.nc:56:
In component `TossimPacketModelC':

/home/user/top/t2_cur/tinyos-2.x/tos/lib/tossim/TossimPacketModelC.nc:140: 
conflicting types for `PacketAcknowledgements.wasAcked'

/home/user/top/t2_cur/tinyos-2.x/tos/interfaces/PacketAcknowledgements.nc:85: 
previous declaration of `PacketAcknowledgements.wasAcked'
make: *** [sim-exe] Error 1

Could anyone help me?

Thanks a lot





___
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] Im unable to install msp430-46 compiler

2014-04-14 Thread Erdélyi Ádám [Edöm]


Hola Jorge,

this is an English speaking mailing list to my best knowledge. Please 
act accordingly.


Cheers,
Adam

On 2014.04.15. 1:19, Jorge Castro wrote:


Hola.

No puedo instalar el compilador msp430-46. Cada vez que trato de 
instalar desde los repositorios me aparece un error . Podrían darme 
alguna solución?


Jorge.
--
*_ ..
Att. Jorge Israel.*


___
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] Sensor nodes sniffer

2014-04-14 Thread Erdélyi Ádám [Edöm]

Hi Wasif,

you don't necessarily need an extra HW for that. I converted once an
ordinary TelosB mote into a sniffer by using KillerBee
.
More info on this:
http://quahogcon.org/QC2010Archive/slides/wright-killerbee.pdf

If you insist to buy separate HW for sniffing I recommend to use a
CC2531  USB Dongle from Texas
Instruments. It works perfectly with the SmartRF Packet Sniffer
.

The collected (sniffed) data of both the above mentioned methods can be
used in WireShark  ;)

Adam

On 13/04/14 19:49, wasif masood wrote:
> Dear All,
>
> I am interested in buying an extra hardware for sniffing the 802.15.4
> packets. The sole purpose would be for debugging the deployed
> applications by sniffing the channels. I would deeply appreciate your
> expert opinions!
>
> BR,
> Wasif Masood
>
>
> ___
> 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] Please code and protocol LEACH PEGASISE

2013-11-15 Thread Erdélyi Ádám [Edöm]


I guess we have a spammer here. Admins please act accordingly.

On 2013.11.15. 21:54, jerbi jerbi wrote:

Hello
Please code and protocol LEACH PEGASISE


___
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] Do not use Latest TinyOS vistual box image

2013-10-24 Thread Erdélyi Ádám [Edöm]

I wanted to update it several times, but my account for the wiki site is
not working anymore and I got no replies on my e-mail to the admins. :(

I can update the virtual image file itself since it on my own webpage,
but then it will be inconsistent with the content on the wiki page...

Adam

On 10/24/13 16:46, sandyireland wrote:
> Following Image in help site should be updated. 
>
> http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_XubunTOS_(with_TinyOS_from_tp-freeforall/prod_repository)_in_VirtualBox.
>  its deficient in following packages and still after that also not list not
> working
>  following packages missing 
> after comparing packages installed in working tinyos image and this image. 
> tinyos-2.1.0 2.1.0-20090326   
>  
> The TinyOS operating system.
>  ii  tinyos-base  2.1-20080806
>   
> Dummy package required by all tinyos realate
>  ii  tinyos-required-all  2.1-20090326
>   
> Dummy package to pull in all packages requir
>  ii  tinyos-required-avr  2.1-20090326
>   
> Dummy package to pull in all required packag
>  ii  tinyos-required-msp430 
> -
>  For motelist not working download moetelist source code. 
> Check the mount structure for 
> As from previous version 8 of last image to Ubuntu 12.4 the directory
> structure is changed little bit
>  hence last version directory required should be copied to new directories 
> check $mount all mount structure 
> then is duplicate unmount using $umount 
> $sudo mount --bind /dev/bus /proc/bus 
> dev structure should be copied to /proc 
>
> then download Google(motelist code perl) 
> open editor copy paste code in editor 
> $nano or gedit (program name ).pl 
>
> Execute the perl code $ perl 
> $ perl (program name).pl 
> 
>  Even then currently motelist is diagnosed but not working have to try more
> options...
>  but this is useful it removed few errors regarding mount structure and more
> control over code over just command
>
>
>
> --
> View this message in context: 
> http://tinyos-help.10906.n7.nabble.com/Do-not-use-Latest-TinyOS-vistual-box-image-tp23715.html
> Sent from the TinyOS - Help mailing list archive at Nabble.com.
> ___
> 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] help

2013-05-07 Thread Erdélyi Ádám [Edöm]

If all your motes are within the range of your base-station radio, you 
can simply broadcast these data from each mote on demand.


Adam

On 07/05/13 13:59, touihri ala wrote:

Hi Ms
i want to ask for the code in nesc who will allow me to discover the 
list of mote present in my wireless sensors networks from the 
terminal, i mean like search  bluetooth.

i work with tinyos , zolertia and code with nesc
in addition want to add code to base station for print a simple 
message contain the id , name and parameter of sensing for each mote 
installed in my wsn

thanks alot in advance


___
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] target-dependant additions, "overwriting" of default implementations

2013-04-09 Thread Erdélyi Ádám [Edöm]

Hi Christian,

I would put it into the folder of that particular platform and then 
rewrite the .platform file accordingly. As far as I know the path list 
in the .platform file is a priority list, so if you put the folder of 
your own version of McuSleepC before the general one it will override it.

For doing it in a more general way I would just simply give a different 
name for the new version and put it next to the old version. Then you 
can decide which one to use when creating a platform (although that 
"decision" should be at a low level /close to HPL/ in order to avoid 
rewriting/overriding the default McuSleepC.

These are just my ideas, I'm sure you'll get more accurate answers from 
more experienced members of the mailing-list ;)

Regards,
Adam

On 09/04/13 16:54, Christian Renner wrote:
> Dear all,
>
> I am wondering how to integrate general additions (modules, interfaces,
> etc.) to the TinyOS tool chain, so that they are
>
> - available for any application and
> - overwrite standard TinyOS implementations.
>
> I'll (try to) give an example of what I want to achieve:
>
> Say I implemented a modified version of McuSleepC.nc for two different
> platforms (for some arbitrary reason). Now I am having several
> applications that want to make use of the modifications. Apparantly, I
> do not want to overwrite the corresponding original implementations, but
> want to store my implementations locally as, e.g.,
>
> SOME_PLACE/chips/atm1281/McuSleepC.nc, and
> SOME_PLACE/chips/atm128rfa1/McuSleepC.nc
>
> The question now is, how do I make TinyOS aware of these new files? Of
> course, I could just add the paths to the Makefile with a dumb addition
> to CFLAGS. However, this would require to select the right path
> depending on the target, and I would have to do that in every single
> makefile.
>
>
> Thanks in advance for pointers and help,
> Christian
> ___
> 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] Texas Instruments 900MHz Mote

2013-04-09 Thread Erdélyi Ádám [Edöm]


Hi there,

the processor itself has some working code in the following repository: 
https://github.com/tp-freeforall/prod (I'm not sure if it's the same 
you've used.)
As for the CC1180 radio I don't know about any implementation. I've 
tried to interface MSP430F5438a with CC2520 (CC2520 has an 
implementation in both the tp-freeforall/prod and the official TinyOS 
repo on google code), but unfortunately there were too many problems and 
it still doesn't work. (The uC works though quite alright alone, but I 
guess you want a wireless node.)


What is included in your .platform file? Maybe some files are missing 
that contain these constants.


Wishes,
Adam

On 09/04/13 09:09, Tim Godfrey wrote:

Hello,

My question is, is the processor MSP430F5438A supported by tinyos? How 
does one take compile apps for that target?


I am attempting to add a new platform to my tinyos installation. The 
mote I want to add support for is a Texas Instruments CC1180DK_DB 
mote. It has an MSP430F5438A microcontroller and a CC1180 radio 
controller.


I have been following the 'Platforms' guide on the wiki 
(http://docs.tinyos.net/tinywiki/index.php/Platforms) to add a new 
platform. At the moment when I compile I get a whole bunch of 
"'Variable' undeclared " errors for the variables


- TACCTL0
- TACCTL1
- TACCTL2
- TACTL
- ME1
- UTXE0
- ...
etc.

As far as I can work out, it is because the header file, 
msp430f5438a.h, does not include definitions for those constants 
(defines?).


I did read in the devel mailing list, that in 2011 Eric Decker was 
working on support for 2nd and 3rd generation msp430 devices, and had 
created tinynode instances on a bunch of those devices, including the 
one I am trying to work with. However, the git repository that he was 
developing is not serving the code (anymore? at least not to me), and 
the current trunk version of tinyos from google code doesn't improve 
my compilation output.


Thanks ahead of time for your help!
Tim



___
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] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

2013-03-17 Thread Erdélyi Ádám [Edöm]


Hi Eric,

I forgot to mention 2 important changes that I had to do when I started 
with this HW:

*1.*
A little patch is needed in tos/system/SimpleFcfsArbiterC.nc and 
tos/system/FcfsArbiterC.nc 
(http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2012-February/053892.html)
Wrong order while initializing hardware resources (SPI is initialized 
later than Radio; SPI should be ready before initializing Radio)


tos/system/SimpleFcfsArbiterC.nc:

uses interface ResourceConfigure[uint8_t id];
  }
  implementation {
-  components MainC;
+  components RealMainP;
components new FcfsResourceQueueC(uniqueCount(resourceName)) as Queue;
components new SimpleArbiterP() as Arbiter;

-  MainC.SoftwareInit -> Queue;
+  RealMainP.PlatformInit -> Queue;

Resource = Arbiter;
ResourceRequested = Arbiter;

tos/system/FcfsArbiterC.nc:

uses interface ResourceConfigure[uint8_t id];
  }
  implementation {
-  components MainC;
+  components RealMainP;
components new FcfsResourceQueueC(uniqueCount(resourceName)) as Queue;
components new ArbiterP(uniqueCount(resourceName)) as Arbiter;

-  MainC.SoftwareInit -> Queue;
+  RealMainP.PlatformInit -> Queue;

Resource = Arbiter;
ResourceRequested = Arbiter;

*2.*
Comment out "inline void UCTR(...)" at 
tos/chips/CC2520/CC2520DriverLayerP.nc:433. (Strange error message: 
syntax error before '0x10') <-- as for this, I still don't know what the 
problem could be :(


If you find something interesting regarding my problem, please let me 
know. Thanks.


Best wishes,
Adam

On 2013.02.28. 0:51, Eric Decker wrote:

not yet.   Still building.  hope to have a compile working today.

I did order a 2520 EVM module as well as a 2520/2591 module.   So now 
have the same environment as you.



On Wed, Feb 27, 2013 at 1:54 AM, "Erdélyi Ádám [Edöm]" 
mailto:erdelyiadam.e...@gmail.com>> wrote:


Hi,

have you by any chance found something regarding my problem?

    Thanks,
Adam


On 19/02/13 20:07, "Erdélyi Ádám [Edöm]" wrote:

Hi Eric,

On 2013.02.18. 1:47, Eric Decker wrote:


Not enough information.

Can you push your tree to your account on github?   If you don't
have a github account please get one so you can push your code
up to it and then I can look at it.


I didn't have a github account so I created one quickly. I hope I
did everything right. Here is the address of my current tree:
https://github.com/erdelyiadam/prod/tree/AE

I created a new platform under the name of "nthfs".



Then I can see how you have things wired.

Since you get one event it probably isn't a wiring problem but
some other kind of failure.


Sorry, my description was ambiguous. I get no event at all, I can
see only the first SFD signal and only on the oscilloscope. So on
SW side I got nothing abour SFD.



What does your h/w look like?How is the 2520 wired to the 5438a?


The HW I'm using is an MSP-EXP430F5438
<http://www.ti.com/tool/msp-exp430f5438> board from TI with a
CC2520EMK <http://www.ti.com/tool/cc2520emk> RF modul.
As for the wiring: MSP-EXP5438 Users's Guide (Schematics).pdf

<https://www.dropbox.com/s/gdv1mu35kx1hzgl/MSP-EXP5438%20User%27s%20Guide%20%28Schematics%29.pdf>
(Page 30) and CC2520EM_2_1_schematics.pdf
<https://www.dropbox.com/s/wv0tnuq0w5eubpk/CC2520EM_2_1_schematics.pdf>



On Sun, Feb 17, 2013 at 4:00 AM, "Erdélyi Ádám [Edöm]"
mailto:erdelyiadam.e...@gmail.com>>
wrote:

Hello Everyone,

I'm (still) trying to interface the MSP430F5438a uC with the
CC2520
radio chip. (I'm using the tp-freeforall/prod repo)
Now I'm facing the following problem:

When sending out (TX) messages the SfdCapture.captured event
never
fires, except after boot-up for the first time.

- I captured some of these "first packets" with a CC2531 USB
dongle and
TI Packet Sniffer and the result looks like this every time:
41 88 11 22 00  FF XX XX XX XX
XX XX XX XX XX (where XXs are different
every time, but the length is the same, 15)

- I also measured the signal with an oscilloscope on GPIO4
of CC2520
(which is set to SFD by default (based on CC2520 Datasheet /
SWRS068)
and connected to P8.1 on MSP430F5438a) and I can see this
first SFD
signal after boot-up, but the high-level of the signal is
only around
0.3V. (I don' really understand why so low.)

- I tried to remap the timers, because by default the radio
uses Micro
timer (my HplCC2520.nc is based on sam3s_ek) which is mapped to
Timer1_A, but the P8.1 (the SFD signal from CC2520) is mapped to
Timer0_A which is a T32

Re: [Tinyos-help] Printf app- not displaying any message

2013-03-06 Thread Erdélyi Ádám [Edöm]

Are you sure that your mote is connected to /dev/ttyUSB1? (You wrote 
/dev/ttyUSB0 when programming.)
You could also try to change the speed of the serial connection. (i.e. 
change :iris to actual values like :115200, or :57600, ...) This usually 
helps when I get "resynchronising".

Adam

On 06/03/13 12:44, gyanesh meena wrote:
> I am trying to run printf app  from  /opt/tinyos-2.1.1/apps/tutorials/Printf
>
> I have compiled and installed it in my iris mote by using "  make iris
> install mib520,/dev/ttyUSB0 "
>
>   and after this  I tried to display message by using  " java
> net.tinyos.tools.PrintfClient -comm serial@/dev/ttyUSB1:iris " but
> still I am not getting any messages.
>
>   It shows
>
> gyanesh@ubuntu:/opt/tinyos-2.1.1/apps/tutorials/Printf$ java
> net.tinyos.tools.PrintfClient -comm serial@/dev/ttyUSB1:iris
> Thread[Thread-1,5,main]serial@/dev/ttyUSB1:iris: resynchronising
>
>
> I am using mib520 and iris mote. I didnt find anything useful  in
> Tinyos-Help library . please help

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

Re: [Tinyos-help] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb

2013-03-05 Thread Erdélyi Ádám [Edöm]


That's exactly what I've done. ;)
I will update the wiki when I will get my account. My registration is 
pending right now.


You're welcome.

Adam

On 2013.03.05. 20:05, Eric Decker wrote:


sweet. can you also update the wiki to reflect? 


  i'm not sure where the XubunTOS stuff is referenced.   But once
you are at docs.tinyos.net <http://docs.tinyos.net> just do a
search for XubunTOS and you should see all the pages.



Also what were the steps you took?Did you simple create a new 
virtual machine in Vbox,   Do the Linux install, do the TinyOS tools 
install, install source, and then called it a day.   Then using VBox 
export this virtual machine?


thanks for doing this.

eric

On Tue, Mar 5, 2013 at 4:12 AM, "Erdélyi Ádám [Edöm]" 
mailto:erdelyiadam.e...@gmail.com>> wrote:


Hi Everyone,

I created a fresh XubunTOS virtual machine. It's Xubuntu 12.04.2
and the latest (on 05. March, 2013) TinyOS is installed from the
tp-freeforall/prod <https://github.com/tp-freeforall/prod>
repository as it's written in 00b_Development_Environment

<https://github.com/tp-freeforall/prod/blob/tp-master/00b_Development_Environment>.
I created it in VirtualBox <https://www.virtualbox.org/> and
exported to OVF 0.9 format, so it should work with VMware and
other virtualization tools as well.

You can download it from here:
http://wwwu.uni-klu.ac.at/aerdelyi/tinyos/xubuntos/XubunTOS.ova

User data for Xubuntu:

USERNAME: *user*
PASSWORD: *password*

Installation procedure:
1. Download and install VirtualBox
<https://www.virtualbox.org/wiki/Downloads>.
2. Download the XubunTOS
<http://wwwu.uni-klu.ac.at/aerdelyi/tinyos/xubuntos/XubunTOS.ova>
virtual machine.
3. Import the virtual machine to VirtualBox. (File->Import
appliance->Open appliance->Next->Import)
4. Start the virtual machine.
(5.) Make a test compilation for TelosB.
In terminal:
$cd ~/top/t2_cur/tinyos-2.x/apps/tutorials/BlinkToRadio/
$make telosb

Have fun!

Best wishes,
Adam Erdelyi

On 21/02/13 11:08, Eric Decker wrote:


Actually, no.  The old XubunTOS images are hideously outdated.  
TinyOS 2.0 or TinyOS 2.1.  Also a very old version of Xbuntos as

well.

The original poster asked explicitly for installing TinyOS (I
assume the current 2.1.2 release) on 12.04.

The Xbuntos VM image does neither of these things. And at best is
a sideways step.

Currently, I have detailed instructions for getting started at

https://github.com/tp-freeforall/prod/blob/tp-master/00b_Development_Environment

But instead of pulling from gh:tp-freeforall/prod one should use
the tinyos/tinyos-release repository.

The above procedure have been done on a 12.04 Ubuntu installation
(I'm currently running it on 11.10).   And should also work on
Debian.


Eric


On Thu, Feb 21, 2013 at 1:10 AM, meriam mailto:merioum...@yahoo.com>> wrote:

salam, hello,

i think this link will help you

http://docs.tinyos.net/tinywiki/index.php/Running_a_XubunTOS_Virtual_Machine_Image
_in_VMware_Player

good luck and best regards

meriam

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
<mailto: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  
<mailto: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
<mailto: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] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb

2013-03-05 Thread Erdélyi Ádám [Edöm]


Hi Everyone,

I created a fresh XubunTOS virtual machine. It's Xubuntu 12.04.2 and the 
latest (on 05. March, 2013) TinyOS is installed from the 
tp-freeforall/prod  repository as 
it's written in 00b_Development_Environment 
. 
I created it in VirtualBox  and exported to 
OVF 0.9 format, so it should work with VMware and other virtualization 
tools as well.


You can download it from here: 
http://wwwu.uni-klu.ac.at/aerdelyi/tinyos/xubuntos/XubunTOS.ova


User data for Xubuntu:

   USERNAME: *user*
   PASSWORD: *password*

Installation procedure:
1. Download and install VirtualBox 
.
2. Download the XubunTOS 
 
virtual machine.
3. Import the virtual machine to VirtualBox. (File->Import 
appliance->Open appliance->Next->Import)

4. Start the virtual machine.
(5.) Make a test compilation for TelosB.
In terminal:
$cd ~/top/t2_cur/tinyos-2.x/apps/tutorials/BlinkToRadio/
$make telosb

Have fun!

Best wishes,
Adam Erdelyi

On 21/02/13 11:08, Eric Decker wrote:


Actually, no.  The old XubunTOS images are hideously outdated. TinyOS 
2.0 or TinyOS 2.1.  Also a very old version of Xbuntos as well.


The original poster asked explicitly for installing TinyOS (I assume 
the current 2.1.2 release) on 12.04.


The Xbuntos VM image does neither of these things.   And at best is a 
sideways step.


Currently, I have detailed instructions for getting started at 
https://github.com/tp-freeforall/prod/blob/tp-master/00b_Development_Environment


But instead of pulling from gh:tp-freeforall/prod one should use the 
tinyos/tinyos-release repository.


The above procedure have been done on a 12.04 Ubuntu installation (I'm 
currently running it on 11.10).   And should also work on Debian.



Eric


On Thu, Feb 21, 2013 at 1:10 AM, meriam > wrote:


salam, hello,

i think this link will help you

http://docs.tinyos.net/tinywiki/index.php/Running_a_XubunTOS_Virtual_Machine_Image
_in_VMware_Player

good luck and best regards

meriam

___
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 mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

2013-02-19 Thread Erdélyi Ádám [Edöm]


Hi Johny,

On 2013.02.17. 23:40, Johny Mattsson wrote:
On 17 February 2013 23:00, "Erdélyi Ádám [Edöm]" 
mailto:erdelyiadam.e...@gmail.com>> wrote:


 the high-level of the signal is only around
0.3V. (I don' really understand why so low.)


Is the pin on the MSP perchance configured as output/lo so what you're 
seeing is a tug-o-war between the internal pull-down and the external 
chip? It does look suspiciously like a 10k vs 100k fight...




Yes, you're probably right. I haven't checked this, BUT I also measured 
the SFD signal of a TelosB mote and it has exactly the same voltage level.



Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.
/where ideas are engineered
/ 


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

Re: [Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

2013-02-19 Thread Erdélyi Ádám [Edöm]


Hi Eric,

On 2013.02.18. 1:47, Eric Decker wrote:


Not enough information.

Can you push your tree to your account on github?   If you don't have 
a github account please get one so you can push your code up to it and 
then I can look at it.


I didn't have a github account so I created one quickly. I hope I did 
everything right. Here is the address of my current tree: 
https://github.com/erdelyiadam/prod/tree/AE


I created a new platform under the name of "nthfs".



Then I can see how you have things wired.

Since you get one event it probably isn't a wiring problem but some 
other kind of failure.


Sorry, my description was ambiguous. I get no event at all, I can see 
only the first SFD signal and only on the oscilloscope. So on SW side I 
got nothing abour SFD.




What does your h/w look like?How is the 2520 wired to the 5438a?


The HW I'm using is an MSP-EXP430F5438 
<http://www.ti.com/tool/msp-exp430f5438> board from TI with a CC2520EMK 
<http://www.ti.com/tool/cc2520emk> RF modul.
As for the wiring: MSP-EXP5438 Users's Guide (Schematics).pdf 
<https://www.dropbox.com/s/gdv1mu35kx1hzgl/MSP-EXP5438%20User%27s%20Guide%20%28Schematics%29.pdf> 
(Page 30) and CC2520EM_2_1_schematics.pdf 
<https://www.dropbox.com/s/wv0tnuq0w5eubpk/CC2520EM_2_1_schematics.pdf>




On Sun, Feb 17, 2013 at 4:00 AM, "Erdélyi Ádám [Edöm]" 
mailto:erdelyiadam.e...@gmail.com>> wrote:


Hello Everyone,

I'm (still) trying to interface the MSP430F5438a uC with the CC2520
radio chip. (I'm using the tp-freeforall/prod repo)
Now I'm facing the following problem:

When sending out (TX) messages the SfdCapture.captured event never
fires, except after boot-up for the first time.

- I captured some of these "first packets" with a CC2531 USB
dongle and
TI Packet Sniffer and the result looks like this every time:
41 88 11 22 00  FF XX XX XX XX XX XX
XX XX XX (where XXs are different
every time, but the length is the same, 15)

- I also measured the signal with an oscilloscope on GPIO4 of CC2520
(which is set to SFD by default (based on CC2520 Datasheet / SWRS068)
and connected to P8.1 on MSP430F5438a) and I can see this first SFD
signal after boot-up, but the high-level of the signal is only around
0.3V. (I don' really understand why so low.)

- I tried to remap the timers, because by default the radio uses Micro
timer (my HplCC2520.nc is based on sam3s_ek) which is mapped to
Timer1_A, but the P8.1 (the SFD signal from CC2520) is mapped to
Timer0_A which is a T32khz timer, so I replaced Timer0_A and Timer1_A
with each other, but it didn't get any better.

At the moment I'm out of ideas, if anyone could give me a hint
what the
problem could be, it'd be great.

(the above mentioned event can be found in
/tos/chips/cc2520/CC2520DriverLayerP.nc around line 1600)

Thank you in advance.

Best wishes,
Adam Erdelyi
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
<mailto:Tinyos-help@millennium.berkeley.edu>
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




--
Eric B. Decker
Senior (over 50 :-) Researcher



It would be great if you could help. I feel totally lost.

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

Re: [Tinyos-help] Problems programming TelosB

2013-02-18 Thread Erdélyi Ádám [Edöm]


It's probably BSL version mismatch:
"MSP430 Bootstrap Loader Version: 1.39-telos-8" vs. "Current bootstrap 
loader version: 1.61 (Device ID: f16c)"


I'm not good with BSL, but there is an option to use custom .txt files 
(provided by TI) with tos-bsl. You should use the proper one that 
matches your HW.


Adam

On 02/18/2013 04:22 PM, quentin strydom wrote:

msp430-gcc (GCC) 3.2.3


*From:* Saeid Yazdani 
*To:* quentin strydom 
*Cc:* "tinyos-help@millennium.berkeley.edu" 


*Sent:* Monday, 18 February 2013, 15:15
*Subject:* Re: [Tinyos-help] Problems programming TelosB

Whichversions of TinyOS and msp430-gcc are you running?

Regards,
Saeid.
www.eetutorials.com 

On 18-2-2013 4:13 PM, quentin strydom wrote:
I tried both and still the same, 3 different TelosB motes and 4 
different usb ports. Added Debug output follows:


MSP430 Bootstrap Loader Version: 1.39-telos-8
Debug level set to 1
Python version: 2.7 (r27:82500, Sep 16 2010, 18:03:06)
[GCC 4.5.1 20100907 (Red Hat 4.5.1-3)]
using serial port '/dev/ttyUSB0'
Preparing device ...
Mass Erase...
Transmit default password ...
Actions ...
Invoking BSL...
Transmit default password ...
Autodetect successful: f16c -> F1x family
Current bootstrap loader version: 1.61 (Device ID: f16c)
Current bootstrap loader version: 0x0161
Changing baudrate to 38400 ...
TODO list:
   actionProgram
Program ...
  Program starting at 0x4000, 224 bytes ...
  Program starting at 0x40e0, 224 bytes ...
  Program starting at 0x41c0, 224 bytes ...
  Program starting at 0x42a0, 224 bytes ...
  Program starting at 0x4380, 224 bytes ...
  Program starting at 0x4460, 224 bytes ...
  Program starting at 0x4540, 224 bytes ...
  Program starting at 0x4620, 224 bytes ...
  Program starting at 0x4700, 224 bytes ...
  Program starting at 0x47e0, 224 bytes ...
  Program starting at 0x48c0, 224 bytes ...
  Program starting at 0x49a0, 184 bytes ...
  Program starting at 0xffe0, 32 bytes ...
Traceback (most recent call last):
  File "/usr/bin/tos-bsl", line 1619, in 
main()
  File "/usr/bin/tos-bsl", line 1583, in main
for f in todo: f() #work through todo list
  File "/usr/bin/tos-bsl", line 1108, in actionProgram
self.programData(self.data, self.ACTION_PROGRAM)
  File "/usr/bin/tos-bsl", line 906, in programData
self.programBlk(currentAddr, seg.data[pstart:pstart+length], action)
  File "/usr/bin/tos-bsl", line 887, in programBlk
self.bslTxRx(self.BSL_TXBLK, addr, len(blkout), blkout)
  File "/usr/bin/tos-bsl", line 652, in bslTxRx
rxFrame = self.comTxRx(cmd, dataOut, len(dataOut))  #Send frame
  File "/usr/bin/tos-bsl", line 438, in comTxRx
raise BSLException("Unknown header 0x%02x\nAre you downloading to 
RAM into an old device that requires the patch? Try option -U" % 
rxHeader)

__main__.BSLException: Unknown header 0xf0
Are you downloading to RAM into an old device that requires the 
patch? Try option -U





*From:* Saeid Yazdani  
*To:* tinyos-help@millennium.berkeley.edu 


*Sent:* Monday, 18 February 2013, 14:54
*Subject:* Re: [Tinyos-help] Problems programming TelosB

Hmmm, looks like a hardware problem, have you tried with another 
telosb mote and/or another USB portor system?


Regards,
Saeid.
www.eetutorials.com 

On 18-2-2013 3:19 PM, quentin strydom wrote:

Hi,

I'm having problems programming the TelosB. Can anyone help?

Thanks

Output as Follow:


$ make telosb install,bsl

mkdir -p build/telosb
compiling BlinkAppC to a telosb binary
ncc -o build/telosb/main.exe  -Os -O -mdisable-hwmul 
-fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb 
-fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"qstrydom\" 
-DIDENT_HOSTNAME=\"Quentin-PC\" -DIDENT_USERHASH=0x4acc32a1L 
-DIDENT_TIMESTAMP=0x5122382fL -DIDENT_UIDHASH=0x864dcb78L 
BlinkAppC.nc -lm

compiled BlinkAppC to build/telosb/main.exe
2648 bytes in ROM
  54 bytes in RAM
msp430-objcopy --output-target=ihex build/telosb/main.exe 
build/telosb/main.ihex

writing TOS image
tos-set-symbols --objcopy msp430-objcopy --objdump msp430-objdump 
--target ihex build/telosb/main.ihex build/telosb/main.ihex.out-bsl 
TOS_NODE_ID=bsl ActiveMessageAddressC__addr=bsl
Could not find symbol ActiveMessageAddressC__addr in 
build/telosb/main.exe, ignoring symbol.
Could not find symbol TOS_NODE_ID in build/telosb/main.exe, ignoring 
symbol.

found mote on /dev/ttyUSB0 (using bsl,auto)
installing telosb binary using bsl
tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p 
build/telosb/main.ihex.out-bsl

MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass Erase...

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



_

[Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

2013-02-17 Thread Erdélyi Ádám [Edöm]

Hello Everyone,

I'm (still) trying to interface the MSP430F5438a uC with the CC2520 
radio chip. (I'm using the tp-freeforall/prod repo)
Now I'm facing the following problem:

When sending out (TX) messages the SfdCapture.captured event never 
fires, except after boot-up for the first time.

- I captured some of these "first packets" with a CC2531 USB dongle and 
TI Packet Sniffer and the result looks like this every time:
41 88 11 22 00 FF XX XX XX XX XX XX XX XX XX (where XXs are different 
every time, but the length is the same, 15)

- I also measured the signal with an oscilloscope on GPIO4 of CC2520 
(which is set to SFD by default (based on CC2520 Datasheet / SWRS068) 
and connected to P8.1 on MSP430F5438a) and I can see this first SFD 
signal after boot-up, but the high-level of the signal is only around 
0.3V. (I don' really understand why so low.)

- I tried to remap the timers, because by default the radio uses Micro 
timer (my HplCC2520.nc is based on sam3s_ek) which is mapped to 
Timer1_A, but the P8.1 (the SFD signal from CC2520) is mapped to 
Timer0_A which is a T32khz timer, so I replaced Timer0_A and Timer1_A 
with each other, but it didn't get any better.

At the moment I'm out of ideas, if anyone could give me a hint what the 
problem could be, it'd be great.

(the above mentioned event can be found in 
/tos/chips/cc2520/CC2520DriverLayerP.nc around line 1600)

Thank you in advance.

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

[Tinyos-help] Resource.request() fails in SoftwareInit.init() (bad inicialization order)

2012-06-27 Thread Erdélyi Ádám [Edöm]

Hi,

I had the same problem while interfacing CC2520 radio with MSP430F5438A uc. 
Martin's second solution eliminates the problem, but this way I cannot rely on 
any TinyOS repository if I want to publish only my platform implementation.
Is there any other way to change the order of function calls during 
initialization?

Adam Erdelyi

Hello.

On Sat, 11 Feb 2012, Eric Decker wrote:
>/I have problem with Resource.request() in SoftwareInit.init(), simple 
code
/>/(the same code as in RF230DriverLayerP.SoftwareInit.init()):
/
>/  You can't do this in SoftwareInit.init.
/>/  Why?   Because FcfsResource gets initialized via SoftwareInit.init and 
order of initialization is not stated nor can you count on it.
/>/  SoftwareInit does not guarantee any ordering.
/>/  > You can't call Resource.request for a Resource that uses Fcfs are 
the queuing mechanism.
/>/  Do it from Boot.booted.
/
I read about this issue in "TOS programming book" in chapter "4.4.
Multiple wirings". (The order of the calls is not defined.)

There are following issues:

1) The standard tinyos code uses this wrong mechanism. For example (at least):
  ./platforms/mulle/fix/RF230DriverHwAckP.nc
  ./platforms/mulle/fix/RF230DriverLayerP.nc
  ./chips/rf230/RF230DriverLayerP.nc
  ./chips/rf230/RF230DriverHwAckP.nc
  ./chips/rf212/RF212DriverLayerP.nc

2) How to implement "LocalIeeeEui64C" on external shared bus that must be
 available before the Boot.booted() event (TEP122).

>/How to establish "specific initialization ordering" for 
MainC.SoftwareInit (tep107) ?
/>/
/>/  What are you referring to in TEP107. 107 doesn't say anything about 
specific ordering.
/
Yes, TEP107.
Yes, TEP107 does not say anything _how_ to implement ordering.
But there is statement:

... "Components whose initialization does not directly depend on hardware
resources SHOULD wire to MainC.SoftwareInit. If a component requires a
specific initialization ordering, then it is responsible for establishing
that ordering. Due to the semantics of Init, this is usually quite rare; a
component SHOULD NOT introduce initialization dependencies unless they are
required." 

Is there some mechanism to establish call order ?

I see two solution.

1) Add next initialization layer between PlatformInit and SoftwareInit.

2) Rebind "component's data initialization"/"software data init" from
SoftwareInit.init() to PlatformInit.init(). (and modify TEP107)

For example:

===
--- tos/system/SimpleFcfsArbiterC.nc(revision 5889)
+++ tos/system/SimpleFcfsArbiterC.nc(working copy)
@@ -89,11 +89,11 @@
 uses interface ResourceConfigure[uint8_t id];
   }
   implementation {
-  components MainC;
+  components RealMainP;
 components new FcfsResourceQueueC(uniqueCount(resourceName)) as Queue;
 components new SimpleArbiterP() as Arbiter;

-  MainC.SoftwareInit -> Queue;
+  RealMainP.PlatformInit -> Queue;

 Resource = Arbiter;
 ResourceRequested = Arbiter;
===
--- tos/system/FcfsArbiterC.nc  (revision 5889)
+++ tos/system/FcfsArbiterC.nc  (working copy)
@@ -96,11 +96,11 @@
 uses interface ResourceConfigure[uint8_t id];
   }
   implementation {
-  components MainC;
+  components RealMainP;
 components new FcfsResourceQueueC(uniqueCount(resourceName)) as Queue;
 components new ArbiterP(uniqueCount(resourceName)) as Arbiter;

-  MainC.SoftwareInit -> Queue;
+  RealMainP.PlatformInit -> Queue;

 Resource = Arbiter;
 ResourceRequested = Arbiter;
===

M.C>

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

Re: [Tinyos-help] compile ToSSIM

Re: [Tinyos-help] compile ToSSIM

Re: [Tinyos-help] Im unable to install msp430-46 compiler

Re: [Tinyos-help] Sensor nodes sniffer

Re: [Tinyos-help] Please code and protocol LEACH PEGASISE

Re: [Tinyos-help] Do not use Latest TinyOS vistual box image

Re: [Tinyos-help] help

Re: [Tinyos-help] target-dependant additions, "overwriting" of default implementations

Re: [Tinyos-help] Texas Instruments 900MHz Mote

Re: [Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

Re: [Tinyos-help] Printf app- not displaying any message

Re: [Tinyos-help] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb

Re: [Tinyos-help] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb

Re: [Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

Re: [Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

Re: [Tinyos-help] Problems programming TelosB

[Tinyos-help] MSP430F5438a+CC2520 - SfdCapture.captured event never happens

[Tinyos-help] Resource.request() fails in SoftwareInit.init() (bad inicialization order)

18 matches

Site Navigation

Mail list logo

Footer information