Re: [Tinyos-help] Tinyos-help Digest, Vol 222, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Thursday, February 23, 2023 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 222, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Special Issue on Industrial IoT networks to support future
  Cloud-to-Things applications ? Ad Hoc Networks, Elsevier ?
  (Francesca Righetti)


--

Message: 1
Date: Thu, 23 Feb 2023 09:01:44 +
From: Francesca Righetti 
Subject: [Tinyos-help] Special Issue on Industrial IoT networks to
support future Cloud-to-Things applications ? Ad Hoc Networks,
Elsevier ?
To: "tinyos-help@millennium.berkeley.edu"

Message-ID: 
Content-Type: text/plain; charset="utf-8"


Please consider to submit your paper:

Special Issue on Industrial IoT networks to support future Cloud-to-Things 
applications

? Ad Hoc Networks, Elsevier ?

The Cloud-to-Things (C2T) continuum is a novel paradigm that extends the 
cloud-computing centralized architecture by introducing intermediate computing 
layers to host industrial applications and services with stringent requirements 
in terms of latency and reliability in the communication with IoT devices and 
sensors.

Recent network architectures that support the integration of IoT devices into 
existing networks, like 6TiSCH or 5G/6G, include by design support for strict 
Quality of Service (QoS) communication requirements to ensure timed and 
reliable data delivery between applications and IoT devices.

The deployment and management of the C2T multi-tier computing infrastructure 
connected with industrial IoT via heterogeneous communication technologies on a 
large-scale will require innovative approaches to guarantee QoS application 
requirements by enabling the convergence between computing and networking. 
Current networking management approaches are not adequate to support this 
convergence, thus leading to research open issues in multiple areas, including, 
for instance, IoT networks performance optimization, efficient resource 
management, scalable device management, novel compute-network joint management 
strategies, etc.

In this special issue, we look for original and high-quality research works in 
these areas to enable the convergence between networking and computing in the 
C2T continuum for industrial applications. The topics relevant to this special 
issue include but are not limited to:

*Network resource allocation and management in Industrial IoT networks
*Integration between cloud-edge infrastructure and 5G/6G networks for the 
Industrial IoT
*Network continuity to support efficient offloading to optimize network 
performance
*Network strict-QoS for Industrial applications in the C2T continuum
*Joint network configuration and workload distribution in the C2T continuum
*Security issues and solutions for industrial systems in the C2T continuum
*Ad-Hoc Networks for industrial applications to support mobility
*Vehicular networks for cooperative autonomous vehicles
*Self-organizing networks in the C2T continuum
*Scalable management solutions in the C2T continuum
*Novel network paradigms to support the C2T continuum with QoS guarantees

Guest editors:

Jiannong Cao, Hong Kong Polytechnic 
University,jiannong@polyu.edu.hk
Sajal K. Das, Missouri University of Science and Technology, 
s...@mst.edu
Francesca Righetti, University of Pisa, 
francesca.righe...@unipi.it
Carlo Vallati, University of Pisa, 
carlo.vall...@unipi.it

Manuscript submission information:

The

Re: [Tinyos-help] Tinyos-help Digest, Vol 221, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Wednesday, January 18, 2023 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 221, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Special Issue on Industrial IoT networks to support future
  Cloud-to-Things applications ? Ad Hoc Networks, Elsevier ?
  (Francesca Righetti)


--

Message: 1
Date: Wed, 18 Jan 2023 08:07:48 +
From: Francesca Righetti 
Subject: [Tinyos-help] Special Issue on Industrial IoT networks to
support future Cloud-to-Things applications ? Ad Hoc Networks,
Elsevier ?
To: "tinyos-help@millennium.berkeley.edu"

Message-ID: <6e671e3f-b9e8-41b6-b65c-c8214a9f7...@unipi.it>
Content-Type: text/plain; charset="utf-8"

Special Issue on Industrial IoT networks to support future Cloud-to-Things 
applications

? Ad Hoc Networks, Elsevier ?

The Cloud-to-Things (C2T) continuum is a novel paradigm that extends the 
cloud-computing centralized architecture by introducing intermediate computing 
layers to host industrial applications and services with stringent requirements 
in terms of latency and reliability in the communication with IoT devices and 
sensors.

Recent network architectures that support the integration of IoT devices into 
existing networks, like 6TiSCH or 5G/6G, include by design support for strict 
Quality of Service (QoS) communication requirements to ensure timed and 
reliable data delivery between applications and IoT devices.

The deployment and management of the C2T multi-tier computing infrastructure 
connected with industrial IoT via heterogeneous communication technologies on a 
large-scale will require innovative approaches to guarantee QoS application 
requirements by enabling the convergence between computing and networking. 
Current networking management approaches are not adequate to support this 
convergence, thus leading to research open issues in multiple areas, including, 
for instance, IoT networks performance optimization, efficient resource 
management, scalable device management, novel compute-network joint management 
strategies, etc.

In this special issue, we look for original and high-quality research works in 
these areas to enable the convergence between networking and computing in the 
C2T continuum for industrial applications. The topics relevant to this special 
issue include but are not limited to:

*Network resource allocation and management in Industrial IoT networks
*Integration between cloud-edge infrastructure and 5G/6G networks for the 
Industrial IoT
*Network continuity to support efficient offloading to optimize network 
performance
*Network strict-QoS for Industrial applications in the C2T continuum
*Joint network configuration and workload distribution in the C2T continuum
*Security issues and solutions for industrial systems in the C2T continuum
*Ad-Hoc Networks for industrial applications to support mobility
*Vehicular networks for cooperative autonomous vehicles
*Self-organizing networks in the C2T continuum
*Scalable management solutions in the C2T continuum
*Novel network paradigms to support the C2T continuum with QoS guarantees

Guest editors:

Jiannong Cao, Hong Kong Polytechnic University,jiannong@polyu.edu.hk
Sajal K. Das, Missouri University of Science and Technology, s...@mst.edu
Francesca Righetti, University of Pisa, francesca.righe...@unipi.it
Carlo Vallati, University of Pisa, carlo.vall...@unipi.it

Manuscript submission information:

The ADHOC's submission system (Editorial 
Manager?) will be open 
fo

Re: [Tinyos-help] Tinyos-help Digest, Vol 221, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Wednesday, January 4, 2023 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 221, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Tinyos help, Hello (Abhishek Trivedi)


--

Message: 1
Date: Wed, 4 Jan 2023 13:39:15 +0300
From: "Abhishek Trivedi" 
Subject: [Tinyos-help] Tinyos help, Hello
To: "tinyos-help" 
Message-ID: <395093gfpqtu$7q117nqb$d99fqkhz$@logo-iq.com>
Content-Type: text/plain; charset="us-ascii"

Tinyos help

https://www.google.com/search?q=tinyos-help@Millennium.Berkeley.EDU





Abhishek

-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20230104/0717c3ce/attachment.html

--

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

End of Tinyos-help Digest, Vol 221, Issue 1
***
--
External Email: Please use caution when opening links and attachments / 
Courriel externe: Soyez prudent avec les liens et documents joints

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 220, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Thursday, December 8, 2022 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 220, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. [Call for Participation] IEEE MSN 2022 (Virtual) Dec. 14-16
  Exciting Keynotes, Panel, and Paper Sessions (Lei Yang)


--

Message: 1
Date: Thu, 8 Dec 2022 11:25:32 +0800
From: Lei Yang 
Subject: [Tinyos-help] [Call for Participation] IEEE MSN 2022
(Virtual) Dec. 14-16 Exciting Keynotes, Panel, and Paper Sessions
To: tinyos-help@millennium.berkeley.edu
Message-ID:

Content-Type: text/plain; charset="utf-8"

*** Please accept our apologies if you receive multiple copies of this call
for participation***

It is our great pleasure to invite you to participate in the IEEE MSN 2022
this year.
Due to the COVID-19 pandemic, MSN 2022 will be held virtually during Dec.
14 ? Dec. 16, 2022.
https://ieee-msn.org/2022/

The registration and program information is provided as follows.
Register at: https://ieee-msn.org/2022/registration.php
Non-author Registration Fee:  $100
Registration Deadline: December 12
Program At Glance: https://ieee-msn.org/2022/glance.php
Online Program: https://msn2022.info/

We are excited to introduce the technical program of MSN 2022, which is
dedicated to exploring new, innovative and diverse directions in the fields
of mobility, sensing and networking. We received 246 technical submissions,
which includes 227 regular submissions and 19 invited submissions. Each
submission was reviewed by at least three technical program committee (TPC)
members or selected external reviewers. Additional reviews were solicited
as needed.
Among the regular submissions, we have selected 62 full papers. Hence the
acceptance rate is 27%. In addition, we have selected 29 short papers for
inclusion in the technical program of the main conference. Together with
the 19 invited papers, the technical program thus includes 110 papers and
covers a wide range of topics, including mobile/edge/fog computing,
networking, algorithms, ubiquitous sensing, big data and AI, security,
trust and privacy, and experiments.

In the main conference, three exciting keynote speeches and one panel
discussion are arranged. Prof. Daqing Zhang, Prof. Falko Dressler and Prof.
Guoliang Xing deliver the exciting keynotes on sensing limits, virtualized
edge computing and real-time AI, respectively.
Besides, the conference has six tracks this year: Track 1: Mobile &
Wireless Sensing and Networking; Track 2: Edge Computing, IoT and Digital
Twins; Track 3: Security, Privacy, Trust, and Blockchain; Track 4: Big Data
and AI; Track 5: Systems, Tools, Testbed; Track 6: Applications in Smart
Cities, Healthcare and Other Areas.
For all tracks, 111 accepted papers have been arranged in 24 technical
sessions in main conference.
Additionally, we selected five workshops: The 1st International Workshop on
Cryptographic Security and Information Hiding Technology for IoT System
(CSIHTIS 2022), The 3th International Workshop on Ubiquitous Electric
Internet of Things (UEIoT 2022), The 4th International Workshop on Edge
Computing and Artificial Intelligence based Sensor-Cloud System (ECAISS
2022), The 4th International Workshop on Network Meets Intelligent
Computations (NMIC 2022), The 4th International Workshop on Artificial
Intelligence Applications in Internet of Things (AI2OT 2022). There is a
total of 41 technical papers to be presented in the workshops.

Looking forward to seeing you at the MSN 2022!

IEEE MSN 2021 Organizing Committee

TPC Co-Chairs:
Giuseppe Anastasi, Univer

[Tinyos-help] Tinyos forum

[Andrea]

Hi everyone! I’m trying to run the application TestSerial on my iris mote. From the command line the packages are sent to the mote, but are not received. The application is already installed with TinyOS, and I am not sure to modify the code. Why the mote is not sending the packages? Regards,Andrea StrappatoInviato da Posta per Windows 
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos forum

[Eric Decker]

yes.  you just did.


On Mon, Sep 13, 2021 at 4:05 AM Andrea Strappato 
wrote:

> Hi,
> How can I post in Tinyos help?
> Regards,
> ___
> 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] Tinyos forum

[Andrea Strappato]

Hi,
How can I post in Tinyos help?
Regards,
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 211, Issue 1

[PREETI BISHT]

Please remove me from your mailing list

Thanks and Regards
Preeti Bisht

On Fri, 23 Jul 2021 at 12:30 AM, <
tinyos-help-requ...@millennium.berkeley.edu> wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. IEEE SMARTCOMP 2021: Student Grant Application (Mattia Campana)
>
>
> --
>
> Message: 1
> Date: Thu, 22 Jul 2021 12:15:01 +0200
> From: Mattia Campana 
> Subject: [Tinyos-help] IEEE SMARTCOMP 2021: Student Grant Application
> To: tinyos-help@millennium.berkeley.edu
> Message-ID: <20210722101501.u0g-d%mattia.camp...@iit.cnr.it>
> Content-Type: text/plain; charset=utf-8
>
> ==
> SMARTCOMP 2021 NSF Participation grants for US-based students - Due August
> 1, 2021 (via EDAS)
> ==
>
> The 7th IEEE International Conference on Smart Computing (IEEE SMARTCOMP
> 2021) is pleased to announce participation grants for US based students to
> attend the conference and co-located events (Workshops, Ph.D. Forum, WiP,
> Industry Track, Demo sessions, etc.) to be held virtually in on August
> 23-27, 2021. Funds for this participation support, which reimburses the
> conference registration fee, have been provided by the US National Science
> Foundation (NSF).
> This funding is available only to full time students attending colleges
> and universities in the US. Underrepresented minority and women students
> from diverse US institutions are particularly encouraged to apply. Although
> student authors may be given priority for participation awards, exceptional
> undergraduate research students (e.g., NSF REU students), MS research
> students, PhD and beginning post-doctoral researchers may also be
> considered even though they may not be authors of accepted papers. To be
> eligible, US based students (referred to as "you") must apply via EDAS no
> later than Sunday, August 1, 2021.
>
> To apply for travel support, please do the following:
>
> 1. Obtain a letter from your advisor/professor confirming that:
> - You are currently a full-time research student in good standing in a US
> institution and working in areas related to smart computing,
> - You will be attending the entire IEEE SMARTCOMP conference and
> associated events.
> 2. Write a personal statement describing your research interests and
> accomplishments to date, how you wish to benefit from attending SMARTCOMP
> 2021. Indicate your full-time student status (B.S., M.S., Ph.D. or
> postdoc).?
> 3. Upload the above documents, along with your two-page CV, on EDAS as
> part of the "SMARTCOMP 2021 NSF supported participation grant for US based
> students".
>
> This participation grant reimburses advance SMARTCOMP registrations.
> Student participation grants are available in the form of reimbursements
> that are sent only after the completion of the conference and receipt of
> all required documents and receipts. Several grants will be awarded with
> the value equivalent to the SMARTCOMP student registration fee of $100.
>
> For any questions, please contact the SMARTCOMP 2021 NSF Travel Award
> Chair, Sajal K. Das at s...@mst.edu.
>
> Important Dates:
> August 1, 2021: Student Application Submission Deadline (via EDAS)
> August 10, 2021: Advisor Letter Submission Deadline (via EDAS)
> August 16, 2021: Award Decisions Made
> August 23-27, 2021: IEEE SMARTCOMP Conference and Affiliated Events
>
>
>
> --
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> End of Tinyos-help Digest, Vol 211, Issue 1
> ***
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 207, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Monday, March 29, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 207, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Call for WIP and DEMO Papers :: SMARTCOMP 2021, Aug 23-27,
  2021, Irvine, CA, USA (Mattia Campana)


--

Message: 1
Date: Mon, 29 Mar 2021 18:15:01 +0200
From: Mattia Campana 
Subject: [Tinyos-help] Call for WIP and DEMO Papers :: SMARTCOMP 2021,
Aug 23-27, 2021, Irvine, CA, USA
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20210329161501.48nvw%mattia.camp...@iit.cnr.it>
Content-Type: text/plain; charset=utf-8

[Apologies if you receive multiple copies of this message]
===

  CALL FOR WIP-DEMO PAPERS
**
The 7th IEEE International Conference on Smart Computing (SMARTCOMP 2021), 
August 23-27, 2021 in Irvine, Orange County, California, USA
https://www.smart-comp.info
**

The 7th IEEE International Conference on Smart Computing (SMARTCOMP 2021) draws 
upon many application disciplines such as transportation, energy, environmental 
protection, resource management, healthcare, security, banking, entertainment, 
and social media. In addition to full-length technical papers, SMARTCOMP 
welcomes Work in Progress (WIP) papers and technical demonstrations (Demos) 
showing innovative and original research in the areas of smart computing. 
Submissions from both industry and academia are strongly encouraged.

WIP papers are expected to report on early or ongoing research activities, 
while Demo papers are expected to present innovative applications and tools.

The WIP and Demo sessions will provide a forum to discuss novel ideas and 
emerging results, presenting innovative applications and tools, and bring about 
novel research questions, approaches, and directions.

Currently the conference is planned to be in Irvine, Orange County, California, 
USA.
However, there is a possibility of moving to either a hybrid or fully online 
mode depending on the pandemic situation.


TOPICS
Areas of interest include (but are not limited to):

* Smart Computing Technologies and Applications
* Smart Cyber-Physical Systems and Energy/ Water/ Agriculture/ Transportation/ 
Healthcare/ Banking Infrastructure
* Future Smart Computing Paradigms
* Smart Human Environments, Health, Entertainment, and Social Activities
* Smart Computing for Environmental change (e.g., Energy Management and 
Analytics, Smart Transportation)
* Big Data, Artificial Intelligence and Machine Learning for Smart Computing
* Middleware Platforms for Smart Environments
* Mobile and Ubiquitous Platforms for Smart Environments
* Cloud, Edge and Fog Computing Platforms for Smart Systems
* Security, Privacy, and Economics in Smart Environments

WIP and Demo papers should be no more than 3 pages in length, including 
figures, tables, and references and formatted according to the two-column IEEE 
proceedings template. IEEE provides corresponding formatting templates at *IEEE 
conference template*. Make sure to use the conference mode of the template, 
i.e., LaTeX users must use the conference option of the IEEEtran document class.

WIP papers are expected to present early or ongoing research activities. Novel 
approaches and preliminary results are especially appreciated.

Demo papers should explicitly state what will be demonstrated to the audience, 
and how the attendees w

Re: [Tinyos-help] Tinyos-help Digest, Vol 206, Issue 7

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Friday, February 19, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 206, Issue 7

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Call for Participation: IEEE PerCom 2021 (Elisabetta Biondi)


--

Message: 1
Date: Fri, 19 Feb 2021 15:16:27 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] Call for Participation: IEEE PerCom 2021
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20210219141627.52s9w%elisabetta.bio...@iit.cnr.it>



Call for Participation: IEEE PerCom 2021


*** Early registration Deadline is February 21st, 2021 ***

** Our sincere apologies if you receive multiple copies of this call for 
participation **

=
CALL FOR PARTICIPATION
=

The 19th IEEE International Conference on Pervasive Computing and Communications
PerCom 2021, Kassel, Germany, March 22 - 26, 2021

http://www.percom.org


Sponsored by: IEEE Computer Society (IEEE TCCC, IEEE TCPP)

Other Sponsors: National Science Foundation, Pervasive and Mobile Computing 
Journal (ELSEVIER),
University of Kassel

Note: In the light of the international situation of the CoVID-19 pandemic 
PerCom 2021 will be
held as a virtual conference (synchronous ZOOM meeting supported by GatherTown 
and Slack).



*** Early Registration Deadline: February 21, 2021 ***

http://www.percom.org/participant_registration


Main Features:

*** Two keynote speeches
*** 14 Full Papers and 6 Concise Contributions - see below
*** Panel discussion session
*** Best Papers Session
*** Work-in-Progress Session
*** Industry session
*** Demonstration Session
*** PhD Forum
*** 13 Workshops - see http://www.percom.org/list_of_workshops


=
Preliminary Program Outline
=

March 22: Pre-conference Workshops
March 23-25: Main Conference
March 23-24: Keynotes
March 23 - 25: Industry, Demo and WiP sessions
March 23: Best Papers Session, PhD Forum
March 25: Panel
March 26: Post Conference Workshops

=


Keynotes
=
Keynote 1: 23 March @15.00 CET
Title; Monitoring People and their Vital Signs Using Radio Signals and Machine 
Learning
Speaker: Prof. Dina Katabi, MIT, USA.

Keynote 2: 24 March @15.00 CET
Title: Indoor Networks with a 6th Sense
Speaker: Dr Klaus Doppler, Nokia Bell Labs, USA

Visit http://www.percom.org/keynote_speakers  for more details
=



Panel, 25 March @15.00 CET
=
Panel topic: "Resilience in Urban and Critical Infrastructures: The Role of 
Pervasive Computing"
Panel Moderator: Prof. Max Muhlhauser, EmergenCity Center, Technical University 
of Darmstadt, Germany
Panelists:
- Prof. Christian Oberli, Chile Research Center for Integrated Disaster 
Risk Management (CIGIDEN), Santiago de Chile
- Prof. Moshe Vardi, Rice University, Houston, TX, USA
- Dr. Tina Comez, 4TU Resilience Engineering, TU Delft, The Netherlands
- Prof. Christoph Holscher, FRS Future Resilient Systems, ETH Zurich / 
CREATE Singapore


Visit   http://www.percom.org/panel for more detail.


=

Re: [Tinyos-help] Tinyos-help Digest, Vol 206, Issue 5

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Wednesday, February 17, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 206, Issue 5

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021 Participation Grants for US-basedstudents
  (Elisabetta Biondi)


--

Message: 1
Date: Wed, 17 Feb 2021 12:15:43 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021 Participation Grants for
US-basedstudents
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20210217111543.s7zhs%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii


-
IEEE PERCOM 2021 PARTICIPATION GRANTS FOR STUDENTS
Submission deadline: February 25, 2021
-
==

PerCom 2021 NSF Participation grants for US-based students - Due 25 February 
2021 (via EDAS)  -

*** Extended deadline ***

===

The 19th IEEE International Conference on Pervasive Computing and 
Communications (IEEE PerCom 2021) is pleased to announce participation grants 
for US based students to attend the conference and co-located events 
(Workshops, Ph.D. Forum, WiP, Industry Track, Demo sessions, etc.) to be held 
virtually in Kassel, Germany, on 22-26 March 2021. Funds for this participation 
support, which reimburses the conference registration fee, have been provided 
by the US National Science Foundation (NSF) - www.nsf.gov. 
This funding is available only to full time students attending colleges and 
universities in the US. Underrepresented minority and women students from 
diverse US institutions are particularly encouraged to apply. Although student 
authors may be given priority for participation awards, exceptional 
undergraduate research students (e.g., NSF REU students), MS research students, 
PhD and beginning post-doctoral researchers may also be considered even though 
they may not be authors o!
 f accepted papers. To be eligible, US based students (referred to as "you") 
must apply via EDAS no later than Thursday, 25 February, 2021.

To apply for travel support, please do the following:

1. Obtain a letter from your advisor/professor confirming that:

- You are currently a full-time research student in good standing and working 
in areas related to pervasive computing,

- You will be attending the entire IEEE PerCom conference and associated events.

2. Write a personal statement describing your research interests and 
accomplishments to date, how you wish to benefit from attending PerCom 2021. 
Indicate your full-time student status (B.S., M.S., Ph.D. or postdoc).

3. Upload the above documents, along with your two-page CV, on EDAS as part of 
the "PerCom 2021 NSF supported participation grant for US based students".

This participation grant reimburses advance PerCom registrations. Student 
participation grants are available in the form of reimbursements that are sent 
only after the completion of the conference and receipt of all required 
documents and receipts. Several grants will be awarded with the value 
equivalent to the PerCom early student registration fee.

For any questions, please contact the PerCom NSF Travel Award Chair, Sajal K. 
Das at s...@mst.edu.

Important Dates:

February 25, 2021: Complete Application Deadline (via EDAS)   *** Extended 
deadline ***

March 1, 2021: Award De

Re: [Tinyos-help] Tinyos-help Digest, Vol 206, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Friday, February 12, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 206, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021 Participation Grants for US-based and non-US
  students (Elisabetta Biondi)


--

Message: 1
Date: Fri, 12 Feb 2021 09:16:28 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021 Participation Grants for
US-based and non-US students
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20210212081628.5qkh9%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii


-
IEEE PERCOM 2021 PARTICIPATION GRANTS FOR STUDENTS
Submission deadline: February 15, 2021
-
==

PerCom 2021 NSF Participation grants for US-based students - Due 15 February 
2021 (via EDAS) 
===

The 19th IEEE International Conference on Pervasive Computing and 
Communications (IEEE PerCom 2021) is pleased to announce participation grants 
for US based students to attend the conference and co-located events 
(Workshops, Ph.D. Forum, WiP, Industry Track, Demo sessions, etc.) to be held 
virtually in Kassel, Germany, on 22-26 March 2021. Funds for this participation 
support, which reimburses the conference registration fee, have been provided 
by the US National Science Foundation (NSF) - www.nsf.gov. 
This funding is available only to full time students attending colleges and 
universities in the US. Underrepresented minority and women students from 
diverse US institutions are particularly encouraged to apply. Although student 
authors may be given priority for participation awards, exceptional 
undergraduate research students (e.g., NSF REU students), MS research students, 
PhD and beginning post-doctoral researchers may also be considered even though 
they may not be authors o!
 f accepted papers. To be eligible, US based students (referred to as "you") 
must apply via EDAS no later than Monday, 15 February, 2021.

To apply for travel support, please do the following:

1. Obtain a letter from your advisor/professor confirming that:

- You are currently a full-time research student in good standing and working 
in areas related to pervasive computing,

- You will be attending the entire IEEE PerCom conference and associated events.

2. Write a personal statement describing your research interests and 
accomplishments to date, how you wish to benefit from attending PerCom 2021. 
Indicate your full-time student status (B.S., M.S., Ph.D. or postdoc).

3. Upload the above documents, along with your two-page CV, on EDAS as part of 
the "PerCom 2021 NSF supported participation grant for US based students".

This participation grant reimburses advance PerCom registrations. Student 
participation grants are available in the form of reimbursements that are sent 
only after the completion of the conference and receipt of all required 
documents and receipts. Several grants will be awarded with the value 
equivalent to the PerCom early student registration fee.

For any questions, please contact the PerCom NSF Travel Award Chair, Sajal K. 
Das at s...@mst.edu.

Important Dates:

February 15, 2021: Complete Application Deadline (via EDAS)

February 26, 2021: Award Decisions Made

March 22-26, 2021: IEEE PerCom Conference and 

Re: [Tinyos-help] Tinyos-help Digest, Vol 206, Issue 3

[Prashan Wanigasekara]

Please unsubscribe me from this mailing list.

On Fri, Feb 12, 2021 at 2:58 PM 
wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. IEEE PerCom 2021 Participation Grants for US-based and non-US
>   students (Elisabetta Biondi)
>
>
> --
>
> Message: 1
> Date: Fri, 12 Feb 2021 09:16:28 +0100
> From: Elisabetta Biondi 
> Subject: [Tinyos-help] IEEE PerCom 2021 Participation Grants for
> US-based and non-US students
> To: tinyos-help@millennium.berkeley.edu
> Message-ID: <20210212081628.5qkh9%elisabetta.bio...@iit.cnr.it>
> Content-Type: text/plain; charset=us-ascii
>
>
> -
> IEEE PERCOM 2021 PARTICIPATION GRANTS FOR STUDENTS
> Submission deadline: February 15, 2021
> -
>
> ==
>
> PerCom 2021 NSF Participation grants for US-based students - Due 15
> February 2021 (via EDAS)
> ===
>
> The 19th IEEE International Conference on Pervasive Computing and
> Communications (IEEE PerCom 2021) is pleased to announce participation
> grants for US based students to attend the conference and co-located events
> (Workshops, Ph.D. Forum, WiP, Industry Track, Demo sessions, etc.) to be
> held virtually in Kassel, Germany, on 22-26 March 2021. Funds for this
> participation support, which reimburses the conference registration fee,
> have been provided by the US National Science Foundation (NSF) -
> www.nsf.gov. This funding is available only to full time students
> attending colleges and universities in the US. Underrepresented minority
> and women students from diverse US institutions are particularly encouraged
> to apply. Although student authors may be given priority for participation
> awards, exceptional undergraduate research students (e.g., NSF REU
> students), MS research students, PhD and beginning post-doctoral
> researchers may also be considered even though they may not be authors o!
>  f accepted papers. To be eligible, US based students (referred to as
> "you") must apply via EDAS no later than Monday, 15 February, 2021.
>
> To apply for travel support, please do the following:
>
> 1. Obtain a letter from your advisor/professor confirming that:
>
> - You are currently a full-time research student in good standing and
> working in areas related to pervasive computing,
>
> - You will be attending the entire IEEE PerCom conference and associated
> events.
>
> 2. Write a personal statement describing your research interests and
> accomplishments to date, how you wish to benefit from attending PerCom
> 2021. Indicate your full-time student status (B.S., M.S., Ph.D. or
> postdoc).
>
> 3. Upload the above documents, along with your two-page CV, on EDAS as
> part of the "PerCom 2021 NSF supported participation grant for US based
> students".
>
> This participation grant reimburses advance PerCom registrations. Student
> participation grants are available in the form of reimbursements that are
> sent only after the completion of the conference and receipt of all
> required documents and receipts. Several grants will be awarded with the
> value equivalent to the PerCom early student registration fee.
>
> For any questions, please contact the PerCom NSF Travel Award Chair, Sajal
> K. Das at s...@mst.edu.
>
> Important Dates:
>
> February 15, 2021: Complete Application Deadline (via EDAS)
>
> February 26, 2021: Award Decisions Made
>
> March 22-26, 2021: IEEE PerCom Conference and Affiliated Events
>
>
> ==
>
> IEEE CS TCPP & TCCC Participation Grant for non-US students Due Feb 15,
> 2021 (via EDAS) 
>
> The 19th IEEE International Conference on Pervasive Computing and
> Communications (IEEE PerCom 2021) is pleased to announce participation
> grants for non-US based students to attend the conference and co-located
> events (Workshops, Ph.D. Forum, WiP, Industry Track, Demo sessions, etc.)
> to be held virtually in Kassel, Germany, 22-26 March 2021. Funds for this
> participation support, which reimburses the conference registration fee,
> have been provided by the IEEE Comput

