Setting board and project configuration options

This section contains steps to set options for your board and Internet of Things project. This includes the name of your board, whether to run the application on the board automatically when the board boots, and more. See the links below:

Changing the name of your board

  1. Click the Manage your daemon/IoT device icon Manage your daemon/IoT device icon in the lower right of the Intel XDK, then select Board Configuration. The Board Configuration dialog box opens.
  2. Type a name for your board in the Board Name field.
  3. Click Submit to apply your changes.

Determine whether to run the application on your board automatically when the board boots

By default, the Node.js* application last uploaded to your board runs automatically as soon as the board boots. You can have your board boot without running the application instead.

  1. Click the Manage your daemon/IoT device icon Manage your daemon/IoT device icon in the lower right of the Intel XDK, then select Board Configuration. The Board Configuration dialog box opens.
  2. Do one of the following:
    • To have the board automatically run your application when it boots, select the Run previously loaded application at startup check box.
    • To have the board boot without running the application, clear the Run previously loaded application at startup check box.
  3. Click Submit to apply your changes.

Syncing the time on your board to the time on your host

You can sync the GMT time on your board with the GMT time on your host system. This is helpful when you have different versions of a file on the host and on the target, and need to determine which version is newer.

  1. Click the Manage your daemon/IoT device icon Manage your daemon/IoT device icon in the lower right of the Intel XDK, then select Sync PC time w/clock on target device.

Determining whether to perform npm installations entirely on your board

By default, when you upload your project to your board, the Intel XDK performs an npm installation as follows:

  1. Fetches the required packages on your host system
  2. Transfers the retrieved files to your IoT device
  3. Executes an npm build on the IoT device

This is usually the best process to use, because it does not require your IoT device to have Internet access and also ensures that any build aspects that rely on the architecture and tools of the board run there. For example, modules that contain C code must be compiled on the board.

However, some modules contain scripts that are run during the fetch. For example, a module could select among several sets of header files depending on the architecture of the machine. With the default npm installation process, this will be the architecture of the host, not the IoT board. Therefore, the installation cannot be expected to work correctly.

Instead, you can choose to perform the entire npm installation on the board. Steps to do so are below.

  1. Click the Manage your daemon/IoT device icon Manage your daemon/IoT device icon in the lower right of the Intel XDK, then select Upload Options. The Upload Options dialog box opens.
  2. Do one of the following:
    • To install npm entirely on your IoT device, select the Perform npm install entirely on board check box.
    • To perform part of the npm installation on your host machine, as described in the introduction, clear the Perform npm install entirely on board check box.

      Your board must have Internet access and (if proxies are needed) the appropriate proxy configuration to perform the "get" operations on npm, or the npm installation will fail.
  3. Click OK to apply your changes.

Setting the amount of time to wait for application cleanup

You can determine the amount of time the Intel XDK waits for your application to finish any cleanup processing before ending the program. When you first click the Stop icon Stop icon, the Intel XDK sends a SIGTERM signal. Your application can catch this signal and perform cleanup by setting pins it has used to a low or high resistance state before it terminates (for example). After a certain time interval, if your application has not terminated, the Intel XDK sends a SIGKILL signal. This signal cannot be caught by the application and terminates the application immediately.

By selecting an appropriate delay interval between the SIGTERM and SIGKILL signals, you can give the application enough time to clean up, while still ending the application quickly enough after you click Stop to give it a responsive feel.

  1. Click the Manage your daemon/IoT device icon Manage your daemon/IoT device icon in the lower right of the Intel XDK, then select Set time to wait for app cleanup.
  2. Type the amount of time, in milliseconds, to wait between sending the SIGTERM and SIGKILL signals in the Delay (milliseconds) field.

    To terminate the application when you click Stop, without any time for application processing, type 0. The Intel XDK will send a SIGKILL signal without a corresponding SIGTERM.
  3. Click OK to apply your changes.

     Set time to wait for app cleanup dialog box
For more complete information about compiler optimizations, see our Optimization Notice.