Spam detection software, running on the system "mail.Millennium.Berkeley.EDU", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details.
Content preview: I am using 2 different versions of TinyOS-2.x: -TinyOS-2.1.1 that I have installed from http://docs.tinyos.net/index.php/Installing_TinyOS_2.1.1#Manual_installation_on_your_host_OS_with_RPMs In this version is working perfectly. [...] Content analysis details: (4.0 points, 3.3 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.2 FH_DATE_PAST_20XX The date is grossly in the future. 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP 0.0 HS_INDEX_PARAM URI: Link contains a common tracker pattern. -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0001] 0.0 HTML_MESSAGE BODY: HTML included in message 1.1 DNS_FROM_OPENWHOIS RBL: Envelope sender listed in bl.open-whois.org. 2.2 AWL AWL: From: address is in the auto white-list The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.
--- Begin Message ---I am using 2 different versions of TinyOS-2.x: -TinyOS-2.1.1 that I have installed from http://docs.tinyos.net/index.php/Installing_TinyOS_2.1.1#Manual_installation_on_your_host_OS_with_RPMs In this version is working perfectly. -TinyOS-2.x that I have updated 1 month ago. With this version I got that error. Sorry but I do not understand what should I do. In my code I have defined these functions: AVR_NONATOMIC_HANDLER(SIG_OUTPUT_COMPARE1A){ call UltrasoundControl.StopDetector(); CLR_BIT(PORTA,3); signal UltrasoundControl.DetectorTimeout(); } AVR_NONATOMIC_HANDLER(SIG_INPUT_CAPTURE1) { uint16_t time = __inw_atomic(ICR1L); CLR_BIT(PORTA,1); } In tos\chips\atm128\HplAtm128TimerP.nc file I have the following: AVR_NONATOMIC_HANDLER(SIG_OUTPUT_COMPARE1A) { signal CompareA.fired(); } AVR_NONATOMIC_HANDLER(SIG_INPUT_CAPTURE1) { signal Capture.captured(call Timer.get()); } Thank you very much. Sofia Subject: Re: Timers in the new version of TinyOS-2.x From: [email protected] Date: Thu, 20 May 2010 17:25:27 -0700 CC: [email protected] To: [email protected] On May 19, 2010, at 7:09 AM, sofia aparicio wrote: Hello, I would like to know if there were changes with timers in the new version of TinyOS-2.x I have a program where I used timer 1 and it is working perfectly with an old TinyOS-2.x but I get the following error in a new version of TinyOS-2.x I got the following error: /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer1P.nc:195: previous declara tion of `__vector_12' /opt/tinyos-2.x/tos/chips/atm128/timer/HplAtm128Timer1P.nc:207: previous declara tion of `__vector_11' Yes. Interrupts that TinyOS 1.x did not define are now defined in TinyOS 2.x. Rather than define these interrupt handlers in your code you should wire to the TinyOS events. Phil _________________________________________________________________ ¿Quieres conocer trucos de Windows 7? ¡Los que ya lo usan te los cuentan! http://www.sietesunpueblodeexpertos.com/index_windows7.html
--- End Message ---
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