Re: [Tinyos-help] Tinyos-help Digest, Vol 206, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Tuesday, February 2, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 206, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021 Participation Grants for US-based and non-US
  students (Elisabetta Biondi)


--

Message: 1
Date: Tue, 02 Feb 2021 15:16:26 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021 Participation Grants for
US-based and non-US students
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20210202141626.s7tll%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii


-
IEEE PERCOM 2021 PARTICIPATION GRANTS FOR STUDENTS
Submission deadline: February 15, 2021
-
==

PerCom 2021 NSF Participation grants for US-based students - Due 15 February 
2021 (via EDAS) 
===

The 19th IEEE International Conference on Pervasive Computing and 
Communications (IEEE PerCom 2021) is pleased to announce participation grants 
for US based students to attend the conference and co-located events 
(Workshops, Ph.D. Forum, WiP, Industry Track, Demo sessions, etc.) to be held 
virtually in Kassel, Germany, on 22-26 March 2021. Funds for this participation 
support, which reimburses the conference registration fee, have been provided 
by the US National Science Foundation (NSF) - www.nsf.gov. 
This funding is available only to full time students attending colleges and 
universities in the US. Underrepresented minority and women students from 
diverse US institutions are particularly encouraged to apply. Although student 
authors may be given priority for participation awards, exceptional 
undergraduate research students (e.g., NSF REU students), MS research students, 
PhD and beginning post-doctoral researchers may also be considered even though 
they may not be authors o!
 f accepted papers. To be eligible, US based students (referred to as "you") 
must apply via EDAS no later than Monday, 15 February, 2021.

To apply for travel support, please do the following:

1. Obtain a letter from your advisor/professor confirming that:

- You are currently a full-time research student in good standing and working 
in areas related to pervasive computing,

- You will be attending the entire IEEE PerCom conference and associated events.

2. Write a personal statement describing your research interests and 
accomplishments to date, how you wish to benefit from attending PerCom 2021. 
Indicate your full-time student status (B.S., M.S., Ph.D. or postdoc).

3. Upload the above documents, along with your two-page CV, on EDAS as part of 
the "PerCom 2021 NSF supported participation grant for US based students".

This participation grant reimburses advance PerCom registrations. Student 
participation grants are available in the form of reimbursements that are sent 
only after the completion of the conference and receipt of all required 
documents and receipts. Several grants will be awarded with the value 
equivalent to the PerCom early student registration fee.

For any questions, please contact the PerCom NSF Travel Award Chair, Sajal K. 
Das at s...@mst.edu.

Important Dates:

February 15, 2021: Complete Application Deadline (via EDAS)

February 26, 2021: Award Decisions Made

March 22-26, 2021: IEEE PerCom Conference and 

Re: [Tinyos-help] Tinyos-help Digest, Vol 205, Issue 1

[BBMcoll]

Un message en fran?ais suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous r?pondrons ? votre demande dans les plus brefs d?lais ? l'int?rieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l'Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d'avoir communiqu? avec l'?quipe Recouvrement de Bell March?s Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Friday, January 1, 2021 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 205, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. (no subject) (Anita Patil)


--

Message: 1
Date: Fri, 1 Jan 2021 23:40:39 +0530
From: Anita Patil 
Subject: [Tinyos-help] (no subject)
To: tinyos-help@millennium.berkeley.edu
Message-ID:

Content-Type: text/plain; charset="utf-8"

Dear Sir/Mam,
Is there any function in nesC to compute memory occupied by a task? (just
like, memory occupied by a function in C program)

with Regards
Anita Patil
-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20210101/22db3c72/attachment.html

--

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

End of Tinyos-help Digest, Vol 205, Issue 1
***
--
External Email: Please use caution when opening links and attachments / 
Courriel externe: Soyez prudent avec les liens et documents joints

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 204, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Tuesday, December 29, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 204, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Re: Time function (Eric Decker)


--

Message: 1
Date: Mon, 28 Dec 2020 22:07:33 -0800
From: Eric Decker 
Subject: Re: [Tinyos-help] Time function
To: Jeremy J 
Cc: tinyos forum 
Message-ID:

Content-Type: text/plain; charset="utf-8"

