crime:sunspot
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
crime:sunspot [2010/07/01 11:17] – cfscholl | crime:sunspot [2011/04/24 11:09] – wamerijc | ||
---|---|---|---|
Line 17: | Line 17: | ||
The project is developed using Eclipse. You can check the project out using the normal SVN plugin. Make sure that you use the wizard and import the project as a java project. | The project is developed using Eclipse. You can check the project out using the normal SVN plugin. Make sure that you use the wizard and import the project as a java project. | ||
- | Configure the built path by selecting the src folder to be included in the built path. Next add the following jar's to the project. | + | Configure the built path by selecting the src folder to be included in the built path. Next add all the jars located in the lib folder |
- | looci.jar | ||
- | multihop_common.jar | ||
- | spotlib_common.jar | ||
- | spotlib_device.jar | ||
- | squawk_common.jar | ||
- | squawk_device.jar | ||
- | transducer_device.jar | ||
===== Configuration ===== | ===== Configuration ===== | ||
Like the deployment process of any application for the sunspot deploying CRIME on your sunspots is done in two steps. | Like the deployment process of any application for the sunspot deploying CRIME on your sunspots is done in two steps. | ||
- | First the sunspot runtime has to be configured so that it contains all the used libraries. Then the actual application (in this case CRIME) has to be deployed to the sunspot. | + | First the sunspot runtime has to be configured so that it contains all the used libraries. Then the actual application (in this case a CrimeSPOT component) has to be deployed to the sunspot. |
+ | |||
+ | === SunSPOT SDK === | ||
+ | First of all, the SunSPOT " | ||
+ | |||
+ | |||
+ | === LooCI === | ||
+ | As CRIME makes use of the Looci firmware you will have to configure your sunspot runtime in order to include Looci in the sunspot vm. Instructions on how to do this can be found [[http:// | ||
+ | |||
+ | |||
+ | === CrimeSPOT === | ||
+ | After installing LooCI, CrimeSPOT also has to be added to the SunSPOT runtime. This can be done in 6 steps: | ||
+ | |||
+ | 1. Checkout the CrimeSPOT project from svn | ||
+ | |||
+ | 2. Build the project: | ||
+ | $ ant jar-app | ||
+ | |||
+ | 3. Move the resulting jar from CrimeSPOT/ | ||
+ | |||
+ | 4. Add the CrimeSPOT jar to the SunSPOT libs by editing the spot.library.addin.jars property in ~/ | ||
+ | spot.library.addin.jars=${sunspot.lib}/ | ||
+ | |||
+ | 5. Rebuild & reflash the SunSPOT library in / | ||
+ | $ ant library | ||
+ | $ ant flashlibrary (to be repeated for each sunspot, connected via usb) | ||
+ | |||
+ | 6. After reflashing the base station, restart it: | ||
+ | $ ant startbasestation | ||
+ | $ ant start-shared-basestation | ||
+ | |||
+ | |||
+ | === CrimeSPOT components === | ||
+ | A CrimeSPOT component can now be deployed over the air using LooCI' | ||
+ | |||
+ | Executing the following commands in the gateway suffices: | ||
+ | |||
+ | # deploy / | ||
+ | |||
+ | < | ||
+ | When your sunspot goes into a loop and restarts itself at boot time you can try to perform a new "ant flashlibrary" | ||
+ | </ | ||
+ | |||
- | < | ||
- | </ |
crime/sunspot.txt · Last modified: 2011/06/02 12:51 by wamerijc