Re: [Tinyos-help] Re: MicaZ standalone AES Encryption
On Thursday 31 May 2007 19:26, Tan Han Chiang wrote: > did anyone here managed to use the micaz standalone AES encryption > sucessfully?? Also does anyone knows the crypto used for the AES > standalone encryption? Is it CBC, counter mode or ?? The micaz uses the CC2420 radio, which has AES-128 functionality built into hardware. It can support Counter, CBC-MAC or CCM modes somewhat seamlessly as part of the packet send and receive workflows. You can also use it to do standalone encryption operations on non-packet data. CCM is the most interesting mode, in that it is a combination of Counter and CBC-Mac. The CC2420 data sheeet has all the details. We're going to be looking into using the CC2420 and AES for an upcoming project. At first blush, it looks like the packet-layer stuff will be pretty straightforward and key mangement will be the challenge if you need to do dynamic keying. TinySec is a security layer developed for TinyOS 1.x that might have some other useful information for you. Steve ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Tinyos-help Digest, Vol 49, Issue 146
Dear customer, Sorry, i am out of office till 02-06-2007. Best regards, Siegfried Schaefer Schaefer EDV-Dienstleistungen und Softwareentwicklungen Goethestr. 29 75031 Eppingen ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] CounterMicro question
Hi Nicolas,
On Thursday 31 May 2007 01:48, Nicolas Esteves wrote:
> I'm working with telosb and I'm trying to find a solution to estimate
> the time taken by some operation accurately (micro second). I first
> tried the TimerMicro but as i found after in the mailing list (here
> http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-May/024953.h
>tml) I understood that it was not a good solution and followed the Cory's
> advice: trying with a Counter and then Counter uint16_t>. I made a very simple test program: an infinite loop in the
> Boot.booted event which calculate dt between 2 loops and generate a 0 or 1
> on one of the pins of the mote if dt >= INTERVAL. Then i looked at the
> signal on an oscilloscope and measured the period of the "wave". I found
> that i can't have it < 16 us, ie with values of INTERVAL between 1 and
> 16-18 the period is the same. I wondered if it was normal since my program
> is only doing this.
If you take a look at the msp430 user's guide (I'm looking at version 'f'),
section 3.4.4 shows processor cycles per instruction, which appear to vary
between 1 and 5. If the average were, say 3.5 cycles per instruction, and
the tmote is running at 4Mhz, then about 19 instructions can execute in 16us
if my math is right. That doesn't seem unreasonable.
> I have also another question, I got jitter in my signal
> and i would like to understand why, i thought that
> gpio.set, gpio.clr and counter.get were done in constant time.
Perhaps interrupts are occurring? From the math above, you can see that it
wouldn't take much code in an ISR to give you visible jitter. The ugly way
to check this out would be to wrap the loop in an atomic section and see what
happens...
All the best,
Steve
>
> here is my loop:
>
> event void Boot.booted()
> {
> uint16_t t;
> uint16_t t0 = call Counter0.get();
>
> call outIO.makeOutput();
>
> while(TRUE)
> {
> t = call Counter0.get();
> if(t-t0 >= INTERVAL)
> {
> if( up )
> call outIO.set();
> else
> call outIO.clr();
>
>up = !up;
>
> t0 = t ;
> }
> }
> }
>
> Maybe I made something wrong. Can anyone help me with it?
> Thanks
>
> Nicolas
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> !DSPAM:465ec828292471804284693!
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] (no subject)
Dear all, I am having some problem with the temperature sensor value that I am getting from MTS310 sensorboard. I am using Crossbow's contrib/xbow/apps/XSensorMTS300 application. This application reads , among other things, the temperature sensor value. My problem is I always get 0 from Temperature.dataReady(uint16_t data) event. Please note that I am using micaz and tinyos 1.1.11. But when I remove the MTS310 board from the micaz mote, the temperature reading that I get is not 0. Please let me know what I am missing here. Thanks a lot, Monica Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: MicaZ standalone AES Encryption
Hi, did anyone here managed to use the micaz standalone AES encryption sucessfully?? Also does anyone knows the crypto used for the AES standalone encryption? Is it CBC, counter mode or ?? Any help would be appreciated. Thanks Institute For Infocomm Research - Disclaimer - This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MicroTimerM.nc:125: old-style parameter lists not supported
On May 31, 2007, at 11:31 AM, Vipin Kashyap wrote: Hi all! Further to my last post, I have been told that the reason for the MicroTimer code not working is that TOSSIM can not simulate hardware interrupts, the behaviour being non deterministic. However, the TOSSIM documentation (TOSSIM: A Simulator for TinyOS Networks) by Philip Levis and Nelson Lee says " Fidelity: By default, TOSSIM captures TinyOS’ behavior at a very low level. It simulates the network at the bit level, simulates each individual ADC capture, and every interrupt in the system." So, which is the correct interpretation? For 1.x, the text in the TOSSIM paper is correct. I think the issue is that you're using an interrupt which TOSSIM doesn't support. The text "every interrupt in the system" meant "every interrupt the TinyOS code uses when we wrote this paper." This generally meant the code in system/ and lib/, not necessarily every application that did special things. You need to write a TOSSIM implementation of MicroTimerM. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Why the accelerometer data value were so large when using MTS310?
Hi, I use MTS310 to sample acceleration data. As the resolution of AD is 10 bit, the maximum data should be 0x3ff, but most of my data are around 0x7A80. I only revised the start time of ADXL202E from 17 ms to 3 ms in file 'AccelP.nc' as I changed two capacitors of ADXL202E from 0.1 uF to 0.01 uF. Is there might some code problem in files of MTS300, which were downloaded from CVS ( http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/tos/sensorboards/mts300/ )? I list some sampled data as follows (in 16 bit format, high byte first): No.accelX accelY 3 68 129 0 122 128 3 72128 192 122 128 3 74129 64 122 64 The No. is not in sequence due to lost data when transmission. Where is problem? regards, Fangming ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MultiHopLEPSM.nc in TinyOS 1.X
Does anyone know where I can find more detailed documentation on MultiHopLEPSM. I need to modify the routing protocol, but I still don't understand fully how it works. -Brian ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Relocation Errors with TOSSIM in T2
I thought that was strange as well. It turns out that I had an older version of ncc (1.2alpha5) on my path from working with T1, and it was calling the wrong compiler. Thanks for the help! - Ryan Aurélien Francillon wrote: Hi Ryan, Le jeudi 31 mai 2007 11:58, J. Ryan Stinnett a écrit : I've just moved from TinyOS 1.x to T2 and was trying to compile TOSSIM for the Blink app, but got these errors which I don't know how to fix. I'd greatly appreciate any suggestions! $ make micaz sim ... avr-gcc: unrecognized option `-tossim' ... You are building with the wrong compiler, tossim is an application to run on your computer it should be built with regular compiler (i.e. not a cross-compiler). You probably have somewhere in your environement or makefile a line like : CC=avr-gcc while you need to build with plain gcc cheers, Aurélien ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MicroTimerM.nc:125: old-style parameter lists not supported
Hi all!
Further to my last post, I have been told that the reason for the
MicroTimer code not working is that TOSSIM can not simulate hardware
interrupts, the behaviour being non deterministic. However, the TOSSIM
documentation (TOSSIM: A Simulator for TinyOS Networks) by Philip Levis
and Nelson Lee says " Fidelity: By default, TOSSIM captures TinyOS
behavior at a very low level. It simulates the network at the bit level,
simulates each individual ADC capture, and every interrupt in the system."
So, which is the correct
interpretation?
Regards,
vipin
> Hi all !
>
> I am having a problem compiling the High frequency sampling in
> /tinyos-1.x/apps using 'make pc'. The error I get is reproduced below:
>
> MicroTimerM.nc:125: old-style parameter lists not supported
> MicroTimerM.nc:125: warning: return-type defaults to `int'
> make: *** [exe0] Error 1
>
> The problematic MicroTimer code is given below-
>
> TOSH_SIGNAL(SIG_OUTPUT_COMPARE1A) {
> signal MicroTimer.fired();
> }
>
> Thanks & regards,
> --
> Vipin Kashyap
> Roll# 05307415
> M Tech (Electronic Systems)
> Hostel-9, Room# 294
> IIT Bombay
> Ph# +91-9969031997
>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
--
Vipin Kashyap
Roll# 05307415
M Tech (Electronic Systems)
Hostel-9, Room# 294
Ph# +91-9969031997
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Tinyos-help Digest, Vol 49, Issue 144
Dear customer, Sorry, i am out of office till 02-06-2007. Best regards, Siegfried Schaefer Schaefer EDV-Dienstleistungen und Softwareentwicklungen Goethestr. 29 75031 Eppingen ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [blink_application]
Hi ! The link below will take you to the Blink folder in CVS repository of the tinyos project at sourceforge.net. There you can view and download THE RIGHT files as desired: http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/apps/Blink/ Regards, vipin > hi > > i want to know if somebody has ever done all tutorials for tinyos 1.1 ? > Indeed, i try to compile the first application but it doesn't work. I look > at files and i see that there are some mistakes? does somebody have got > the > right files for the blink application ? > > > thanks. > > _ > Windows Live Messenger sur i-mode : dialoguez avec vos amis depuis votre > mobile comme sur PC ! http://mobile.live.fr/messenger/bouygues/ > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- Vipin Kashyap Roll# 05307415 M Tech (Electronic Systems) Hostel-9, Room# 294 Ph# +91-9969031997 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] How to post replies?
Question is, how do I post an addendum to a thread that was existing before I joined the mailing list? Regards, vipin > > You must subscribe to the list you want to participate. After that, > you'll get all postings by email. Remember to "reply all" or whatever > your mail reader offers to include the list as a recipient. Please read > the FAQ to see how to subscribe and unsubscribe. > > Regards, > > Harri > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Vipin > Kashyap > Sent: Thursday, May 31, 2007 12:31 PM > To: Tinyos-help@Millennium.Berkeley.EDU > Subject: [Tinyos-help] How to post replies? > > Hi ! > > Can anyone tell me how to post replies / add further comments to an > existing thread. I am not able to find an option on the pages. > > Thanks & regards, > -- > Vipin Kashyap > Roll# 05307415 > M Tech (Electronic Systems) > Hostel-9, Room# 294 > IIT Bombay > Ph# +91-9969031997 > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel > p > -- Vipin Kashyap Roll# 05307415 M Tech (Electronic Systems) Hostel-9, Room# 294 Ph# +91-9969031997 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Linux client with Windows Server
Hi, Yes, I can ping both machines. I tried to close the firewall on my Windows machine but with no use. I can telnet from the Linux machine to the windows machine over port 9001 Regards islheg - Original Message - From: "Urs Hunkeler" <[EMAIL PROTECTED]> To: "Islam Hegazy" <[EMAIL PROTECTED]>; Sent: Wednesday, May 30, 2007 12:32 AM Subject: Re: [Tinyos-help] Linux client with Windows Server Hi, This sounds like you have either a firewall on the windows machine. Most likely you have to somewhere allow connections to the serial forwarder port(s). If you don't have a firewall or if you are sure that its configured properly, try the following: - Can you ping the windows machine from your linux machine? Often works in spite of the firewall and shows that the network is ok. If it doesn't work, it might be because of the firewall. Try the reverse (ping linux from windows). - Can you establish a connection with telnet? "telnet :" Cheers, Urs Islam Hegazy schrieb: Hi all I have a sensor network of mica2 motes. I use tinyos1.x. My base mote is connected to a Windows XP machine. I ran the SerialForwarder on the Windows machine that should accept client connections to send the collected data to them. If I write the client application under Windows, it will work correct. But if I write the client application under Linux, the client cannot connect to the server returning the error 'Connection timed out'. I use C++ and C# under Windows and C under Linux. To make sure that my Linux client is correct, I wrote a server application under Linux and they worked correct. So I wonder why my Linux client doesn't want to connect to the SerialForwarder on the windows machine? Regards islheg ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem compiling Blink to telosb platform
I tried to set up TinyOS as describe here: http://www.moteiv.com/community/Tmote_Linux_install for my Gentoo Linux box. I installed msp430 from ebuilds, and all the rest from sources. I seem to have the required tools ready: $ ncc --version ncc: 1.2alpha5 nescc: 1.2.8a $ msp430-gcc --version msp430-gcc (GCC) 3.2.3 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. also, telosb platform support seems to be there: $ ncc -print-platforms pc mica mica2 micaz rene2 telos mica128 mica2dot msp430 telosb atmega8 but still, this is what I get: $ make telosb mkdir -p build/telosb compiling Blink to a telosb binary ncc -o build/telosb/main.exe -O -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -I%T/lib/Deluge -Wl,--section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DIDENT_PROGRAM_NAME=\"Blink\" -DIDENT_USER_ID=\"maroy\" -DIDENT_HOSTNAME=\"tomodachi\" -DIDENT_USER_HASH=0xb6f4aef8L -DIDENT_UNIX_TIME=0x465eddbeL -DIDENT_UID_HASH=0x17c52c1dL -mdisable-hwmul -I/home/maroy/src/tyrell/src/corpora/tmote/var/tinyos-1.1.15Dec2005cvs/tos/lib/CC2420Radio Blink.nc -lm /tmp/ccYDpC1q.s: Assembler messages: /tmp/ccYDpC1q.s:255: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:255: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:259: Error: unknown opcode `msp430clockm$set_dco_calib:' /tmp/ccYDpC1q.s:261: Error: unknown pseudo-op: `.l__framesize_msp430clockm' /tmp/ccYDpC1q.s:262: Error: unknown pseudo-op: `.l__frameoffset_msp430clockm' /tmp/ccYDpC1q.s:276: Error: expected comma after name `MSP430ClockM' in .size directive /tmp/ccYDpC1q.s:280: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:280: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:284: Error: unknown opcode `timerm$settimer:' /tmp/ccYDpC1q.s:286: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:287: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:349: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:353: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:353: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:357: Error: unknown opcode `timerm$localtime$read:' /tmp/ccYDpC1q.s:359: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:360: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:392: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:396: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:396: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:400: Error: unknown opcode `timerm$inserttimer:' /tmp/ccYDpC1q.s:402: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:403: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:444: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:448: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:448: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:452: Error: unknown opcode `timerm$setnextshortevent:' /tmp/ccYDpC1q.s:454: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:455: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:564: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:568: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:568: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:572: Error: unknown opcode `timerm$post_checkshorttimers:' /tmp/ccYDpC1q.s:574: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:575: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:596: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:600: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:600: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:604: Error: unknown opcode `timerm$executetimers:' /tmp/ccYDpC1q.s:606: Error: unknown pseudo-op: `.l__framesize_timerm' /tmp/ccYDpC1q.s:607: Error: unknown pseudo-op: `.l__frameoffset_timerm' /tmp/ccYDpC1q.s:707: Error: expected comma after name `TimerM' in .size directive /tmp/ccYDpC1q.s:1122: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:1122: Error: junk at end of line, first unrecognized character is `$' /tmp/ccYDpC1q.s:1126: Error: unknown opcode `msp430dcocalibm$timermicro$overf' /tmp/ccYDpC1q.s:1128: Error: unknown pseudo-op: `.l__framesize_msp430dcocalibm' /tmp/ccYDpC1q.s:1129: Error: unknown pseudo-op: `.l__frameoffset_msp430dcocalibm' /tmp/ccYDpC1q.s:1167: Error: expected comma after name `MSP430DCOCalibM' in .size directive /tmp/ccYDpC1q.s:1171: Error: unrecognized symbol type "" /tmp/ccYDpC1q.s:1171: Error: junk at end of line, first unrecognized character is `$'
RE: [Tinyos-help] [blink_application]
You can get correct files from http://tinyos.cvs.sourceforge.net/tinyos/ to compare with yours. Are you sure that your installation is complete without error? Firat TARAKTAS Electrical&Electronics Engineer Reseracher GENETLAB INFORMATION TECHNOLOGIES Kayisdagi Caddesi Kar Plaza D Blok Kat:3 34752 Icerenkoy / ISTANBUL / TURKIYE Phone: +90 (216) 573 00 85 (int.354) Fax: +90 (216) 469 85 07 [EMAIL PROTECTED] www.genetlab.com -Original Message- From: vazoumana fofana [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 4:55 PM To: Firat TARAKTAS Subject: RE: [Tinyos-help] [blink_application] In component `Blink': Blink.nc:42: component Main not found In file included from Blink.nc:42: In component `BlinkM': BlinkM.nc:46: too few arguments to interface `Timer' In file included from Blink.nc:42: BlinkM.nc:58: syntax error before `StdControl' BlinkM: `StdControl.start' not implemented BlinkM: `StdControl.stop' not implemented BlinkM: `Timer.fired' not implemented In component `Blink': Blink.nc:42: component SingleTimer not found Blink.nc:43: cannot find `StdControl' Blink.nc:44: cannot find `StdControl' Blink.nc:45: cannot find `Timer' Here are the message error. I thought that the wiring wasn't good so i put the arrow in other sense for main but it doesn't work. It says that some methods are not implemented: i don't understand it because it's not the case i chek the name and they are equals. For singleTimer i try t o replace by TimerMillic as Timer 0 like in tinyos 2.O but it dosn't work . thanks for your answer. >From: "Firat TARAKTAS" <[EMAIL PROTECTED]> >To: "vazoumana fofana" ><[EMAIL PROTECTED]>, >Subject: RE: [Tinyos-help] [blink_application] >Date: Thu, 31 May 2007 16:28:59 +0300 > >Hi, >Can you send us the error and your actions? > > >Firat TARAKTAS > >Electrical&Electronics Engineer > >Reseracher >GENETLAB INFORMATION TECHNOLOGIES >Kayisdagi Caddesi Kar Plaza D Blok Kat:3 34752 Icerenkoy / ISTANBUL / >TURKIYE >Phone: +90 (216) 573 00 85 (int.354) >Fax: +90 (216) 469 85 07 >[EMAIL PROTECTED] >www.genetlab.com > > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >vazoumana fofana >Sent: Thursday, May 31, 2007 4:05 PM >To: tinyos-help@Millennium.Berkeley.EDU >Subject: [Tinyos-help] [blink_application] > >hi > >i want to know if somebody has ever done all tutorials for tinyos 1.1 ? >Indeed, i try to compile the first application but it doesn't work. I >look at files and i see that there are some mistakes? does somebody >have got the right files for the blink application ? > > >thanks. > >_ >Windows Live Messenger sur i-mode(tm) : dialoguez avec vos amis depuis >votre mobile comme sur PC ! http://mobile.live.fr/messenger/bouygues/ > >___ >Tinyos-help mailing list >Tinyos-help@Millennium.Berkeley.EDU >https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-he >l >p _ Découvrez le Blog heroic Fantaisy d'Eragon! http://eragon-heroic-fantasy.spaces.live.com/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] communicate with UART port
Hi, I am looking for a simple way to communicate with an UART port of a tmote, on which is connected a reader. The reader supports a specific message format. I therefore need to send a massage to the tmote on which runs an application that will forward the message to the reader. And it should answer the same way back. Any idea how i could to that? Julien ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] [blink_application]
Hi, Can you send us the error and your actions? Firat TARAKTAS Electrical&Electronics Engineer Reseracher GENETLAB INFORMATION TECHNOLOGIES Kayisdagi Caddesi Kar Plaza D Blok Kat:3 34752 Icerenkoy / ISTANBUL / TURKIYE Phone: +90 (216) 573 00 85 (int.354) Fax: +90 (216) 469 85 07 [EMAIL PROTECTED] www.genetlab.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of vazoumana fofana Sent: Thursday, May 31, 2007 4:05 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] [blink_application] hi i want to know if somebody has ever done all tutorials for tinyos 1.1 ? Indeed, i try to compile the first application but it doesn't work. I look at files and i see that there are some mistakes? does somebody have got the right files for the blink application ? thanks. _ Windows Live Messenger sur i-mode(tm) : dialoguez avec vos amis depuis votre mobile comme sur PC ! http://mobile.live.fr/messenger/bouygues/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel p ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [blink_application]
hi i want to know if somebody has ever done all tutorials for tinyos 1.1 ? Indeed, i try to compile the first application but it doesn't work. I look at files and i see that there are some mistakes? does somebody have got the right files for the blink application ? thanks. _ Windows Live Messenger sur i-mode : dialoguez avec vos amis depuis votre mobile comme sur PC ! http://mobile.live.fr/messenger/bouygues/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Relocation Errors with TOSSIM in T2
Hi Ryan, Le jeudi 31 mai 2007 11:58, J. Ryan Stinnett a écrit : > I've just moved from TinyOS 1.x to T2 and was trying to compile TOSSIM for > the Blink app, but got these errors which I don't know how to fix. I'd > greatly appreciate any suggestions! > > $ make micaz sim ... > avr-gcc: unrecognized option `-tossim' ... You are building with the wrong compiler, tossim is an application to run on your computer it should be built with regular compiler (i.e. not a cross-compiler). You probably have somewhere in your environement or makefile a line like : CC=avr-gcc while you need to build with plain gcc cheers, Aurélien ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] InternalFlash question
Hi Raj , Le jeudi 31 mai 2007 04:51, raj raj a écrit : > Hi all, > > Sorry I forgot to add one more question: > >From Deluge's code, I think Golden image starts from 0x of program > > memory. But InternalFlashC can write from (0x000 to 0xfff). How is that > > possible (that is if InternalFlashC writes to program memory)? So, if > > InternalFlashC writes to internal EEPROM (4KB), then the addresses like > > 0xfd6 (used by Deluge to store gvNum using InternalFlashC) lies outside > > the I/O space of Atmega128 ( EEPROM's addresses). I am confused here. > > Where does InternalFlashC write to- 128KB program memory or 4KB internal > > EEPROM)? > Those are different addresses spaces wrting to the 128kB flash (the elf TXT zone i.e. the actual code instructions to be executed ) is done in tos/lib/Deluge/TOSBoot/avr/ProgFlashM.nc while the 4kB "internal flash" (which is actually an eeprom) is read/written using tos/lib/Deluge/TOSBoot/avr/InternalFlashC.nc IIRC both addresses spaces starts at 0x but are not accessed with similar instructions ... > DOES InternalFlashC WRITE TO 128KB PROGRAM FLASH MEMORY OR 4KB INTERNAL > EEPROM? Please help, > so that's the 4KB INTERNAL EEPROM cheers Aurélien ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Relocation Errors with TOSSIM in T2
I've just moved from TinyOS 1.x to T2 and was trying to compile TOSSIM for the Blink app, but got these errors which I don't know how to fix. I'd greatly appreciate any suggestions! $ make micaz sim mkdir -p build/micaz placing object files in build/micaz writing XML schema to app.xml compiling BlinkAppC to object file sim.o ncc -c -DUSE_DL_IMPORT -fpic -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -finline-limit=10 -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -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 avr-gcc: unrecognized option `-tossim' /opt/tinyos-2.x/tos/system/SchedulerBasicP.nc: In function `SchedulerBasicP$Scheduler$init': /opt/tinyos-2.x/tos/system/SchedulerBasicP.nc:117: warning: implicit declaration of function `sim_node' /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc: In function `__nesc_nido_resolve': /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:322: warning: implicit declaration of function `strcmp' /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc: In function `__nesc_nido_initialise': /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:553: warning: passing arg 1 of `memset' discards qualifiers from pointer target type /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:554: warning: passing arg 1 of `memset' discards qualifiers from pointer target type /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:558: warning: implicit declaration of function `memcpy' /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc: At top level: /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:194: warning: '__nesc_nido_resolve' defined but not used /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer0AsyncP.nc:420: warning: '__nesc_nido_initialise' defined but not used compiling Python support and C libraries into pytossim.o, tossim.o, and c-support.o g++ -c -DUSE_DL_IMPORT -fpic -o build/micaz/pytossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.5 -I/opt/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:1: warning: -fpic ignored for target (all code is position independent) g++ -c -DUSE_DL_IMPORT -fpic -o build/micaz/tossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim.c -I/usr/include/python2.5 -I/opt/tinyos-2.x/tos/lib/tossim /opt/tinyos-2.x/tos/lib/tossim/tossim.c:1: warning: -fpic ignored for target (all code is position independent) g++ -c -DUSE_DL_IMPORT -fpic -o build/micaz/c-support.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/hashtable.c -I/usr/include/python2.5 -I/opt/tinyos-2.x/tos/lib/tossim /opt/tinyos-2.x/tos/lib/tossim/hashtable.c:1: warning: -fpic ignored for target (all code is position independent) linking into shared object ./_TOSSIM.dll g++ -fpic -W1,--enabled-auto-image-base build/micaz/pytossim.o build/micaz/sim.o build/micaz/tossim.o build/micaz/c-support.o -shared -L/usr/lib/python2.5/config -L//usr/include/python2.5/config -lstdc++ -lpython2.5 -o _TOSSIM.dll /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: build/micaz/sim.o: Relocations in generic ELF (EM: 83) /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: build/micaz/sim.o: Relocations in generic ELF (EM: 83) build/micaz/sim.o: could not read symbols: File in wrong format collect2: ld returned 1 exit status make: *** [sim-exe] Error 1 Thanks, Ryan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] How to post replies?
You must subscribe to the list you want to participate. After that, you'll get all postings by email. Remember to "reply all" or whatever your mail reader offers to include the list as a recipient. Please read the FAQ to see how to subscribe and unsubscribe. Regards, Harri -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vipin Kashyap Sent: Thursday, May 31, 2007 12:31 PM To: Tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] How to post replies? Hi ! Can anyone tell me how to post replies / add further comments to an existing thread. I am not able to find an option on the pages. Thanks & regards, -- Vipin Kashyap Roll# 05307415 M Tech (Electronic Systems) Hostel-9, Room# 294 IIT Bombay Ph# +91-9969031997 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel p ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to post replies?
Hi ! Can anyone tell me how to post replies / add further comments to an existing thread. I am not able to find an option on the pages. Thanks & regards, -- Vipin Kashyap Roll# 05307415 M Tech (Electronic Systems) Hostel-9, Room# 294 IIT Bombay Ph# +91-9969031997 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MicroTimerM.nc:125: old-style parameter lists not supported
Hi all !
I am having a problem compiling the High frequency sampling in
/tinyos-1.x/apps using 'make pc'. The error I get is reproduced below:
MicroTimerM.nc:125: old-style parameter lists not supported
MicroTimerM.nc:125: warning: return-type defaults to `int'
make: *** [exe0] Error 1
The problematic MicroTimer code is given below-
TOSH_SIGNAL(SIG_OUTPUT_COMPARE1A) {
signal MicroTimer.fired();
}
Thanks & regards,
--
Vipin Kashyap
Roll# 05307415
M Tech (Electronic Systems)
Hostel-9, Room# 294
IIT Bombay
Ph# +91-9969031997
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CounterMicro question
Hi,
I'm working with telosb and I'm trying to find a solution to estimate
the time taken by some operation accurately (micro second). I first
tried the TimerMicro but as i found after in the mailing list (here
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-May/024953.html)
I understood that it was not a good solution and followed the Cory's
advice: trying with a Counter and then Counteruint16_t>. I made a very simple test program: an infinite loop in the
Boot.booted event which calculate dt between 2 loops and generate a 0 or
1 on one of the pins of the mote if dt >= INTERVAL. Then i looked at the
signal on an oscilloscope and measured the period of the "wave". I found
that i can't have it < 16 us, ie with values of INTERVAL between 1 and
16-18 the period is the same. I wondered if it was normal since my
program is only doing this. I have also another question, I got jitter
in my signal and i would like to understand why, i thought that
gpio.set, gpio.clr and counter.get were done in constant time.
here is my loop:
event void Boot.booted()
{
uint16_t t;
uint16_t t0 = call Counter0.get();
call outIO.makeOutput();
while(TRUE)
{
t = call Counter0.get();
if(t-t0 >= INTERVAL)
{
if( up )
call outIO.set();
else
call outIO.clr();
up = !up;
t0 = t ;
}
}
}
Maybe I made something wrong. Can anyone help me with it?
Thanks
Nicolas
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