actually this has already been done in the tp-freeforall tree (
https://github.com/tp-freeforall/prod)
<https://github.com/tp-freeforall/prod>

It is implemented in
https://github.com/tp-freeforall/prod/blob/tp-master/tos/system/SchedulerBasicP.nc

it is in memory logging.  there are some gdb functions that deal with this
available at...
https://github.com/tp-freeforall/prod/blob/tp-master/tools/99_gdb/gdb_tasks.py

you need to be using GDB talking to a gdb remote stub implemented by a JTAG
probe to the device under test (DUT).  such as a segger jlink.


On Sun, Dec 27, 2020 at 6:41 AM Jeremy J  wrote:

> There are no built in functions. you will have to manually snapshot the
> timer count at the startand stop  of a task
>
> On Sun, Dec 27, 2020 at 8:59 AM Anita Patil 
> wrote:
>
>> Is there any function in nesC to compute time taken by a task processing?
>>
>> In Timer.nc interface there are functions Iike getnow(), gett0() ,
>> getdt(), startperiodic() etc. But I didn't get any function to compute time
>> taken by a task processing. I.e to start and stop the timer respectively
>> before posting a task and after posting a task.
>>
>> Thank you 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



--
Eric B. Decker
Senior (over 50 :-) Researcher
-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20201228/1a43a556/attachment.html

--

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

End of Tinyos-help Digest, Vol 204, Issue 3
***
--
External Email: Please use caution when opening links and attachments / 
Courriel externe: Soyez prudent avec les liens et documents joints

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 204, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Sunday, December 27, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 204, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Time function (Anita Patil)
   2. Re: Time function (Jeremy J)


--

Message: 1
Date: Sun, 27 Dec 2020 19:27:17 +0530
From: Anita Patil 
Subject: [Tinyos-help] Time function
To: Tinyos-help@millennium.berkeley.edu
Message-ID:

Content-Type: text/plain; charset="utf-8"

Is there any function in nesC to compute time taken by a task processing?

In Timer.nc interface there are functions Iike getnow(), gett0() , getdt(),
startperiodic() etc. But I didn't get any function to compute time taken by
a task processing. I.e to start and stop the timer respectively before
posting a task and after posting a task.

Thank you in advance.
-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20201227/e4b2b266/attachment.html

--

Message: 2
Date: Sun, 27 Dec 2020 09:39:15 -0500
From: Jeremy J 
Subject: Re: [Tinyos-help] Time function
To: Anita Patil 
Cc: tinyos forum 
Message-ID:

Content-Type: text/plain; charset="utf-8"

There are no built in functions. you will have to manually snapshot the
timer count at the startand stop  of a task

On Sun, Dec 27, 2020 at 8:59 AM Anita Patil 
wrote:

> Is there any function in nesC to compute time taken by a task processing?
>
> In Timer.nc interface there are functions Iike getnow(), gett0() ,
> getdt(), startperiodic() etc. But I didn't get any function to compute time
> taken by a task processing. I.e to start and stop the timer respectively
> before posting a task and after posting a task.
>
> Thank you in advance.
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20201227/c979271f/attachment-0001.htm

--

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

End of Tinyos-help Digest, Vol 204, Issue 1
***
--
External Email: Please use caution when opening links and attachments / 
Courriel externe: Soyez prudent avec les liens et documents joints

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 203, Issue 3

[BBMcoll]

Hi,



Please dont send us these emails .

This is Bell Canada business department email address.





Thank you







-Original Message-
From: tinyos-help-requ...@millennium.berkeley.edu 
[mailto:tinyos-help-requ...@millennium.berkeley.edu]
Sent: Tuesday, November 24, 2020 3:00:02 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 203, Issue 3



Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom PhD Forum 2021: Call for Papers (Elisabetta Biondi)


--

Message: 1
Date: Tue, 24 Nov 2020 12:15:44 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom PhD Forum 2021: Call for Papers
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20201124111544.dvqlx%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii


-
CALL FOR PAPERS ON IEEE PERCOM PHD FORUM
Submission deadline: December 18, 2020
-

| PhD Forum on Pervasive Computing and Communications
| IEEE PerCom 2021
| March 22-26 2021
| http://www.percom.org/call_for_phd_forum_papers

Call for PhD Forum Contributions

# PHD FORUM ON PERVASIVE COMPUTING AND COMMUNICATIONS

The Fourteenth Ph.D. Forum on Pervasive Computing and Communication will be 
hosted by PerCom 2021 (virtual with synchronous zoom meeting). The Forum 
provides an excellent opportunity for Ph.D. students to present their 
dissertation research, including work in progress, to the wider pervasive 
computing and communication community. This meeting offers an opportunity to 
share experiences with other Ph.D. students and meet with accomplished 
international researchers and obtain feedback from them.

# PHD FORUM FORMAT

The Forum will be organized as a co-located PerCom event attended by experts in 
pervasive computing and communication, and will be supplemented by a 
one-minute-madness session plus a poster session during the main conference, so 
as to facilitate extended interaction opportunities between Ph.D. student 
participants and researchers from academia, industry, and government. During 
the workshop, senior members of the community will be present to provide 
constructive technical comments to each attendee. The Forum will provide a 
working environment for students to  refine and practice their presentations, 
helping them to improve communication skills. Special recognition will be given 
to the most innovative and/or most promising research project(s) presented at 
the Ph.D. Forum based on the pitch talk, the presented poster and the 
discussions with the participants during the poster session.

# PAPER SUBMISSION AND PUBLICATION

Ph.D. students are invited to submit two-page extended abstracts in English 
that describe their current research and potential contributions to innovative 
theory, algorithm development, and applications in pervasive computing and 
communications. The abstract should include the author's name, affiliation and 
email address. The name of the supervisor should be marked ("supervised by 
...") on the paper, under the author's name. Submissions must be in PDF format, 
be no more than two pages in length (all inclusive) and adhere to the IEEE 
two-column conference format (the same format used for paper submissions to 
PerCom 2021). Submissions that are substantially similar to presentations from 
a previous Ph.D. Forum are not allowed. Submissions will be reviewed by the 
Ph.D. Forum Technical Program Committee to ensure quality and relevance. In 
case of acceptance, the length of the camera-ready paper will be limited to two 
pages. Accepted abstracts will appear in the conference's works!
 hop proceedings and will be indexed by DBLP and the IEEE digital library.

All manuscripts must be registered and submitted through the EDAS submission 
site: https://edas.info/N27738

# PARTICIPATION

Authors of accepted submissions are expected to participate in the Ph.D. Forum, 
deliver an elevator pitch for their work, and present their poster at the 
PerCom 2021 conference. Standard PerCom 2021 registration fees apply. 
Participants who are current full-time students are eligible for the student 
registration fee. US-based students can apply for an NSF travel grant (when 
details are available they will be published on the PerCom web site).

# IMPORTANT DAT

Re: [Tinyos-help] Tinyos-help Digest, Vol 203, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Tuesday, November 24, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 203, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom PhD Forum 2021: Call for Papers (Elisabetta Biondi)


--

Message: 1
Date: Tue, 24 Nov 2020 12:15:44 +0100
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom PhD Forum 2021: Call for Papers
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20201124111544.dvqlx%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii


-
CALL FOR PAPERS ON IEEE PERCOM PHD FORUM
Submission deadline: December 18, 2020
-

| PhD Forum on Pervasive Computing and Communications
| IEEE PerCom 2021
| March 22-26 2021
| http://www.percom.org/call_for_phd_forum_papers

Call for PhD Forum Contributions

# PHD FORUM ON PERVASIVE COMPUTING AND COMMUNICATIONS

The Fourteenth Ph.D. Forum on Pervasive Computing and Communication will be 
hosted by PerCom 2021 (virtual with synchronous zoom meeting). The Forum 
provides an excellent opportunity for Ph.D. students to present their 
dissertation research, including work in progress, to the wider pervasive 
computing and communication community. This meeting offers an opportunity to 
share experiences with other Ph.D. students and meet with accomplished 
international researchers and obtain feedback from them.

# PHD FORUM FORMAT

The Forum will be organized as a co-located PerCom event attended by experts in 
pervasive computing and communication, and will be supplemented by a 
one-minute-madness session plus a poster session during the main conference, so 
as to facilitate extended interaction opportunities between Ph.D. student 
participants and researchers from academia, industry, and government. During 
the workshop, senior members of the community will be present to provide 
constructive technical comments to each attendee. The Forum will provide a 
working environment for students to  refine and practice their presentations, 
helping them to improve communication skills. Special recognition will be given 
to the most innovative and/or most promising research project(s) presented at 
the Ph.D. Forum based on the pitch talk, the presented poster and the 
discussions with the participants during the poster session.

# PAPER SUBMISSION AND PUBLICATION

Ph.D. students are invited to submit two-page extended abstracts in English 
that describe their current research and potential contributions to innovative 
theory, algorithm development, and applications in pervasive computing and 
communications. The abstract should include the author's name, affiliation and 
email address. The name of the supervisor should be marked ("supervised by 
...") on the paper, under the author's name. Submissions must be in PDF format, 
be no more than two pages in length (all inclusive) and adhere to the IEEE 
two-column conference format (the same format used for paper submissions to 
PerCom 2021). Submissions that are substantially similar to presentations from 
a previous Ph.D. Forum are not allowed. Submissions will be reviewed by the 
Ph.D. Forum Technical Program Committee to ensure quality and relevance. In 
case of acceptance, the length of the camera-ready paper will be limited to two 
pages. Accepted abstracts will appear in the conference's works!
 hop proceedings and will be indexed by DBLP and the IEEE digital library.

All manuscripts must be registered and s

Re: [Tinyos-help] Tinyos-help Digest, Vol 203, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Thursday, November 12, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 203, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. CFP: IEEE COMMUNICATIONS MAGAZINE Series on INTERNET OF
  THINGS AND SENSOR NETWORKS (Ngoc-Dung Dao)


--

Message: 1
Date: Wed, 11 Nov 2020 22:38:42 -0500
From: Ngoc-Dung Dao 
Subject: [Tinyos-help] CFP: IEEE COMMUNICATIONS MAGAZINE Series on
INTERNET OF THINGS AND SENSOR NETWORKS
To: tinyos-help@millennium.berkeley.edu
Message-ID:

Content-Type: text/plain; charset="utf-8"

Please accept our sincere apologies if you receive multiple copies of this
CFP.
---
Call for Papers

IEEE COMMUNICATIONS MAGAZINE

Series on

INTERNET OF THINGS AND SENSOR NETWORKS

https://www.comsoc.org/publications/magazines/ieee-communications-magazine/cfp/internet-things-and-sensor-networks
---

The Internet of Things (IoT) undergoes a fundamental transformation as an
increasing diversity of intelligent devices are being connected to it.
Underpinning this global development, the Series on IoT and Sensor Networks
of the IEEE Communications Magazine aims at bringing together the latest
industrial and academic progress, research, and development efforts within
the rapidly maturing IoT ecosystem. The Series profoundly explores the
concept of IoT and sensor networks, highlights the recent activities and
achievements therein, as well as provides insights into the theoretical and
practical matters related to breakthroughs in this field from different
perspectives. We welcome contributions on the emerging IoT topics that
support prospective ?critical? IoT applications as well as on further
evolution of the conventional ?massive? sensor network based enablers. The
submissions should be tutorial in nature and significantly advance the
state-of-the-art in the topics on IoT and sensor networks, which include
but are not limited to:

- System architecture and protocol design (access, mobility, routing,
scalability, etc.)
- New communication and sensing devices for IoT
- Enabling communication technologies for IoT (e.g., wireless, optical,
acoustic, molecular, quantum)
- IoT-specific radio solutions (NB-IoT, LTE-M, LoRa, SigFox, etc.)
- Novel Internet of Everything (IoE) paradigms (e.g., Internet of Bio-Nano
Things, Internet of Vehicles, Internet of Drones, Internet of Space,
Internet of People)
- Converged communication, computing, and storage technologies for IoT
- Integrated communication, positioning, navigation, and control in IoT
- Energy efficiency, energy harvesting, power management, and green
operation
- Smart objects, devices, environments, middleware, platforms, and tools
for IoT applications
- Analysis, simulation, testbed, and measurement campaigns
- Emerging applications (e.g., IoT for Agriculture, Smart City, Smart
Energy, Smart Health, Smart Transport, Public Safety, Humanitarian
Technologies, Industry 4.0, Society 5.0)
- Socio-economic, security and privacy, standardization, policy, and
regulatory aspects of IoT

This list is not exhaustive: submissions on new and interesting ideas
related to Internet of Things and Sensor Networks are encouraged.

SUBMISSION GUIDELINES
--

Manuscripts must be submitted through the magazine?s submissions Website at
http://mc.manuscriptcentral.com/com

Re: [Tinyos-help] Tinyos-help Digest, Vol 202, Issue 5

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Saturday, October 17, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 202, Issue 5

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. [CFP- Deadline extended] IEEE CCNC 2021 WKSHPS: 2nd
  International Workshop on Cyber Forensics & Advanced Threat
  Investigations in Emerging Networks (Chilean Scholar)


--

Message: 1
Date: Fri, 16 Oct 2020 23:42:07 +0100
From: Chilean Scholar 
Subject: [Tinyos-help] [CFP- Deadline extended] IEEE CCNC 2021 WKSHPS:
2nd International Workshop on Cyber Forensics & Advanced Threat
Investigations in Emerging Networks
To: tinyos-help@millennium.berkeley.edu
Message-ID:

Content-Type: text/plain; charset="UTF-8"

Dear Colleagues,

We cordially invite you to submit your paper to the 2nd International
Workshop on Cyber Forensics and Advanced Threat Investigations in
Emerging Networks (CFATI?21)

Held in conjunction with the IEEE CCNC 2021 (https://ccnc2021.ieee-ccnc.org)
9 January 2021, Virtual Conference

Website: 
https://ccnc2021.ieee-ccnc.org/workshop/2nd-international-workshop-cyber-forensics-and-advanced-threat-investigations-emerging

- Submission deadline: 6 November 2020 (Extended!)
- Notification: 23 November 2020
- Camera ready: 14 December 2020
- Workshop Day: January 9th, 2021

EDAS link for submissions: https://edas.info/newPaper.php?c=27781&track=103638

===
CALL FOR TECHNICAL PAPERS
===

The increasing proliferation of Information and communication
technologies (ICT) in our lives, has facilitated the connectivity
growth between distinct parts of our world. Various types of data are
continuously streaming across many boundaries in the world with
different models, policies, and purposes. Additionally, this data is
usually analyzed or stored on edge or gateways devices which have
highly limited capabilities and are vulnerable to sophisticated
attacks. With the growth of connectivity between various heterogeneous
systems, numerous attack vectors are constantly evolving, that can
potentially be exploited for malicious or criminal purposes (e.g. data
breaches, identity theft, and stealing of intellectual property and
trade secrets, etc.). Recent cyberattacks dangerously aim a broad
array of computing systems varying from data centers and personal
machines to mobile devices and industrial control systems.

There is a growing need for new methodologies, tools, and techniques,
capable of extracting, preserving, and analyzing different evidence
trails in various networked services and devices such as routers,
firewalls, web proxies, and network monitoring tools. Additionally,
there is also a growing need for research in new systems that are
capable of analyzing network traffic, netflows, and systems logs.
Satisfying these demands will aid in reconstructing the timeline of
the cyber-crime/attack under investigation and, possibly, the
identification of the potential actor(s).

The evolution of networked technologies, such as the internet of
things and cyber-physical systems, possess challenges based on the
highly limited capabilities of their infrastructure devices and the
type of data that can be processed by these devices. Complicated
efforts are required in suitable and timely manners against any
detected threats. Moreover, new frameworks are required to collect and
preserve potential evidential data in suitable and timely manners as
well. To guarantee proper cyber-defenses and strategies against the
expanding landscape of criminal activities as well as rapidly
advan

Re: [Tinyos-help] Tinyos-help Digest, Vol 202, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Friday, October 16, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 202, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021 Consolidated CALL FOR PAPERS for AFFILIATED
  EVENTS and WORKSHOPS (Elisabetta Biondi)


--

Message: 1
Date: Fri, 16 Oct 2020 14:17:52 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021 Consolidated CALL FOR PAPERS
for AFFILIATED EVENTS and WORKSHOPS
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20201016121752.v95ck%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii

IEEE PerCom 2021 / CONSOLIDATED CALL FOR PAPERS FOR AFFILIATED EVENTS AND 
WORKSHOPS
March 22-26, 2021 -Kassel, Germany
www.percom.org

PerCom is the premier scholarly venue in the areas of pervasive computing and 
communications. Detailed information about the scope of events, paper 
submission process, etc. can be obtained at http://www.percom.org/ and also at 
the URLs given below.

AFFILIATED EVENTS (www.percom.org):

PerCom'21 Industry Track
This year, PerCom continues the dedicated Industry Track. Accepted papers will 
be published in the PerCom Workshops and other Affiliated Events proceedings. 
This track will be an opportunity for people associated with industry and 
academia to present their novel ideas while attracting funding and/or further 
expanding collaborations. These papers will be presented with focus on research 
that has direct Industry impact and potential for industry uptake. For this 
track, important criteria for papers to be submitted to the Industry Track is 
clear industrial association, either in the form of extensive evaluation of 
research results in industrial use cases or active participation of industry 
representatives as co-authors. Having this condition in mind, contributions 
related to ongoing or finished, but previously unpublished research papers are 
welcomed. Submissions from a broad spectrum of research fields with common 
interest in pervasive computing and communications are expected!
 . There will be a Best Industry Track Paper Award to acknowledge and encourage 
excellence in collaborative industry research. (Paper submission: November 9, 
2020)

PerCom'21 Work in Progress
The Work in Progress (WiP) session provides an opportunity to present and 
discuss new challenges and visions, showcase early research results, and 
explore novel research directions. Papers (4 pages in the IEEE proceedings 
format) are expected to report on early or ongoing research on any aspect of 
pervasive computing and communications. The authors of accepted papers will 
present their work during the main conference and must register for the 
conference. (Paper submission: December 15, 2020)

PerCom'21 Demos
The PerCom Demo session provides a venue for the latest breakthroughs in 
pervasive computing to be presented live to the research community. Demos 
ranging from examples of working prototypes, novel applications, groundbreaking 
ideas, and live experiments related to PerCom are all welcome. In particular, 
we encourage demos from industrial researchers who are leading the way in 
pushing pervasive technology into the hands of the public. A "Best Demo Award" 
will be presented based on research value, originality, and presentation. 
(Paper submission: December 5, 2020)

PerCom'21 PhD Forum
The PerCom PhD Forum provides an excellent opportunity for Ph.D. students to 
present their dissertation research, including work in progress, to the 

Re: [Tinyos-help] Tinyos-help Digest, Vol 202, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Thursday, October 1, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 202, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021: Call For Papers - Extended Deadlines
  (Elisabetta Biondi)


--

Message: 1
Date: Thu, 01 Oct 2020 16:16:26 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021: Call For Papers - Extended
Deadlines
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20201001141626.xbzte%elisabetta.bio...@iit.cnr.it>

==
CALL FOR PAPERS - DEADLINE EXTENSION ANNOUNCEMENT
* Paper registration: October 4, 2020
* Submission: October 10, 2020
**
The 19th International Conference on Pervasive Computing and
Communications (PerCom 2021), March 22-26, 2021
in Kassel, Germany.
http://www.percom.org
**

IEEE PerCom, now in its 19th year, will be held in Kassel, Germany in March
2021. PerCom is the premier annual scholarly venue in pervasive computing and
communications. Pervasive computing has found its way into many commercial
systems due to tremendous advances in a broad spectrum of technologies and
topics such as wireless networking, mobile and distributed computing, sensor
systems, ambient intelligence, and smart devices.


SCOPE

PerCom 2021 solicits research contributions in all areas pertinent to
pervasive computing and communications, especially those that cross
traditional research boundaries. In particular, we target:
  * Advances in pervasive systems and infrastructures: middleware systems and
services; data engineering for pervasive computing; clouds, fog and edge
computing; integrations of smartphones in pervasive experiences; 
applications
of device-to-device coordination
  * Theories, models, and algorithms: context modeling and reasoning; adaptive
computing; activity and emotion recognition; programming paradigms; applied
machine learning; deep machine learning; federated learning; casual
learning; cognitive computing; complex networks; spatio-temporal modeling
techniques
  * Domain-specific challenges and novel applications: urban/mobile
crowdsensing & intelligence; PerCom for healthcare and well-being;
cyber-physical PerCom; smart homes and virtual assistants; innovative PerCom
applications (e.g., sports analytics, crime prevention, pervasive
nowcasting).
  * Intersections of PerCom with: opportunistic networks; IoT and sensor
systems; RFID systems; pervasive data science, cyber physical systems.
  * New techniques for user-level concerns: participatory and social sensing;
trust, security, and privacy; user interface, interaction, and persuasion;
online and offline social networking and pervasive computing.
  * Technological innovations: architectures, protocols, and technologies for
pervasive communications; energy-harvesting, self-powered, or battery-less
systems; mobile and wearable systems; smart devices and environments;
positioning and tracking technologies; wireless crowd-recharging;
device-free human sensing.

Contributions can be analytical, empirical, technological, methodological, or
a combination. Papers reporting strong systems engineering contributions
backed by solid and appropriate evaluations are strongly encouraged. The
impact of the contributions should be demonstrated in the context of perva

Re: [Tinyos-help] Tinyos-help Digest, Vol 201, Issue 5

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Tuesday, September 29, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 201, Issue 5

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021 Consolidated CALL FOR PAPERS for AFFILIATED
  EVENTS and WORKSHOPS (Elisabetta Biondi)


--

Message: 1
Date: Tue, 29 Sep 2020 09:17:53 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021 Consolidated CALL FOR PAPERS
for AFFILIATED EVENTS and WORKSHOPS
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20200929071753.l0kxy%elisabetta.bio...@iit.cnr.it>
Content-Type: text/plain; charset=us-ascii

===
IEEE PerCom 2021 / CONSOLIDATED CALL FOR PAPERS FOR AFFILIATED EVENTS AND 
WORKSHOPS
March 22-26, 2021 - Kassel, Germany
www.percom.org
===
PerCom is the premier scholarly venue in the areas of pervasive computing and 
communications. Detailed information about the scope of events,  paper 
submission process, etc. can be obtained at http://www.percom.org/ and also at 
the URLs given below.



AFFILIATED EVENTS (www.percom.org)

PerCom'21 Industry Track
This year, PerCom continues the dedicated Industry Track. Accepted papers will 
be published in the PerCom Workshops and other Affiliated Events proceedings. 
This track will be an opportunity for people associated with industry and 
academia to present their novel ideas while attracting funding and/or further 
expanding collaborations. These papers will be presented with focus on research 
that has direct Industry impact and potential for industry uptake. For this 
track, important criteria for papers to be submitted to the Industry Track is 
clear industrial association, either in the form of extensive evaluation of 
research results in industrial use cases or active participation of industry 
representatives as co-authors. Having this condition in mind, contributions 
related to ongoing or finished, but previously unpublished research papers are 
welcomed. Submissions from a broad spectrum of research fields with common 
interest in pervasive computing and communications are expected!
 . There will be a Best Industry Track Paper Award to acknowledge and encourage 
excellence in collaborative industry research. (Paper submission: November 9, 
2020)

PerCom'21 Work in Progress
The Work in Progress (WiP) session provides an opportunity to present and 
discuss new challenges and visions, showcase early research results, and 
explore novel research directions. Papers (4 pages in the IEEE proceedings 
format) are expected to report on early or ongoing research on any aspect of 
pervasive computing and communications. The authors of accepted papers will 
present their work during the main conference and must register for the 
conference. (Paper submission: December 15, 2020)

PerCom'21 Demos
The PerCom Demo session provides a venue for the latest breakthroughs in 
pervasive computing to be presented live to the research community. Demos 
ranging from examples of working prototypes, novel applications, groundbreaking 
ideas, and live experiments related to PerCom are all welcome. In particular, 
we encourage demos from industrial researchers who are leading the way in 
pushing pervasive technology into the hands of the public. A "Best Demo Award" 
will be presented based on research value, originality, and presentation. 
(Paper submission: December 5, 2020

Re: [Tinyos-help] Tinyos-help Digest, Vol 201, Issue 3

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Thursday, September 24, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 201, Issue 3

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021: Call For Papers - Deadline  Approaching
  (Elisabetta Biondi)


--

Message: 1
Date: Thu, 24 Sep 2020 10:05:09 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021: Call For Papers - Deadline
Approaching
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20200924080509.mabl6%elisabetta.bio...@iit.cnr.it>

==
CALL FOR PAPERS
**
The 19th International Conference on Pervasive Computing and
Communications (PerCom 2021), March 22-26, 2021
in Kassel, Germany
http://www.percom.org
**

In 2021, IEEE PerCom will visit Kassel, situated at the geographic center of
Germany and a dynamic industrial and cultural city. It is known for its UNESCO
World Heritage site "Bergpark Wilhemshohe" and famous for a leading exhibition
of contemporary art "documenta".

PerCom is the premier annual scholarly venue in pervasive computing and
communications. Pervasive computing has found its way into many commercial
systems due to tremendous advances in a broad spectrum of technologies and
topics such as wireless networking, mobile and distributed computing, sensor
systems, ambient intelligence, and smart devices.


SCOPE

PerCom 2021 solicits research contributions in all areas pertinent to
pervasive computing and communications, especially those that cross
traditional research boundaries. In particular, we target:
  * Advances in pervasive systems and infrastructures: middleware systems and
services; data engineering for pervasive computing; clouds, fog and edge
computing; integrations of smartphones in pervasive experiences; 
applications
of device-to-device coordination
  * Theories, models, and algorithms: context modeling and reasoning; adaptive
computing; activity and emotion recognition; programming paradigms; applied
machine learning; deep machine learning; federated learning; casual
learning; cognitive computing; complex networks; spatio-temporal modeling
techniques
  * Domain-specific challenges and novel applications: urban/mobile
crowdsensing & intelligence; PerCom for healthcare and well-being;
cyber-physical PerCom; smart homes and virtual assistants; innovative PerCom
applications (e.g., sports analytics, crime prevention, pervasive
nowcasting).
  * Intersections of PerCom with: opportunistic networks; IoT and sensor
systems; RFID systems; pervasive data science, cyber physical systems.
  * New techniques for user-level concerns: participatory and social sensing;
trust, security, and privacy; user interface, interaction, and persuasion;
online and offline social networking and pervasive computing.
  * Technological innovations: architectures, protocols, and technologies for
pervasive communications; energy-harvesting, self-powered, or battery-less
systems; mobile and wearable systems; smart devices and environments;
positioning and tracking technologies; wireless crowd-recharging;
device-free human sensing.

Contributions can be analytical, empirical, technological, methodological, or
a combination. Papers reporting strong systems engineering contributions
backed by solid and appropriate evaluations are strongly encouraged. The
impact of the contributions

Re: [Tinyos-help] Tinyos-help Digest, Vol 201, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Tuesday, September 15, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 201, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021: Call For Papers (Elisabetta Biondi)


--

Message: 1
Date: Tue, 15 Sep 2020 10:05:10 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021: Call For Papers
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20200915080510.kimqy%elisabetta.bio...@iit.cnr.it>

==
CALL FOR PAPERS
**
The 19th International Conference on Pervasive Computing and
Communications (PerCom 2021), March 22-26, 2021
in Kassel, Germany
http://www.percom.org
**

In 2021, IEEE PerCom will visit Kassel, situated at the geographic center of
Germany and a dynamic industrial and cultural city. It is known for its UNESCO
World Heritage site "Bergpark Wilhemshohe" and famous for a leading exhibition
of contemporary art "documenta".

PerCom is the premier annual scholarly venue in pervasive computing and
communications. Pervasive computing has found its way into many commercial
systems due to tremendous advances in a broad spectrum of technologies and
topics such as wireless networking, mobile and distributed computing, sensor
systems, ambient intelligence, and smart devices.


SCOPE

PerCom 2021 solicits research contributions in all areas pertinent to
pervasive computing and communications, especially those that cross
traditional research boundaries. In particular, we target:
  * Advances in pervasive systems and infrastructures: middleware systems and
services; data engineering for pervasive computing; clouds, fog and edge
computing; integrations of smartphones in pervasive experiences; 
applications
of device-to-device coordination
  * Theories, models, and algorithms: context modeling and reasoning; adaptive
computing; activity and emotion recognition; programming paradigms; applied
machine learning; deep machine learning; federated learning; casual
learning; cognitive computing; complex networks; spatio-temporal modeling
techniques
  * Domain-specific challenges and novel applications: urban/mobile
crowdsensing & intelligence; PerCom for healthcare and well-being;
cyber-physical PerCom; smart homes and virtual assistants; innovative PerCom
applications (e.g., sports analytics, crime prevention, pervasive
nowcasting).
  * Intersections of PerCom with: opportunistic networks; IoT and sensor
systems; RFID systems; pervasive data science, cyber physical systems.
  * New techniques for user-level concerns: participatory and social sensing;
trust, security, and privacy; user interface, interaction, and persuasion;
online and offline social networking and pervasive computing.
  * Technological innovations: architectures, protocols, and technologies for
pervasive communications; energy-harvesting, self-powered, or battery-less
systems; mobile and wearable systems; smart devices and environments;
positioning and tracking technologies; wireless crowd-recharging;
device-free human sensing.

Contributions can be analytical, empirical, technological, methodological, or
a combination. Papers reporting strong systems engineering contributions
backed by solid and appropriate evaluations are strongly encouraged. The
impact of the contributions should be demonstrated in the context of pervasive
computing and 

Re: [Tinyos-help] Tinyos-help Digest, Vol 200, Issue 1

[BBMcoll]

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the 
next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710.
Thank you for contacting BBM -Bell Business Markets Collections
++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des 
prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710.
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: tinyos-help-requ...@millennium.berkeley.edu
Sent: Wednesday, August 19, 2020 03:00 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [EXT]Tinyos-help Digest, Vol 200, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. IEEE PerCom 2021: Call For Papers (Elisabetta Biondi)


--

Message: 1
Date: Tue, 18 Aug 2020 09:05:10 +0200
From: Elisabetta Biondi 
Subject: [Tinyos-help] IEEE PerCom 2021: Call For Papers
To: tinyos-help@millennium.berkeley.edu
Message-ID: <20200818070510.-eghw%elisabetta.bio...@iit.cnr.it>

==
CALL FOR PAPERS
**
The 19th International Conference on Pervasive Computing and
Communications (PerCom 2021), March 22-26, 2021
in Kassel, Germany
http://www.percom.org
**

In 2021, IEEE PerCom will visit Kassel, situated at the geographic center of
Germany and a dynamic industrial and cultural city. It is known for its UNESCO
World Heritage site "Bergpark Wilhemshohe" and famous for a leading exhibition
of contemporary art "documenta".

PerCom is the premier annual scholarly venue in pervasive computing and
communications. Pervasive computing has found its way into many commercial
systems due to tremendous advances in a broad spectrum of technologies and
topics such as wireless networking, mobile and distributed computing, sensor
systems, ambient intelligence, and smart devices.


SCOPE

PerCom 2021 solicits research contributions in all areas pertinent to
pervasive computing and communications, especially those that cross
traditional research boundaries. In particular, we target:
  * Advances in pervasive systems and infrastructures: middleware systems and
services; data engineering for pervasive computing; clouds, fog and edge
computing; integrations of smartphones in pervasive experiences; 
applications
of device-to-device coordination
  * Theories, models, and algorithms: context modeling and reasoning; adaptive
computing; activity and emotion recognition; programming paradigms; applied
machine learning; deep machine learning; federated learning; casual
learning; cognitive computing; complex networks; spatio-temporal modeling
techniques
  * Domain-specific challenges and novel applications: urban/mobile
crowdsensing & intelligence; PerCom for healthcare and well-being;
cyber-physical PerCom; smart homes and virtual assistants; innovative PerCom
applications (e.g., sports analytics, crime prevention, pervasive
nowcasting).
  * Intersections of PerCom with: opportunistic networks; IoT and sensor
systems; RFID systems; pervasive data science, cyber physical systems.
  * New techniques for user-level concerns: participatory and social sensing;
trust, security, and privacy; user interface, interaction, and persuasion;
online and offline social networking and pervasive computing.
  * Technological innovations: architectures, protocols, and technologies for
pervasive communications; energy-harvesting, self-powered, or battery-less
systems; mobile and wearable systems; smart devices and environments;
positioning and tracking technologies; wireless crowd-recharging;
device-free human sensing.

Contributions can be analytical, empirical, technological, methodological, or
a combination. Papers reporting strong systems engineering contributions
backed by solid and appropriate evaluations are strongly encouraged. The
impact of the contributions should be demonstrated in the context of pervasive
computing and c

Re: [Tinyos-help] Tinyos-help Digest, Vol 188, Issue 1

[mon vikanth]

Respected TinyOS Teams,

Please cancel the newsletter from the following address


   1. *vikanth1...@gmail.co m*

Thank a lot.

Best Regards,
Mon.

On Fri, May 17, 2019 at 12:36 AM <
tinyos-help-requ...@millennium.berkeley.edu> wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. Cfp: Special Section: Advances in Intelligent Transportation
>   Systems in Smart Cities (Rodolfo I. Meneguette)
>
>
> --
>
> Message: 1
> Date: Thu, 16 May 2019 19:33:47 -0300 (BRT)
> From: "Rodolfo I. Meneguette" 
> Subject: [Tinyos-help] Cfp: Special Section: Advances in Intelligent
> Transportation Systems in Smart Cities
> To: Tinyos-help@millennium.berkeley.edu
> Message-ID:
> <2008584627.71066758.1558046027539.javamail.zim...@ifsp.edu.br>
> Content-Type: text/plain; charset="utf-8"
>
>
>
> Special Section: Advances in Intelligent Transportation Systems in Smart
> Cities
>
>
>
>
> International Journal of Distributed Sensor Network
>
> 2017 Impact Factor : 1.787
>
>
>
> Deadline for manuscript submissions: June 30, 2019
>
>
>
> Intelligent Transport Systems (ITS) comprise the union of several
> technologies with the aim of providing comprehensive optimization of the
> urban mobility of a city and bringing greater safety to drivers, as well as
> comfort and entertainment for passengers. As a result, ITS employ data,
> communication, and computing to provide services and applications for
> tackling and possibly solving a wide range of transportation problems in
> modern large cities. These applications rely on the collaboration between
> elements that integrate urban and transportation systems, such as sensors,
> mobile devices, and vehicles, for introducing real-time awareness of the
> environment. The appropriate junction of all these factors considerably
> contributes to the sensing and gathering of data for evaluation and later
> implementation of due responses by a control system.
>
>
>
>
> Due to the dynamic nature of entities in ITS, it offers a diverse set of
> challenges including, but not limited to, interoperability, high mobility,
> decentralization, anonymity, security, privacy, trust management,
> uncertainty, and pervasiveness. Besides these challenges, several issues
> like scalability, reliability, adaptability, and validity of available
> solutions are still unexplored.
>
>
>
>
> This Special Collection is expected to provide a platform for academics
> and industrial researchers to identify and debate technical problems and
> recent accomplishments associated with ITS. Specific topics include, but
> are not limited to:
>
>
>
>
> * Architecture, resource management and applications
>
> * Leveraging Fog Computing (Edge Computing)
>
> * Design challenges for protocol development in ITS
>
> * ITS security and privacy
>
> * Smart-cities-based Machine Learning;
>
> * Intelligent data mining and forecasting;
>
> * Multi-agent systems applications;
>
> * Inteligent structural engineering;
>
> * Computer graphics and performability;
>
> * Blockchain and remote sensing;
>
> * Ubiquitous computing;
>
> * Fuzzy logic and emerging applications in smart IoT/Cloud paradigms;
>
> * Designing energy efficient Road Side Units (RSUs)
>
> * Quality of Service (QoS) in ITS
>
> * Smart and connected vehicles: V2V; V2I V2X
>
> * Cloud based VANETs
>
> * Vehicular Cloud
>
> * Demand responsive smart vehicles
>
> * Detection, recognition, and classification of traffic
>
> * Vehicle location and event prediction
>
> * Autonomous vehicle technologies
>
> * Context-aware computing and Internet of Things Services in ITS
>
> * Artificial intelligent in ITS
>
> * Protocols and infrastructure and standards for ITS
>
>
>
> Guest Editors:
>
> Rodolfo Ipolito Meneguette, Federal Institute of S?o Paulo, Brazi,
>
> Luis Hideo Vasconcelos Nakamura, Federal Institute of S?o Paulo, Brazil
>
> Thiago Augusto Lopes Genez, University of Bern, Switzerland
>
> Stephan Reiff-Marganiec, University of Leicester, UK
>
>
>
>
> Manuscript Preparation and Submission
>
> Follow the guidelines in the International Journal of Distributed Sensor
> Networks https://us.sagepub.com/en-us/sam/manuscript-submission-guidelines
> . Please submit your manuscript in electronic form through Manuscript
> Central web site: https://mc.manuscriptcentral.com/tii .
>
> Submissions to this Special Section must represent original material that
> 

[Tinyos-help] TinyOS and nesC support for coding application programs.

[anita patil]

Can TinyOS and nesC support  the concepts

   - Inline Functions
   - Virtual and pure virtual functions
   - Constructors
   - Memory management technique - Segmentation

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

Re: [Tinyos-help] TinyOS website

[Mustafa Yassin]

Thank you very much, now it’s working.

It was down for me for a long time.

 

Regards,

Mustafa Yassin

 

From: Eric Decker [mailto:cire...@gmail.com] 
Sent: Wednesday, June 28, 2017 1:09 PM
To: Mustafa Yassin 
Cc: Tinyos-Help 
Subject: Re: [Tinyos-help] TinyOS website

 

works for me.

 

hasn't been updated in 4 years.

 

 

On Mon, Jun 26, 2017 at 5:49 PM, Mustafa Yassin mailto:yassin.m...@m.titech.ac.jp> > wrote:

Hello TinyOS developers,

 

My name is Mustafa Yassin. I’m a Master’s degree student at Tokyo Institute of 
Technology.

I’m doing research about developing a low power TinyOS platform.

The website www.tinyos.net <http://www.tinyos.net>  is down for the last 
period. 

I would appreciate if someone can bring it back.

 

 

* * * *
東京工業大学 理工学研究科
通信情報工学専攻　一色研究室

Tokyo Institute of Technologies

Communications and Computer Engineering

Isshiki lab
ムスタファ.ヤスイーン（Mustafa Yassin）
Email: must...@vlsi.ict.e.titech.ac.jp <mailto:must...@vlsi.ict.e.titech.ac.jp> 

* * * *

 


___
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 website

[Eric Decker]

works for me.

hasn't been updated in 4 years.


On Mon, Jun 26, 2017 at 5:49 PM, Mustafa Yassin 
wrote:

> Hello TinyOS developers,
>
>
>
> My name is Mustafa Yassin. I’m a Master’s degree student at Tokyo
> Institute of Technology.
>
> I’m doing research about developing a low power TinyOS platform.
>
> The website www.tinyos.net is down for the last period.
>
> I would appreciate if someone can bring it back.
>
>
>
>
>
> * * * *
> 東京工業大学 理工学研究科
> 通信情報工学専攻 一色研究室
>
> Tokyo Institute of Technologies
>
> Communications and Computer Engineering
>
> Isshiki lab
> ムスタファ.ヤスイーン（Mustafa Yassin）
> Email: must...@vlsi.ict.e.titech.ac.jp
>
> * * * *
>
>
>
> ___
> 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] TinyOS website

[Mustafa Yassin]

Hello TinyOS developers,



My name is Mustafa Yassin. I’m a Master’s degree student at Tokyo
Institute of Technology.

I’m doing research about developing a low power TinyOS platform.

The website www.tinyos.net   is down for the last
period.

I would appreciate if someone can bring it back.





* * * *
東京工業大学 理工学研究科
通信情報工学専攻　一色研究室

Tokyo Institute of Technologies

Communications and Computer Engineering

Isshiki lab
ムスタファ.ヤスイーン（Mustafa Yassin）
Email: must...@vlsi.ict.e.titech.ac.jp

* * * *



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

Re: [Tinyos-help] TinyOS with TOSSIM

[arsaraiva]

Thanks to Matthew Bradbury that with just one line altered in the file
sim.extra, solved my problem and some more people.

Thank you Matthew.

So that you still have the same problem, just change the line:

PYTHON_VERSION ?= $(shell python --version 2>&1 | sed 's/Python
2\.\([0-9]\)\.[0-9]+\{0,1\}/2.\1/')

by

PYTHON_VERSION ?= $(shell python --version 2>&1 | sed 's/Python
\([0-9]\)\.\([0-9]\)\.[0-9]+\{0,1\}.*/\1.\2/')



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048p25054.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

Re: [Tinyos-help] TinyOS with TOSSIM

[James Allen (PGR)]

Are you using the stable 2.1.2 release from 
https://github.com/tinyos/tinyos-release or the latest code from the main trunk 
https://github.com/tinyos/tinyos-main?


If you're using the release version, might be worth checking your PYTHONPATH 
environment variable is set correctly:


printenv PYTHONPATH


it should be:


$PYTHONPATH:$TOSROOT/support/sdk/python:$PYTHONPATH


If you're using the latest code from the main trunk, I'm not sure what to 
suggest because there's a completely new build system which I haven't studied 
(see the readme text on the tinyos-main GitHub page) which doesn't rely on 
environment variables.


PS If you're interested, I've just written an install guide for configuring a 
TinyOS dev virtual machine on Ubuntu using Vagrant - might give you some ideas:


https://www.linkedin.com/pulse/installing-tinyos-ubuntu-using-vagrant-james-allen


From: tinyos-help-boun...@millennium.berkeley.edu 
 on behalf of arsaraiva 

Sent: 17 January 2017 09:05:15
To: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] TinyOS with TOSSIM

Hello Eric,

I'm using TinyOS 2.1.2, openjdk version 1.8.0_111 and Python 2.7.12 on
Ubuntu 16.04 x64.

If you know a more stable previous version, please tell me, because I am new
to TinyOS and I do not know your options well.

I believe the problem may be in the Python variable that is not being found,
for the first lines of the output are:
@note: ~ / tinyos-main / apps / Blink $ make micaz yes
Mkdir -p simbuild / micaz
Make: python2.72-config: Command not found
Make: python2.72-config: Command not found
Make: python2.72-config: Command not found

But following the TOSSIM appendix A, it did not work.



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048p25052.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] TinyOS with TOSSIM

[arsaraiva]

Hello Eric, 

I'm using TinyOS 2.1.2, openjdk version 1.8.0_111 and Python 2.7.12 on
Ubuntu 16.04 x64.

If you know a more stable previous version, please tell me, because I am new
to TinyOS and I do not know your options well.

I believe the problem may be in the Python variable that is not being found,
for the first lines of the output are:
@note: ~ / tinyos-main / apps / Blink $ make micaz yes
Mkdir -p simbuild / micaz
Make: python2.72-config: Command not found
Make: python2.72-config: Command not found
Make: python2.72-config: Command not found

But following the TOSSIM appendix A, it did not work.



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048p25052.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

Re: [Tinyos-help] TinyOS with TOSSIM

[Eric Decker]

which tinyos sources are you using?

that looks familar, i may have fixed it already on the dev trunk


On Mon, Jan 16, 2017 at 9:28 AM, arsaraiva  wrote:

> Hi James,
>
> This error occurs with micaz too.
>
> @note:~/tinyos-main/apps/Blink$ make micaz sim
> mkdir -p simbuild/micaz
> make: python2.72-config: Comando não encontrado
> make: python2.72-config: Comando não encontrado
> make: python2.72-config: Comando não encontrado
>   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 --param max-inline-insns-single=10
> -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"andre\"
> -DIDENT_HOSTNAME=\"note\" -DIDENT_USERHASH=0xb00a83f3L
> -DIDENT_TIMESTAMP=0x587d14ecL -DIDENT_UIDHASH=0xa32ed3f5L
> -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
> /home/andre/tinyos-main/tos/lib/tossim/sim_noise.c: In function
> ‘sim_noise_gen’:
> /home/andre/tinyos-main/tos/lib/tossim/sim_noise.c:291:7: warning:
> variable
> ‘noiseIndex’ set but not used [-Wunused-but-set-variable]
>int noiseIndex = 0;
>^
> /home/andre/tinyos-main/tos/lib/tossim/SimMoteP.nc: At top level:
> /home/andre/tinyos-main/tos/chips/atm128/sim/atm128hardware.h:101:3:
> warning: ‘__nesc_disable_interrupt’ is static but used in inline function
> ‘__nesc_atomic_start’ which is not static
>  __nesc_disable_interrupt();
>^
>   compiling Python support and C libraries into pytossim.o, tossim.o, and
> c-support.o
> g++ -c  -shared -fPIC -o simbuild/micaz/pytossim.o -g -O0
> -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"andre\"
> -DIDENT_HOSTNAME=\"note\" -DIDENT_USERHASH=0xb00a83f3L
> -DIDENT_TIMESTAMP=0x587d14ecL -DIDENT_UIDHASH=0xa32ed3f5L
> /home/andre/tinyos-main/tos/lib/tossim/tossim_wrap.cxx
> -I/include/python2.72
> -I/home/andre/tinyos-main/tos/lib/tossim -DHAVE_CONFIG_H
> /home/andre/tinyos-main/tos/lib/tossim/tossim_wrap.cxx:139:20: fatal
> error:
> Python.h: Arquivo ou diretório não encontrado
> compilation terminated.
> */home/andre/tinyos-main/support/make/sim.extra:66: recipe for target
> 'sim-exe' failed
> make: *** [sim-exe] Error 1*
>
> please if you know how to help me thank you.
> I have to create a small topology with 3 sensors in TOSSIM, a sink and two
> nodes in a row, but I am new to simulators and I could not even start
> TOSSIM, as I do not know how to start this work.
>
> Thank you very much in advance
>
>
>
> --
> View this message in context: http://tinyos-help.10906.n7.
> nabble.com/TinyOS-with-TOSSIM-tp25048p25050.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




-- 
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 with TOSSIM

[arsaraiva]

Hi James,

This error occurs with micaz too.

@note:~/tinyos-main/apps/Blink$ make micaz sim
mkdir -p simbuild/micaz
make: python2.72-config: Comando não encontrado
make: python2.72-config: Comando não encontrado
make: python2.72-config: Comando não encontrado
  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 --param max-inline-insns-single=10
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"andre\"
-DIDENT_HOSTNAME=\"note\" -DIDENT_USERHASH=0xb00a83f3L
-DIDENT_TIMESTAMP=0x587d14ecL -DIDENT_UIDHASH=0xa32ed3f5L
-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
/home/andre/tinyos-main/tos/lib/tossim/sim_noise.c: In function
‘sim_noise_gen’:
/home/andre/tinyos-main/tos/lib/tossim/sim_noise.c:291:7: warning: variable
‘noiseIndex’ set but not used [-Wunused-but-set-variable]
   int noiseIndex = 0;
   ^
/home/andre/tinyos-main/tos/lib/tossim/SimMoteP.nc: At top level:
/home/andre/tinyos-main/tos/chips/atm128/sim/atm128hardware.h:101:3:
warning: ‘__nesc_disable_interrupt’ is static but used in inline function
‘__nesc_atomic_start’ which is not static
 __nesc_disable_interrupt();
   ^
  compiling Python support and C libraries into pytossim.o, tossim.o, and
c-support.o
g++ -c  -shared -fPIC -o simbuild/micaz/pytossim.o -g -O0
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"andre\"
-DIDENT_HOSTNAME=\"note\" -DIDENT_USERHASH=0xb00a83f3L
-DIDENT_TIMESTAMP=0x587d14ecL -DIDENT_UIDHASH=0xa32ed3f5L
/home/andre/tinyos-main/tos/lib/tossim/tossim_wrap.cxx -I/include/python2.72
-I/home/andre/tinyos-main/tos/lib/tossim -DHAVE_CONFIG_H 
/home/andre/tinyos-main/tos/lib/tossim/tossim_wrap.cxx:139:20: fatal error:
Python.h: Arquivo ou diretório não encontrado
compilation terminated.
*/home/andre/tinyos-main/support/make/sim.extra:66: recipe for target
'sim-exe' failed
make: *** [sim-exe] Error 1*

please if you know how to help me thank you.
I have to create a small topology with 3 sensors in TOSSIM, a sink and two
nodes in a row, but I am new to simulators and I could not even start
TOSSIM, as I do not know how to start this work.

Thank you very much in advance



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048p25050.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

Re: [Tinyos-help] TinyOS with TOSSIM

[James Allen (PGR)]

Hi André,


The key part of your output is "Unknown target telosb". If you check out the 
TOSSIM documentation on the TinyOS wiki you'll see that "Currently, micaz is 
the only platform supported by TOSSIM":


http://tinyos.stanford.edu/tinyos-wiki/index.php/TOSSIM


There is a contrib project which extends powerTOSSIM (an extension to TOSSIM 
for energy simulation) for TelosB which you might find useful:


https://github.com/tyll/tinyos-2.x-contrib/tree/master/unlpt/PowerTossim-TelosB


Regards


James


From: tinyos-help-boun...@millennium.berkeley.edu 
 on behalf of arsaraiva 

Sent: 13 January 2017 17:42:50
To: tinyos-help@millennium.berkeley.edu
Subject: [NOTSPAM?] [Tinyos-help] TinyOS with TOSSIM

Hello dear

I have TinyOS 2.1.2 installed on Ubuntu 16.04 correctly. Even when I run $
make telosb it does not return any errors.

But when I try to use the TOSSIM simulator, through $ make telosb, there are
several errors, as follows below the terminal:

$ make telosb sim
mkdir -p simbuild/telosb
make: python2.71+-config: Comando não encontrado
make: python2.71+-config: Comando não encontrado
make: python2.71+-config: Comando não encontrado
  placing object files in simbuild/telosb
  writing XML schema to app.xml
  compiling BlinkAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/telosb/sim.o -g -O0 -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate
-fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all
-target=telosb -fnesc-cfile=simbuild/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"andre\" -DIDENT_HOSTNAME=\"ars\"
-DIDENT_USERHASH=0x7b8ee136L -DIDENT_TIMESTAMP=0x5874b542L
-DIDENT_UIDHASH=0x74578f5bL -Wno-nesc-data-race BlinkAppC.nc
-fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants
-fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags
-fnesc-dumpfile=app.xml
Unknown target telosb
Known targets for TinyOS directory /home/andre/tinyos-main/tos
and the specified include directories are:
  eyesIFXv1 eyesIFXv2 shimmer2 ucmini sam3s_ek micaz mica2 telosa sam3u_ek
shimmer2r telosb iris z1 span null tinynode intelmote2 btnode3 shimmer epic
mica2dot mulle
/home/andre/tinyos-main/support/make/sim.extra:66: recipe for target
'sim-exe' failed
make: *** [sim-exe] Error 2

This is exactly the exit from the terminal. I do not know exactly what is
missing from the system or what to do. Can someone help me.

Thanks in advance.

André

PS: forgive the translation of google translator, but I'm Brazilian and I'm
not an expert in English.



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048.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

[Tinyos-help] TinyOS with TOSSIM

[arsaraiva]

Hello dear 

I have TinyOS 2.1.2 installed on Ubuntu 16.04 correctly. Even when I run $
make telosb it does not return any errors. 

But when I try to use the TOSSIM simulator, through $ make telosb, there are
several errors, as follows below the terminal: 

$ make telosb sim 
mkdir -p simbuild/telosb 
make: python2.71+-config: Comando não encontrado 
make: python2.71+-config: Comando não encontrado 
make: python2.71+-config: Comando não encontrado 
  placing object files in simbuild/telosb 
  writing XML schema to app.xml 
  compiling BlinkAppC to object file sim.o 
ncc -c -shared -fPIC -o simbuild/telosb/sim.o -g -O0 -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate
-fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all
-target=telosb -fnesc-cfile=simbuild/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
-DIDENT_USERNAME=\"andre\" -DIDENT_HOSTNAME=\"ars\"
-DIDENT_USERHASH=0x7b8ee136L -DIDENT_TIMESTAMP=0x5874b542L
-DIDENT_UIDHASH=0x74578f5bL -Wno-nesc-data-race BlinkAppC.nc  
-fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants
-fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags
-fnesc-dumpfile=app.xml 
Unknown target telosb 
Known targets for TinyOS directory /home/andre/tinyos-main/tos 
and the specified include directories are: 
  eyesIFXv1 eyesIFXv2 shimmer2 ucmini sam3s_ek micaz mica2 telosa sam3u_ek
shimmer2r telosb iris z1 span null tinynode intelmote2 btnode3 shimmer epic
mica2dot mulle 
/home/andre/tinyos-main/support/make/sim.extra:66: recipe for target
'sim-exe' failed 
make: *** [sim-exe] Error 2

This is exactly the exit from the terminal. I do not know exactly what is
missing from the system or what to do. Can someone help me. 

Thanks in advance. 

André 

PS: forgive the translation of google translator, but I'm Brazilian and I'm
not an expert in English.



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-with-TOSSIM-tp25048.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] Tinyos-help@millennium.berkeley.edu

[RODOLFO IPOLITO MENEGUETTE]

=== 
Call-For-Papers: 
13th DCOSS 2017 
Ottawa, Canada, June 5 - 7, 2017 
http://www.dcoss.org/ 
 
IMPORTANT: 
Paper Submission (Extended): January 20th, 2017 
=== 

-- 

DCOSS 2017 is the 13th International Conference on Distributed Computing in 
Sensor Systems to be hosted in Ottawa, Canada in June 5-7, 2017. Due to their 
potential of impacting an entire host of application areas, distributed sensor 
systems have become a highly visible research area. The focus of DCOSS series 
of conferences is on distributed computing issues in large scale networked 
sensor systems, including, but not limited to, algorithms and applications, 
systems design techniques and tools, and in-network signal and information 
processing. DCOSS puts together a highly selective program where it primes for 
quality and innovation on works. 

Potential authors are invited to submit original unpublished manuscripts that 
demonstrate current research on computational aspects of distributed sensor 
systems. Topics of interest include but are not limited to: 

Social networks and applications 
Sensors for smart grid systems, green networks and sustainability 
Computation and programming models 
Energy models, minimization, awareness 
Distributed collaborative information processing 
Detection and tracking 
Theoretical performance analysis: complexity, correctness, scalability 
Abstractions for modular design 
Fault tolerance and security 
Task allocation, reprogramming and reconfiguration 
Dynamic resource management 
Scalable, heterogeneous architectures (node and system-level) 
Middleware interfaces, communication and processing primitives 
Design, simulation and optimization tools for deployment and operation 
Design automation and application synthesis techniques 
Closed-loop control for sensing and actuation 
Case studies: lessons from real world deployments 
Network coding and compression 


Paper Submission and Publication: 

High-quality original papers are solicited. Papers must be unpublished and must 
not be submitted for publication elsewhere. All papers will be reviewed by 
Technical Program Committee members and other experts active in the field to 
ensure high quality and relevance to the conference. 

Please submit your paper through EDAS link ( https://edas.info/N23046 ). More 
detailed instructions about paper submissions can be fount at the link below. 
- http://www.dcoss.org/ 


Important Dates: 

Paper Submission Deadline (Extended): 20th January, 2017 


Organizing Committee: 

GENERAL CHAIR 
Azzedine Boukerche, University of Ottawa, Canada 

PROGRAM CO-CHAIRS 
Salil Kanhere, University of New South Wales, Australia 
Soumaya Charkaoui, University of Sherbrooke, Canada 
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Tinyos-2.1.2 GUI problem

[NANDINI S]

Hi all,

  I Have successfully installed tinyos-2.1.2 on ubuntu 12. The problem is
how to make use of GUI.

Please help me for this issue

Thanks in advance






With Regards,
Nandini S.
Teaching Assistant
Department of Computer Science and Engg.
Acharya Institute of Technology
Bangalore-90
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Tinyos-2.1.2 avr package error

[Selahattin KOŞUNALP]

Hi all,


I have successfully installed the required rpm files for Tinyos-2.1.2 from 
http://tinyos.stanford.edu/tinyos/dists/cygwin/avr-beta/ and set the 
environment variables as requested. I had no problem until making the blink 
application. When I build blink application, I am getting the following error:


pc@DESKTOP-9E33J9E /opt/tinyos-2.1.2/apps/blink

$ make micaz

mkdir -p build/micaz

compiling BlinkAppC to a micaz binary

ncc -o build/micaz/main.exe  -Os -fnesc-separator=__ -Wall -Wshadow -Wnesc-all 
-target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb 
-DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=10 -DIDENT_APPNAME=\"BlinkAppC\" 
-DIDENT_USERNAME=\"pc\" -DIDENT_HOSTNAME=\"DESKTOP-9E33J9E\" 
-DIDENT_USERHASH=0xf280260eL -DIDENT_TIMESTAMP=0x57f7501fL 
-DIDENT_UIDHASH=0x21a51a3aL -fnesc-dump=wiring 
-fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, 
components)' -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm

make: *** [/opt/tinyos-2.1.2/support/make/avr/avr.rules:149: exe0] Error 127


Can anyone help me for this issue?


Thanks,



Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu 
e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde 
kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini 
kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. 
Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, 
yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi 
anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta 
mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus 
icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir 
sorumlulugu kabul etmez. ESET Mail Security Anti-spam tarafından kontrol 
edilmiştir.
This message is intended solely for the use of the individual or entity to whom 
it is addressed , and may contain confidential information. If you are not the 
intended recipient of this message or you receive this mail in error, you 
should refrain from making any use of the contents and from opening any 
attachment. In that case, please notify the sender immediately and return the 
message to the sender, then, delete and destroy all copies. This e-mail 
message, can not be copied, published or sold for any reason. This e-mail 
message has been swept by anti-virus systems for the presence of computer 
viruses. In doing so, however, sender cannot warrant that virus or other forms 
of data corruption may not be present and do not take any responsibility in any 
occurrence.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS installation on cygwin

[Eric Decker]

First, it would be helpful if you included the URL for the page you are
looking for.

support for the msp430 on Cygwin is no longer actively supported.

Active support for the msp430 can be found at
http://tinyprod.net/repos/debian/

But that is only supported on Debian based Linux boxes (Debian/Ubuntu etc.)



On Sat, Aug 27, 2016 at 11:09 AM, priya deep 
wrote:

> Hello
>
> I am trying in install packages for msp430 and I am unable to find because
> of the Page not found error. Kindly let me know the link from where can all
> the rpm packages be found.
>
>
> Thank you
> Priyadeep
>
>
> ___
> 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] TinyOS installation on cygwin

[priya deep]

Hello
I am trying in install packages for msp430 and I am unable to find because of 
the Page not found error. Kindly let me know the link from where can all the 
rpm packages be found. 

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 159, Issue 3

[achmad ariansyah]

 how i can leave from this group?thx 

On Thursday, July 14, 2016 3:03 AM, 
"tinyos-help-requ...@millennium.berkeley.edu" 
 wrote:
 

 Send Tinyos-help mailing list submissions to
    tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
    tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
    tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

  1. Re: Tinyos-help Digest, Vol 159, Issue 1 (V?tor Biajo)


--

Message: 1
Date: Wed, 13 Jul 2016 12:12:02 -0300
From: V?tor Biajo 
Subject: Re: [Tinyos-help] Tinyos-help Digest, Vol 159, Issue 1
To: Asim Maiti 
Cc: tinyos-help@millennium.berkeley.edu
Message-ID:
    
Content-Type: text/plain; charset="utf-8"

Hi Asim,

Understood! I guess its the same thing exporting the motecom and typing
-comm serial@/dev/ttyS0:micaz. And when I do that, I get the following
error:

serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not open
/dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
find the specified path.in NativeSerialPort.CreateFile)

As I posted previously.

Thank you,
Vitor Biajo



2016-07-13 2:55 GMT-03:00 Asim Maiti :

> Hi  Vitor H. M. Biajo,
>
> You should export motecom environment variable like...
>
> export MOTECOM=serial@COM1:19200 # mica baud rate
> export MOTECOM=serial@COM1:mica  # mica baud rate, again
>
> Also, you should read
> Mote-PC serial communication and SerialForwarder (TOS 2.1.1 and later)
>
> from tutorial.
> Most probably it solved your problem.
> Thanking you
> Asim
>
>
>
> On Wed, Jul 13, 2016 at 12:30 AM, <
> tinyos-help-requ...@millennium.berkeley.edu> wrote:
>
>> Send Tinyos-help mailing list submissions to
>>        tinyos-help@millennium.berkeley.edu
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> or, via email, send a message with subject or body 'help' to
>>        tinyos-help-requ...@millennium.berkeley.edu
>>
>> You can reach the person managing the list at
>>        tinyos-help-ow...@millennium.berkeley.edu
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Tinyos-help digest..."
>>
>>
>> Today's Topics:
>>
>>    1. [HELP] Reading Serial Data from Serial Port error3        TOSComm
>>      Jni (vbiajo)
>>
>>
>> --
>>
>> Message: 1
>> Date: Tue, 12 Jul 2016 08:47:58 -0700 (MST)
>> From: vbiajo 
>> Subject: [Tinyos-help] [HELP] Reading Serial Data from Serial Port
>>        error3  TOSComm Jni
>> To: tinyos-help@millennium.berkeley.edu
>> Message-ID: <1468338478643-24980.p...@n7.nabble.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi guys!
>>
>> I am using Windows + Cygwin + mib510 and micaz motes and I?m having some
>> problems to read data from serial port.
>>
>> I?ve tested the serial communication with Realterm (a serial terminal for
>> windows) and checked the output with the standard outputs given by the 4th
>> lesson of the tutorial and it was okay. So I think that the problem isn?t
>> the cable or any other hardware part.
>>
>> But, when I try to run the Java tools for reading data from serial, I dont
>> have success. When I execute the commands
>>
>>                $ java RssiDemo
>>                $ java net.tinyos.tools.Listen
>>
>> I get the error:
>>
>> sf@localhost:9002 died - exiting (java.net.ConnectException: Connection
>> refused: connect)
>>
>>
>> And with these commands:
>>
>> $ java RssiDemo -comm serial@/dev/ttyS0:micaz
>>                $ java net.tinyos.tools.Listen -comm serial@
>> /dev/ttyS0:micaz
>>
>> I get the error:
>>
>> serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not
>> open
>> /dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
>> find the specified path.in NativeSerialPort.CreateFile)
>>
>> My java and javac versions are:
>>
>> java version "1.8.0_25"
>>

