MTS420 Progress

Completed Work

Code Organization

The code for a sensorboard consists of multiple layers. This section describes how those layers are organized in the tos directory structure.

• Independent Chip Code - The sensorboard will be an assembly of different chips. Some of those chips will be complicated enough to merit platform independent code and should be located in tos/chips/<chipname> directory.
• Sensorboard Dependent Chip Code - Some chips will require code specific to the physical connections made on the sensorboard and the code should be located in tos/sensorboards/<boardname>/chips/<chipname> directory.
• Platform Dependent Sensorboard Code - Some code will depend on the specific platform it is being connected to (for example, anything that uses buses controlled by the platform). That code should be located in tos/platforms/<platformname>/sensorboards/<boardname>/ and organized in a similar chips/<chipname> sub directory as appropriate.
• Independent Helper Code - Code that can be written to be independent of the sensorboard should be added in an appropriate tos/lib/<name> directory.
• Dependent Helper Code - Code that exposes useful features of the sensorboard and is specific to the sensorboard should be located in the tos/sensorboards/<boardname>/ directory and any appropriate sub directories if required.

MTS420CA/CB GPS

TODO

Remaining Work

• Documentation and Code for all sensors except the GPS on the MTS420CA
• Documentation for the GPS 420CA
• Documentation for supporting code
• Refining and Testing GPS Code
  • SiRF packet reception
  • Controlling GPS
  • Test Power (does GPS_ENA need to be high? what does GPS_PWR do?)
• How To documentation
  • How to use the code
  • File List

Where to find the code

TODO