How do I know what version of Reference Operating System for IoT is running on the development platform?
From the command line on your development platform, enter the command:
See Programmers Guide for details.
When trying to write Reference Operating System for IoT to my microSD* card, the file is "in use by another process"
This can become an issue if your file is included for backup in a program like Syncplicity*. Be sure that no other applications are using the Reference Operating System for IoT image file.
I can't install Reference Operating System for IoT onto my board
Make sure your development platform is booting from your bootable device by going into the BIOS and setting the boot order to boot from the EFI USB Device (or your microSD* card) first. See Changing the Boot Order for detailed steps.
If you are seeing a message about the image on the USB drive being "tainted" (e.g. The USB-stick has been booted at least once and looks tainted. Installer skipped! Press any key to boot from the USB stick.) then:
- Delete the /etc/machine.id file from the development platform's eMMC (onboard memory).
- Rewrite the Reference Operating System for IoT image on your bootable device and try booting your development platform again. Once the development platform fully boots up using the image on your bootable device, you should automatically be presented with the choice to install Reference Operating System for IoT on your development platform.
How do I set up my environment to cross compile my application code?
Please see Configuring Environment for Cross Compilation for steps.
How do I enable Robot OS (ROS) in Ref-OS-IoT?
Robot OS (ROS – see http://wiki.ros.org/) features are supported by Ref-OS-IoT but not included in the official image by default. These can be included in your own build of Ref-OS-IoT. See OS Custom Recipe for details.