Re: [Tinyos-help] Tinyos-help Digest, Vol 159, Issue 1

[Vítor Biajo]

Hi Asim,

Understood! I guess its the same thing exporting the motecom and typing
-comm serial@/dev/ttyS0:micaz. And when I do that, I get the following
error:

serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not open
/dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
find the specified path.in NativeSerialPort.CreateFile)

As I posted previously.

Thank you,
Vitor Biajo



2016-07-13 2:55 GMT-03:00 Asim Maiti :

> Hi  Vitor H. M. Biajo,
>
> You should export motecom environment variable like...
>
> export MOTECOM=serial@COM1:19200 # mica baud rate
> export MOTECOM=serial@COM1:mica  # mica baud rate, again
>
> Also, you should read
> Mote-PC serial communication and SerialForwarder (TOS 2.1.1 and later)
>
> from tutorial.
> Most probably it solved your problem.
> Thanking you
> Asim
>
>
>
> On Wed, Jul 13, 2016 at 12:30 AM, <
> tinyos-help-requ...@millennium.berkeley.edu> wrote:
>
>> Send Tinyos-help mailing list submissions to
>> tinyos-help@millennium.berkeley.edu
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> or, via email, send a message with subject or body 'help' to
>> tinyos-help-requ...@millennium.berkeley.edu
>>
>> You can reach the person managing the list at
>> tinyos-help-ow...@millennium.berkeley.edu
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Tinyos-help digest..."
>>
>>
>> Today's Topics:
>>
>>1. [HELP] Reading Serial Data from Serial Port error3TOSComm
>>   Jni (vbiajo)
>>
>>
>> --
>>
>> Message: 1
>> Date: Tue, 12 Jul 2016 08:47:58 -0700 (MST)
>> From: vbiajo 
>> Subject: [Tinyos-help] [HELP] Reading Serial Data from Serial Port
>> error3  TOSComm Jni
>> To: tinyos-help@millennium.berkeley.edu
>> Message-ID: <1468338478643-24980.p...@n7.nabble.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi guys!
>>
>> I am using Windows + Cygwin + mib510 and micaz motes and I?m having some
>> problems to read data from serial port.
>>
>> I?ve tested the serial communication with Realterm (a serial terminal for
>> windows) and checked the output with the standard outputs given by the 4th
>> lesson of the tutorial and it was okay. So I think that the problem isn?t
>> the cable or any other hardware part.
>>
>> But, when I try to run the Java tools for reading data from serial, I dont
>> have success. When I execute the commands
>>
>> $ java RssiDemo
>> $ java net.tinyos.tools.Listen
>>
>> I get the error:
>>
>> sf@localhost:9002 died - exiting (java.net.ConnectException: Connection
>> refused: connect)
>>
>>
>> And with these commands:
>>
>> $ java RssiDemo -comm serial@/dev/ttyS0:micaz
>> $ java net.tinyos.tools.Listen -comm serial@
>> /dev/ttyS0:micaz
>>
>> I get the error:
>>
>> serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not
>> open
>> /dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
>> find the specified path.in NativeSerialPort.CreateFile)
>>
>> My java and javac versions are:
>>
>> java version "1.8.0_25"
>> Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
>> Java HotSpot(TM) Client VM (build 25.25-b02, mixed mode, sharing)
>>
>> javac 1.7.0_72
>>
>> Can anybody help me? I need to run the serial through java for a better
>> comprehension of RSSI application, because I can?t evaluate the data that
>> the Realterm shows me.
>>
>> Thx!
>>
>> V?tor H. M. Biajo
>>
>>
>>
>> --
>> View this message in context:
>> http://tinyos-help.10906.n7.nabble.com/HELP-Reading-Serial-Data-from-Serial-Port-error3-TOSComm-Jni-tp24980.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
>>
>> End of Tinyos-help Digest, Vol 159, Issue 1
>> ***
>>
>
>
>
> --
> Regards :
> Asim Kumar Maiti
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Att.
*Vítor H. M. Biajo*
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 159, Issue 1

[Asim Maiti]

Hi  Vitor H. M. Biajo,

You should export motecom environment variable like...

export MOTECOM=serial@COM1:19200 # mica baud rate
export MOTECOM=serial@COM1:mica  # mica baud rate, again

Also, you should read
Mote-PC serial communication and SerialForwarder (TOS 2.1.1 and later)

from tutorial.
Most probably it solved your problem.
Thanking you
Asim



On Wed, Jul 13, 2016 at 12:30 AM, <
tinyos-help-requ...@millennium.berkeley.edu> wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. [HELP] Reading Serial Data from Serial Port error3TOSComm
>   Jni (vbiajo)
>
>
> --
>
> Message: 1
> Date: Tue, 12 Jul 2016 08:47:58 -0700 (MST)
> From: vbiajo 
> Subject: [Tinyos-help] [HELP] Reading Serial Data from Serial Port
> error3  TOSComm Jni
> To: tinyos-help@millennium.berkeley.edu
> Message-ID: <1468338478643-24980.p...@n7.nabble.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi guys!
>
> I am using Windows + Cygwin + mib510 and micaz motes and I?m having some
> problems to read data from serial port.
>
> I?ve tested the serial communication with Realterm (a serial terminal for
> windows) and checked the output with the standard outputs given by the 4th
> lesson of the tutorial and it was okay. So I think that the problem isn?t
> the cable or any other hardware part.
>
> But, when I try to run the Java tools for reading data from serial, I dont
> have success. When I execute the commands
>
> $ java RssiDemo
> $ java net.tinyos.tools.Listen
>
> I get the error:
>
> sf@localhost:9002 died - exiting (java.net.ConnectException: Connection
> refused: connect)
>
>
> And with these commands:
>
> $ java RssiDemo -comm serial@/dev/ttyS0:micaz
> $ java net.tinyos.tools.Listen -comm serial@
> /dev/ttyS0:micaz
>
> I get the error:
>
> serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not
> open
> /dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
> find the specified path.in NativeSerialPort.CreateFile)
>
> My java and javac versions are:
>
> java version "1.8.0_25"
> Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
> Java HotSpot(TM) Client VM (build 25.25-b02, mixed mode, sharing)
>
> javac 1.7.0_72
>
> Can anybody help me? I need to run the serial through java for a better
> comprehension of RSSI application, because I can?t evaluate the data that
> the Realterm shows me.
>
> Thx!
>
> V?tor H. M. Biajo
>
>
>
> --
> View this message in context:
> http://tinyos-help.10906.n7.nabble.com/HELP-Reading-Serial-Data-from-Serial-Port-error3-TOSComm-Jni-tp24980.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
>
> End of Tinyos-help Digest, Vol 159, Issue 1
> ***
>



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

Re: [Tinyos-help] Tinyos-help Digest, Vol 159, Issue 1

[He Dajiang]

For the first error, as far as I can recall, by default SerialForwarder tries 
to talk to a local TCP server at port 9002, which was not there; so it throws 
error. Maybe there is a way to go without it. I cannot remember how; you can 
check the source code for clues.

The second error sometimes happens in Cygwin; I suggest you can test it in a 
Linux environment.



From: tinyos-help-boun...@millennium.berkeley.edu 
 on behalf of 
tinyos-help-requ...@millennium.berkeley.edu 

Sent: Wednesday, 13 July 2016 3:00 AM
To: tinyos-help@millennium.berkeley.edu
Subject: Tinyos-help Digest, Vol 159, Issue 1

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Tinyos-help Info Page - University of California, 
Berkeley<https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help>
www.millennium.berkeley.edu
To see the collection of prior postings to the list, visit the Tinyos-help 
Archives. Using Tinyos-help: To post a message to all the list members ...




or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. [HELP] Reading Serial Data from Serial Port error3TOSComm
  Jni (vbiajo)


--

Message: 1
Date: Tue, 12 Jul 2016 08:47:58 -0700 (MST)
From: vbiajo 
Subject: [Tinyos-help] [HELP] Reading Serial Data from Serial Port
error3  TOSComm Jni
To: tinyos-help@millennium.berkeley.edu
Message-ID: <1468338478643-24980.p...@n7.nabble.com>
Content-Type: text/plain; charset=UTF-8

Hi guys!

I am using Windows + Cygwin + mib510 and micaz motes and I?m having some
problems to read data from serial port.

I?ve tested the serial communication with Realterm (a serial terminal for
windows) and checked the output with the standard outputs given by the 4th
lesson of the tutorial and it was okay. So I think that the problem isn?t
the cable or any other hardware part.

But, when I try to run the Java tools for reading data from serial, I dont
have success. When I execute the commands

$ java RssiDemo
$ java net.tinyos.tools.Listen

I get the error:

sf@localhost:9002 died - exiting (java.net.ConnectException: Connection
refused: connect)


And with these commands:

$ java RssiDemo -comm serial@/dev/ttyS0:micaz
$ java net.tinyos.tools.Listen -comm serial@/dev/ttyS0:micaz

I get the error:

serial@/dev/ttyS0:57600 died - exiting (java.io.IOException: Could not open
/dev/ttyS0: TOSComm JNI library runtime error: Error 3. The system couldnt
find the specified path.in NativeSerialPort.CreateFile)

My java and javac versions are:

java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) Client VM (build 25.25-b02, mixed mode, sharing)

javac 1.7.0_72

Can anybody help me? I need to run the serial through java for a better
comprehension of RSSI application, because I can?t evaluate the data that
the Realterm shows me.

Thx!

V?tor H. M. Biajo



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/HELP-Reading-Serial-Data-from-Serial-Port-error3-TOSComm-Jni-tp24980.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

End of Tinyos-help Digest, Vol 159, Issue 1
***
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 158, Issue 4

[rupesh vishwakarma]

Tiny OS is no more , use contiki instead tiny OSrupesh09716935137 

On Sunday, 26 June 2016 12:46 AM, 
"tinyos-help-requ...@millennium.berkeley.edu" 
 wrote:
 

 Send Tinyos-help mailing list submissions to
    tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
    tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
    tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

  1. TinyOs Installation (bilal_khan02228)


--

Message: 1
Date: Sat, 25 Jun 2016 04:05:16 -0700 (MST)
From: bilal_khan02228 
Subject: [Tinyos-help] TinyOs Installation
To: tinyos-help@millennium.berkeley.edu
Message-ID: <1466852716562-24978.p...@n7.nabble.com>
Content-Type: text/plain; charset=us-ascii

Hello Sir/Madam,
                    I am working on undergrad project for which i need to
install tinyos. but the the  http://tinyos.net <http://tinyos.net>  is
unreachable. Due to which i fail to download the required rpm files. Kindly
tell me how can i get rpm otherwise. Or if possible kindly do email me on my
email ddp-sp13-bte-...@ciitlahore.edu.pk



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOs-Installation-tp24978.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

End of Tinyos-help Digest, Vol 158, Issue 4
***


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

[Tinyos-help] TinyOs Installation

[bilal_khan02228]

Hello Sir/Madam,
 I am working on undergrad project for which i need to
install tinyos. but the the  http://tinyos.net    is
unreachable. Due to which i fail to download the required rpm files. Kindly
tell me how can i get rpm otherwise. Or if possible kindly do email me on my
email ddp-sp13-bte-...@ciitlahore.edu.pk



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOs-Installation-tp24978.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] Tinyos 2.x get power consumption during application simulating

[M.Farahani, asl]

Hi
I want to impliment new power aware algorithm. I use powerTOSSIM-z and i
khonw that it use a custom interface that only log devices (CPU, Radio,
...) switch on and off. After simulate, (by python MySimulation.py) it
return a file with this name "Energy.txt". you can find device log like
this:

File: Energy.txt
**
DEBUG (0): 23542399,LED_STATE,LED2,ON
DEBUG (0): 23542399,LED_STATE,LED1,ON
DEBUG (0): 23542399,LED_STATE,LED0,ON
DEBUG (0): 23542399,LED_STATE,LED0,OFF
DEBUG (0): 23542399,LED_STATE,LED1,OFF
DEBUG (0): 23542399,LED_STATE,LED2,OFF
DEBUG (0): 23542399,CPU_STATE,CPU_POWER_DOWN
DEBUG (0): 23542399,CPU_STATE,CPU_POWER_DOWN
DEBUG (0): 23542399,RADIO_STATE,ON
DEBUG (0): 23542499,CPU_STATE,CPU_ACTIVE
DEBUG (0): 23542699,CPU_STATE,CPU_POWER_DOWN
DEBUG (1): 25893616,LED_STATE,LED2,ON
DEBUG (1): 25893616,LED_STATE,LED1,ON
.
**

Finally by postprocessZ.py, it can measure power consumption (time, mote
energy model and sum of all).
But my problem is here. I need power consumption in simulation time, not is
post process! I want to use this value for get decision during my new
algorithm!
I will be happy if anyone help me.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos 2.x power consumption

[Antonis Tzounis]

Good morning,

I can't check right now, but I would suggest going for VoltageC and print
the value through dbg or send it as message.

>From what I can see though, in a quick search, this problem has been
reported before here:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2014-October/058682.html

I am not sure if this is true, but you can keep it in mind.

You may also be interested in these articles too:

http://web.stanford.edu/class/cs344a/papers/sensys04ptossim.pdf

http://lens1.csie.ncku.edu.tw/Library/Paper/SenSys/SenSys2003/TOSSIM_%20Accurate%20and%20Scalable%20Simulation%20of%20Entire%20TinyOS%20Applications.pdf


Good luck.

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

[Tinyos-help] Tinyos 2.x power consumption

[M.Farahani, asl]

Hi
I use Tinyos 2.x and powerTOSSIM-z for measure mote power consumption.
How can i get mote remind power during runtime simulation?
I need this value for my algorithm decision!
I will be happy for your replay.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 148, Issue 6

[Niyifasha Robert]

Hello everyone,

I need help from you.

I am doing my project in tinyos-2.1.2. , my aim is to secure
transmission channel in WSN. I will need to do same
encryption,decryption and ECDSA.

It`s my first time to use TinyEEC and TinyOS, i don`t know how i can
start, now i have installed TinyOS-2.1.2 the the problem is the
installation and implementation of TnyECC.

I need your support to solve that problem.

Thanks.


On Mon, Aug 10, 2015 at 3:00 AM, <
tinyos-help-requ...@millennium.berkeley.edu> wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. Re: frequency of a received signal (Nahr Elk)
>
>
> --
>
> Message: 1
> Date: Sun, 9 Aug 2015 16:40:28 +0100
> From: Nahr Elk 
> Subject: Re: [Tinyos-help] frequency of a received signal
> To: Eric Decker 
> Cc: tinyos-help 
> Message-ID:
>  vbual3pckj4mpu7xqufwoyaq...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I am using it in the context of localization, could I also compute the
> amplitude and the phase of the signal?
>
> Many thanks.
>
> --
> Nahr Elk
>
> 2015-08-06 18:36 GMT+01:00 Eric Decker :
>
> >
> >
> > On Thu, Aug 6, 2015 at 4:00 AM, Nahr Elk  wrote:
> >
> >> Hello,
> >>
> >> Please, how can I measure the frequency of a signal received by my
> TelosB?
> >>
> >
> > what problem are you trying to solve?
> >
> > why do you want to do that?
> >
> > please provide more context.
> >
> > the telosb uses a CC2420 radio which is tuned to one  of the 2.4GHz ISM
> > bands.
> >
> > The channel depends on how the telosb is programmed.
> >
> > why would you want to measure it?  Measure in what fashion?
> >
> >
> >> Thanks!
> >>
> >> --
> >> Nahr Elk
> >> Independent Researcher
> >>
> >>
> >> ___
> >> 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
> >
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150809/ea0e11fc/attachment.html
>
> --
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> End of Tinyos-help Digest, Vol 148, Issue 6
> ***
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 148, Issue 1(Including headers from C files)

[He Dajiang (I2R)]

if your c file not so big, you can just copy your c code into your existing nc 
file.

if your c file is big, you can convert it into a nc module.

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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 145, Issue 8

[Alexander]

Hello Alex,
Where you got GainTx and GainRx from?

Regards, Alex.

12 мая 2015 г., в 22:07, Alex Cp  написал(а):

> Dear Jobish John.
> 
> You know the reason about why the measure of the Rssi in the Base is -3dBm, 
> because after make a link budget calculus it should be: 10 dBm when the two 
> antennas are touching? 
> 
> 
> Ptx+GainTx+GainRx= 
> 0dBm+5dBi+5dBi= 
> 10dBm
> 
> Nevertheless the currently value obtained is -3dBm (The maximum value 
> obtained in terms of wireless power)
> 
> Thanks in advance for your kind answer.
> 
> 
> Alex CP
> CUC.
> 
> 
> 
> 
> 
> On Sat, May 9, 2015 at 2:00 PM,  
> wrote:
> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
> 
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
> 
> 
> Today's Topics:
> 
>1. Re: Rssi convert to dBm in TelosB (Alex Cp)
> 
> 
> --
> 
> Message: 1
> Date: Sat, 9 May 2015 12:45:00 -0500
> From: Alex Cp 
> Subject: Re: [Tinyos-help] Rssi convert to dBm in TelosB
> To: tinyos-help 
> Cc: ketan patel 
> Message-ID:
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Dear Jobish Jhon and Alexander.
> 
> Thanks a lot for all advices. Currently are worked fine, and the best is
> the fact that I know the calculus is very trustworthy (accurate information
> Jobish Jhon).
> 
> Finally the file RssiDemo.java is now:
> 
> ...
>int source = message.getSerialPacket().get_header_src();
>double rssi = msg.get_rssi()-45;
> System.out.println("Rssi Message received from node " + source +
>": Rssi = " +  rssi + " " + "dBm");
>   }
> ...
> 
> And mantaining the two TelosB motes very, very close (touching its
> antennas) I've obtained:
> 
> Rssi Message received from node 1: Rssi = -4.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -4.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> 
> Thanks a lot again!!
> 
> Alex CP
> CUC
> 
> 
> On Sat, May 9, 2015 at 2:14 AM, JOBISH JOHN 
> wrote:
> 
> > Hi Alex,
> >
> > The datasheet (Page No: 11) of CC2420 says ? The range for RSSI is
> > approximately from ?100 dBm to 0 dBm ?. Page No: 49 of CC2420 datasheet
> > talks about substracting the offset value, -45 to get the dBm equivalent.
> > Page No: 10 of datasheet talks about the Receiver Sensitivity (Typ: -95
> > dBm).
> >
> > Your previous readings shows approx. 0 dBm (when both the motes placed
> > very close)
> >
> > Try to increase the distance between the motes. When they get
> > disconnected, the Rssi Message received on your PC will be close to -50 (
> > so that -50 -45 = -95dBm) ( I am getting this value).
> >
> > Thus I believe subtracting -45 is enough.
> >
> > Thanks
> >
> > Jobish John
> >
> >
> >
> >
> >
> > On Sat, May 9, 2015 at 10:37 AM, Alex Cp  wrote:
> >
> >> Hi all.
> >>
> >> Im trying to convert in dBm the values obtained from the app:
> >>
> >> 
> >>
> >> In my case appears the next values:
> >>
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 41
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 41
> >>
> >> Because is very close both motes TelosB (Sending Mote and Rssi Base )
> >>
> >> In the TinyOS tutorial appears the next: "...that this app prints only
> >> the raw RSSI values ..."
> >>
> >> On the other hand I have the Data sheet of the RF Transceiver CC2420:
> >>
> >> 
> >>
> >> But is not clear to me How I can do the conversion from raw RSSI to dBm.
> >>
> >>
> >> I read, someone in the TinyOS mail-list, who wrote that is only necessary
> >> substract -45:
> >>
> >> <
> >> https://www.millennium.berkeley.edu/pipermail/tinyos-help/2014-March/058162.html
> >> >
> >>
> >> But I suppose is not a exact calculation.
> >>
> >> I'll be gr

