Differences

This shows you the differences between two versions of the page.

--- crime:sunspot [2010/07/01 11:17] – cfscholl
+++ crime:sunspot [2010/07/01 14:18] – cfscholl
@@ 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.
-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 the project.
-looci.jar
-multihop_common.jar
-spotlib_common.jar
-spotlib_device.jar
-squawk_common.jar
-squawk_device.jar
-transducer_device.jar
 ===== Configuration =====
@@ Line 31: / Line 23: @@
 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.
+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.
+This has to be repeated for each sunspot:
+  - Connected the sunspot to the usb.
+  - Open a terminal to the Crime path.
+  - $ ant flashlibrary
+  - $ ant deploy
+After deploying the CRIME application on each of your sunspots you will have to start them over the air as follows.
 <code>
+ant startapp -DremoteId=0014.4F01.0000.XXXX -Duri=spotsuite://Sun_Microsystems_Inc/CrimeComponentTest/1.0.0
 </code>
+In this command you will have to replace XXXX with your sunspot ID. This ID can be found at the back of your sunspot. Usually under the form of 0000.XXXX
+<note>
+When your sunspot goes into a loop and restarts itself at boot time you can try to perform a new "ant flashlibrary". This sometimes resolves the problem.
+</note>