You can bring up the IoT Developer Kit tab from the Help menu.
This usually happens if you left your program running on the device and try to upload it again, because the application binary is already in use. A simple way to fix it is to do a software disconnect from the IDE. On the Window -> Show View -> Other menu select Remote Systems (under the Remote Systems group). Then from this new tab right click on your Intel® Galileo/Edison board and select Disconnect, which will terminate the running process and fix the issue.
If you worked with the Intel® IoT Developer Kit versionn of Eclipse before, you can load your older projects using this version too. To do so, either set your workspace path to the previous one, or copy your previous project files over if you ended up using a newly created workspace. Then go to File -> Import and from the General category select Existing Projects into Workspace.
See the Starting/Duplicating a Project article.
From the Intel IoT Developer Kit tab open the Sensors Examples using UPM libraries and browse through the example files to identify the sensor you would like to add. You can also use this list: http://iotdk.intel.com/docs/master/upm/modules.html to see if the sensor is currently supported; however, some newly added sensors might not be included. Once you find the sensor, open up the project properties, go to C/C++ Build -> Settings -> Tool Settings -> Cross G++ Linker -> Miscellaneous, and add your library to the linker flags. Some sensors share the same library file while others have their own. For instance, if you want to use the Grove - Air Quality Sensor, put –lupm-gas in the Miscellaneous box, while for the Grove - Digital Accelerometer (16g) enter –lupm-adxl345. Alternatively, you can find all the UPM library files under /usr/lib on your Intel Galileo/Edison device, and you can update MRAA and UPM with opkg.
We’re sorry, but because there are thousands of sensors out there, it’s not unlikely you might want to use a sensor that is not currently implemented in UPM. Your starting point in this situation is to identify what kind of sensor you’re dealing with, as lib MRAA provides some generic interfaces that might be useful in your quest to get the sensor working. Sometimes it’s as simple as reading a value of an analog pin and processing it, but other sensors might be a lot more complicated. As a general rule of thumb, try to identify a similar sensor to the one you have that already exists in UPM and take a look at the code to understand how it works. You will notice that different manufacturers may use the same chip on a similar sensor, in which case the UPM code should work with little or no changes at all. When this is not the case, use the existing sources and examples when possible, but most importantly the sensor data sheets to get you on your way. More details, including porting Arduino examples and building UPM, are here: http://iotdk.intel.com/docs/master/upm/pages.html
We actually encourage the community to contribute to lib UPM by adding new and cool sensors you used in a project. Interface code must adhere to a few guidelines before we add it to the library. Thus we encourage you to read through our contributions guide as it will speed up the review process. You can find more information here: http://iotdk.intel.com/docs/master/upm/contributions.html
This is not an easy task, but should be possible with some effort. UPM uses CMake* to generate makefiles that will compile the source code. While there is an Eclipse plugin available for this sort of project (CMakeBuilder), most users report having better success using the existing makefile project type available by default in Eclipse and running CMake separately. To set this up you will have to import your UPM clone into Eclipse as a Makefile project and set the toolchain accordingly. A good way to understand this process is by performing a separate build of UPM first. You can find more about this in the build guide: http://iotdk.intel.com/docs/master/upm/building.html
Tested on Windows 7, with an Edison and Eclipse IoT Dev kit v1.0.
Step 1:
Source: http://wiki.eclipse.org/CDT/User/FAQ#CDT_does_not_recognize_C.2B.2B11_features
Go to Project Properties->C/C++ Build->Settings->Tool Settings->GCC C++ Compiler->Miscellaneous->Other Flags.
Put "-std=c++11" at the end.
Step 2
Source: http://stackoverflow.com/questions/17457069/enabling-c11-in-eclipse-juno-kepler-luna-cdt
Go to Project Properties->C/C++ General-> Preprocessor Include Paths, Macros etc. ->Providers
In "CDT CROSS GCC Built-in Compiler settings", put "-std=c++11" at the end.
Step 3
Rebuild the index with Project -> C/C++ Index -> Rebuild
Get access to the new Intel® IoT Developer Kit, a complete hardware and software solution that allows developers to create exciting new solutions with the Intel® Galileo and Intel® Edison boards. Visit the Intel® Developer Zone for IoT.