Re: [Tinyos-help] Tinyos-help Digest, Vol 145, Issue 8

[Alex Cp]

Dear Jobish John.

You know the reason about why the measure of the Rssi in the Base is -3dBm,
because after make a link budget calculus it should be: 10 dBm when the two
antennas are touching?


Ptx+GainTx+GainRx=
0dBm+5dBi+5dBi=
10dBm

Nevertheless the currently value obtained is -3dBm (The maximum value
obtained in terms of wireless power)

Thanks in advance for your kind answer.


Alex CP
CUC.





On Sat, May 9, 2015 at 2:00 PM,  wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. Re: Rssi convert to dBm in TelosB (Alex Cp)
>
>
> --
>
> Message: 1
> Date: Sat, 9 May 2015 12:45:00 -0500
> From: Alex Cp 
> Subject: Re: [Tinyos-help] Rssi convert to dBm in TelosB
> To: tinyos-help 
> Cc: ketan patel 
> Message-ID:
>  jilo-oukvz7ol5ua1ayh+y3ae-e6pneb0w0ukzdk...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Dear Jobish Jhon and Alexander.
>
> Thanks a lot for all advices. Currently are worked fine, and the best is
> the fact that I know the calculus is very trustworthy (accurate information
> Jobish Jhon).
>
> Finally the file RssiDemo.java is now:
>
> ...
>int source = message.getSerialPacket().get_header_src();
>double rssi = msg.get_rssi()-45;
> System.out.println("Rssi Message received from node " + source +
>": Rssi = " +  rssi + " " + "dBm");
>   }
> ...
>
> And mantaining the two TelosB motes very, very close (touching its
> antennas) I've obtained:
>
> Rssi Message received from node 1: Rssi = -4.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -4.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
> Rssi Message received from node 1: Rssi = -3.0 dBm
>
> Thanks a lot again!!
>
> Alex CP
> CUC
>
>
> On Sat, May 9, 2015 at 2:14 AM, JOBISH JOHN 
> wrote:
>
> > Hi Alex,
> >
> > The datasheet (Page No: 11) of CC2420 says ? The range for RSSI is
> > approximately from ?100 dBm to 0 dBm ?. Page No: 49 of CC2420 datasheet
> > talks about substracting the offset value, -45 to get the dBm equivalent.
> > Page No: 10 of datasheet talks about the Receiver Sensitivity (Typ: -95
> > dBm).
> >
> > Your previous readings shows approx. 0 dBm (when both the motes placed
> > very close)
> >
> > Try to increase the distance between the motes. When they get
> > disconnected, the Rssi Message received on your PC will be close to -50 (
> > so that -50 -45 = -95dBm) ( I am getting this value).
> >
> > Thus I believe subtracting -45 is enough.
> >
> > Thanks
> >
> > Jobish John
> >
> >
> >
> >
> >
> > On Sat, May 9, 2015 at 10:37 AM, Alex Cp  wrote:
> >
> >> Hi all.
> >>
> >> Im trying to convert in dBm the values obtained from the app:
> >>
> >> 
> >>
> >> In my case appears the next values:
> >>
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 41
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 40
> >> Rssi Message received from node 1: Rssi = 41
> >>
> >> Because is very close both motes TelosB (Sending Mote and Rssi Base )
> >>
> >> In the TinyOS tutorial appears the next: "...that this app prints only
> >> the raw RSSI values ..."
> >>
> >> On the other hand I have the Data sheet of the RF Transceiver CC2420:
> >>
> >> 
> >>
> >> But is not clear to me How I can do the conversion from raw RSSI to dBm.
> >>
> >>
> >> I read, someone in the TinyOS mail-list, who wrote that is only
> necessary
> >> substract -45:
> >>
> >> <
> >>
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/2014-March/058162.html
> >> >
> >>
> >> But I suppose is not a exact calculation.
> >>
> >> I'll be grateful if somebody can generously explain how is the correct
> >> way to convert raw RSSI values from a TelosB to a dBm.
> >>
> >> Thanks 

Re: [Tinyos-help] TinyOS system image and bootloader

[Johny Mattsson]

On 30 April 2015 at 18:42, Li, Wenting  wrote:

> Hi Eric, Hi Johny,
>
> Thank you all for the answer! I still need to digest the information, for
> example, I don't know if in TinyOS we can generate a linking library. Are
> you suggesting writing c code instead of tos components?
>

Nope. It's still TinyOS (though TosBoot itself is a bit more C-ish due to
its low-level nature). You essentially first build the TinyOS TosBoot app,
then take that binary as input to objcopy, and extract the symbol entries
for flash_read/flash_write, putting those into a link library (see the
Makefile I linked in the earlier email for the exact details on how it does
that for the atxm256). This library is just a helper for when you link your
main TinyOS application, so that it can find where to call for the
flash_read/flash_write functions.

If you've placed those functions at fixed addresses, it would probably
possible to manually specify those symbols/addresses to the linker, but I
preferred doing it via a library since that way I'm sure that there is no
mismatch between the TosBoot and the main app.

I'd recommend you keep reading up on TosBoot / Deluge. For the project we
did $years ago, we didn't actually use the Deluge protocol (though we did
use TosBoot), but ran something on top of CoAP instead. Dealing with the
new firmware blocks once you get them to your device is quite easy - just
write them to the correct offset of the correct partition, and when fully
received, set the flags for TosBoot and reset the micro. Done!

Cheers,
/Johny
-- 
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.

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

Re: [Tinyos-help] TinyOS system image and bootloader

[Li, Wenting]

Hi Eric, Hi Johny,

Thank you all for the answer! I still need to digest the information, for
example, I don't know if in TinyOS we can generate a linking library. Are
you suggesting writing c code instead of tos components?

To answer Eric's question, what I want to do is to add some bootstrapping
code to receive data over the network and fill up all the writable memory
of the device (external flash, eeprom, most of the internal flash) with the
received data. This does the job of secure erasure of the device in order
to later get a clean system image and boot up. And I think this
bootstrapping code should reside in the bootloader section along with
TOSBoot. In theory all seems easy until it comes to the real device. I
don't even know if my questions are in the right direction to achieve that.

Thanks again!
Vivien

On 30 April 2015 at 06:18, Eric Decker  wrote:

> cool.  thanks Johny.
>
> Any chance you can finish writing/documenting this up and possibly add it
> to the mainline?
>
> On Wed, Apr 29, 2015 at 6:02 PM, Johny Mattsson 
> wrote:
>
>> On 30 April 2015 at 04:03, Eric Decker  wrote:
>>
>>> On Wed, Apr 29, 2015 at 9:06 AM, Li, Wenting  wrote:
>>>

 1. I want to put an application in the bootloader section and the other
 part in the applicatioin section, because I need the capability to write to
 internal flash. But the whole TOS image is too big to fit in bootloader
 section. So can I selectively choose a component to stay in bootloader
 section, and the other parts outside.

>>>
>>> no
>>>
>>
>> Make that a "no, not easily" :)
>>
>> For what you're wanting to do, you'll definitely want to use TosBoot.
>> Even so, with an AVR you'll need a few extra tweaks to work with/around the
>> flash programming restrictions. It's been a few years since I worked in
>> this area, but as a very brief summary, for remote firmware upgrade you
>> need to:
>>
>> - Use TosBoot to provider basic loader functionality, and get ensure it's
>> installed in the privileged/bootloader area of the flash.
>>
>> - Put the flash writing/erasing routines for the AVR into TosBoot, and
>> the function prototypes for them in some header file somewhere.
>>
>> - Generate a linking library from the TosBoot binary, containing only the
>> symbols for your flash read/write functions.
>>
>> - Create the volumes-{something}.xml to specify partitioning of your
>> flash - you'll need at least two application volumes to allow downloading
>> and switching to new firmware. There's a TEP or intro on how all that bit
>> works (I've forgotten most of it by now *cough*); It's probably together
>> with the rest of the TosBoot information.
>>
>> - Add "-Wl,-R$(path_to_above_generated.lib)" to your application
>> Makefile's LDFLAGS, to allow the linker to resolve your flash read/write
>> functions.
>>
>> - Include the header file for the flash read/write in whichever module
>> handles receiving new firmware data, and call them from there. Since these
>> functions actually reside in the boot loader area of the flash, they're
>> allowed to do the reprogramming. You're effectively sharing these functions
>> between both TosBoot and your application. This is the key to making it all
>> work.
>>
>> - All the other details that I've glossed over or forgotten about :)
>>
>> - And finally, be very very very careful if you ever need to make changes
>> to your TosBoot, since if you change the address of the read/write
>> functions, Things Will Break(tm). If possible, place those functions at
>> fixed addresses to avoid such headaches.
>>
>>
>>
>>
>>> How can I do it if TinyOS only allows the upload of one packaged system
 image?

>>>
>>> you can't in the context of TinyOS.  The question above is  outside the
>>> scope of how TinyOS gets built.
>>>
>>> You are actually asking a question about how to you make use of the
>>> embedded atmel environment.  And how do you load two different pieces of
>>> code into the Atmel flash and have them cooperate in some fashion.
>>>
>>> TinyOS doesn't directly support doing those kinds of things.
>>>
>>
>> While, as Eric says, there's no direct support for it, the structure does
>> work quite well for slotting it in though, largely thanks to TosBoot.
>>
>>
>>
>>> You can do this but it is outside the scope of how TinyOS works.  So it
>>> is something that you would have to figure out.
>>>
>>
>> Having been in the position of having to figure those things out, allow
>> me to point you at our (now somewhat outdated) TinyOS fork with support for
>> the atxm256, including the above mentioned boot loader / reprogramming
>> support. The most interesting file to peruse is probably the TosBoot
>> Makefile:
>>
>>
>> https://github.com/DiUS/tinyos-siflex02/blob/master/tos/lib/tosboot/Makefile
>>
>> The siflex02 & modflex related targets have the relevant bits.
>>
>> Getting it all to work isn't what I'd call trivial, but it *is* doable if
>> you're willing to put the time into it!
>>
>>
>> Good luck,

Re: [Tinyos-help] TinyOS system image and bootloader

[Eric Decker]

cool.  thanks Johny.

Any chance you can finish writing/documenting this up and possibly add it
to the mainline?

On Wed, Apr 29, 2015 at 6:02 PM, Johny Mattsson 
wrote:

> On 30 April 2015 at 04:03, Eric Decker  wrote:
>
>> On Wed, Apr 29, 2015 at 9:06 AM, Li, Wenting  wrote:
>>
>>>
>>> 1. I want to put an application in the bootloader section and the other
>>> part in the applicatioin section, because I need the capability to write to
>>> internal flash. But the whole TOS image is too big to fit in bootloader
>>> section. So can I selectively choose a component to stay in bootloader
>>> section, and the other parts outside.
>>>
>>
>> no
>>
>
> Make that a "no, not easily" :)
>
> For what you're wanting to do, you'll definitely want to use TosBoot. Even
> so, with an AVR you'll need a few extra tweaks to work with/around the
> flash programming restrictions. It's been a few years since I worked in
> this area, but as a very brief summary, for remote firmware upgrade you
> need to:
>
> - Use TosBoot to provider basic loader functionality, and get ensure it's
> installed in the privileged/bootloader area of the flash.
>
> - Put the flash writing/erasing routines for the AVR into TosBoot, and the
> function prototypes for them in some header file somewhere.
>
> - Generate a linking library from the TosBoot binary, containing only the
> symbols for your flash read/write functions.
>
> - Create the volumes-{something}.xml to specify partitioning of your flash
> - you'll need at least two application volumes to allow downloading and
> switching to new firmware. There's a TEP or intro on how all that bit works
> (I've forgotten most of it by now *cough*); It's probably together with the
> rest of the TosBoot information.
>
> - Add "-Wl,-R$(path_to_above_generated.lib)" to your application
> Makefile's LDFLAGS, to allow the linker to resolve your flash read/write
> functions.
>
> - Include the header file for the flash read/write in whichever module
> handles receiving new firmware data, and call them from there. Since these
> functions actually reside in the boot loader area of the flash, they're
> allowed to do the reprogramming. You're effectively sharing these functions
> between both TosBoot and your application. This is the key to making it all
> work.
>
> - All the other details that I've glossed over or forgotten about :)
>
> - And finally, be very very very careful if you ever need to make changes
> to your TosBoot, since if you change the address of the read/write
> functions, Things Will Break(tm). If possible, place those functions at
> fixed addresses to avoid such headaches.
>
>
>
>
>> How can I do it if TinyOS only allows the upload of one packaged system
>>> image?
>>>
>>
>> you can't in the context of TinyOS.  The question above is  outside the
>> scope of how TinyOS gets built.
>>
>> You are actually asking a question about how to you make use of the
>> embedded atmel environment.  And how do you load two different pieces of
>> code into the Atmel flash and have them cooperate in some fashion.
>>
>> TinyOS doesn't directly support doing those kinds of things.
>>
>
> While, as Eric says, there's no direct support for it, the structure does
> work quite well for slotting it in though, largely thanks to TosBoot.
>
>
>
>> You can do this but it is outside the scope of how TinyOS works.  So it
>> is something that you would have to figure out.
>>
>
> Having been in the position of having to figure those things out, allow me
> to point you at our (now somewhat outdated) TinyOS fork with support for
> the atxm256, including the above mentioned boot loader / reprogramming
> support. The most interesting file to peruse is probably the TosBoot
> Makefile:
>
>
> https://github.com/DiUS/tinyos-siflex02/blob/master/tos/lib/tosboot/Makefile
>
> The siflex02 & modflex related targets have the relevant bits.
>
> Getting it all to work isn't what I'd call trivial, but it *is* doable if
> you're willing to put the time into it!
>
>
> Good luck,
> /Johny
> --
> Johny Mattsson
> Senior Software Engineer
>
> DiUS Computing Pty. Ltd.
>
> *where ideas are engineered *
>



-- 
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 system image and bootloader

[Johny Mattsson]

On 30 April 2015 at 04:03, Eric Decker  wrote:

> On Wed, Apr 29, 2015 at 9:06 AM, Li, Wenting  wrote:
>
>>
>> 1. I want to put an application in the bootloader section and the other
>> part in the applicatioin section, because I need the capability to write to
>> internal flash. But the whole TOS image is too big to fit in bootloader
>> section. So can I selectively choose a component to stay in bootloader
>> section, and the other parts outside.
>>
>
> no
>

Make that a "no, not easily" :)

For what you're wanting to do, you'll definitely want to use TosBoot. Even
so, with an AVR you'll need a few extra tweaks to work with/around the
flash programming restrictions. It's been a few years since I worked in
this area, but as a very brief summary, for remote firmware upgrade you
need to:

- Use TosBoot to provider basic loader functionality, and get ensure it's
installed in the privileged/bootloader area of the flash.

- Put the flash writing/erasing routines for the AVR into TosBoot, and the
function prototypes for them in some header file somewhere.

- Generate a linking library from the TosBoot binary, containing only the
symbols for your flash read/write functions.

- Create the volumes-{something}.xml to specify partitioning of your flash
- you'll need at least two application volumes to allow downloading and
switching to new firmware. There's a TEP or intro on how all that bit works
(I've forgotten most of it by now *cough*); It's probably together with the
rest of the TosBoot information.

- Add "-Wl,-R$(path_to_above_generated.lib)" to your application Makefile's
LDFLAGS, to allow the linker to resolve your flash read/write functions.

- Include the header file for the flash read/write in whichever module
handles receiving new firmware data, and call them from there. Since these
functions actually reside in the boot loader area of the flash, they're
allowed to do the reprogramming. You're effectively sharing these functions
between both TosBoot and your application. This is the key to making it all
work.

- All the other details that I've glossed over or forgotten about :)

- And finally, be very very very careful if you ever need to make changes
to your TosBoot, since if you change the address of the read/write
functions, Things Will Break(tm). If possible, place those functions at
fixed addresses to avoid such headaches.




> How can I do it if TinyOS only allows the upload of one packaged system
>> image?
>>
>
> you can't in the context of TinyOS.  The question above is  outside the
> scope of how TinyOS gets built.
>
> You are actually asking a question about how to you make use of the
> embedded atmel environment.  And how do you load two different pieces of
> code into the Atmel flash and have them cooperate in some fashion.
>
> TinyOS doesn't directly support doing those kinds of things.
>

While, as Eric says, there's no direct support for it, the structure does
work quite well for slotting it in though, largely thanks to TosBoot.



> You can do this but it is outside the scope of how TinyOS works.  So it is
> something that you would have to figure out.
>

Having been in the position of having to figure those things out, allow me
to point you at our (now somewhat outdated) TinyOS fork with support for
the atxm256, including the above mentioned boot loader / reprogramming
support. The most interesting file to peruse is probably the TosBoot
Makefile:


https://github.com/DiUS/tinyos-siflex02/blob/master/tos/lib/tosboot/Makefile

The siflex02 & modflex related targets have the relevant bits.

Getting it all to work isn't what I'd call trivial, but it *is* doable if
you're willing to put the time into it!


Good luck,
/Johny
-- 
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.

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

Re: [Tinyos-help] TinyOS system image and bootloader

[Eric Decker]

On Wed, Apr 29, 2015 at 9:06 AM, Li, Wenting  wrote:

> Dear all,
>
> I have several question with regard to the relation between the bootloader
> and TinyOS with the underlying device as MicaZ (or Atmega128). My goal is
> to understand how to upload an application to a specific memory address in
> the internal flash of Atmega128.
>
> First, I want to confirm if what I learned is correct.
>
> 1. It seems that once I compiled a TinyOS application, e.g. Blink, the
> output (and uploaded) image includes the whole OS (necessary components and
> libraries in the dependencies) and the application BlinkApp, is it correct?
>

yes.


>
> 2. From the tutorial, it seems that I can only package one application
> into the system image, because in the Makefile I can only define one
> component. Is it correct?
>

yes.  TinyOS uses whole program optimization.  Only one program gets built
and it is complete.


>
> 3. If 2. is correct, then the TinyOS is like a one task application.
>

calling the above a task is confusing in the TinyOS context because tasks
have a different meaning.


> If I want to add another function, e.g., Bark, I have to modify the top
> component module as "BlinkAndBark", wire Blink and Bark components and
> start them asynchronously. Is it correct?
>

Mostly.  There are many different ways to accomplish this.  You can have a
Blink module that implements the Blink functionality.  You can also have a
Bark module that implements Bark.  You main top level could do nothing and
Blink and Bark both get activated via Boot.booted.


> Here are my main questions:
>
> I learned from the datasheet of Atmega128 that its internal flash is
> comprised of bootloader section (e.g. 0xF000 ~ 0x) and the application
> section (e.g. 0x~0xEFFF).
>
> 1. I want to put an application in the bootloader section and the other
> part in the applicatioin section, because I need the capability to write to
> internal flash. But the whole TOS image is too big to fit in bootloader
> section. So can I selectively choose a component to stay in bootloader
> section, and the other parts outside.
>

no


> How can I do it if TinyOS only allows the upload of one packaged system
> image?
>

you can't in the context of TinyOS.  The question above is  outside the
scope of how TinyOS gets built.

You are actually asking a question about how to you make use of the
embedded atmel environment.  And how do you load two different pieces of
code into the Atmel flash and have them cooperate in some fashion.

TinyOS doesn't directly support doing those kinds of things.

You can do this but it is outside the scope of how TinyOS works.  So it is
something that you would have to figure out.


>
> 2. I checked a bit about Deluge (using TOSBoot). It seems that the tosboot
> indicates -DTOSBOOT_START in the Makefile where to put tosboot. Does it
> mean that the rest stays elsewhere? But I compiled app/test/deluge/Blink,
> and its main.srec does not include address within 0xF000~0x according
> to the description of SREC format, only 0x~0x3610. I am confused...
>

sorry I haven't gone done the Deluge/TosBoot path so can't answer any more
of your questions.


>
> 3. How to write bootloader in TinyOS? Any tutorials, principle? I have
> only seen avr bootloader.
>

What are you actually trying to do?  Do you need to change the code load on
the fly?  That is what Deluge/TosBoot are for.


>
> I am trying to understand it and finally build something. Any hint would
> be welcome!! Thanks a lot for your help!
>
> regards,
> Vivien
>
>
>
>
>
> ___
> 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] TinyOS system image and bootloader

[Li, Wenting]

Dear all,

I have several question with regard to the relation between the bootloader
and TinyOS with the underlying device as MicaZ (or Atmega128). My goal is
to understand how to upload an application to a specific memory address in
the internal flash of Atmega128.

First, I want to confirm if what I learned is correct.

1. It seems that once I compiled a TinyOS application, e.g. Blink, the
output (and uploaded) image includes the whole OS (necessary components and
libraries in the dependencies) and the application BlinkApp, is it correct?

2. From the tutorial, it seems that I can only package one application into
the system image, because in the Makefile I can only define one component.
Is it correct?

3. If 2. is correct, then the TinyOS is like a one task application. If I
want to add another function, e.g., Bark, I have to modify the top
component module as "BlinkAndBark", wire Blink and Bark components and
start them asynchronously. Is it correct?

Here are my main questions:

I learned from the datasheet of Atmega128 that its internal flash is
comprised of bootloader section (e.g. 0xF000 ~ 0x) and the application
section (e.g. 0x~0xEFFF).

1. I want to put an application in the bootloader section and the other
part in the applicatioin section, because I need the capability to write to
internal flash. But the whole TOS image is too big to fit in bootloader
section. So can I selectively choose a component to stay in bootloader
section, and the other parts outside. How can I do it if TinyOS only allows
the upload of one packaged system image?

2. I checked a bit about Deluge (using TOSBoot). It seems that the tosboot
indicates -DTOSBOOT_START in the Makefile where to put tosboot. Does it
mean that the rest stays elsewhere? But I compiled app/test/deluge/Blink,
and its main.srec does not include address within 0xF000~0x according
to the description of SREC format, only 0x~0x3610. I am confused...

3. How to write bootloader in TinyOS? Any tutorials, principle? I have only
seen avr bootloader.

I am trying to understand it and finally build something. Any hint would be
welcome!! Thanks a lot for your help!

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 143, Issue 10

[Aruna Kurhade]

i m doing sinktrail a proactive data reporting protocol for wireless sensor
network using tossim plz help throught for completion of this
project,thank you...

On Thu, Mar 26, 2015 at 5:38 PM, Aruna Kurhade 
wrote:

> tossim execution requires actual mote for execution of the program
>
> On Thu, Mar 26, 2015 at 12:30 AM, <
> tinyos-help-requ...@millennium.berkeley.edu> wrote:
>
>> Send Tinyos-help mailing list submissions to
>> tinyos-help@millennium.berkeley.edu
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> or, via email, send a message with subject or body 'help' to
>> tinyos-help-requ...@millennium.berkeley.edu
>>
>> You can reach the person managing the list at
>> tinyos-help-ow...@millennium.berkeley.edu
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Tinyos-help digest..."
>>
>>
>> Today's Topics:
>>
>>1. Workaround for Timer bug ( IRIS modules) (Roadstar Runner)
>>
>>
>> --
>>
>> Message: 1
>> Date: Wed, 25 Mar 2015 00:46:58 -0400
>> From: Roadstar Runner 
>> Subject: [Tinyos-help] Workaround for Timer bug ( IRIS modules)
>> To: tinyos forum , Miklos Maroti
>> ,Janos Sallai ,
>> Eric
>> Decker 
>> Message-ID:
>> <
>> can3ao+wg18yqirvfdzaihbx8co9x77m8cz+edd5e-4pa388...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I recently cam across a possible bug in the Timer module for the IRIS
>> motes. I occasionally noticed that the timer would fire very late thus
>> causing a whole series of cascading failures in my modules.
>>
>> After days of debugging, I traced the problem to the routine
>> setInterrupt()
>> in the  module Atm1281AlarmAsyncP.
>> If the alarm is armed to fire after 1 TCNT tick, in some situations OCR2A
>> will be loaded with a value that will essentially be in the "past",  thus
>> requiring TCNT2 to wrap around for the compare to occur (about 255 ms
>> late).
>> Since TCNT2 is a free running timer, if TCNT2 increments after the current
>> time is captured by the call to Counter.get(), the *fired *flag will not
>> be
>> set, even though the alarm has technically expired. After this, under some
>> circumstances, the compare register can be loaded with a wrong value.
>> Consider the following situation when setInterrupt() is called
>>
>>
>> to = 24
>> dt = 1
>> TCNT2 =1
>> base = 23
>>
>> now if TCNT increments (TCNT2 = 2)  after the current  time is captured
>>   uint32_t now = call Counter.get();
>>
>> Then the following condition will fail
>>  /* Check if alarm expired */
>>if ((uint32_t)(now - t0) >= dt)
>> The following variables will be updated as indicated below, to compute
>>  anew value for OCCR2A
>> alarm_in = 2
>> newOcr2A = 1
>>
>> Since newOcr2A   =1  and TCNT2 =2 , When OCCR2A is loaded, it will delay
>> the next alarm by 255 ms.
>>
>> As a quick workaround, i added the following code to force the timers to
>> fire after calling setOcr2A(newOcr2A);
>>
>> //work around
>> if(newOcr2A >= TCNT)
>> {
>> diff =  newOcr2A - TCNT   ;
>> }
>> else
>> {
>> diff =  (0xFF - TCNT) + newOcr2A ;
>> }
>> if( diff   > MAXT)
>> {
>> fired = TRUE;
>> }
>> -- next part --
>> An HTML attachment was scrubbed...
>> URL:
>> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150325/ca091374/attachment-0001.htm
>>
>> --
>>
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> End of Tinyos-help Digest, Vol 143, Issue 10
>> 
>>
>
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 143, Issue 10

[Aruna Kurhade]

tossim execution requires actual mote for execution of the program

On Thu, Mar 26, 2015 at 12:30 AM, <
tinyos-help-requ...@millennium.berkeley.edu> wrote:

> Send Tinyos-help mailing list submissions to
> tinyos-help@millennium.berkeley.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
> tinyos-help-requ...@millennium.berkeley.edu
>
> You can reach the person managing the list at
> tinyos-help-ow...@millennium.berkeley.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>1. Workaround for Timer bug ( IRIS modules) (Roadstar Runner)
>
>
> --
>
> Message: 1
> Date: Wed, 25 Mar 2015 00:46:58 -0400
> From: Roadstar Runner 
> Subject: [Tinyos-help] Workaround for Timer bug ( IRIS modules)
> To: tinyos forum , Miklos Maroti
> ,Janos Sallai ,
> Eric
> Decker 
> Message-ID:
> <
> can3ao+wg18yqirvfdzaihbx8co9x77m8cz+edd5e-4pa388...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I recently cam across a possible bug in the Timer module for the IRIS
> motes. I occasionally noticed that the timer would fire very late thus
> causing a whole series of cascading failures in my modules.
>
> After days of debugging, I traced the problem to the routine setInterrupt()
> in the  module Atm1281AlarmAsyncP.
> If the alarm is armed to fire after 1 TCNT tick, in some situations OCR2A
> will be loaded with a value that will essentially be in the "past",  thus
> requiring TCNT2 to wrap around for the compare to occur (about 255 ms
> late).
> Since TCNT2 is a free running timer, if TCNT2 increments after the current
> time is captured by the call to Counter.get(), the *fired *flag will not be
> set, even though the alarm has technically expired. After this, under some
> circumstances, the compare register can be loaded with a wrong value.
> Consider the following situation when setInterrupt() is called
>
>
> to = 24
> dt = 1
> TCNT2 =1
> base = 23
>
> now if TCNT increments (TCNT2 = 2)  after the current  time is captured
>   uint32_t now = call Counter.get();
>
> Then the following condition will fail
>  /* Check if alarm expired */
>if ((uint32_t)(now - t0) >= dt)
> The following variables will be updated as indicated below, to compute
>  anew value for OCCR2A
> alarm_in = 2
> newOcr2A = 1
>
> Since newOcr2A   =1  and TCNT2 =2 , When OCCR2A is loaded, it will delay
> the next alarm by 255 ms.
>
> As a quick workaround, i added the following code to force the timers to
> fire after calling setOcr2A(newOcr2A);
>
> //work around
> if(newOcr2A >= TCNT)
> {
> diff =  newOcr2A - TCNT   ;
> }
> else
> {
> diff =  (0xFF - TCNT) + newOcr2A ;
> }
> if( diff   > MAXT)
> {
> fired = TRUE;
> }
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150325/ca091374/attachment-0001.htm
>
> --
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> End of Tinyos-help Digest, Vol 143, Issue 10
> 
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS 2.1.1 - IP-tunnel shuts down unexpectedly

