HW wiki - User contributions [en]

Parkinsons disease monitoring project

2007-09-13T23:40:11Z

Auersm1:

<div style="background-color: #DCDDF6; width:200px; border: solid #BA0000 1px; float: right; padding: 1em; margin-top: 4em; margin-right: 2em; margin-left: 2em">

Aktuální práce - úkoly v sekci "Tasks"

</div>

== '''Project definition''' ==
Wireless sensor motes placed on limbs (legs, arms) transmit periodically measured data to a central node for storing and evaluation. Once a day (or in predefined period) data from central node is downloaded to PC or PDA for analysis and computation of feedback in the form of brain stimulation or appropriate dose of medicine. 
Central node stores received data from wireless sensor motes with time stamps to embedded memory card (MMC, SD, CF or similar). Central node consists of 802.15.4/ZigBee radio chip, MCU and memory card. Central node can be wear on belt therefore its size is not so important. Wireless sensor mote includes 802.15.4/ZigBee radio chip, MCU and accelerometer and should be worn on wrist similar a watch is weared. This motes should be as small as possible.
 
[http://rtime.felk.cvut.cz/hw/images/e/e1/Spec_ParkinsonsDisease.pdf Project specification link]
 
<CENTER>[[Image:Body.png]]</CENTER>

== '''Developing phase''' ==

 
=== Extension boards with accelerometers ===

PCB design was created in OrCAD 10.3. PCB was made by firm Pragoboard (PCB producer) and soldered manually. 

*'''Analog accelerometer MMA7260Q (Freescale)''' 
: 3-Axis, selectable sensitivity 1.5g/2g/4g/6g, low current consumption 500 μA, low voltage operation 2.2V-3.6V, high sensitivity (800mV/g @1.5g) 
[[Image:telosb&MMA.jpg]] 

*'''Digital accelerometer LIS3LV02DQ (ST)''' 
: 3-Axis, selectable sensitivity 2g/6g, 2.16V-3.6V single supply operation, 1.8V compatible IOs, I2C/SPI digital output interfaces, programable 12 or 16bit data representation 
[[Image:telosb&LIS.jpg]]

 
=== Application DataSendAccel ===

Program for the Tmote Sky module with the accelerometer's extension board is developed by using TinyOS/nesC and open-ZB protocol stack designed at Polytechnical Institute of Porto. 
Program is based on the example application DataSendExample (created by André Cunha). The devices already have a short address meaning they are associated with the PAN coordinator. It's possible to associate three devices with accelerometer's extension board. 
Sensor's data are read, processed and send via IEEE 802.15.4 protocol during the CAP period using the CSMA/CA in data frame of packet. Coordinator receives and processes packet, sensor's data places in data frame of TinyOS message and the message send over the USB to computer. By means of drivers "USB to serial comm port" we can read data from USB as well as from serial port. 

'''TinyOS files:''' 
: ''datasendaccel.h'' - definitions and variables 
: ''DataSendAccel.nc'' - the configuration component, file containing the top-level configuration 
: ''DataSendAccelM.nc'' - the module component, contains implementation and own program for two different operation modes depending if the device is the coordinator or not 
: ''mma7260q.h'' - header file with the configuration of connecting external sensor 
: ''TRead.h'' - header file with structure's definition of TinyOS message 
: ''LocalTime.h, LocalTime.nc, LocalTimeC.nc, LocalTimeM.nc, LocalTimeInfo.nc, AbsoluteTimer.nc'' - interfaces, configuration and implementation of reading the Tmote's local time and its conversing to milliseconds.

 
=== C# application ===
The application in C# is running on computer and proccesing and displaying the received data from the USB/serial port. 
Application uses class handles of the bit and hexadecimal manipulations. And the ZedGraph module. It's a set of classes, written in C#, for creating 2D line and bar graphs of arbitrary datasets.
 
<CENTER>[[Image:CollectDataAppl_Csharp.jpg]]</CENTER>

Application form: 
: ''Connect'' - open port connection 
: ''Disconnect'' - close port connection 
: ''Port scan'' - find active ports 
: ''Test'' - one-shot depiction of collected sensor's data 
: ''Graph'' - on/off graphical representation 

 
== '''Tasks''' ==
* osadit 3x akcelerometr (analogove)
* otestovat digitalni akcelerometr (I2C)
* topologie hvezda - 1x PAN Coordinator, 3x slaves
* program (C, Java) na ukladani sebranych dat do textoveho souboru
* asociace/disasociace do PAN
* GTS - otestovat a porovnat s CSMA/CA
* ztratovost paketu - najit slabe misto
* chybovost paketu
* casova synchronizace mezi slaves (synchronization between wireless sensor motes and central node: common time for the samples capture)
* aktualizovat WiKi

 
== '''SW & Documentation''' ==
* [http://www.cadence.com/products/orcad/index.aspx OrCAD 10.3]
* [http://www.tinyos.net/ TinyOS 1.1.15 (Dec 2005)]
* [http://nescc.sourceforge.net/ nesC 1.2.7a]
* [http://www.open-zb.net/ An IEEE 802.15.4/Zigbee protocol implementation v1.2 (in nesC/TinyOS)]
* [http://msdn2.microsoft.com/en-us/evalcenter/bb188238.aspx Microsoft Visual Studio 2005]
* [http://zedgraph.org/wiki/index.php?title=Main_Page ZedGraph]

 
== '''HW & Documentation''' ==
* [http://www.moteiv.com/products/tmotesky.php Tmote Sky (TelosB platform)]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/117096/STMICROELECTRONICS/LIS3LV02DQ.html LIS3LV02DQ (ST) - 3-Axis 2g/6g digital accelerometer]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/103487/MOTOROLA/MMA7260Q.html MMA7260Q (Freescale) - 3-Axis 1.5g-6g analog accelerometer]
* For central unit we can use [http://www.vinculum.com/prd_vnc1l.html VNC1L] - it is USB host controler. Its perfect way how to storage data on USB disks.

 
== '''Other Links''' ==
* [http://www.pragoboard.cz/ PragoBoard s.r.o. - PCB producer]
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]

Parkinsons disease monitoring project

2007-09-13T23:36:29Z

Auersm1:

<div style="background-color: #DCDDF6; width:200px; border: solid #BA0000 1px; float: right; padding: 1em; margin-top: 4em; margin-right: 2em; margin-left: 2em">

Aktuální práce - úkoly v sekci "Tasks"

</div>

== '''Project definition''' ==
Wireless sensor motes placed on limbs (legs, arms) transmit periodically measured data to a central node for storing and evaluation. Once a day (or in predefined period) data from central node is downloaded to PC or PDA for analysis and computation of feedback in the form of brain stimulation or appropriate dose of medicine. 
Central node stores received data from wireless sensor motes with time stamps to embedded memory card (MMC, SD, CF or similar). Central node consists of 802.15.4/ZigBee radio chip, MCU and memory card. Central node can be wear on belt therefore its size is not so important. Wireless sensor mote includes 802.15.4/ZigBee radio chip, MCU and accelerometer and should be worn on wrist similar a watch is weared. This motes should be as small as possible.
 
[http://rtime.felk.cvut.cz/hw/images/e/e1/Spec_ParkinsonsDisease.pdf Project specification link]
 
<CENTER>[[Image:Body.png]]</CENTER>

== '''Developing phase''' ==

 
=== Extension boards with accelerometers ===

PCB design was created in OrCAD 10.3. PCB was made by firm Pragoboard (PCB producer) and soldered manually. 

*'''Analog accelerometer MMA7260Q (Freescale)''' 
: 3-Axis, selectable sensitivity 1.5g/2g/4g/6g, low current consumption 500 μA, low voltage operation 2.2V-3.6V, high sensitivity (800mV/g @1.5g) 
[[Image:telosb&MMA.jpg]] 

*'''Digital accelerometer LIS3LV02DQ (ST)''' 
: 3-Axis, selectable sensitivity 2g/6g, 2.16V-3.6V single supply operation, 1.8V compatible IOs, I2C/SPI digital output interfaces, programable 12 or 16bit data representation 
[[Image:telosb&LIS.jpg]]

 
=== Application DataSendAccel ===

Program for the Tmote Sky module with the accelerometer's extension board is developed by using TinyOS/nesC and open-ZB protocol stack designed at Polytechnical Institute of Porto. 
Program is based on the example application DataSendExample (created by André Cunha). The devices already have a short address meaning they are associated with the PAN coordinator. It's possible to associate three devices with accelerometer's extension board. 
Sensor's data are read, processed and send via IEEE 802.15.4 protocol during the CAP period using the CSMA/CA in data frame of packet. Coordinator receives and processes packet, sensor's data places in data frame of TinyOS message and the message send over the USB to computer. By means of drivers "USB to serial comm port" we can read data from USB as well as from serial port. 
The application in C# is running on computer and proccesing and displaying the received data from the USB/serial port.

'''TinyOS files:''' 
: ''datasendaccel.h'' - definitions and variables 
: ''DataSendAccel.nc'' - the configuration component, file containing the top-level configuration 
: ''DataSendAccelM.nc'' - the module component, contains implementation and own program for two different operation modes depending if the device is the coordinator or not 
: ''mma7260q.h'' - header file with the configuration of connecting external sensor 
: ''TRead.h'' - header file with structure's definition of TinyOS message 
: ''LocalTime.h, LocalTime.nc, LocalTimeC.nc, LocalTimeM.nc, LocalTimeInfo.nc, AbsoluteTimer.nc'' - interfaces, configuration and implementation of reading the Tmote's local time and its conversing to milliseconds.

 
=== C# application ===
Application uses class handles of the bit and hexadecimal manipulations. And the ZedGraph module. It's a set of classes, written in C#, for creating 2D line and bar graphs of arbitrary datasets.
 
<CENTER>[[Image:CollectDataAppl_Csharp.jpg]]</CENTER>

Application form: 
: ''Connect'' - open port connection 
: ''Disconnect'' - close port connection 
: ''Port scan'' - find active ports 
: ''Test'' - one-shot depiction of collected sensor's data 
: ''Graph'' - on/off graphical representation 

 
== '''Tasks''' ==
* osadit 3x akcelerometr (analogove)
* otestovat digitalni akcelerometr (I2C)
* topologie hvezda - 1x PAN Coordinator, 3x slaves
* program (C, Java) na ukladani sebranych dat do textoveho souboru
* asociace/disasociace do PAN
* GTS - otestovat a porovnat s CSMA/CA
* ztratovost paketu - najit slabe misto
* chybovost paketu
* casova synchronizace mezi slaves (synchronization between wireless sensor motes and central node: common time for the samples capture)
* aktualizovat WiKi

 
== '''SW & Documentation''' ==
* [http://www.cadence.com/products/orcad/index.aspx OrCAD 10.3]
* [http://www.tinyos.net/ TinyOS 1.1.15 (Dec 2005)]
* [http://nescc.sourceforge.net/ nesC 1.2.7a]
* [http://www.open-zb.net/ An IEEE 802.15.4/Zigbee protocol implementation v1.2 (in nesC/TinyOS)]
* [http://msdn2.microsoft.com/en-us/evalcenter/bb188238.aspx Microsoft Visual Studio 2005]
* [http://zedgraph.org/wiki/index.php?title=Main_Page ZedGraph]

 
== '''HW & Documentation''' ==
* [http://www.moteiv.com/products/tmotesky.php Tmote Sky (TelosB platform)]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/117096/STMICROELECTRONICS/LIS3LV02DQ.html LIS3LV02DQ (ST) - 3-Axis 2g/6g digital accelerometer]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/103487/MOTOROLA/MMA7260Q.html MMA7260Q (Freescale) - 3-Axis 1.5g-6g analog accelerometer]
* For central unit we can use [http://www.vinculum.com/prd_vnc1l.html VNC1L] - it is USB host controler. Its perfect way how to storage data on USB disks.

 
== '''Other Links''' ==
* [http://www.pragoboard.cz/ PragoBoard s.r.o. - PCB producer]
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]

File:CollectDataAppl Csharp.jpg

2007-09-13T22:52:16Z

Auersm1:

File:Telosb&LIS.jpg

2007-09-13T22:50:51Z

Auersm1:

File:Telosb&MMA.jpg

2007-09-13T22:50:41Z

Auersm1:

Parkinsons disease monitoring project

2007-09-13T22:32:00Z

Auersm1:

<div style="background-color: #DCDDF6; width:200px; border: solid #BA0000 1px; float: right; padding: 1em; margin-top: 4em; margin-right: 2em; margin-left: 2em">

Aktuální práce - úkoly v sekci "Tasks"

</div>

== '''Project definition''' ==
Wireless sensor motes placed on limbs (legs, arms) transmit periodically measured data to a central node for storing and evaluation. Once a day (or in predefined period) data from central node is downloaded to PC or PDA for analysis and computation of feedback in the form of brain stimulation or appropriate dose of medicine. 
Central node stores received data from wireless sensor motes with time stamps to embedded memory card (MMC, SD, CF or similar). Central node consists of 802.15.4/ZigBee radio chip, MCU and memory card. Central node can be wear on belt therefore its size is not so important. Wireless sensor mote includes 802.15.4/ZigBee radio chip, MCU and accelerometer and should be worn on wrist similar a watch is weared. This motes should be as small as possible.
 
[http://rtime.felk.cvut.cz/hw/images/e/e1/Spec_ParkinsonsDisease.pdf Project specification link]
 
<CENTER>[[Image:Body.png]]</CENTER>

== '''Developing phase''' ==

 
=== Application DataSendAccel ===
Program for the Tmote Sky module with the accelerometer's extension board is developed by using TinyOS/nesC and open-ZB protocol stack designed at Polytechnical institute of Porto. 
Program is based on the example application DataSendExample (created by André Cunha). The devices already have a short address meaning they are associated with the PAN coordinator. 
It's possible to associate three devices with accelerometer's extension board. 
Sensor's data are read, processed and send via IEEE 802.15.4 protocol during the CAP period using the CSMA/CA in data frame of packet. Coordinator receives packet, sensor's data place in data frame of TinyOS message and the message send over the USB to computer. 
By means of drivers "USB to serial comm port" we can read data from USB as well as from serial port. The application in C# is running on computer and proccesing and displaying the received data from the USB/serial port.

'''TinyOS files:''' 
: ''datasendaccel.h'' - definitions and variables 
: ''DataSendAccel.nc'' - the configuration component, file containing the top-level configuration 
: ''DataSendAccelM.nc'' - the module component, contains implementation and own program for two different operation modes depending if the device is the coordinator or not 
: ''mma7260q.h'' - header file with the configuration of connecting external sensor 
: ''TRead.h'' - header file with structure's definition of TinyOS message 
: ''LocalTime.h, LocalTime.nc, LocalTimeC.nc, LocalTimeM.nc, LocalTimeInfo.nc, AbsoluteTimer.nc'' - interfaces, configuration and implementation of reading and conversion the Tmote's local time

 
=== C# application ===
Application uses class handles of the bit and hexadecimal manipulations. And the ZedGraph module. It's a set of classes, written in C#, for creating 2D line and bar graphs of arbitrary datasets.

Application form: 
: ''Connect'' - open port connection 
: ''Disconnect'' - close port connection 
: ''Port scan'' - find active ports 
: ''Test'' - one-shot depiction of collected sensor's data 
: ''Graph'' - on/off graphical representation 

 
== '''Tasks''' ==
* osadit 3x akcelerometr (analogove)
* otestovat digitalni akcelerometr (I2C)
* topologie hvezda - 1x PAN Coordinator, 3x slaves
* program (C, Java) na ukladani sebranych dat do textoveho souboru
* asociace/disasociace do PAN
* GTS - otestovat a porovnat s CSMA/CA
* ztratovost paketu - najit slabe misto
* chybovost paketu
* casova synchronizace mezi slaves (synchronization between wireless sensor motes and central node: common time for the samples capture)
* aktualizovat WiKi

 
== '''SW & Documentation''' ==
* [http://www.tinyos.net/ TinyOS 1.1.15 (Dec 2005)]
* [http://nescc.sourceforge.net/ nesC 1.2.7a]
* [http://www.open-zb.net/ An IEEE 802.15.4/Zigbee protocol implementation v1.2 (in nesC/TinyOS)]
* [http://msdn2.microsoft.com/en-us/evalcenter/bb188238.aspx Microsoft Visual Studio 2005]
* [http://zedgraph.org/wiki/index.php?title=Main_Page ZedGraph]

 
== '''HW & Documentation''' ==
* [http://www.moteiv.com/products/tmotesky.php Tmote Sky (TelosB platform)]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/117096/STMICROELECTRONICS/LIS3LV02DQ.html LIS3LV02DQ (ST) - 3-Axis 2g/6g digital accelerometer]
* [http://www.alldatasheet.com/datasheet-pdf/pdf/103487/MOTOROLA/MMA7260Q.html MMA7260Q (Freescale) - 3-Axis 1.5g-6g analog accelerometer]
* For central unit we can use [http://www.vinculum.com/prd_vnc1l.html VNC1L] - it is USB host controler. Its perfect way how to storage data on USB disks.

 
== '''Other Links''' ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]

Weekly Reports

2007-04-16T03:31:03Z

Auersm1: /* week [3,4 - 2007] */

Weekly Reports

2007-04-16T03:30:56Z

Auersm1: /* week [5,6 - 2007] */

Weekly Reports

2007-04-16T03:30:48Z

Auersm1: /* week [7,8 - 2007] */

=== week [15,16 - 2007] ===
* DONE
: - Website "Main modifications of Open-ZB stack" was moved
* TODO
----

=== week [13,14 - 2007] ===
* DONE
: - I updated website "Main modifications of Open-ZB stack"
* TODO
----

=== week [11,12 - 2007] ===
* DONE
: - I'm starting to collaborate with Andre Cunha, author of the OpenZB stack.
: - I created website "Main modifications of Open-ZB stack".

* TODO
----

=== week [9,10 - 2007] ===
* DONE
: - small changes in the first, second and third error, visit the consistent part of section on the front page

* TODO
: - solve the third error - problem with TimerAsync and HPLTimer2C
----

=== week [7,8 - 2007] ===
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

=== week [5,6 - 2007] ===
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

=== week [3,4 - 2007] ===
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''
----

=== week [1,2 - 2007] (CZ) ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

Weekly Reports

2007-04-16T03:30:37Z

Auersm1: /* week [9,10 - 2007] */

Weekly Reports

2007-04-16T03:30:27Z

Auersm1: /* week [11,12 - 2007] */

Weekly Reports

2007-04-16T03:30:17Z

Auersm1: /* week [13,14 - 2007] */

Weekly Reports

2007-04-16T03:30:08Z

Auersm1: /* week [15,16 - 2007] */

Weekly Reports

2007-04-16T03:29:12Z

Auersm1: /* week [1,2 - 2007] */

Open-ZB stack porting to TmoteSky

2007-04-16T03:20:20Z

Auersm1: /* Developing phase */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [15,16 - 2007] ===

Website "Main modifications of Open-ZB stack" was moved:
--- [http://rtime.felk.cvut.cz/wsn/ New location of pages "Main modifications of Open-ZB stack"] ---

----

=== [13,14 - 2007] ===

update website:
: [http://rtime.felk.cvut.cz/wsn/ Main modifications of Open-ZB stack]

----

=== [11,12 - 2007] ===

: created website:
: [http://rtime.felk.cvut.cz/wsn/ Main modifications of Open-ZB stack]

----

=== [9,10 - 2007] ===
I did small changes, see down..

- add the first error:
: I dont't rename PIN but add PIN
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
: new code:
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

- add the second error:
: implementation of functions for Telos:
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.edge(0); <- CHANGE
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}

async command result_t HPLCC2420.disableFIFOP() {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
} return SUCCESS; }

async event void FIFOPInterrupt.fired(){
// signal the interrupt
signal HPLCC2420.FIFOPIntr(); <- CHANGE
}

- add the third error:
: I try replace the function "Timer2.setIntervalAndScale" in HPLTimer2 (TimerAsync.start), which sets timer and starts and enables interrupt, directly calling to make the Timer with tick granularity equals 69 microseconds (requirement is 69.54 us), by interface with argument (tinyos-programming, pages 29-32).
: ..and link to it the nacessary steps and TinyOS would set, start and enables interrupt. In "TimerAsync.stop" would be call the Timer destructor instead disable interupt.
: But I don't thing that it would be so simple. Since no other idea how we going to deal with this problem on a low-level.

----

=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
(the problem from [5,6 - 2007] solved)
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN: <- CHANGE, don't rename but addition
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably. <- Since OK.
: Excerpts, implementation of functions for Telos <- CHANGE
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Weekly Reports

2007-04-04T19:01:48Z

Auersm1: /* week [13,14 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

== week [7,8 - 2007] ==
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

== week [9,10 - 2007] ==
* DONE
: - small changes in the first, second and third error, visit the consistent part of section on the front page

* TODO
: - solve the third error - problem with TimerAsync and HPLTimer2C
----

== week [11,12 - 2007] ==
* DONE
: - I'm starting to collaborate with Andre Cunha, author of the OpenZB stack.
: - I created website "Main modifications of Open-ZB stack".

* TODO
----

== week [13,14 - 2007] ==
* DONE
: - I updated website "Main modifications of Open-ZB stack"
* TODO
----

== week [15,16 - 2007] ==
* DONE
* TODO
----

Weekly Reports

2007-04-04T19:00:46Z

Auersm1: /* week [11,12 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

== week [7,8 - 2007] ==
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

== week [9,10 - 2007] ==
* DONE
: - small changes in the first, second and third error, visit the consistent part of section on the front page

* TODO
: - solve the third error - problem with TimerAsync and HPLTimer2C
----

== week [11,12 - 2007] ==
* DONE
: - I'm starting to collaborate with Andre Cunha, author of the OpenZB stack.
: - I created website "Main modifications of Open-ZB stack".

* TODO
----

== week [13,14 - 2007] ==
* DONE
* TODO
----
== week [15,16 - 2007] ==
* DONE
* TODO
----

Open-ZB stack porting to TmoteSky

2007-04-04T18:59:00Z

Auersm1: /* Developing phase */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [13,14 - 2007] ===

update website:
--- [http://veverka.sh.cvut.cz/~seamus/porting/index.htm Main modifications of Open-ZB stack] ---

----

=== [11,12 - 2007] ===

: created website:
: [http://veverka.sh.cvut.cz/~seamus/porting/index.htm Main modifications of Open-ZB stack]

----

=== [9,10 - 2007] ===
I did small changes, see down..

- add the first error:
: I dont't rename PIN but add PIN
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
: new code:
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

- add the second error:
: implementation of functions for Telos:
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.edge(0); <- CHANGE
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}

async command result_t HPLCC2420.disableFIFOP() {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
} return SUCCESS; }

async event void FIFOPInterrupt.fired(){
// signal the interrupt
signal HPLCC2420.FIFOPIntr(); <- CHANGE
}

- add the third error:
: I try replace the function "Timer2.setIntervalAndScale" in HPLTimer2 (TimerAsync.start), which sets timer and starts and enables interrupt, directly calling to make the Timer with tick granularity equals 69 microseconds (requirement is 69.54 us), by interface with argument (tinyos-programming, pages 29-32).
: ..and link to it the nacessary steps and TinyOS would set, start and enables interrupt. In "TimerAsync.stop" would be call the Timer destructor instead disable interupt.
: But I don't thing that it would be so simple. Since no other idea how we going to deal with this problem on a low-level.

----

=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
(the problem from [5,6 - 2007] solved)
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN: <- CHANGE, don't rename but addition
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably. <- Since OK.
: Excerpts, implementation of functions for Telos <- CHANGE
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Open-ZB stack porting to TmoteSky

2007-03-21T23:49:35Z

Auersm1: /* Developing phase */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [11,12 - 2007] ===

--- [http://veverka.sh.cvut.cz/~seamus/porting/index.htm Main modifications of Open-ZB stack] ---

----

=== [9,10 - 2007] ===
I did small changes, see down..

- add the first error:
: I dont't rename PIN but add PIN
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
: new code:
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

- add the second error:
: implementation of functions for Telos:
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.edge(0); <- CHANGE
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}

async command result_t HPLCC2420.disableFIFOP() {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
} return SUCCESS; }

async event void FIFOPInterrupt.fired(){
// signal the interrupt
signal HPLCC2420.FIFOPIntr(); <- CHANGE
}

- add the third error:
: I try replace the function "Timer2.setIntervalAndScale" in HPLTimer2 (TimerAsync.start), which sets timer and starts and enables interrupt, directly calling to make the Timer with tick granularity equals 69 microseconds (requirement is 69.54 us), by interface with argument (tinyos-programming, pages 29-32).
: ..and link to it the nacessary steps and TinyOS would set, start and enables interrupt. In "TimerAsync.stop" would be call the Timer destructor instead disable interupt.
: But I don't thing that it would be so simple. Since no other idea how we going to deal with this problem on a low-level.

----

=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
(the problem from [5,6 - 2007] solved)
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN: <- CHANGE, don't rename but addition
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably. <- Since OK.
: Excerpts, implementation of functions for Telos <- CHANGE
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Weekly Reports

2007-03-21T23:24:33Z

Auersm1: /* week [11,12 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

== week [7,8 - 2007] ==
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

== week [9,10 - 2007] ==
* DONE
: - small changes in the first, second and third error, visit the consistent part of section on the front page

* TODO
: - solve the third error - problem with TimerAsync and HPLTimer2C
----

== week [11,12 - 2007] ==
* DONE
: - I'm starting to collaborate with Andre Cunha, author of the OpenZB stack.

* TODO
----

== week [13,14 - 2007] ==
* DONE
* TODO
----
== week [15,16 - 2007] ==
* DONE
* TODO
----

Weekly Reports

2007-03-21T23:22:33Z

Auersm1: /* week [9,10 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

== week [7,8 - 2007] ==
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

== week [9,10 - 2007] ==
* DONE
: - small changes in the first, second and third error, visit the consistent part of section on the front page

* TODO
: - solve the third error - problem with TimerAsync and HPLTimer2C
----

== week [11,12 - 2007] ==
* DONE
* TODO
----
== week [13,14 - 2007] ==
* DONE
* TODO
----
== week [15,16 - 2007] ==
* DONE
* TODO
----

Open-ZB stack porting to TmoteSky

2007-03-21T23:14:34Z

Auersm1: /* Developing phase */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [9,10 - 2007] ===
I did small changes, see down..

- add the first error:
: I dont't rename PIN but add PIN
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
: new code:
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

- add the second error:
: implementation of functions for Telos:
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.edge(0); <- CHANGE
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}

async command result_t HPLCC2420.disableFIFOP() {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
} return SUCCESS; }

async event void FIFOPInterrupt.fired(){
// signal the interrupt
signal HPLCC2420.FIFOPIntr(); <- CHANGE
}

- add the third error:
: I try replace the function "Timer2.setIntervalAndScale" in HPLTimer2 (TimerAsync.start), which sets timer and starts and enables interrupt, directly calling to make the Timer with tick granularity equals 69 microseconds (requirement is 69.54 us), by interface with argument (tinyos-programming, pages 29-32).
: ..and link to it the nacessary steps and TinyOS would set, start and enables interrupt. In "TimerAsync.stop" would be call the Timer destructor instead disable interupt.
: But I don't thing that it would be so simple. Since no other idea how we going to deal with this problem on a low-level.

----

=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
(the problem from [5,6 - 2007] solved)
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN: <- CHANGE, don't rename but addition
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably. <- Since OK.
: Excerpts, implementation of functions for Telos <- CHANGE
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Open-ZB stack porting to TmoteSky

2007-03-21T22:58:27Z

Auersm1: /* [7,8 - 2007] */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
(the problem from [5,6 - 2007] solved)
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN: <- CHANGE, don't rename but addition
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably. <- Since OK.
: Excerpts, implementation of functions for Telos <- CHANGE
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Open-ZB stack porting to TmoteSky

2007-03-21T22:46:26Z

Auersm1: /* [5,6 - 2007] */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN:
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably.
: Excerpts, implementation of functions for Telos
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\
: -> ''this problem solved''

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

AssociationExample HPLCC2420

2007-02-22T05:00:39Z

Auersm1:

== Mica ==
=== HPLCC2420C ===
configuration HPLCC2420C {
provides {
interface StdControl;
interface HPLCC2420;
interface HPLCC2420FIFO;
interface HPLCC2420RAM;
}
}
implementation
{
components HPLCC2420M, HPLCC2420FIFOM;
//
StdControl = HPLCC2420M;
HPLCC2420 = HPLCC2420M;
HPLCC2420FIFO = HPLCC2420FIFOM;
HPLCC2420RAM = HPLCC2420M;
}

=== HPLCC2420M ===
module HPLCC2420M {
provides {
interface StdControl;
interface HPLCC2420;
interface HPLCC2420RAM;
}
}
implementation
{
norace bool bSpiAvail; //true if Spi bus available
norace uint8_t* rambuf;
norace uint8_t ramlen;
norace uint16_t ramaddr;
//
/*********************************************************
* function: init
* set Atmega pin directions for cc2420
* enable SPI master bus
********************************************************/
command result_t StdControl.init() {
//
bSpiAvail = TRUE;
TOSH_MAKE_MISO_INPUT();
TOSH_MAKE_MOSI_OUTPUT();
TOSH_MAKE_SPI_SCK_OUTPUT();
TOSH_MAKE_CC_RSTN_OUTPUT();
TOSH_MAKE_CC_VREN_OUTPUT();
TOSH_MAKE_CC_CS_OUTPUT();
TOSH_MAKE_CC_FIFOP1_INPUT();
TOSH_MAKE_CC_CCA_INPUT();
TOSH_MAKE_CC_SFD_INPUT();
TOSH_MAKE_CC_FIFO_INPUT();
atomic {
TOSH_MAKE_SPI_SCK_OUTPUT();
TOSH_MAKE_MISO_INPUT(); // miso
TOSH_MAKE_MOSI_OUTPUT(); // mosi
sbi(SPSR, SPI2X); // Double speed spi clock
sbi(SPCR, MSTR); // Set master mode
cbi(SPCR, CPOL); // Set proper polarity...
cbi(SPCR, CPHA); // ...and phase
cbi(SPCR, SPR1); // set clock, fosc/2 (~3.6 Mhz)
cbi(SPCR, SPR0);
// sbi(SPCR, SPIE); // enable spi port interrupt
sbi(SPCR, SPE); // enable spie port
}
return SUCCESS;
}
//
command result_t StdControl.start() { return SUCCESS; }
command result_t StdControl.stop() { return SUCCESS; }
//
/*********************************************************
* function: enableFIFOP
* enable CC2420 fifop interrupt
CC2420 is configured for FIFOP interrupt on RXFIFO > Thresh
where thresh is programmed in CC2420Const.h CP_IOCFGO reg.
Threshold is 127 asof 15apr04 (AlmostFull)
FIFOP is asserted as long as RXFIFO>Threshold
FIFOP is active LOW
********************************************************/
async command result_t HPLCC2420.enableFIFOP(){
cbi(EICRB,ISC60); //trigger on low level
// cbi(EICRB,ISC61); //low level
sbi(EICRB,ISC61); //falling edge for standard release
CC2420_FIFOP_INT_ENABLE();
return SUCCESS;
}
/*********************************************************
* function: disbleFIFOP
* disable CC2420 fifop interrupt
********************************************************/
async command result_t HPLCC2420.disableFIFOP(){
CC2420_FIFOP_INT_DISABLE();
return SUCCESS;
}
//
TOSH_SIGNAL(TOSH_CC_FIFOP_INT) {
// signal the interrupt
signal HPLCC2420.FIFOPIntr();
}
/*
* .............
*
*/
}//HPLCC2420M.nc

== Telos ==
=== HPLCC2420C ===
configuration HPLCC2420C {
provides {
interface StdControl;
interface HPLCC2420;
interface HPLCC2420RAM;
interface HPLCC2420FIFO;
//interface HPLCC2420Interrupt as InterruptFIFOP;
}
}
implementation
{
components HPLCC2420M
, HPLUSART0M
// , HPLCC2420InterruptM
, MSP430InterruptC
, BusArbitrationC;
//
StdControl = BusArbitrationC;
StdControl = HPLCC2420M;
HPLCC2420 = HPLCC2420M;
HPLCC2420RAM = HPLCC2420M;
HPLCC2420FIFO = HPLCC2420M;
//
//InterruptFIFOP = HPLCC2420InterruptM.FIFOP;
//InterruptFIFO = HPLCC2420InterruptM.FIFO;
//
HPLCC2420M.USARTControl -> HPLUSART0M;
HPLCC2420M.BusArbitration -> BusArbitrationC.BusArbitration[unique("BusArbitration")];
//
HPLCC2420M.FIFOPInterrupt -> MSP430InterruptC.Port10;
//HPLCC2420InterruptM.FIFOInterrupt -> MSP430InterruptC.Port13;
}

=== HPLCC2420M ===
module HPLCC2420M {
provides {
interface StdControl;
interface HPLCC2420;
interface HPLCC2420RAM;
interface HPLCC2420FIFO;
}
uses {
interface HPLUSARTControl as USARTControl;
interface BusArbitration;
interface MSP430Interrupt as FIFOPInterrupt;
}
}
implementation
{
//
norace uint8_t* txbuf;
norace uint8_t* rxbuf;
norace uint8_t* rambuf;
norace uint8_t* rxrambuf;
norace uint8_t txlen;
norace uint8_t rxlen;
norace uint8_t ramlen;
norace uint16_t ramaddr;
norace uint8_t rxramlen;
norace uint16_t rxramaddr;
norace struct {
bool enabled : 1;
bool busy : 1;
bool rxbufBusy : 1;
bool txbufBusy : 1;
} f; // f for flags
/**
* Zero out the reserved bits since they can be either 0 or 1.
* This allows the use of "if !cmd(x)" in the radio stack
*/
uint8_t adjustStatusByte(uint8_t status) {
return status & 0x7E;
}
//
command result_t StdControl.init() {
atomic {
f.busy = f.enabled = f.rxbufBusy = f.txbufBusy = FALSE;
}
TOSH_SET_RADIO_CSN_PIN();
TOSH_MAKE_RADIO_CSN_OUTPUT();
call USARTControl.setModeSPI();
call USARTControl.disableRxIntr();
call USARTControl.disableTxIntr();
return SUCCESS;
}
command result_t StdControl.start() {
atomic {
if (!f.busy) {
TOSH_SET_RADIO_CSN_PIN();
TOSH_MAKE_RADIO_CSN_OUTPUT();
call USARTControl.setModeSPI();
call USARTControl.disableRxIntr();
call USARTControl.disableTxIntr();
f.busy = f.rxbufBusy = f.txbufBusy = FALSE;
f.enabled = TRUE;
}
}
return SUCCESS;
}
command result_t StdControl.stop() {
atomic {
// if we're not in the middle of doing something, we can shut off the
// SPI operations too
if (!f.busy)
call USARTControl.disableSPI();
f.enabled = FALSE;
}
return SUCCESS;
}
/*********************************************************
* function: enableFIFOP
* enable CC2420 fifop interrupt
CC2420 is configured for FIFOP interrupt on RXFIFO > Thresh
where thresh is programmed in CC2420Const.h CP_IOCFGO reg.
Threshold is 127 asof 15apr04 (AlmostFull)
FIFOP is asserted as long as RXFIFO>Threshold
FIFOP is active LOW!!!!!!!!!!
********************************************************/
async command result_t HPLCC2420.enableFIFOP(){
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
//call FIFOPInterrupt.edge(low_to_high); <- problem
call FIFOPInterrupt.enable();
}
return SUCCESS;
}
/*********************************************************
* function: disbleFIFOP
* disable CC2420 fifop interrupt
********************************************************/
async command result_t HPLCC2420.disableFIFOP(){
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
}
return SUCCESS;
}
/**
* Event fired by lower level interrupt dispatch for FIFOP
*/
async event void FIFOPInterrupt.fired(){
//result_t val = SUCCESS;
call FIFOPInterrupt.clear();
// val = signal FIFOP.fired(); <- problem
// if (val == FAIL) {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
// }
}
/*
* default async event result_t FIFOP.fired() { return FAIL; } <- problem
*/
/*********************************************************
/*
* ........................
*/
} //HPLCC2420M

=== HPLCC2420InterruptM ===
module HPLCC2420InterruptM {
provides {
interface HPLCC2420Interrupt as FIFOP;
interface HPLCC2420Interrupt as FIFO;
interface HPLCC2420Interrupt as CCA;
interface HPLCC2420Capture as SFD;
}
uses {
interface MSP430Interrupt as FIFOPInterrupt;
interface MSP430Interrupt as FIFOInterrupt;
interface MSP430Interrupt as CCAInterrupt;
interface MSP430Capture as SFDCapture;
interface MSP430TimerControl as SFDControl;
}
}
implementation
{
// ************* FIFOP Interrupt handlers and dispatch *************
/**
* enable an edge interrupt on the FIFOP pin
*/
async command result_t FIFOP.startWait(bool low_to_high) {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.edge(low_to_high);
call FIFOPInterrupt.enable();
}
return SUCCESS;
}
/**
* disables FIFOP interrupts
*/
async command result_t FIFOP.disable() {
atomic {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
}
return SUCCESS;
}
/**
* Event fired by lower level interrupt dispatch for FIFOP
*/
async event void FIFOPInterrupt.fired() {
result_t val = SUCCESS;
call FIFOPInterrupt.clear();
val = signal FIFOP.fired();
if (val == FAIL) {
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
}
}
default async event result_t FIFOP.fired() { return FAIL; }
/*
* ..........................
*/
} // HPLCC2420InterruptM

Open-ZB stack porting to TmoteSky

2007-02-22T04:56:03Z

Auersm1: /* [7,8 - 2007] */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN:
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
: Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
: Changes were inspired by the implementation for MicaZ platform. Comparing files (HPLCC2420C, HPLCC2420M, HPLCC2420InterruptM) for MicaZ platform in TinyOS with files (HPLCC2420C, HPLCC2420M, file HPLCC2420InterruptM isn't here - requisite functions are implemented into HPLCC2420M) in stack.
: I discovered a diferrences and apply changes for Telos platform the same way. I'm testing it now. I will try out the assumed code. It won't work errorless probably.
: Excerpts, implementation of functions for Telos
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Open-ZB stack porting to TmoteSky

2007-02-22T03:43:27Z

Auersm1: /* [7,8 - 2007] */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
: some Makefiles: [[Blink_makefiles]]
: a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN:
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
Changes were inspired by the implementation for MicaZ platform. I'm testing it now. I will try out the assumed code. It won't work errorless probably.
: Excerpts, implementation of functions for Telos
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
: "In component TimerAsyncC component HPLTimer2C not found"
: Will probably be need some larger modification of code. I must study documentation properly - Reference Guide, Cunha, Alves, pgs.42-51

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
: deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
: addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

AssociationExample HPLCC2420

2007-02-22T03:21:23Z

Auersm1: New page: == Mica == === HPLCC2420C === configuration HPLCC2420C { provides { interface StdControl; interface HPLCC2420; interface HPLCC2420FIFO; interface HPLCC2420RAM; } } i...

Blink makefiles

2007-02-22T02:57:06Z

Auersm1: New page: == Makefile v1 == COMPONENT=Blink #SENSORBOARD=mts310 PFLAGS=-I../Blink HURRAYROOT=%T/../contrib/hurray/tos # pro platformy TPLATFORM = telos a telosb TPLATFORM := $(filter telos tel...

== Makefile v1 ==
COMPONENT=Blink
#SENSORBOARD=mts310
PFLAGS=-I../Blink
HURRAYROOT=%T/../contrib/hurray/tos
# pro platformy TPLATFORM = telos a telosb
TPLATFORM := $(filter telos telosb, $(MAKECMDGOALS))
PFLAGS := -tosdir=$(HURRAYROOT)
PFLAGS = \
-I$(HURRAYROOT)/interfaces \
-I$(HURRAYROOT)/interfaces/ieee802154/phy \
-I$(HURRAYROOT)/interfaces/ieee802154/mac \
-I$(HURRAYROOT)/platform/$(PLATFORM)
ifeq ($(TPLATFORM),telos)
PFLAGS += -I$(HURRAYROOT)/platform/msp430
endif
ifeq ($(TPLATFORM),telosb)
PFLAGS += \
-I$(HURRAYROOT)/platform/telos \
-I$(HURRAYROOT)/platform/msp430
endif
PFLAGS += \
-I$(HURRAYROOT)/system \
-I$(HURRAYROOT)/lib/CC2420Radio \
-I$(HURRAYROOT)/lib/phy \
-I$(HURRAYROOT)/lib/mac \
-I$(HURRAYROOT)/sensorboards/$(SENSORBOARD)
include ../MakeXbowlocal
include $(TOSROOT)/tools/make/Makerules

== Makefile v2 ==
COMPONENT=Blink
#SENSORBOARD=mts310
PFLAGS=-I../Blink
HURRAYROOT=%T/../contrib/hurray/tos
# pro platformy TPLATFORM = telos a telosb
TPLATFORM := $(filter telos telosb, $(MAKECMDGOALS))
PFLAGS := -tosdir=$(HURRAYROOT)
PFLAGS = \
-I$(HURRAYROOT)/interfaces \
-I$(HURRAYROOT)/interfaces/ieee802154/phy \
-I$(HURRAYROOT)/interfaces/ieee802154/mac \
-I$(HURRAYROOT)/platform/$(PLATFORM)
ifeq ($(TPLATFORM),telos)
PFLAGS += -I$(HURRAYROOT)/platform/msp430
endif
ifeq ($(TPLATFORM),telosb)
PFLAGS += \
-I$(TOSROOT)/tos/platform/msp430 \
-I$(HURRAYROOT)/platform/msp430
endif
PFLAGS += \
-I$(HURRAYROOT)/system \
-I$(HURRAYROOT)/lib/CC2420Radio \
-I$(HURRAYROOT)/lib/phy \
-I$(HURRAYROOT)/lib/mac \
-I$(HURRAYROOT)/sensorboards/$(SENSORBOARD)
include ../MakeXbowlocal
include $(TOSROOT)/tools/make/Makerules

== Makefile v3 ==
COMPONENT=Blink
#SENSORBOARD=mts310
PFLAGS=-I../Blink
HURRAYROOT=%T/../contrib/hurray/tos
PFLAGS := -tosdir=$(HURRAYROOT)
PFLAGS = \
-I$(HURRAYROOT)/interfaces \
-I$(HURRAYROOT)/interfaces/ieee802154/phy \
-I$(HURRAYROOT)/interfaces/ieee802154/mac \
-I$(HURRAYROOT)/platform/$(PLATFORM)
# pro platformy TPLATFORM = telos a telosb
ifeq ($(MAKECMDGOALS),telos)
PFLAGS += -I$(HURRAYROOT)/platform/msp430
endif
ifeq ($(MAKECMDGOALS),telosb)
PFLAGS += \
-I$(HURRAYROOT)/platform/telos \
-I$(HURRAYROOT)/platform/msp430
endif
PFLAGS += \
-I$(HURRAYROOT)/system \
-I$(HURRAYROOT)/lib/CC2420Radio \
-I$(HURRAYROOT)/lib/phy \
-I$(HURRAYROOT)/lib/mac \
-I$(HURRAYROOT)/sensorboards/$(SENSORBOARD)
include ../MakeXbowlocal
include $(TOSROOT)/tools/make/Makerules

Open-ZB stack porting to TmoteSky

2007-02-22T02:49:47Z

Auersm1: /* [7,8 - 2007] */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform. The new code:
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb
some Makefiles: [[Blink_makefiles]]
a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile is similar to the file for Blink application
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN:
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
Changes were inspired by the implementation for MicaZ platform. I'm testing it now. I will try out the assumed code. It won't work errorless probably.
: - Excerpts, implementation of functions for Telos
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}
: in detail: [[AssociationExample_HPLCC2420]]

*** third error:
Will probably be need some larger modification of code.

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
addition of telosb platform data

----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

AssociationExample make

2007-02-22T02:33:12Z

Auersm1: New page: == AssociationExample application == ==== compilation before modifications: ==== Image:AssociationExample_make-telos-cbch.jpg ==== final compilation: ====

== AssociationExample application ==
==== compilation before modifications: ====
[[Image:AssociationExample_make-telos-cbch.jpg]]
==== final compilation: ====

File:AssociationExample make-telos-cbch.jpg

2007-02-22T02:31:12Z

Auersm1:

Blink make

2007-02-22T02:28:52Z

Auersm1: New page: == Blink application == ==== compilation before modifications: ==== Image:Blink make-telos-cbch.jpg ==== final compilation: ==== Image:Blink make.jpg

== Blink application ==
==== compilation before modifications: ====
[[Image:Blink make-telos-cbch.jpg]]
==== final compilation: ====
[[Image:Blink make.jpg]]

File:Blink make.jpg

2007-02-22T02:24:10Z

Auersm1: for MicaZ, Telos and TelosB platforms

for MicaZ, Telos and TelosB platforms

File:Blink make-telos-cbch.jpg

2007-02-22T02:22:42Z

Auersm1:

Open-ZB stack porting to TmoteSky

2007-02-22T02:14:40Z

Auersm1:

== Weekly reports ==
[[Weekly_Reports | Weekly Reports]] - what is done, what is doing, what will be done.

== Project definition ==
Open-ZB protocol stack designed at Polytechnical institute of Porto, Portugal is implemented for MicaZ platform in TinyOS/nesC and we would like to port it to TmoteSky (TelosB) platform.

OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
=== [7,8 - 2007] ===

* Rectifying errors:
** Blink application (''\tinyos-1.x\contrib\hurray\apps\Blink\'')
modification of file
''\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc''
changes were inspired by the PowerManagementM file of MicaZ platform
module HPLPowerManagementM {
provides { interface PowerManagement;
command result_t Enable();
command result_t Disable(); }
}
implementation {
async command uint8_t PowerManagement.adjustPower() { return SUCCESS; }
command result_t Enable() { LPMode_enable();
return SUCCESS; }
command result_t Disable() { LPMode_disable();
return SUCCESS; }
}

modification of Makefile to accept the another two platforms - telos and telosb

some Makefiles:
: - jeden
: - druhej
: - treti
a sample of compilation: [[Blink_make]]

** AssociationExample application (''\tinyos-1.x\contrib\hurray\apps\AssociationExample\'')
modification of Makefile to accept the another two platforms - telos and telosb
Makefile
a sample of compilation: [[AssociationExample_make]]

*** first error:
location of header files:
: - avr-system
: ''\usr\local\avr\include\''
: - avr-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
: - mica-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\mica|mica2|micaz\hardware.h''

: - msp430-system
: ''\usr\local\mspgcc\msp430\include\''
: - msp430-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
: - telos-hardware
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''

I want MAC and PHY files to remain unchanged. I found the matching PIN on hardware files.
: Excerpts:
''\tinyos-1.x\contrib\hurray\tos\platform\avrmote\avrhardware.h''
#define TOSH_ASSIGN_PIN(name, port, bit) \
static inline int TOSH_READ_##name##_PIN() \
{return (inp(PIN##port) & (1 << bit)) != 0;}
#define TOSH_ALIAS_PIN(alias, connector) \
static inline char TOSH_READ_##alias##_PIN() \
{return TOSH_READ_##connector##_PIN();}

''\tinyos-1.x\contrib\hurray\tos\platform\micaz\hardware.h''
TOSH_ASSIGN_PIN(CC_CCA, D, 6);

''\tinyos-1.x\contrib\hurray\tos\platform\msp430\msp430hardware.h''
#define TOSH_ASSIGN_PIN_HEX(name, port, hex) \
uint8_t TOSH_READ_##name##_PIN() \
{ MSP430REG_NORACE2(r,P##port##IN); return (r & hex); }

''\tinyos-1.x\contrib\hurray\tos\platform\telos|telosb\hardware.h''
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
modification - rename PIN:
RADIO_CCA -> CC_CCA:
TOSH_ASSIGN_PIN(CC_CCA, 1, 4);

*** second error:
Simple insertion the missing functions from HPLCC2420M (MicaZ platform) to HPLCC2420M (telos platform, telosb haven't its own modul, use this one) is impossible.
Changes were inspired by the implementation for MicaZ platform. I'm testing it now. I will try out the assumed code. It won't work errorless probably.
: - Excerpts, implementation of functions for Telos
module HPLCC2420M {
provides { ... }
uses { ...
interface MSP430Interrupt as FIFOPInterrupt; }
}
implementation { ...
async command result_t HPLCC2420.enableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear();
call FIFOPInterrupt.enable(); }
return SUCCESS; }
async command result_t HPLCC2420.disableFIFOP(){
atomic { call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
return SUCCESS; }
async event void FIFOPInterrupt.fired(){
call FIFOPInterrupt.clear();
call FIFOPInterrupt.disable();
call FIFOPInterrupt.clear(); }
}

*** third error:
Will probably be need some larger modification of code.

* Small changes on files:
: ''\tinyos-1.x\contrib\hurray\tos\platform\telos\.platform''
: ''\tinyos-1.x\contrib\hurray\tos\platform\telosb\.platform''
deletion of unnecessary specification "push"

: ''\tinyos-1.x\contrib\hurray\apps\platform.properties''
: ''\tinyos-1.x\contrib\hurray\platform.properties''
addition of telosb platform data
----

=== [5,6 - 2007] ===
I used the TinyOS Tmote Sky hardware modules:
: ''\tinyos-1.x\tos\platform\msp430\''
: ''\tinyos-1.x\tos\platform\telos\''
: ''\tinyos-1.x\tos\platform\telosb\''
copied it to:
: ''\tinyos-1.x\contrib\hurray\tos\platform\''
(during the testing and improvements, it's not necessary to copy all files, but only a modified files)
and I'm trying to modify some files.

Since wasn't necessary change the PHY-layer files, because I have basic problem:
During compiling the Blink application to a telosb binary:

: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\Main.nc from Blink.nc''
: ''In component 'PotC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\PotC.nc component HPLPotC not found''
: ''In file included from Blink.nc:''
: ''In component 'Main':''
: ''\tinyos-1.x\contrib\hurray\tos\system\Main.nc component HPLInit not found''
: ''In file included from \tinyos-1.x\contrib\hurray\tos\system\TimerC.nc from SingleTimer.nc and Blink.nc''
: ''In component 'ClockC':''
: ''\tinyos-1.x\contrib\hurray\tos\system\ClockC.nc component HPLClock not found''

That's right. I thing, I have to change the directory ''\tinyos-1.x\contrib\hurray\tos\system\'' to ''\tinyos-1.x\contrib\hurray\tos\platform\msp430'' before linking someway, so that all files
included in ''\tos\system'' (as well as in ''\platform\msp430'') were replace by the files from
''\platform\msp430''.
The files in ''\tos\system\'' are primarily determined for other platforms (e.g. Mica). You can see:

The Blink application uses these files:
MicaZ platform:
: ''platform/micaz/PowerManagementM.nc''
: ''system/ClockC.nc, LedsC.nc, Main.nc, NoLeds.nc, PotC.nc, PotM.nc, RealMain.nc, TimerC.nc, TimerM.nc''
: ''tos/platform/avrmote/HPLInit.nc''
: ''tos/platform/mica/HPLClock.nc''
: ''tos/platform/mica2/HPLPotC.nc''

TelosB platform:
: ''tos/platform/msp430/HPLInitC.nc, HPLInitM.nc, LocalTime.nc, MSP430Capture.nc, MSP430ClockC.nc, MSP430ClockInit.nc, MSP430ClockM.nc, MSP430Compare.nc, MSP430DCOCalibC.nc, MSP430DCOCalibM.nc, MSP430Timer.nc, MSP430TimerC.nc, MSP430TimerControl.nc, MSP430TimerM.nc, Main.nc, MainM.nc, TimerC.nc, TimerJiffy.nc, TimerM.nc, TimerMilli.nc''
: ''tos/system/LedsC.nc''

I think, it's a problem in a 'Makefile' file.
I tried to add to the 'Makefile' (\tinyos-1.x\contrib\hurray\apps\Blink\)
: ''PFLAGS += -I$(HURRAYROOT)/platform/msp430''
but the compiler takes the files still from \tinyos-1.x\contrib\hurray\tos\system\

----

=== [3,4 - 2007] ===
* zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy, je tvorena soubory:
: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
: \contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: najit odpovidajici soubory pro msp430

: \contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc,
:: HPLTimer2.nc, HPLTimer2C.nc
:: najit odpovidajici soubory pro telos a telosb

: \contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: mely by zustat stejne

: \contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: mely by zustat stejne

* protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
: [http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Priklad komentovaneho souboru Phy.nc]

* pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: [http://veverka.sh.cvut.cz/~seamus/diplomka/preklad.html viz. pictures]
: Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Weekly Reports

2007-02-22T00:48:03Z

Auersm1: /* week [7,8 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
: - ''Wiki upgrade - section Project description''
: - ''study of the physical layer files structure for MSP430 and Telos''
: - ''problems with a generation of documentation (graphviz) ''
:: - ''compilation of MAC layer files OK, build documentation fails''
:: - ''compilation of PHY layer files fails, build documentation fails''
: - ''[http://rtime.felk.cvut.cz/hw/images/a/a9/Phy.nc.pdf Phy.nc commented file]''
* TODO
: - ''implementation of missing commands to appropriate files for MSP430, Telos and TelosB''

----

== week [5,6 - 2007] ==
* DONE
: - ''duplicate files of telos, telosb and msp430 platform: from "\tinyos-1.x\tos\platform\" to "\tinyos-1.x\contrib\hurray\tos\platform\" - during the testing and improvements (it's not necessary to copy all files, but only a modified files)''
: - ''modification of file "\tinyos-1.x\contrib\hurray\tos\platform\msp430\PowerManagementM.nc" - changes were inspired by the PowerManagementM file of MicaZ platform"
: - ''small changes on files (addition of telosb platform data) - modification of both files "platforms.properties" form "\tinyos-1.x\contrib\hurray\apps\ and \tinyos-1.x\contrib\hurray\", linking TmoteSky structure always doesn't work''
* TODO
: ''- change the directories before linking so that all files included in "\tinyos-1.x\tos\system\" (as well as in "\tinyos-1.x\contrib\hurray\tos\platform\msp430\") were replace by the files from "\tinyos-1.x\contrib\hurray\tos\platform\msp430\"''
----

== week [7,8 - 2007] ==
* DONE
: - ''small changes on files (deletion of unnecessary specification "push") - modification of both files ".platform" from "\tinyos-1.x\contrib\hurray\tos\platform\telos\" and "\tinyos-1.x\contrib\hurray\tos\platform\telosb\"''
: - ''rectifying errors: Blink application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''rectifying errors: AssociationExample application - modification of Makefile to accept the another two platforms - telos and telosb''
: - ''strange behaviour of cygwing program during the compilation Blink and also AssociationExample application, after compilation error code "make *** [exe0] Error 1", the restart of cygwin environment helps (sometimes) and this error code disappears (sometimes)''
: - ''application Blink is functional for some generated Makefiles''
: - ''location of header files for avr and msp430 platform''
: - ''rectifying errors: "implicit declaration of function TOSH_READ_CC_CCA_PIN" - problem with HW-header files, this function is not declared for telos platform. I want MAC and PHY files to remain unchanged, therefore I found the matching PIN on hardware files and rename this one. I'm testing it now.
: - ''rectifying errors: In component HPLCC2420M: "HPLCC2420.enableFIFOP" and "HPLCC2420.disableFIFOP " not implemented. Simple insertion the missing functions from HPLCC2420M.nc (MicaZ platform) to HPLCC2420M.nc (telos platform, telosb haven't its own modul, use this one) is impossible. Changes were inspired by the implementation for MicaZ platform. I'm testing it now.
* TODO
: - ''rectifying error: In component TimerAsyncC: component HPLTimer2C not found. Will probably be need some larger modification of code.''
----

== week [9,10 - 2007] ==
* DONE
* TODO
----
== week [11,12 - 2007] ==
* DONE
* TODO
----
== week [13,14 - 2007] ==
* DONE
* TODO
----
== week [15,16 - 2007] ==
* DONE
* TODO
----

Weekly Reports

2007-02-22T00:11:00Z

Auersm1: /* week [5,6 - 2007] */

Weekly Reports

2007-02-21T16:32:46Z

Auersm1: /* week [7,8 - 2007] */

Weekly Reports

2007-02-11T02:53:43Z

Auersm1: /* week [5,6 - 2007] */

Open-ZB stack porting to TmoteSky

2007-02-11T02:41:43Z

Auersm1: /* Developing phase */

Open-ZB stack porting to TmoteSky

2007-01-31T14:10:11Z

Auersm1: /* Developing phase */

Weekly Reports

2007-01-30T14:38:45Z

Auersm1: /* week [1,2 - 2007] */

=== week [1,2 - 2007] ===
* DONE
: - ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
: - ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
: - ''procetl jsem nejake datasheety k Tmote Sky TelosB''
: - ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
: - ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
: - ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
: - ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
0) drobny upgrade informaci ve WIKI (puvodni sekce)

1) zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy
je tvorena soubory:
:: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: - je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
::\contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: - z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: - mely by zustat stejne

::\contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: - najit odpovidajici soubory pro msp430

::\contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc, HPLTimer2.nc, HPLTimer2C.nc
:: - najit odpovidajici soubory pro telos a telosb

::\contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: - mely by zustat stejne

::\contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: - mely by zustat stejne

::\contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: - mely by zustat stejne

2) protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
Jakym zpusobem - viz. priloha.

3) pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
:: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
:: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: (viz. prilozene obrazky)
Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

* TODO
# najit odpovidajici soubory s prikazy a udalostmi pro msp430, telos a telosb (viz. bod DONE 1)
# dokoncit analyzu souboru fyzicke vrstvy (viz. bod DONE 2)
# "vhodne" pouzit misto souboru pro micaz soubory pro telos/telosb
# pripadne upravit/doimplementovat chybejici prikazy a udalosti
# zajimalo by me, jestli jsou adresare pro jednotlive platformy nezavisle nebo mezi sebou sdileji soubory, podle aplikace AssociationExample se zda ze vzdy vyssi verze pouziva+upgraduje soubory nizsi verze.

----

== week [5,6 - 2007] ==
* DONE
* TODO
----
== week [7,8 - 2007] ==
* DONE
* TODO
----

Weekly Reports

2007-01-30T14:37:07Z

Auersm1: /* week [3,4 - 2007] */

=== week [1,2 - 2007] ===
* DONE
** ''procetl jsem dalsi lekce TinyOS, jsem u seste "Displaying Data on a PC, The Oscilloscope application"''
** ''procetl jsem dalsi kapitoly dokumentu "Telos and Aegis Quick Start Guide" az po "The Aegis application"''
** ''procetl jsem nejake datasheety k Tmote Sky TelosB''
** ''opet jsem procetl a prelozil cast o fyzicke vrstve v "Reference Guide IEEE 802.15.4 protocol implementation"''
** ''vyzkousel jsem si praci s Wiki na rtime.felk''

* TODO
** ''co nejrychleji uspesne absolvovat zkousky (hlavne z MTR) a pote se venovat praci na diplomce''
** ''pokrocit s implementaci 802.15.4 stacku na TelosB''
----

== week [3,4 - 2007] ==
* DONE
0) drobny upgrade informaci ve WIKI (puvodni sekce)

1) zjistil jsem, ktere soubory pouziva implementace fyzicke vrstvy
je tvorena soubory:
:: \contrib\hurray\tos\lib\phy\ phy_const.h, phy_enumerations.h, Phy.nc, PhyM.nc
:: - je treba najit odpovidajici soubory patrici msp430 a telosu, ktere spravuji prikazy a udalosti, ktere obsahuji posledni dva hlavni soubory a upravit je - implementovat v nich dalsi obsazene prikazy a udalosti

: pouziva:
::\contrib\hurray\tos\lib\CC2420Radio\ byteorder.h, HPLCC2420.nc, HPLCC2420FIFO.nc, HPLCC2420RAM.nc
:: - z CC2420Control.nc a CC2420ControlM.nc jsou pouzity parametry a data pro PhyM.nc
:: - mely by zustat stejne

::\contrib\hurray\tos\platform\avrmote\ HPLInit.nc, HPLPotC.nc
:: - najit odpovidajici soubory pro msp430

::\contrib\hurray\tos\platform\micaz\ HPLCC2420C.nc, HPLCC2420FIFOM.nc, HPLCC2420M.nc, HPLPowerManagementM.nc, HPLTimer2.nc, HPLTimer2C.nc
:: - najit odpovidajici soubory pro telos a telosb

::\contrib\hurray\tos\system\ frame_format.h, Main.nc, RealMain.nc, PotC.nc, PotM.nc
:: - mely by zustat stejne

::\contrib\hurray\tos\interfaces\ Pot.nc, HPLPot.nc, PowerManagement.nc, StdControl.nc,
:: - mely by zustat stejne

::\contrib\hurray\tos\interfaces\ieee802154\phy\ all
:: - mely by zustat stejne

2) protoze nelze pouze jednoduse zamenit soubory a jejich provazani je do velke hloubky, zacal jsem prodrobne analyzovat vsechny soubory vyse, abych mel alespon "predstavu" jak vse spolu komunikuje, jak je vse provazano, co co vola a pouziva, na co se co odkazuje, protoze abych porozumel, jak presne vrstva funguje a co se v ni pri behu deje, na to (snad postupem casu) nemam znalosti.
Jakym zpusobem - viz. priloha.

3) pro nalezeni veskerych provazani jsem chtel pouzit vytvorenou dokumentaci (pomoci graphviz), moje jedine informace jsou z Technical Report (Andre Cunha, Mario Alves), coz je malo, bohuzel s temito problemy:
:: - prelozit soubory MAC vrstvy nelze, vytvorit dokumentaci lze
:: - prelozit soubory PHY vrstvy ani vytvorit dokumentaci nelze
:: (viz. prilozene obrazky)
Nevite proc? Jestli se soubory kompiluji vsechny spolecne s aplikaci nebo nejak jinak, protoze pri prekladu aplikace pro micaz probehne vse ok (ale neoverim jestli to funguje, mam k dispozici pouze modul telosb).

* TODO
# najit odpovidajici soubory s prikazy a udalostmi pro msp430, telos a telosb (viz. bod DONE 1)
# dokoncit analyzu souboru fyzicke vrstvy (viz. bod DONE 2)
# "vhodne" pouzit misto souboru pro micaz soubory pro telos/telosb
# pripadne upravit/doimplementovat chybejici prikazy a udalosti
# zajimalo by me, jestli jsou adresare pro jednotlive platformy nezavisle nebo mezi sebou sdileji soubory, podle aplikace AssociationExample se zda ze vzdy vyssi verze pouziva+upgraduje soubory nizsi verze.

----

== week [5,6 - 2007] ==
* DONE
* TODO
----
== week [7,8 - 2007] ==
* DONE
* TODO
----

Open-ZB stack modification

2007-01-29T18:12:22Z

Auersm1: /* Links */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports (CZ)]] - what is done, what is doing, what will be done.

== Project definition ==
OpenZB-stack is developed for the MicaZ platform. My first task is to transform OpenZB-stack to the TelosB platform (Tmote Sky). Second task is develop aplication by using TinyOS for data collection along through the wireless body area network for monitoring physical condition of a Parkinson’s disease patient.

== Developing phase ==
Now Im modifying Physical layer of OpenZB-stack.

== Results ==

== Documentation ==

== Links ==
* [http://sensorweb.vancouver.wsu.edu/wiki/index.php/Tinyos TinyOS Start Guide (Sensorweb Research Laboratory at Washington State University)]
* [http://www.open-zb.net/downloads.php An IEEE 802.15.4/Zigbee protocol implementation (in nesC/TinyOS)]

Open-ZB stack modification

2007-01-29T18:06:40Z

Auersm1: /* Links */

Open-ZB stack modification

2007-01-29T18:01:02Z

Auersm1: /* Results */

Open-ZB stack modification

2007-01-29T17:54:05Z

Auersm1: /* Project definition */

Open-ZB stack modification

2007-01-29T17:42:01Z

Auersm1: /* Summary & Motivation */

== Weekly reports ==
[[Weekly_Reports | Weekly Reports (CZ)]] - what is done, what is doing, what will be done.

== Project definition ==

== Results ==

== Documentation ==

== Links ==