[laptopcss]

Hallo together,
 
it is Ubuntu 10.04.
 
Regards, Corinna




 

Gesendet: Dienstag, 17. Februar 2015 um 14:40 Uhr
Von: laptop...@gmx.de
An: Tinyos-help@millennium.berkeley.edu
Betreff: [Tinyos-help] TinyOS 2.1.1 - IP-tunnel shuts down unexpectedly

Hallo together,
 
I currently run TinyOS 2.1.1 in Ubuntu 10.4 in Virtual Box.
After upgrading virtualbox to 4.3.22 I have trouble with TinyOS.
 
My code runs blip and uses the common IP-Tunnel.
The IP-tunnel now aborts latest every 5 minutes without any error messages.
 
Does anyone have the same problem or have ideas how to solve it?
 
Regards,
Conny

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

[Tinyos-help] TinyOS 2.1.1 - IP-tunnel shuts down unexpectedly

[laptopcss]

Hallo together,

 

I currently run TinyOS 2.1.1 in Ubuntu 10.4 in Virtual Box.

After upgrading virtualbox to 4.3.22 I have trouble with TinyOS.

 

My code runs blip and uses the common IP-Tunnel.

The IP-tunnel now aborts latest every 5 minutes without any error messages.

 

Does anyone have the same problem or have ideas how to solve it?

 

Regards,

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

Re: [Tinyos-help] TinyOS 6LowPAN implementation in Beagleboard without using Epic Cape

[Eric Decker]

I'm not sure what you are asking.

want to try again?

On Tue, Dec 30, 2014 at 11:26 PM, Bipin  wrote:

> Hello  Sir..,
> This  is  the  Question to  Eric  Decker  and  all  other  members  in
> this  forum  who  have  very  good  knowledge  about  the  6LowPAN  concept
> in TinyOS.  I  have  one  problem  while  implementing  an  application
>  of
> 6LowPAN  in  Beagle board(BB)(TinyOS  doesn't  have any packages  for  BB
> version  of  Ubuntu  OS).  Here  i  don't  want  to use  epic  board  to
> build  an  application  in  BB.  Without  using  a  epic  board  is  it
> possible  to  build  an  application in  the  BB.  Like
>
>  I  have  TCP Echo  and  IPBase-station  Application  in  my  Micaz
> Mote.  IPBaseStation  mote  is  attached  to  the  BB  and   in  BB  Can  i
> use  any  of  the Edge  router (6LBR,NanoRouter, Open-Labs,Grinch ,Arch
> Rock
> PhyNet Router ,JenNet-IP Border-Router)  for  building  application...?
>
>An  advance  Thank  you  for  your  help  ... :)
>
>
>
> --
> View this message in context:
> http://tinyos-help.10906.n7.nabble.com/TinyOS-6LowPAN-implementation-in-Beagleboard-without-using-Epic-Cape-tp24722.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
>



-- 
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] TinyOS 6LowPAN implementation in Beagleboard without using Epic Cape

[Bipin]

Hello  Sir..,
This  is  the  Question to  Eric  Decker  and  all  other  members  in 
this  forum  who  have  very  good  knowledge  about  the  6LowPAN  concept
in TinyOS.  I  have  one  problem  while  implementing  an  application   of
6LowPAN  in  Beagle board(BB)(TinyOS  doesn't  have any packages  for  BB
version  of  Ubuntu  OS).  Here  i  don't  want  to use  epic  board  to  
build  an  application  in  BB.  Without  using  a  epic  board  is  it 
possible  to  build  an  application in  the  BB.  Like
 
 I  have  TCP Echo  and  IPBase-station  Application  in  my  Micaz 
Mote.  IPBaseStation  mote  is  attached  to  the  BB  and   in  BB  Can  i 
use  any  of  the Edge  router (6LBR,NanoRouter, Open-Labs,Grinch ,Arch Rock
PhyNet Router ,JenNet-IP Border-Router)  for  building  application...?

   An  advance  Thank  you  for  your  help  ... :)



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-6LowPAN-implementation-in-Beagleboard-without-using-Epic-Cape-tp24722.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

Re: [Tinyos-help] tinyos not running in micaz board

[He Dajiang (I2R)]

thanks phil.
We've found the problem. Due to manufacturing issue, the Crystal of some 
hardwares does not work, so tinyos is stuck at some timer checking function.

From: Philip Levis [p...@cs.stanford.edu]
Sent: Monday, 8 December, 2014 10:15:20 AM
To: He Dajiang (I2R)
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] tinyos not running in micaz board

Calculate the clock cycles per jiffy (32kHz ticks), configure I/O pins as 
input/output.

Phil

> On Nov 6, 2014, at 4:57 AM, He Dajiang (I2R)  wrote:
>
> Hi all,
>
> We've made sensor board based on micaz architecture. The board does not work 
> even for the simple Blink application; we managed to flash firmware into the 
> board by using tinyos make tools (make micaz reinstall.x ...).
> However, if we bypass tinyos and flash simple blinking code into the board 
> (SET and CLEAR the MCU pins linking to the led), it can function and hardare 
> leds blink. I take a look at app.c of tinyos blink app, before Blink__booted 
> function is called, there are some other hardware, platform, and software 
> init functions being called. Can I ask questions to the creators of tinyos, 
> what are the checkings tinyos does when booting up? I guess some of the 
> checkings failed on my board so that tinyos Blink app does not run in my 
> board.
>
> Thx & Regards
> dajiang
>
> 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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] tinyos not running in micaz board

[Philip Levis]

Calculate the clock cycles per jiffy (32kHz ticks), configure I/O pins as 
input/output.

Phil

> On Nov 6, 2014, at 4:57 AM, He Dajiang (I2R)  wrote:
> 
> Hi all,
> 
> We've made sensor board based on micaz architecture. The board does not work 
> even for the simple Blink application; we managed to flash firmware into the 
> board by using tinyos make tools (make micaz reinstall.x ...).
> However, if we bypass tinyos and flash simple blinking code into the board 
> (SET and CLEAR the MCU pins linking to the led), it can function and hardare 
> leds blink. I take a look at app.c of tinyos blink app, before Blink__booted 
> function is called, there are some other hardware, platform, and software 
> init functions being called. Can I ask questions to the creators of tinyos, 
> what are the checkings tinyos does when booting up? I guess some of the 
> checkings failed on my board so that tinyos Blink app does not run in my 
> board.
> 
> Thx & Regards
> dajiang
> 
> 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://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] tinyos not running in micaz board

[He Dajiang (I2R)]

Hi all,

We've made sensor board based on micaz architecture. The board does not work 
even for the simple Blink application; we managed to flash firmware into the 
board by using tinyos make tools (make micaz reinstall.x ...).
However, if we bypass tinyos and flash simple blinking code into the board (SET 
and CLEAR the MCU pins linking to the led), it can function and hardare leds 
blink. I take a look at app.c of tinyos blink app, before Blink__booted 
function is called, there are some other hardware, platform, and software init 
functions being called. Can I ask questions to the creators of tinyos, what are 
the checkings tinyos does when booting up? I guess some of the checkings failed 
on my board so that tinyos Blink app does not run in my board.

Thx & Regards
dajiang

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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] tinyos help 8

[Prashan]

http://lojawebsite.com/jahscn/fqfbonpssfwdn.ijmgcztentthjctu

































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

Re: [Tinyos-help] tinyos compile error "multiple targets specified" make: *** [exe0] Error 2 pls help

[Eric Decker]

I've never seen oppxmac before.   I don't know what that does.

does "make telosb" work?

the other thing that is strange is the "overriding commands" warnings.


On Fri, Sep 19, 2014 at 5:36 AM, Thanh Ngoc Dinh <
s3453...@student.rmit.edu.au> wrote:

> Hello everyone,
> I am testing the low power listening protocol using the TestNetworkLPL in
> tinyos-2.1.2 and tinyos-2.1.1. I used msp430-gcc version 4.7.0. However, i
> got a compile error "multiple targets specified". The detail of error is
> described below. Do you know why this error happens? and please advise me a
> way to solve the error.
> Thank you very much!!!
>
>  detail of compiling and error--
>
> "
> root@TinyOS:/opt/tinyos-2.1.2/apps/TestNetworkLpl$ make telosb oppxmac
> /opt/tinyos-2.1.2/support/make/ident_flags.extra:13: warning: overriding
> commands for target `ident_cache'
> ../../support/make//ident_flags.extra:13: warning: ignoring old commands
> for target `ident_cache'
> /opt/tinyos-2.1.2/support/make/tos_image.extra:8: warning: overriding
> commands for target `build_tosimage'
> ../../support/make//tos_image.extra:8: warning: ignoring old commands for
> target `build_tosimage'
> ../../support/make//msp/msp.rules:92: warning: overriding commands for
> target `setid'
> ../../support/make//msp/msp.rules:92: warning: ignoring old commands for
> target `setid'
> ../../support/make//msp/msp.rules:98: warning: overriding commands for
> target `tosimage'
> ../../support/make//msp/msp.rules:98: warning: ignoring old commands for
> target `tosimage'
> ../../support/make//msp/msp.rules:101: warning: overriding commands for
> target `ihex'
> ../../support/make//msp/msp.rules:101: warning: ignoring old commands for
> target `ihex'
> ../../support/make//msp/msp.rules:104: warning: overriding commands for
> target `exe'
> ../../support/make//msp/msp.rules:104: warning: ignoring old commands for
> target `exe'
> ../../support/make//msp/msp.rules:107: warning: overriding commands for
> target `exe0'
> ../../support/make//msp/msp.rules:107: warning: ignoring old commands for
> target `exe0'
> ../../support/make//msp/msp.rules:120: warning: overriding commands for
> target `builddir'
> ../../support/make//msp/msp.rules:120: warning: ignoring old commands for
> target `builddir'
> ../../support/make//msp/msp.rules:123: warning: overriding commands for
> target `bytes'
> ../../support/make//msp/msp.rules:123: warning: ignoring old commands for
> target `bytes'
> /opt/tinyos-2.1.2/support/make/telosb.target:19: warning: overriding
> commands for target `telos'
> ../../support/make//telosb.target:19: warning: ignoring old commands for
> target `telos'
> /opt/tinyos-2.1.2/support/make/telosb.target:22: warning: overriding
> commands for target `telosb'
> ../../support/make//telosb.target:22: warning: ignoring old commands for
> target `telosb'
> mkdir -p build/telosb
> compiling TestNetworkLplAppC to a telosb binary
> ncc -o build/telosb/main.exe  -Os -I../../tos/chips/cc2420
> -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive
> -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces
> -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug
> -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc
> -I../../tos/chips/cc2420/lpl  -I../../tos/chips/cc2420
> -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive
> -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces
> -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug
> -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc
> -I../../tos/chips/cc2420/lpl  -fnesc-separator=__ -Wall -Wshadow -Wnesc-all
> -target=telosb -fnesc-cfile=build/telosb/app.c -board=
> -DDEFINED_TOS_AM_GROUP=0x23 -fnesc-separator=__ -Wall -Wshadow -Wnesc-all
> -target=telosb -fnesc-cfile=build/telosb/app.c -board=
> -DDEFINED_TOS_AM_GROUP=0x23 -DLOW_POWER_LISTENING
> -DCC2420_NO_ADDRESS_RECOGNITION -DDELAY_AFTER_RECEIVE=30 -DNO_OPP_DEBUG
> -DLPL_DEF_LOCAL_WAKEUP=2048 -DLPL_DEF_REMOTE_WAKEUP=2048
> -DTEST_NETWORK_PACKET_RATE=4096 -DIDENT_APPNAME=\"TestNetworkLplA\"
> -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\"
> -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL
> -DIDENT_UIDHASH=0xdc56cefcL -DIDENT_APPNAME=\"TestNetworkLplA\"
> -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\"
> -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL
> -DIDENT_UIDHASH=0xdc56cefcL  TestNetworkLplAppC.nc -lm
> *multiple targets specified*
> *make: *** [exe0] Error 2*
>
>
> "
>
> Best regards,
> William
>
> ___
> 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/listin

[Tinyos-help] tinyos compile error "multiple targets specified" make: *** [exe0] Error 2 pls help

[Thanh Ngoc Dinh]

Hello everyone,
I am testing the low power listening protocol using the TestNetworkLPL in
tinyos-2.1.2 and tinyos-2.1.1. I used msp430-gcc version 4.7.0. However, i
got a compile error "multiple targets specified". The detail of error is
described below. Do you know why this error happens? and please advise me a
way to solve the error.
Thank you very much!!!

 detail of compiling and error--

"
root@TinyOS:/opt/tinyos-2.1.2/apps/TestNetworkLpl$ make telosb oppxmac
/opt/tinyos-2.1.2/support/make/ident_flags.extra:13: warning: overriding
commands for target `ident_cache'
../../support/make//ident_flags.extra:13: warning: ignoring old commands
for target `ident_cache'
/opt/tinyos-2.1.2/support/make/tos_image.extra:8: warning: overriding
commands for target `build_tosimage'
../../support/make//tos_image.extra:8: warning: ignoring old commands for
target `build_tosimage'
../../support/make//msp/msp.rules:92: warning: overriding commands for
target `setid'
../../support/make//msp/msp.rules:92: warning: ignoring old commands for
target `setid'
../../support/make//msp/msp.rules:98: warning: overriding commands for
target `tosimage'
../../support/make//msp/msp.rules:98: warning: ignoring old commands for
target `tosimage'
../../support/make//msp/msp.rules:101: warning: overriding commands for
target `ihex'
../../support/make//msp/msp.rules:101: warning: ignoring old commands for
target `ihex'
../../support/make//msp/msp.rules:104: warning: overriding commands for
target `exe'
../../support/make//msp/msp.rules:104: warning: ignoring old commands for
target `exe'
../../support/make//msp/msp.rules:107: warning: overriding commands for
target `exe0'
../../support/make//msp/msp.rules:107: warning: ignoring old commands for
target `exe0'
../../support/make//msp/msp.rules:120: warning: overriding commands for
target `builddir'
../../support/make//msp/msp.rules:120: warning: ignoring old commands for
target `builddir'
../../support/make//msp/msp.rules:123: warning: overriding commands for
target `bytes'
../../support/make//msp/msp.rules:123: warning: ignoring old commands for
target `bytes'
/opt/tinyos-2.1.2/support/make/telosb.target:19: warning: overriding
commands for target `telos'
../../support/make//telosb.target:19: warning: ignoring old commands for
target `telos'
/opt/tinyos-2.1.2/support/make/telosb.target:22: warning: overriding
commands for target `telosb'
../../support/make//telosb.target:22: warning: ignoring old commands for
target `telosb'
mkdir -p build/telosb
compiling TestNetworkLplAppC to a telosb binary
ncc -o build/telosb/main.exe  -Os -I../../tos/chips/cc2420
-I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive
-I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces
-I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug
-I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc
-I../../tos/chips/cc2420/lpl  -I../../tos/chips/cc2420
-I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive
-I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces
-I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug
-I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc
-I../../tos/chips/cc2420/lpl  -fnesc-separator=__ -Wall -Wshadow -Wnesc-all
-target=telosb -fnesc-cfile=build/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x23 -fnesc-separator=__ -Wall -Wshadow -Wnesc-all
-target=telosb -fnesc-cfile=build/telosb/app.c -board=
-DDEFINED_TOS_AM_GROUP=0x23 -DLOW_POWER_LISTENING
-DCC2420_NO_ADDRESS_RECOGNITION -DDELAY_AFTER_RECEIVE=30 -DNO_OPP_DEBUG
-DLPL_DEF_LOCAL_WAKEUP=2048 -DLPL_DEF_REMOTE_WAKEUP=2048
-DTEST_NETWORK_PACKET_RATE=4096 -DIDENT_APPNAME=\"TestNetworkLplA\"
-DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\"
-DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL
-DIDENT_UIDHASH=0xdc56cefcL -DIDENT_APPNAME=\"TestNetworkLplA\"
-DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\"
-DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL
-DIDENT_UIDHASH=0xdc56cefcL  TestNetworkLplAppC.nc -lm
*multiple targets specified*
*make: *** [exe0] Error 2*


"

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

Re: [Tinyos-help] Tinyos-help Digest, Vol 137, Issue 6

[He Dajiang (I2R)]

I've tried seriallisten on Ubuntu Linux, it works perfectly for 460800 baud 
rate.

From: tinyos-help-boun...@millennium.berkeley.edu 
[tinyos-help-boun...@millennium.berkeley.edu] on behalf of 
tinyos-help-requ...@millennium.berkeley.edu 
[tinyos-help-requ...@millennium.berkeley.edu]
Sent: Friday, 5 September, 2014 3:00:01 AM
To: tinyos-help@millennium.berkeley.edu
Subject: Tinyos-help Digest, Vol 137, Issue 6

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Re: Efficient ways to dump LogStorage (Andr?s B?r?)


--

Message: 1
Date: Thu, 4 Sep 2014 14:16:28 +0200
From: Andr?s B?r? 
Subject: Re: [Tinyos-help] Efficient ways to dump LogStorage
To: Ugo Maria Colesanti 
Cc: tinyos forum 
Message-ID:

Content-Type: text/plain; charset="utf-8"

Keep in mind that 500kbaud is a good value for atmel based motes with round
numbered oscillator, like the rfa1 and it's internal 16MHz RC oscillator.
The iris main clock is designed for traditional clockrates, so you might
want to use 460800 (I'm not sure if it works or not on linux, but the mote
is capable to do it). I'm not familiar with the other platforms.

Andris


On Thu, Sep 4, 2014 at 1:37 PM, Ugo Maria Colesanti <
colesa...@dis.uniroma1.it> wrote:

> Sorry, my mistake! I put 5Mbps instead of 500kbps. With tos-install-jre it
> works now. Thanks!
>
> Ugo
>
>
> 2014-09-04 13:23 GMT+02:00 Ugo Maria Colesanti 
> :
>
> Hmm... still having issues:
>> - I did the tos-install-jni and it no longer says that it does not find
>> toscomm, but the baud error is still there.
>> - I made a make clean and make again inside the jni folder and it created
>> new libtoscomm.so
>> - I manually copied libtoscomm.so inside the jre path (and removed the
>> old one that was there) but nothing, still it does not recognize 50 as
>> a valid baudrate.
>> Another strange thing, if a use make install inside jni, it copies the
>> libtoscomm.so and libgetenv.so in /usr/local/lib/tinyos/ is it the normal
>> default behavior?
>>
>> Ugo
>>
>>
>> 2014-09-04 12:48 GMT+02:00 Andr?s B?r? :
>>
>> You're on a good track, but you deleted the wrong file. You should
>>> replace libtoscomm.so. If you compiled and installed tinyos-tools from
>>> source, just run "sudo tos-install-jni". Or you can do it by hand: Search
>>> the compiled file and copy it to "tos-locate-jre --jni"
>>> Another trick I usually use is the c based serialforwarder ("sf"), which
>>> never had this limitation.
>>>
>>> And naturally, this will be included in the upcoming release.
>>>
>>> But still, if you have a bit of time, use serialactivemessage. Printf is
>>> mostly designed for debug, not for data download.
>>>
>>> Andris
>>>
>>>
>>> On Thu, Sep 4, 2014 at 9:52 AM, Ugo Maria Colesanti <
>>> colesa...@dis.uniroma1.it> wrote:
>>>
 Wow, I was not aware that uart could handle that kind of speeds, I
 tried even 1Mbps and still works... that's cool :)
 On that point I have one question:
 I just installed the more recent tinyos-main and compiled the tools
 folder, but the java PrintfClient still doesn't support speeds over
 230400bps (it gives me "TOSComm JNI library runtime error: baud_to_enum,
 bad baud rate"). However, if I go in
 tools/tinyos/jni/serial/NativeSerial_linux.cpp which seems to be the file
 that generates this error, greater speeds are enumerated. I removed
 tools/tinyos/java/tinyos.jar just to be sure it was taking all files from
 the compiled sources and not from jar, but it still continues to give me
 the same error... any hints?
 I managed to make the PrintfClient to work using the c version of
 serial forwarder and binding the java PrintfClient on it.

 Ugo


 2014-09-01 13:28 GMT+02:00 Andr?s B?r? :

 Hi Guys,
>
> Fastserial doesn't provide faster communication, it's just using much
> less blocking (atomic) segments, so it doesn't mess up important
> interrupts. This is very useful when you want to use it as a really fast
> basestation. You can turn it on with the fastserial extra (e.g. "make iris
> fastserial").
>
> You can also try to increase baudrate with the PLATFORM_BAUDRATE
> constant in the makefile. I'm not sure about the telosb, but the ucmotes
> usually works well with "CFLAGS+=-DPLATFORM_BAUDRATE=50U", probably
> even better than with 115

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Ugo Maria Colesanti]

Actually it was more simple than expected, after having implemented the
Counter and Compare component based on RTC everything built-up quite
quickly up to the TimerMilli.
Now Blink is compiling and working correctly.

Ugo


2014-08-17 11:23 GMT+02:00 Ugo Maria Colesanti :

> Hi all,
> it is just to inform that I started the port of the Atmel SamR21Xplained
> board. The board has the SamR21 which is a bundle of the SamD21 (cortex
> m0+) and AT86RF233 transceiver. I'm using the Linaro gcc 4.8.3 patched
> following instructions for the Opal (Sam3u) port (
> https://github.com/csiro-wsn/tinyos-csiro-opal).
> I started from scratch, hence, there is not that much. I implemented the
> GeneralIO and Leds interface, and  wrote two components for managing the
> Generic Clock Controller, which selects clock sources and distribute them
> in the chip. I briefly tested, using direct register access, the RTC (set
> to 32bit mode), Timer/Counter (both, 16 bit and 32 bit), EIC (External
> Interrupt Controller) and they seem to work. Now I want to start writing
> components implementing Counter,Alarm and Timer interfaces, but I got lost
> looking at implementations for MSP430 and RFA1 thus, I think it will take a
> little bit for doing that in a clean way. In addition I have one more week
> of holidays, then the port will become low-priority again.
>
> If anybody is interested in helping me (or even giving me some hints), I
> can share the code on git. In particular, I know almost nothing on linker
> scripts and startup codes, I copied them from the Atmel Studio ASF
> framework and it worked, but for me it's magic :)
> I don't have a linux programming tool, I compile the code and load the
> ihex from atmel studio on windows using the EDBG chip onboard.
> Bye,
>
> Ugo
>
>
>
> 2014-04-20 20:44 GMT+02:00 Ugo Colesanti :
>
> On 04/20/2014 06:09 PM, Martin Cerveny wrote:
>>
>>> Hello.
>>>
>>> Is there some progress or stable/final/tested code for Atmel newer RF
>>> chips on ZigBit (ATZB) modules ?
>>> Did someone check/test compatibility with previous chip generations ?
>>> Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
>>> And what about ARM Cortex-M0+ CPU (ATSAMR21xxx,
>>> https://code.google.com/p/tinyos-cortex/) ?
>>>
>> We just bought an R21XplainedPro board, we are playing bit with it but
>> with atmel studio only. There is almost no documentation (atmel sent us a
>> very preliminary datasheet). We scheduled to work on a tinyos porting, but
>> with very-low priority. The problem is that we are not familiar with cortex
>> and with arm-gcc in general... if anyone wants to join...
>>
>>
>>
>>> RF:
>>> - AT86RF233 - compatible with RF230 ?
>>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
>>> Some references:
>>> - http://wiesel.ece.utah.edu/projects/10/
>>> - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)
>>>
>>> - AT86RF212B - compatible with RF212 ?
>>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
>>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx
>>>
>>> CPU&RF:
>>> - ATmega256RFR2 - compatible with 128RFA1 ?
>>> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
>>> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx
>>>
>> We are very familiar with RFA1 (we have a custom board based on this
>> chip) and we have a couple of RFR2 bought from dresden elektronik, we
>> didn't had time to focus on RFR2 yet, but it is planned very soon. We can
>> let you know on any updates about this topic (it seems there are few
>> changes in transceiver and ADC modules, for the rest they seem the same).
>>
>>
>>
>>> CPU+RF:
>>> - ATxmega256A3U + AT86RF233
>>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx
>>>
>>> - ATxmega256A3U + AT86RF212B
>>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
>>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx
>>>
>>> Thanks for answers, Martin Cerveny
>>> ___
>>> Tinyos-help mailing list
>>> Tinyos-help@millennium.berkeley.edu
>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>>
>>
>>
>> --
>> Ugo Maria Colesanti
>> Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio
>> Ruberti"
>> Sapienza Universita' di Roma
>> Via Ariosto 25, II floor, room A221
>> 00185, Rome
>> http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-
>> postdoc/4-ugo-colesanti
>> Phone:  +39 06 77274056
>> Fax:+39 06 77274002
>>
>>
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Ugo Maria Colesanti]

Hi all,
it is just to inform that I started the port of the Atmel SamR21Xplained
board. The board has the SamR21 which is a bundle of the SamD21 (cortex
m0+) and AT86RF233 transceiver. I'm using the Linaro gcc 4.8.3 patched
following instructions for the Opal (Sam3u) port (
https://github.com/csiro-wsn/tinyos-csiro-opal).
I started from scratch, hence, there is not that much. I implemented the
GeneralIO and Leds interface, and  wrote two components for managing the
Generic Clock Controller, which selects clock sources and distribute them
in the chip. I briefly tested, using direct register access, the RTC (set
to 32bit mode), Timer/Counter (both, 16 bit and 32 bit), EIC (External
Interrupt Controller) and they seem to work. Now I want to start writing
components implementing Counter,Alarm and Timer interfaces, but I got lost
looking at implementations for MSP430 and RFA1 thus, I think it will take a
little bit for doing that in a clean way. In addition I have one more week
of holidays, then the port will become low-priority again.

If anybody is interested in helping me (or even giving me some hints), I
can share the code on git. In particular, I know almost nothing on linker
scripts and startup codes, I copied them from the Atmel Studio ASF
framework and it worked, but for me it's magic :)
I don't have a linux programming tool, I compile the code and load the ihex
from atmel studio on windows using the EDBG chip onboard.
Bye,

Ugo



2014-04-20 20:44 GMT+02:00 Ugo Colesanti :

> On 04/20/2014 06:09 PM, Martin Cerveny wrote:
>
>> Hello.
>>
>> Is there some progress or stable/final/tested code for Atmel newer RF
>> chips on ZigBit (ATZB) modules ?
>> Did someone check/test compatibility with previous chip generations ?
>> Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
>> And what about ARM Cortex-M0+ CPU (ATSAMR21xxx,
>> https://code.google.com/p/tinyos-cortex/) ?
>>
> We just bought an R21XplainedPro board, we are playing bit with it but
> with atmel studio only. There is almost no documentation (atmel sent us a
> very preliminary datasheet). We scheduled to work on a tinyos porting, but
> with very-low priority. The problem is that we are not familiar with cortex
> and with arm-gcc in general... if anyone wants to join...
>
>
>
>> RF:
>> - AT86RF233 - compatible with RF230 ?
>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
>> Some references:
>> - http://wiesel.ece.utah.edu/projects/10/
>> - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)
>>
>> - AT86RF212B - compatible with RF212 ?
>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
>> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx
>>
>> CPU&RF:
>> - ATmega256RFR2 - compatible with 128RFA1 ?
>> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
>> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx
>>
> We are very familiar with RFA1 (we have a custom board based on this chip)
> and we have a couple of RFR2 bought from dresden elektronik, we didn't had
> time to focus on RFR2 yet, but it is planned very soon. We can let you know
> on any updates about this topic (it seems there are few changes in
> transceiver and ADC modules, for the rest they seem the same).
>
>
>
>> CPU+RF:
>> - ATxmega256A3U + AT86RF233
>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx
>>
>> - ATxmega256A3U + AT86RF212B
>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
>> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx
>>
>> Thanks for answers, Martin Cerveny
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>
>
> --
> Ugo Maria Colesanti
> Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio
> Ruberti"
> Sapienza Universita' di Roma
> Via Ariosto 25, II floor, room A221
> 00185, Rome
> http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-
> postdoc/4-ugo-colesanti
> Phone:  +39 06 77274056
> Fax:+39 06 77274002
>
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 135, Issue 12

[Jisha Mary Jose]

ry Jose
> > ..jMj..
> >
> >
> >
> > On 10 July 2014 13:05, Eric Decker  wrote:
> >
> >
> >
> > asked and answered.
> >
> >
> >
> > The random number generator is pseudo-random.
> >
> >
> >
> > It starts up using a SEED which you need to modify to get different
> > sequences.
> >
> >
> >
> >
> >
> > On Wed, Jul 9, 2014 at 11:52 PM, Jisha Mary Jose <
> jishamary1...@gmail.com>
> > wrote:
> >
> >Hi,
> >
> > I have to generate random number for a node to use in key generation. But
> > i always get the same random number. So ichanged seed value using the
> > current system time as shown below.
> >
> >
> > module SecurityC{
> >
> > uses interface Boot;
> > uses interface Random;
> > uses interface ParameterInit as SeedInit;
> > uses interface Timer;
> > }
> >
> > implementation{
> >
> > uint32_t rand1;
> > uint32_t t;
> >
> > event void Timer.fired() {
> >
> >  t=call Timer.getNow();
> > dbg("Boot", "%s Current time: %d \n", sim_time_string(), t);
> > }
> >
> > event void Boot.booted()
> > {
> >
> > dbg("Boot", "Application booted.\n");
> > t=call Timer.getNow();
> > call SeedInit.init(t);
> >
> > rand1 = (call Random.rand32()%10)+7;
> >
> > dbg("Boot", "%s Random number 1: %d \n", sim_time_string(),
> rand1);
> >
> > }
> > }
> >
> > But still i am getting the same number always. How to solve this?
> >
> > Regards,
> >
> > Jisha Mary Jose
> > ..jMj..
> >
> >
> >
> > ___
> > 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
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20140710/500dfe23/attachment-0001.htm
>
> --
>
> Message: 2
> Date: Fri, 11 Jul 2014 06:14:53 +0530
> From: Jisha Mary Jose 
> Subject: Re: [Tinyos-help] SHA1 error in TOSSIM
> To: Christian Haas ,Tinyos-Help
> ,  Tinyos Help Request
> 
> Message-ID:
> <
> cadnvx9oueqfmwz_-z0cygrwkcq5b-7s-e+cmjpnrov5swc7...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> #include "sha1.h"
>
> module DisseminationC {
>   uses {
> interface SHA1;
> }
> implementation{
>
> void hash(){
>
> uint8_t x=123;
>
> call SHA1.context(context);
> call SHA1.update(context, x, sizeof(x));
> call SHA1.digest(context, Message_Digest[SHA1HashSize]);
>
> dbg("All", "%s Hash is : %d \n", sim_time_string(), Message_Digest);
> }
>
> Here the three functions called are defined in TinyECC-2.0 in SHA1.nc.
>
> This always returns different results for the same input say "123". Am I
> doing it the correct way?
>
> Please help me..
>
>
>
> Regards,
>
> Jisha Mary Jose
> ..jMj..
>
>
> On 10 July 2014 16:08, Christian Haas  wrote:
>
> > On 07/10/2014 12:22 PM, Jisha Mary Jose wrote:
> > > Hi,
> > >
> > > I am using TinyOS-2.1.2 and to achieve security techniques i am using
> > > TinyECC-2.0. I want to use the SHA1 available in tinyecc. But,
> > >
> > > When i take the hash of a value say,
> > >
> > > uint8_t data=123;
> > >
> > > I use the three functions of sha given in SHA1.nc namely, SHA1.reset,
> > > SHA1.update and SHA1.digest to obtain the result. But each time i run
> the
> > > code ie. do "make micaz sim" I get different hash results for the same
> > data.
> > >
> > > How to get a unique hash value for each data taken? Please help me...
> >
> > Post the code please.
> >
> >
> > --
> > Karlsruher Institut f?r Te

Re: [Tinyos-help] TinyOS BLIP - UDPEcho - bursts of duplicate packets

[Srikanth Nori]

e showing
> the same warning. (Ok that's quite reasonable since they were changed in
> a similar way by the blip2-patch) Only telosb didn't (CC2420 anyways).
> (This might be a problem if the MessageBuffers aren't exchanged properly
> or there is no return value?)
>
>
> Static routing -> the same:
> Moreover I have tried to use another scenario with static link routing.
> I have turned off RPL and interfaced the ForwardTable of IPStackC to
> load my routes.
> They were: (3)---(2)---(1)---(PC)
>
> 3:  fec0::3 UDPEcho
> 2:  fec0::2 UDPEcho
> 1:  fec0::1 PPPRouter
> PC: fec0::100 & fec0::
>
> Routing table entries looked like:
>
> -fec0::1/128   fe80::22:ff:fe00:11
> -fec0::3/128   fe80::22:ff:fe00:31
> -fec0::/128fe80::22:ff:fe00:11
>
> for node 2 (as an example).
>
> But I have experienced very similar results.
>
>
> I barely remember I have tried a similar setting with three nodes
> (1)---(2)---(3) with node 1 being a UDP packet sender and the other two
> running UDPEcho. Although without ppprouter, the problems were the same.
>
>
>
> I know, this have been loads of information but I am a bit stressed out.
> I just hope somebody will come up with an idea how to solve this burst
> problem. If you need further data, just request it.
>
>
> Thank you very much in advance
> Jonas
>
>
>
>
>
> ___
> 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Eric Decker]

I started with the Sam code for the CC2520 and ended up chucking the lot
and started from scratch.

I have a well tested CC2520 and CC2520/2591 driver off in the tinyprod code.



On Wed, Apr 23, 2014 at 9:50 AM, András Bíró  wrote:

> That's intresting, we tried to use the SAM3U code on a prototype board,
> but almost nothing worked. No uart, one of the spi bus was broken, no sd
> card. Maybe our SAM3U has different peripherials than yours? I don't have
> much information on this, a colleage of mine worked on it, I just heard him
> complaining.
>
> Andris
>
>
> On Wed, Apr 23, 2014 at 4:26 PM, Thomas Schmid wrote:
>
>> The ARM toolchain doesn't need anything extra for TinyOS. I would suggest
>> not to use the Atmel specific one, but the one from launchpad (
>> https://launchpad.net/gcc-arm-embedded). I moved away from the CodeBench
>> one after they got acquired by Mentor.
>>
>> It really is all about writing drivers for those chips. The port for the
>> SAM3U and SAM3S are pretty good, though they lack a little bit in low-power
>> features (e.g. turning peripherals properly on and off).
>>
>> Cheers,
>>
>> Thomas
>>
>> - Thomas
>>
>>
>>
>> On Wed, Apr 23, 2014 at 4:26 AM, András Bíró wrote:
>>
>>>
>>>
>>>
>>> On Wed, Apr 23, 2014 at 1:08 AM, Thomas Schmid 
>>> wrote:
>>>
 The rf233 driver has been modified and tested, not just renamed. But I
 am not 100% sure if we did all the mods mentioned in that app note.
  On Apr 22, 2014 4:48 PM, "Martin Cerveny"  wrote:

> Hello.
>
> Thanks for answers.
>
> On Tue, 22 Apr 2014, András Bíró wrote:
>
>>   Is there some progress or stable/final/tested code for Atmel
>> newer RF chips on ZigBit (ATZB) modules ?
>> We used the ATZB900 and ATZB24 modules without a problem, with a new
>> platform of course. We dropped the atzb24 in
>> favor of the rfa1, and we dropped the atzb900, because it was very
>> hard to get it in larger quantities, it's
>> expensive, hard to solder on, and we want to use the rfa1's better
>> timer stack.
>>
>
> I am using 
> http://www.an-solutions.de/products/900_mhz.html(mega1281+rf212) and 
> preparing migration to rf212b.
> And original zigbit/meshbeen (mega1281+rf230).
>
>
>>   RF:
>>   - AT86RF233 - compatible with RF230 ?
>>  - Atmel module - http://www.atmel.com/tools/
>> ATZB-RF-233-1-C.aspx
>>  Some references:
>>  - http://wiesel.ece.utah.edu/projects/10/
>>  - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch
>> wiesel)
>>
>> With small modifications:
>> http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-
>> from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
>> The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably
>> more, especially with HWACK.
>>
>
> Is the WIESEL/WREN project driver modified acording to this pdf or
> only "renamed" files & components (Can http://wiesel.ece.utah.edu/answer 
> this question?) ?
>
>
>> I don't know much about xmegas, but they seemed very different from
>> atmegas, so it will probably hard work to make
>> the basic drivers. It's probably doesn't worth it: The ARM based MCUs
>> are much more intresting, and it seems the
>> industry moves towards ARM.
>>
>
> Yes, Xmega is different but it may be possible to implement TinyOS on
> it (with atmel bundles). Yes, ARM (Cortex M0+/M3) is probably right way.
>
> This leads me to new questions:
>
> What is the timeframe of updating https://github.com/tinyos/
> tinyos-main/tree/master/packaging ?
>
> AVR - to newer toolchain to support new devices (TinyOS: AVR binutils
> 2.22 + gcc 4.6.2 + libc 1.8.0) (Atmel: AVR binutils 2.23.2 + gcc 4.8.1 +
> libc 1.8)
> ( http://distribute.atmel.no/tools/opensource/Atmel-AVR-
> GNU-Toolchain/3.4.3/ )
> I do some tests on my Solaris/OpenSolaris platform with some issues
> ( https://github.com/tinyos/tinyos-main/issues/139 ).
>
> I saw discussion @dev, any progress/timeline ?
>

>>> I'm waiting for Miklos' code review to push the needed modifications.
>>> The toolchain itself might came out after 2.1.3, I'm not sure. But after
>>> the modifications, you can use the binaries from atmel - the official
>>> package would be the repackaging of that anyway. I'm really impatiant too,
>>> at least the progmem fixes should be in 2.1.3.
>>>
>>>

> ARM - add & check support for ARM Cortex (not only Atmel)
> (for example http://distribute.atmel.no/tools/opensource/Atmel-ARM-
> GNU-Toolchain/4.7.4/ )
>
> Does ARM toolchain need special patching for TinyOS/nescc ?
>

>>> Thomas Schmid might have better answer for this, he's the developer for
>>> the cortex parts of tinyos. He used CodeBench ARM Toolchain. It works, but
>>> the ARM drivers are in a very early stage

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Thomas Schmid]

The SAM3 family is HUGE! Many chips work slightly different, with different
sets of peripherals. We used the SAM3U-EK kit, and TinyOS worked on there.

I have the SAM3S-EK board too, and that port worked just fine too. Yes,
probably not all peripherals were implemented, but many things were (e.g.
we had a CC2520 hooked up to it).

@Phil: the only common things on the Cortex-M's are the interrupt
controller (NVIC) as well as a system timer. That's what ARM mandates. All
the other peripherals are custom to every chip family. The System Timer
could be used for a simple scheduler, e.g. a default timer. However, it
doesn't have many features. It was intended to be used as a system tick
timer, which TinyOS tries to avoid.

Cheers,

- Thomas



On Wed, Apr 23, 2014 at 11:30 AM, Michiel Konstapel
wrote:

> We're currently using an STM32F373CC [1] on our router/gateway nodes,
> running a very minimal TinyOS port (just GPIO, timer, UART and SPI, no low
> power modes or ADCs yet). Quite nice to work with so far, and excellent
> bang for the buck compared to the big MSP430s if the power consumption is
> no issue.
> Kind regards,
> Michiel
>
> [1] http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1576/LN10/PF253090
>
> > -Original Message-
> > From: tinyos-help-boun...@millennium.berkeley.edu [mailto:tinyos-help-
> > boun...@millennium.berkeley.edu] On Behalf Of Philip Levis
> > Sent: Wednesday, April 23, 2014 18:41
> > To: Thomas Schmid
> > Cc: Tinyos-Help
> > Subject: Re: [Tinyos-help] TinyOS support for Atmel chips on newer
> > ZigBit modules (ATZB)
> >
> > On Apr 23, 2014, at 7:26 AM, Thomas Schmid 
> > wrote:
> >
> > > It really is all about writing drivers for those chips. The port for
> > the SAM3U and SAM3S are pretty good, though they lack a little bit in
> > low-power features (e.g. turning peripherals properly on and off).
> >
> > I'm definitely interested to hear what Cortex M chips people are
> > using/want to use, to see if it's possible to do reasonable chip-
> > independent implementations. I've poked around at the SAM3 code but
> > haven't looked at other chip data sheets to have a sense of how
> > much/what differs, if at all.
> >
> > Phil
> > ___
> > 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Michiel Konstapel]

We're currently using an STM32F373CC [1] on our router/gateway nodes, running a 
very minimal TinyOS port (just GPIO, timer, UART and SPI, no low power modes or 
ADCs yet). Quite nice to work with so far, and excellent bang for the buck 
compared to the big MSP430s if the power consumption is no issue.
Kind regards,
Michiel

[1] http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1576/LN10/PF253090

> -Original Message-
> From: tinyos-help-boun...@millennium.berkeley.edu [mailto:tinyos-help-
> boun...@millennium.berkeley.edu] On Behalf Of Philip Levis
> Sent: Wednesday, April 23, 2014 18:41
> To: Thomas Schmid
> Cc: Tinyos-Help
> Subject: Re: [Tinyos-help] TinyOS support for Atmel chips on newer
> ZigBit modules (ATZB)
> 
> On Apr 23, 2014, at 7:26 AM, Thomas Schmid 
> wrote:
> 
> > It really is all about writing drivers for those chips. The port for
> the SAM3U and SAM3S are pretty good, though they lack a little bit in
> low-power features (e.g. turning peripherals properly on and off).
> 
> I'm definitely interested to hear what Cortex M chips people are
> using/want to use, to see if it's possible to do reasonable chip-
> independent implementations. I've poked around at the SAM3 code but
> haven't looked at other chip data sheets to have a sense of how
> much/what differs, if at all.
> 
> Phil
> ___
> 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Ugo Colesanti]

Talking with Philipp Sommer last year, he told me that the opal mote 
(cortex m3u) was working with the tinyos distribution, despite it has 
not been tested for long periods. Have a look to its github: 
https://github.com/csiro-wsn/tinyos-csiro-opal , maybe it could help.


Ugo

On 04/23/2014 06:50 PM, András Bíró wrote:
That's intresting, we tried to use the SAM3U code on a prototype 
board, but almost nothing worked. No uart, one of the spi bus was 
broken, no sd card. Maybe our SAM3U has different peripherials than 
yours? I don't have much information on this, a colleage of mine 
worked on it, I just heard him complaining.


Andris


On Wed, Apr 23, 2014 at 4:26 PM, Thomas Schmid 
mailto:thomas.sch...@gmail.com>> wrote:


The ARM toolchain doesn't need anything extra for TinyOS. I would
suggest not to use the Atmel specific one, but the one from
launchpad (https://launchpad.net/gcc-arm-embedded). I moved away
from the CodeBench one after they got acquired by Mentor.

It really is all about writing drivers for those chips. The port
for the SAM3U and SAM3S are pretty good, though they lack a little
bit in low-power features (e.g. turning peripherals properly on
and off).

Cheers,

Thomas

- Thomas



On Wed, Apr 23, 2014 at 4:26 AM, András Bíró
mailto:andras.b...@ucmote.com>> wrote:




On Wed, Apr 23, 2014 at 1:08 AM, Thomas Schmid
mailto:thomas.sch...@utah.edu>> wrote:

The rf233 driver has been modified and tested, not just
renamed. But I am not 100% sure if we did all the mods
mentioned in that app note.

On Apr 22, 2014 4:48 PM, "Martin Cerveny"
mailto:mar...@c-home.cz>> wrote:

Hello.

Thanks for answers.

On Tue, 22 Apr 2014, András Bíró wrote:

  Is there some progress or
stable/final/tested code for Atmel newer RF chips
on ZigBit (ATZB) modules ?
We used the ATZB900 and ATZB24 modules without a
problem, with a new platform of course. We dropped
the atzb24 in
favor of the rfa1, and we dropped the atzb900,
because it was very hard to get it in larger
quantities, it's
expensive, hard to solder on, and we want to use
the rfa1's better timer stack.


I am using
http://www.an-solutions.de/products/900_mhz.html
(mega1281+rf212) and preparing migration to rf212b.
And original zigbit/meshbeen (mega1281+rf230).

  RF:
  - AT86RF233 - compatible with RF230 ?
 - Atmel module -
http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
 Some references:
 - http://wiesel.ece.utah.edu/projects/10/
 -
git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git
 (branch
wiesel)

With small modifications:

http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
The problematic parts: PREP_DEEP_SLEEP,
TX_AUTO_CRC_ON, probably more, especially with HWACK.


Is the WIESEL/WREN project driver modified acording to
this pdf or only "renamed" files & components (Can
http://wiesel.ece.utah.edu/ answer this question?) ?

I don't know much about xmegas, but they seemed
very different from atmegas, so it will probably
hard work to make
the basic drivers. It's probably doesn't worth it:
The ARM based MCUs are much more intresting, and
it seems the
industry moves towards ARM.


Yes, Xmega is different but it may be possible to
implement TinyOS on it (with atmel bundles). Yes, ARM
(Cortex M0+/M3) is probably right way.

This leads me to new questions:

What is the timeframe of updating
https://github.com/tinyos/tinyos-main/tree/master/packaging
?

AVR - to newer toolchain to support new devices
(TinyOS: AVR binutils 2.22 + gcc 4.6.2 + libc 1.8.0)
(Atmel: AVR binutils 2.23.2 + gcc 4.8.1 + libc 1.8)
(

http://distribute.atmel.no/tools/opensource/Atmel-AVR-GNU-Toolchain/3.4.3/
)
I do some tests on my Solaris/OpenSolaris platform
with some issues
( ht

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[András Bíró]

That's intresting, we tried to use the SAM3U code on a prototype board, but
almost nothing worked. No uart, one of the spi bus was broken, no sd card.
Maybe our SAM3U has different peripherials than yours? I don't have much
information on this, a colleage of mine worked on it, I just heard him
complaining.

Andris


On Wed, Apr 23, 2014 at 4:26 PM, Thomas Schmid wrote:

> The ARM toolchain doesn't need anything extra for TinyOS. I would suggest
> not to use the Atmel specific one, but the one from launchpad (
> https://launchpad.net/gcc-arm-embedded). I moved away from the CodeBench
> one after they got acquired by Mentor.
>
> It really is all about writing drivers for those chips. The port for the
> SAM3U and SAM3S are pretty good, though they lack a little bit in low-power
> features (e.g. turning peripherals properly on and off).
>
> Cheers,
>
> Thomas
>
> - Thomas
>
>
>
> On Wed, Apr 23, 2014 at 4:26 AM, András Bíró wrote:
>
>>
>>
>>
>> On Wed, Apr 23, 2014 at 1:08 AM, Thomas Schmid wrote:
>>
>>> The rf233 driver has been modified and tested, not just renamed. But I
>>> am not 100% sure if we did all the mods mentioned in that app note.
>>>  On Apr 22, 2014 4:48 PM, "Martin Cerveny"  wrote:
>>>
 Hello.

 Thanks for answers.

 On Tue, 22 Apr 2014, András Bíró wrote:

>   Is there some progress or stable/final/tested code for Atmel
> newer RF chips on ZigBit (ATZB) modules ?
> We used the ATZB900 and ATZB24 modules without a problem, with a new
> platform of course. We dropped the atzb24 in
> favor of the rfa1, and we dropped the atzb900, because it was very
> hard to get it in larger quantities, it's
> expensive, hard to solder on, and we want to use the rfa1's better
> timer stack.
>

 I am using 
 http://www.an-solutions.de/products/900_mhz.html(mega1281+rf212) and 
 preparing migration to rf212b.
 And original zigbit/meshbeen (mega1281+rf230).


>   RF:
>   - AT86RF233 - compatible with RF230 ?
>  - Atmel module - http://www.atmel.com/tools/
> ATZB-RF-233-1-C.aspx
>  Some references:
>  - http://wiesel.ece.utah.edu/projects/10/
>  - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch
> wiesel)
>
> With small modifications:
> http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-
> from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
> The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably more,
> especially with HWACK.
>

 Is the WIESEL/WREN project driver modified acording to this pdf or only
 "renamed" files & components (Can http://wiesel.ece.utah.edu/ answer
 this question?) ?


> I don't know much about xmegas, but they seemed very different from
> atmegas, so it will probably hard work to make
> the basic drivers. It's probably doesn't worth it: The ARM based MCUs
> are much more intresting, and it seems the
> industry moves towards ARM.
>

 Yes, Xmega is different but it may be possible to implement TinyOS on
 it (with atmel bundles). Yes, ARM (Cortex M0+/M3) is probably right way.

 This leads me to new questions:

 What is the timeframe of updating https://github.com/tinyos/
 tinyos-main/tree/master/packaging ?

 AVR - to newer toolchain to support new devices (TinyOS: AVR binutils
 2.22 + gcc 4.6.2 + libc 1.8.0) (Atmel: AVR binutils 2.23.2 + gcc 4.8.1 +
 libc 1.8)
 ( http://distribute.atmel.no/tools/opensource/Atmel-AVR-
 GNU-Toolchain/3.4.3/ )
 I do some tests on my Solaris/OpenSolaris platform with some issues
 ( https://github.com/tinyos/tinyos-main/issues/139 ).

 I saw discussion @dev, any progress/timeline ?

>>>
>> I'm waiting for Miklos' code review to push the needed modifications. The
>> toolchain itself might came out after 2.1.3, I'm not sure. But after the
>> modifications, you can use the binaries from atmel - the official package
>> would be the repackaging of that anyway. I'm really impatiant too, at least
>> the progmem fixes should be in 2.1.3.
>>
>>
>>>
 ARM - add & check support for ARM Cortex (not only Atmel)
 (for example http://distribute.atmel.no/tools/opensource/Atmel-ARM-
 GNU-Toolchain/4.7.4/ )

 Does ARM toolchain need special patching for TinyOS/nescc ?

>>>
>> Thomas Schmid might have better answer for this, he's the developer for
>> the cortex parts of tinyos. He used CodeBench ARM Toolchain. It works, but
>> the ARM drivers are in a very early stage, and nobody seems to working on
>> them. We tried to make an atmel cortex-m3/cortex-m4 based mote, but
>> developing the drivers to a mature state would take a lot of time, so we
>> shelved the plan.
>>
>> Best,
>> Andras Biro
>> http://ucmote.com
>>
>>
 Thanks, M.C>
>>>
>>>
>>
>
___
Tinyos-help mailing list
Tinyos-help@m

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Philip Levis]

On Apr 23, 2014, at 7:26 AM, Thomas Schmid  wrote:

> It really is all about writing drivers for those chips. The port for the 
> SAM3U and SAM3S are pretty good, though they lack a little bit in low-power 
> features (e.g. turning peripherals properly on and off).

I'm definitely interested to hear what Cortex M chips people are using/want to 
use, to see if it's possible to do reasonable chip-independent implementations. 
I've poked around at the SAM3 code but haven't looked at other chip data sheets 
to have a sense of how much/what differs, if at all.

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

Re: [Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Thomas Schmid]

The ARM toolchain doesn't need anything extra for TinyOS. I would suggest
not to use the Atmel specific one, but the one from launchpad (
https://launchpad.net/gcc-arm-embedded). I moved away from the CodeBench
one after they got acquired by Mentor.

It really is all about writing drivers for those chips. The port for the
SAM3U and SAM3S are pretty good, though they lack a little bit in low-power
features (e.g. turning peripherals properly on and off).

Cheers,

Thomas

- Thomas



On Wed, Apr 23, 2014 at 4:26 AM, András Bíró  wrote:

>
>
>
> On Wed, Apr 23, 2014 at 1:08 AM, Thomas Schmid wrote:
>
>> The rf233 driver has been modified and tested, not just renamed. But I am
>> not 100% sure if we did all the mods mentioned in that app note.
>>  On Apr 22, 2014 4:48 PM, "Martin Cerveny"  wrote:
>>
>>> Hello.
>>>
>>> Thanks for answers.
>>>
>>> On Tue, 22 Apr 2014, András Bíró wrote:
>>>
   Is there some progress or stable/final/tested code for Atmel
 newer RF chips on ZigBit (ATZB) modules ?
 We used the ATZB900 and ATZB24 modules without a problem, with a new
 platform of course. We dropped the atzb24 in
 favor of the rfa1, and we dropped the atzb900, because it was very hard
 to get it in larger quantities, it's
 expensive, hard to solder on, and we want to use the rfa1's better
 timer stack.

>>>
>>> I am using http://www.an-solutions.de/products/900_mhz.html(mega1281+rf212) 
>>> and preparing migration to rf212b.
>>> And original zigbit/meshbeen (mega1281+rf230).
>>>
>>>
   RF:
   - AT86RF233 - compatible with RF230 ?
  - Atmel module - http://www.atmel.com/tools/
 ATZB-RF-233-1-C.aspx
  Some references:
  - http://wiesel.ece.utah.edu/projects/10/
  - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch
 wiesel)

 With small modifications:
 http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-
 from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
 The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably more,
 especially with HWACK.

>>>
>>> Is the WIESEL/WREN project driver modified acording to this pdf or only
>>> "renamed" files & components (Can http://wiesel.ece.utah.edu/ answer
>>> this question?) ?
>>>
>>>
 I don't know much about xmegas, but they seemed very different from
 atmegas, so it will probably hard work to make
 the basic drivers. It's probably doesn't worth it: The ARM based MCUs
 are much more intresting, and it seems the
 industry moves towards ARM.

>>>
>>> Yes, Xmega is different but it may be possible to implement TinyOS on it
>>> (with atmel bundles). Yes, ARM (Cortex M0+/M3) is probably right way.
>>>
>>> This leads me to new questions:
>>>
>>> What is the timeframe of updating https://github.com/tinyos/
>>> tinyos-main/tree/master/packaging ?
>>>
>>> AVR - to newer toolchain to support new devices (TinyOS: AVR binutils
>>> 2.22 + gcc 4.6.2 + libc 1.8.0) (Atmel: AVR binutils 2.23.2 + gcc 4.8.1 +
>>> libc 1.8)
>>> ( http://distribute.atmel.no/tools/opensource/Atmel-AVR-
>>> GNU-Toolchain/3.4.3/ )
>>> I do some tests on my Solaris/OpenSolaris platform with some issues
>>> ( https://github.com/tinyos/tinyos-main/issues/139 ).
>>>
>>> I saw discussion @dev, any progress/timeline ?
>>>
>>
> I'm waiting for Miklos' code review to push the needed modifications. The
> toolchain itself might came out after 2.1.3, I'm not sure. But after the
> modifications, you can use the binaries from atmel - the official package
> would be the repackaging of that anyway. I'm really impatiant too, at least
> the progmem fixes should be in 2.1.3.
>
>
>>
>>> ARM - add & check support for ARM Cortex (not only Atmel)
>>> (for example http://distribute.atmel.no/tools/opensource/Atmel-ARM-
>>> GNU-Toolchain/4.7.4/ )
>>>
>>> Does ARM toolchain need special patching for TinyOS/nescc ?
>>>
>>
> Thomas Schmid might have better answer for this, he's the developer for
> the cortex parts of tinyos. He used CodeBench ARM Toolchain. It works, but
> the ARM drivers are in a very early stage, and nobody seems to working on
> them. We tried to make an atmel cortex-m3/cortex-m4 based mote, but
> developing the drivers to a mature state would take a lot of time, so we
> shelved the plan.
>
> Best,
> Andras Biro
> http://ucmote.com
>
>
>>> Thanks, 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[András Bíró]

On Wed, Apr 23, 2014 at 1:08 AM, Thomas Schmid wrote:

> The rf233 driver has been modified and tested, not just renamed. But I am
> not 100% sure if we did all the mods mentioned in that app note.
>  On Apr 22, 2014 4:48 PM, "Martin Cerveny"  wrote:
>
>> Hello.
>>
>> Thanks for answers.
>>
>> On Tue, 22 Apr 2014, András Bíró wrote:
>>
>>>   Is there some progress or stable/final/tested code for Atmel newer
>>> RF chips on ZigBit (ATZB) modules ?
>>> We used the ATZB900 and ATZB24 modules without a problem, with a new
>>> platform of course. We dropped the atzb24 in
>>> favor of the rfa1, and we dropped the atzb900, because it was very hard
>>> to get it in larger quantities, it's
>>> expensive, hard to solder on, and we want to use the rfa1's better timer
>>> stack.
>>>
>>
>> I am using http://www.an-solutions.de/products/900_mhz.html(mega1281+rf212) 
>> and preparing migration to rf212b.
>> And original zigbit/meshbeen (mega1281+rf230).
>>
>>
>>>   RF:
>>>   - AT86RF233 - compatible with RF230 ?
>>>  - Atmel module - http://www.atmel.com/tools/
>>> ATZB-RF-233-1-C.aspx
>>>  Some references:
>>>  - http://wiesel.ece.utah.edu/projects/10/
>>>  - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch
>>> wiesel)
>>>
>>> With small modifications:
>>> http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-
>>> from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
>>> The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably more,
>>> especially with HWACK.
>>>
>>
>> Is the WIESEL/WREN project driver modified acording to this pdf or only
>> "renamed" files & components (Can http://wiesel.ece.utah.edu/ answer
>> this question?) ?
>>
>>
>>> I don't know much about xmegas, but they seemed very different from
>>> atmegas, so it will probably hard work to make
>>> the basic drivers. It's probably doesn't worth it: The ARM based MCUs
>>> are much more intresting, and it seems the
>>> industry moves towards ARM.
>>>
>>
>> Yes, Xmega is different but it may be possible to implement TinyOS on it
>> (with atmel bundles). Yes, ARM (Cortex M0+/M3) is probably right way.
>>
>> This leads me to new questions:
>>
>> What is the timeframe of updating https://github.com/tinyos/
>> tinyos-main/tree/master/packaging ?
>>
>> AVR - to newer toolchain to support new devices (TinyOS: AVR binutils
>> 2.22 + gcc 4.6.2 + libc 1.8.0) (Atmel: AVR binutils 2.23.2 + gcc 4.8.1 +
>> libc 1.8)
>> ( http://distribute.atmel.no/tools/opensource/Atmel-AVR-
>> GNU-Toolchain/3.4.3/ )
>> I do some tests on my Solaris/OpenSolaris platform with some issues
>> ( https://github.com/tinyos/tinyos-main/issues/139 ).
>>
>> I saw discussion @dev, any progress/timeline ?
>>
>
I'm waiting for Miklos' code review to push the needed modifications. The
toolchain itself might came out after 2.1.3, I'm not sure. But after the
modifications, you can use the binaries from atmel - the official package
would be the repackaging of that anyway. I'm really impatiant too, at least
the progmem fixes should be in 2.1.3.


>
>> ARM - add & check support for ARM Cortex (not only Atmel)
>> (for example http://distribute.atmel.no/tools/opensource/Atmel-ARM-
>> GNU-Toolchain/4.7.4/ )
>>
>> Does ARM toolchain need special patching for TinyOS/nescc ?
>>
>
Thomas Schmid might have better answer for this, he's the developer for the
cortex parts of tinyos. He used CodeBench ARM Toolchain. It works, but the
ARM drivers are in a very early stage, and nobody seems to working on them.
We tried to make an atmel cortex-m3/cortex-m4 based mote, but developing
the drivers to a mature state would take a lot of time, so we shelved the
plan.

Best,
Andras Biro
http://ucmote.com


>> Thanks, 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Martin Cerveny]

Hello.

Thanks for answers.

On Tue, 22 Apr 2014, András Bíró wrote:

  Is there some progress or stable/final/tested code for Atmel newer RF 
chips on ZigBit (ATZB) modules ?
We used the ATZB900 and ATZB24 modules without a problem, with a new platform 
of course. We dropped the atzb24 in
favor of the rfa1, and we dropped the atzb900, because it was very hard to get 
it in larger quantities, it's
expensive, hard to solder on, and we want to use the rfa1's better timer stack.


I am using http://www.an-solutions.de/products/900_mhz.html 
(mega1281+rf212) and preparing migration to rf212b.

And original zigbit/meshbeen (mega1281+rf230).
  

  RF:
  - AT86RF233 - compatible with RF230 ?
     - Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
     Some references:
     - http://wiesel.ece.utah.edu/projects/10/
     - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)

With small modifications:
http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably more, 
especially with HWACK.


Is the WIESEL/WREN project driver modified acording to this pdf or only 
"renamed" files & components (Can http://wiesel.ece.utah.edu/ answer this question?) ?

  

I don't know much about xmegas, but they seemed very different from atmegas, so 
it will probably hard work to make
the basic drivers. It's probably doesn't worth it: The ARM based MCUs are much 
more intresting, and it seems the
industry moves towards ARM.


Yes, Xmega is different but it may be possible to implement TinyOS on it (with atmel bundles). 
Yes, ARM (Cortex M0+/M3) is probably right way.


This leads me to new questions:

What is the timeframe of updating 
https://github.com/tinyos/tinyos-main/tree/master/packaging ?

AVR - to newer toolchain to support new devices (TinyOS: AVR binutils 2.22 
+ gcc 4.6.2 + libc 1.8.0) (Atmel: AVR binutils 2.23.2 + gcc 4.8.1 + libc 1.8)

( http://distribute.atmel.no/tools/opensource/Atmel-AVR-GNU-Toolchain/3.4.3/ )
I do some tests on my Solaris/OpenSolaris platform with some issues
( https://github.com/tinyos/tinyos-main/issues/139 ).

I saw discussion @dev, any progress/timeline ?

ARM - add & check support for ARM Cortex (not only Atmel)
(for example 
http://distribute.atmel.no/tools/opensource/Atmel-ARM-GNU-Toolchain/4.7.4/ )

Does ARM toolchain need special patching for TinyOS/nescc ?

Thanks, 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[András Bíró]

Hi Martin,


On Sun, Apr 20, 2014 at 6:09 PM, Martin Cerveny  wrote:

> Hello.
>
> Is there some progress or stable/final/tested code for Atmel newer RF
> chips on ZigBit (ATZB) modules ?
>

We used the ATZB900 and ATZB24 modules without a problem, with a new
platform of course. We dropped the atzb24 in favor of the rfa1, and we
dropped the atzb900, because it was very hard to get it in larger
quantities, it's expensive, hard to solder on, and we want to use the
rfa1's better timer stack.


> Did someone check/test compatibility with previous chip generations ?
> Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
> And what about ARM Cortex-M0+ CPU (ATSAMR21xxx,
> https://code.google.com/p/tinyos-cortex/) ?
>
> RF:
> - AT86RF233 - compatible with RF230 ?
>- Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
>Some references:
>- http://wiesel.ece.utah.edu/projects/10/
>- git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)
>
>
With small modifications:
http://www.atmel.com/ja/jp/Images/Atmel-42198-Migration-from-AT86RF230-to-AT86RF233_AP-Note_AT02601.pdf
The problematic parts: PREP_DEEP_SLEEP, TX_AUTO_CRC_ON, probably more,
especially with HWACK.


> - AT86RF212B - compatible with RF212 ?
>- Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
>- Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx
>

Probably will work, but obviously wont use new features.
http://www.atmel.com/Images/Atmel-42178-Migration-from-AT86RF212-to-AT86RF212B_AP-Note_AT02598.pdf
Didn't found any problematic part.

>
> CPU&RF:
> - ATmega256RFR2 - compatible with 128RFA1 ?
>- Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
>- Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx
>
>
Unfortunatelly there's no migration guide, but it is indeed very similar.
I've gone through the datasheet, and the only compatibility breaking
modification I found was in the ADC. But, you need compiler support, which
is - as far as I know - only in the official atmel AVR toolchain. I have
some modified ucprotonb with 256rfr2, and I'm working on the compiler, it
will probably work soon. Oh, and all RFR2s are the same, the difference is
only the amount of RAM/ROM (64/128/256), and/or the pinout (128 vs 1284,
etc), so all of them should work at the same time.


> CPU+RF:
> - ATxmega256A3U + AT86RF233
>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx
>
> - ATxmega256A3U + AT86RF212B
>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx
>
>
I don't know much about xmegas, but they seemed very different from
atmegas, so it will probably hard work to make the basic drivers. It's
probably doesn't worth it: The ARM based MCUs are much more intresting, and
it seems the industry moves towards ARM.

Best,
Andras Biro
http://ucmote.com



> Thanks for answers, Martin Cerveny
> _______
> 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Philip Levis]

I'm very interested in incorporating support for the newer Atmel chips in the 
main tree. Cortex M3 is also a priority, but given the diversity of chips I 
want to take a look at the space and figure out which we should focus on.

Phil




On Apr 20, 2014, at 11:44 AM, Ugo Colesanti  wrote:

> On 04/20/2014 06:09 PM, Martin Cerveny wrote:
>> Hello.
>> 
>> Is there some progress or stable/final/tested code for Atmel newer RF chips 
>> on ZigBit (ATZB) modules ?
>> Did someone check/test compatibility with previous chip generations ?
>> Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
>> And what about ARM Cortex-M0+ CPU (ATSAMR21xxx, 
>> https://code.google.com/p/tinyos-cortex/) ?
> We just bought an R21XplainedPro board, we are playing bit with it but 
> with atmel studio only. There is almost no documentation (atmel sent us 
> a very preliminary datasheet). We scheduled to work on a tinyos porting, 
> but with very-low priority. The problem is that we are not familiar with 
> cortex and with arm-gcc in general... if anyone wants to join...
> 
>> 
>> RF:
>> - AT86RF233 - compatible with RF230 ?
>>- Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
>>Some references:
>>- http://wiesel.ece.utah.edu/projects/10/
>>- git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)
>> 
>> - AT86RF212B - compatible with RF212 ?
>>- Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
>>- Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx
>> 
>> CPU&RF:
>> - ATmega256RFR2 - compatible with 128RFA1 ?
>>- Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
>>- Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx
> We are very familiar with RFA1 (we have a custom board based on this 
> chip) and we have a couple of RFR2 bought from dresden elektronik, we 
> didn't had time to focus on RFR2 yet, but it is planned very soon. We 
> can let you know on any updates about this topic (it seems there are few 
> changes in transceiver and ADC modules, for the rest they seem the same).
> 
>> 
>> CPU+RF:
>> - ATxmega256A3U + AT86RF233
>>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx
>> 
>> - ATxmega256A3U + AT86RF212B
>>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
>>- Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx
>> 
>> Thanks for answers, Martin Cerveny
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 
> 
> -- 
> Ugo Maria Colesanti
> Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio 
> Ruberti"
> Sapienza Universita' di Roma
> Via Ariosto 25, II floor, room A221
> 00185, Rome
> http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-postdoc/4-ugo-colesanti
> Phone:  +39 06 77274056
> Fax:+39 06 77274002
> 
> ___
> 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] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Ugo Colesanti]

On 04/20/2014 06:09 PM, Martin Cerveny wrote:
> Hello.
>
> Is there some progress or stable/final/tested code for Atmel newer RF chips 
> on ZigBit (ATZB) modules ?
> Did someone check/test compatibility with previous chip generations ?
> Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
> And what about ARM Cortex-M0+ CPU (ATSAMR21xxx, 
> https://code.google.com/p/tinyos-cortex/) ?
We just bought an R21XplainedPro board, we are playing bit with it but 
with atmel studio only. There is almost no documentation (atmel sent us 
a very preliminary datasheet). We scheduled to work on a tinyos porting, 
but with very-low priority. The problem is that we are not familiar with 
cortex and with arm-gcc in general... if anyone wants to join...

>
> RF:
> - AT86RF233 - compatible with RF230 ?
> - Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
> Some references:
> - http://wiesel.ece.utah.edu/projects/10/
> - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)
>
> - AT86RF212B - compatible with RF212 ?
> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
> - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx
>
> CPU&RF:
> - ATmega256RFR2 - compatible with 128RFA1 ?
> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
> - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx
We are very familiar with RFA1 (we have a custom board based on this 
chip) and we have a couple of RFR2 bought from dresden elektronik, we 
didn't had time to focus on RFR2 yet, but it is planned very soon. We 
can let you know on any updates about this topic (it seems there are few 
changes in transceiver and ADC modules, for the rest they seem the same).

>
> CPU+RF:
> - ATxmega256A3U + AT86RF233
> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx
>
> - ATxmega256A3U + AT86RF212B
> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
> - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx
>
> Thanks for answers, Martin Cerveny
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


-- 
Ugo Maria Colesanti
Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio 
Ruberti"
Sapienza Universita' di Roma
Via Ariosto 25, II floor, room A221
00185, Rome
http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-postdoc/4-ugo-colesanti
Phone:  +39 06 77274056
Fax:+39 06 77274002

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

[Tinyos-help] TinyOS support for Atmel chips on newer ZigBit modules (ATZB)

[Martin Cerveny]

Hello.

Is there some progress or stable/final/tested code for Atmel newer RF chips on 
ZigBit (ATZB) modules ?
Did someone check/test compatibility with previous chip generations ?
Is there some TinyOS implementation with XMega CPU (ATxmegaxxx) ?
And what about ARM Cortex-M0+ CPU (ATSAMR21xxx, 
https://code.google.com/p/tinyos-cortex/) ?

RF:
- AT86RF233 - compatible with RF230 ?
   - Atmel module - http://www.atmel.com/tools/ATZB-RF-233-1-C.aspx
   Some references:
   - http://wiesel.ece.utah.edu/projects/10/
   - git://wiesel.ece.utah.edu/tinyos/tinyos-prod.git (branch wiesel)

- AT86RF212B - compatible with RF212 ?
   - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-U.aspx
   - Atmel module - http://www.atmel.com/tools/ATZB-RF-212B-0-CN.aspx

CPU&RF:
- ATmega256RFR2 - compatible with 128RFA1 ?
   - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-U.aspx
   - Atmel module - http://www.atmel.com/tools/ATZB-S1-256-3-0-C.aspx

CPU+RF:
- ATxmega256A3U + AT86RF233
   - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-3-0-C.aspx

- ATxmega256A3U + AT86RF212B
   - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-U.aspx
   - Atmel module - http://www.atmel.com/tools/ATZB-X0-256-4-0-CN.aspx

Thanks for answers, Martin Cerveny
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TinyOS 2.1.3, packages, and repository

[Philip Levis]

So it looks like tinyprod is down and won't be coming back up. I'm going to 
move TinyOS and its support packages (e.g., msp430-46) back to being hosted at 
tinyos.stanford.edu. In part, this means I'd like to package up version 2.1.3 
of TinyOS.

If anyone would like to help with the packaging and maintenance of the 
repository, please drop me a line (p...@cs.stanford.edu), I'd of course 
appreciate help. My plan is to start working on this in May and have a release 
ready by mid-June. I've started an issue on tinyos-main so we can come up with 
a to-do list of what to pull into the main repository (and issues to address) 
for 2.1.3 under that timeframe.

Phil





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

Re: [Tinyos-help] Tinyos-help Digest, Vol 131, Issue 33

[Sajithvariyar V V]

ivileged users.
>
> Regards
> Michael
>
>
> On 31 March 2014 09:24, Liao Qingbi  wrote:
>
> > Hi, everybody
> >
> > I'm new to TinyOS and trying to write the simple Blink application into
> > sensor mib510.  But I didn't succeed yet since there is always an error:
> > Permission denied.
> > I have already tried the command:
> > $ sudo chown qingbi:qingbi -R /opt/tinyos-2.1.2/
> > And it still doesn't work.
> > By the way, the *make micaz sim* part could work well in my PC.
> > The running result is attached below, hoping someone could help me out.
> > Thank you so much.
> >
> > qingbi@qingbi-VirtualBox:~$ cd tinyos-2.1.2/apps/Blink/
> > qingbi@qingbi-VirtualBox:~/tinyos-2.1.2/apps/Blink$ make micaz install
> > mib510,/dev/ttyUSB0
> > mkdir -p build/micaz
> > compiling BlinkAppC to a micaz binary
> > ncc -o build/micaz/main.exe  -Os -fnesc-separator=__ -Wall -Wshadow
> > -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb
> > -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10
> > -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"qingbi\"
> > -DIDENT_HOSTNAME=\"qingbi-VirtualB\" -DIDENT_USERHASH=0xdca414e2L
> > -DIDENT_TIMESTAMP=0x53399425L -DIDENT_UIDHASH=0x1fc3b583L
> > -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())'
> > -fnesc-dump='referenced(interfacedefs, components)'
> > -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm
> > compiled BlinkAppC to build/micaz/main.exe
> > 2044 bytes in ROM
> >   51 bytes in RAM
> > avr-objcopy --output-target=srec build/micaz/main.exe
> build/micaz/main.srec
> > avr-objcopy --output-target=ihex build/micaz/main.exe
> build/micaz/main.ihex
> > writing TOS image
> > cp build/micaz/main.srec build/micaz/main.srec.out
> > installing micaz binary using mib510
> > uisp -dprog=mib510 -dserial=/dev/ttyUSB0 --wr_fuse_h=0xd9
> -dpart=ATmega128
> >  --wr_fuse_e=ff   --erase --upload if=build/micaz/main.srec.out --verify
> > Error: Permission denied
> >  -> /dev/ttyUSB0
> > make: *** [program] Error 1
> >
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@millennium.berkeley.edu
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20140331/d1a7310a/attachment-0001.htm
>
> --
>
> Message: 4
> Date: Mon, 31 Mar 2014 13:32:21 -0300
> From: Guilherme Politta 
> Subject: Re: [Tinyos-help] make micaz install, permission denied
> To: Michael Andersen 
> Cc: Liao Qingbi , tinyos forum
> 
> Message-ID:
>  e...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> For a quick fix use:
>
> chmod 777 /dev/ttyUSB0
>
>
>
>
> 2014-03-31 13:28 GMT-03:00 Michael Andersen :
>
> > Hi
> >
> > This is due to a lack of permissions on the USB serial device. The quick
> > hack is to program as root, the correct solution is to set up your udev
> > rules so that the permissions on the ttyUSB device allow writing by
> > unprivileged users.
> >
> > Regards
> > Michael
> >
> >
> > On 31 March 2014 09:24, Liao Qingbi  wrote:
> >
> >> Hi, everybody
> >>
> >> I'm new to TinyOS and trying to write the simple Blink application into
> >> sensor mib510.  But I didn't succeed yet since there is always an error:
> >> Permission denied.
> >> I have already tried the command:
> >> $ sudo chown qingbi:qingbi -R /opt/tinyos-2.1.2/
> >> And it still doesn't work.
> >> By the way, the *make micaz sim* part could work well in my PC.
> >> The running result is attached below, hoping someone could help me out.
> >> Thank you so much.
> >>
> >> qingbi@qingbi-VirtualBox:~$ cd tinyos-2.1.2/apps/Blink/
> >> qingbi@qingbi-VirtualBox:~/tinyos-2.1.2/apps/Blink$ make micaz install
> >> mib510,/dev/ttyUSB0
> >> mkdir -p build/micaz
> >> compiling BlinkAppC to a micaz binary
> >> ncc -o build/micaz/main.exe  -Os -fnesc-separator=__ -Wall -Wshadow
> >> -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb
> >> -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10
> >> -DIDENT_A

[Tinyos-help] TinyOS Installation fails due to 'nesc' (and all other ways too fail !)

[Sabniveesu Shashank]

Hi

1) I am unable to install TinyOS after following all the instructions from
the web page:
   [Same error as in the case below] Also I am unable to resolve the issue
of 'public key'

2) Following  -- Slightly different instructions from this
link,
I could add appropriate public keys but still receive the same error as in
previous case, during installation:

Unpacking nescc (from .../nescc_1.3.4-2_i386.deb) ...
> dpkg: error processing /var/cache/apt/archives/nescc_1.3.4-2_i386.deb
> (--unpack):
>  trying to overwrite '/usr/bin/nescc-wiring', which is also in package
> nesc 1.3.3-20110821
>

3) I did clean up my system and did a 'build from source' which throws up
too many 'Not Found/Unbuilt' warnings when 'make ' is run on any example in
'apps' directory

Please respond

Thanks
Shashank

We've created the greatest collection of shared knowledge in history. Help
protect Wikipedia. Donate now: https://donate.wikimedia.org
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] tinyos build problem which is making nesdoc documents(doc/nesdoc/platform)?

[taehee Park]

i am a newcommer with tinyos and have a problem with making some documents.

i could write this command like "make micaz docs" in the apps/Sense Folder
then documents with micaz platporm could be created in the doc/nesdoc/micaz
folder
i've already check with this.

but i am working with cc2530 MCU(Texas Instrument), but atually i will work
on CC2538 later
this time i am studing with CC2530. and i want to make documents like micaz
platform.
but i could not make those document with this cc2538 platform.

the sources with CC2530 are obtained below address
 address http://code.google.com/p/tinyv6/

i write like this "make cc2530 docs" in the apps/UdpEchoServer folder
then i got this error message like below

  Couldn't access nesdoc repository

what does this message mean?  genhtml.py problem?

is there anyone who help me with this problem?


 full log message

Making documentation for UdpEchoServerAppC on cc2530
nesdoc -o /home/thpark/tinyOS/exercise-tinyos/doc/nesdoc  -D__cc2530__=1
-I/home/thpark/tinyOS/exercise-tinyos/support/make/cc2530/inc
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/preinc
-DTOSH_DATA_LENGTH=102 -DIPV6_ADDR_PREFIX_0=0x2001
-DIPV6_ADDR_PREFIX_1=0x0250 -DIPV6_ADDR_PREFIX_2=0x1004
-DIPV6_ADDR_PREFIX_3=0x5020 -DIDENT_APPNAME=\"UdpEchoServerAp\"
-DIDENT_USERNAME=\"thpark\" -DIDENT_HOSTNAME=\"VirtualBox\"
-DIDENT_USERHASH=0xe7466ee3L -DIDENT_TIMESTAMP=0x53245422L
-DIDENT_UIDHASH=0x28bac233L -U__BLOCKS__ -fnesc-include=deputy_nodeputy
-fnesc-include=nesc_nx -fnesc-include=tos -fnesc-separator=__  -DNESC=134
-Wnesc-all -DPLATFORM_CC2530
-I/home/thpark/tinyOS/exercise-tinyos/tos/platforms/cc2530
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/radio
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/timer
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/uart
-I/home/thpark/tinyOS/exercise-tinyos/tos/chips/cc2530/adc
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/rfxlink/layers
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/rfxlink/util
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/timer
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/serial
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/net
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/net/ctp
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/net/4bitle
-I/home/thpark/tinyOS/exercise-tinyos/tos/lib/net/tinyv6
-I/home/thpark/tinyOS/exercise-tinyos/tos/interfaces
-I/home/thpark/tinyOS/exercise-tinyos/tos/types
-I/home/thpark/tinyOS/exercise-tinyos/tos/system -fnesc-no-debug
-fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask
UdpEchoServerAppC.nc
interface CC2530DriverConfig (tos.chips.cc2530.radio.CC2530DriverConfig)
interface RootControl (tos.lib.net.RootControl)
interface ResourceRequested (tos.interfaces.ResourceRequested)
interface BusyWait (tos.lib.timer.BusyWait)
interface RadioCCA (tos.lib.rfxlink.util.RadioCCA)
interface SplitControl (tos.interfaces.SplitControl)
interface ResourceConfigure (tos.interfaces.ResourceConfigure)
interface DummyConfig (tos.lib.rfxlink.layers.DummyConfig)
interface CollectionDebug (tos.lib.net.CollectionDebug)
interface CollectionPacket (tos.lib.net.CollectionPacket)
interface PacketTimeStamp (tos.interfaces.PacketTimeStamp)
interface LinkEstimator (tos.lib.net.4bitle.LinkEstimator)
interface TrafficMonitorConfig (tos.lib.rfxlink.layers.TrafficMonitorConfig)
interface ActiveMessageConfig (tos.lib.rfxlink.layers.ActiveMessageConfig)
interface CtpRoutingPacket (tos.lib.net.ctp.CtpRoutingPacket)
interface Boot (tos.interfaces.Boot)
interface SendNotifier (tos.interfaces.SendNotifier)
interface PacketField (tos.lib.rfxlink.util.PacketField)
interface Pool (tos.interfaces.Pool)
interface TaskBasic (tos.interfaces.TaskBasic)
interface NeighborhoodFlag (tos.lib.rfxlink.util.NeighborhoodFlag)
interface SlottedCollisionConfig
(tos.lib.rfxlink.layers.SlottedCollisionConfig)
interface RadioAlarm (tos.lib.rfxlink.util.RadioAlarm)
interface LocalTime (tos.lib.timer.LocalTime)
interface Intercept (tos.interfaces.Intercept)
interface Packet (tos.interfaces.Packet)
interface RadioState (tos.lib.rfxlink.util.RadioState)
interface Queue (tos.interfaces.Queue)
interface AMSend (tos.interfaces.AMSend)
interface Neighborhood (tos.lib.rfxlink.util.Neighborhood)
interface Ieee154Packet (tos.interfaces.Ieee154Packet)
interface Random (tos.interfaces.Random)
interface RadioPacket (tos.lib.rfxlink.util.RadioPacket)
interface Send (tos.interfaces.Send)
interface CsmaConfig (tos.lib.rfxlink.layers.CsmaConfig)
interface Cache (tos.interfaces.Cache)
interface LowPowerListening (tos.interfaces.LowPowerListening)
interface CtpInfo (tos.lib.net.ctp.CtpInfo)
interface ActiveMessageAddress (tos.interfaces.ActiveMessageAddress)
interface RadioReceive (tos.lib.rfxlink.util.RadioReceive)
interface Ieee154PacketLayer (tos.lib.rfxlink.layers.Ieee154PacketLayer)
interface SoftwareAckConfig (tos.lib.rfxli

Re: [Tinyos-help] Tinyos-help Digest, Vol 131, Issue 6

[He Dajiang (I2R)]

i think you should take a look at the mcu manual.

From: tinyos-help-boun...@millennium.berkeley.edu 
[tinyos-help-boun...@millennium.berkeley.edu] on behalf of 
tinyos-help-requ...@millennium.berkeley.edu 
[tinyos-help-requ...@millennium.berkeley.edu]
Sent: Wednesday, 5 March, 2014 4:00:01 AM
To: tinyos-help@millennium.berkeley.edu
Subject: Tinyos-help Digest, Vol 131, Issue 6

Send Tinyos-help mailing list submissions to
tinyos-help@millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
tinyos-help-requ...@millennium.berkeley.edu

You can reach the person managing the list at
tinyos-help-ow...@millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Re: Tinyos-help Digest, Vol 121, Issue 7 (sofia aparicio)


--

Message: 1
Date: Tue, 4 Mar 2014 13:40:54 +0100
From: sofia aparicio 
Subject: Re: [Tinyos-help] Tinyos-help Digest, Vol 121, Issue 7
To: "tinyos-help@millennium.berkeley.edu"

Message-ID: 
Content-Type: text/plain; charset="iso-8859-1"

Hello,

I would like to compute the battery level of my iris mote. I am using the 
function VoltageC of mica. I would like to know the conversion formula from ADC 
readings to Voltios for IRIS motes. It seems that it is not the same that for 
mica motes.

Thank you very much.

Yours,

Sofia



-- next part --
An HTML attachment was scrubbed...
URL: 
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20140304/de90a5ec/attachment-0001.htm

--

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

End of Tinyos-help Digest, Vol 131, Issue 6
***

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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos-help Digest, Vol 121, Issue 7

[sofia aparicio]

Hello,

I would like to compute the battery level of my iris mote. I am using the 
function VoltageC of mica. I would like to know the conversion formula from ADC 
readings to Voltios for IRIS motes. It seems that it is not the same that for 
mica motes.

Thank you very much.

Yours,

Sofia


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

Re: [Tinyos-help] TinyOS TestPromiciuos not Receiving the XBee packet

[Bipin]

Hello  sir,
   i   just  flash  the  XBee  IEEE 802.15.4  Firmwire  on  the  XBee 
device  ,  so  i  can   commuicate  with  the  tkn15.4 stack  enabled 
TinyOS  device.Now  its  just  simple   wireless  communication  between 
two  devices. And  i  got  one  packet  from  the  XBee  device   and  its 
a  *Beacon  packet*.  I  dont  know  you  are  done  this  way  or  not...
Just  google  it...  you  can  get  lot  of  information  about  it...  



--
View this message in context: 
http://tinyos-help.10906.n7.nabble.com/TinyOS-TestPromiciuos-not-Receiving-the-XBee-packet-tp23845p24123.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