Product Information

What features does the Intel® Joule™ compute module have?
The Intel® Joule™ compute module includes:
  • A high-performance, 64-bit, 1.7 GHz, quad-core Intel Atom® processor available at two clock speeds: 1.5 GHz (fixed) and 1.7 GHz with a 2.4 GHz burst mode
  • 4 GB LPDDR4 RAM and 16 GB eMMC memory
  • Intel® HD Graphics with 4K video capture and display
  • 802.11ac Wi-Fi with MIMO and Bluetooth® 4.1
  • USB 3.0 and multiple GPIO, I2C, and UART interfaces
  • A Linux*-based OS tailored for IoT and smart devices
  • Enhanced support for the Intel® RealSense™ cameras and libraries


Using the Intel® Joule™ Module

Which baud do I use for the serial port?
Use the baud of 115,200. In older versions of the BIOS and OS, the baud was 230,400.
Why is my board displaying incorrectly in the Device Manager? Why is the driver for the serial device missing?
If you're trying to open serial communication with your development platform on a Windows* host, you may find that when you open Device Manager, the serial device has no driver. The Device Manager may show an error or an unknown driver message, along with a yellow warning triangle icon. If this happens:
  1. On your host computer, download the CDM v2.12.18 WHQL Certified.zip file from the FTDI website.
  2. Unzip the file.
  3. Right-click on the broken serial device entry in the Device Manager, and then select Update driver software.
  4. Click Browse my computer and select the folder you extracted the files to. The driver should automatically be found.
Why does my board keep rebooting while I am using it?
There are a couple possible causes for this.
  1. Equipment issues:
    • You may have an issue with rebooting if you attempt to power your development platform using the Type C USB cable. For general operation, use the power supply to provide power to the development platform. If flashing your BIOS, be sure to follow the directions to power your board in the correct order.
    • Be sure that you are using a 12 V power supply when powering your development platform, as described in the requirements.
    • Restarting may be caused by your development platform overheating, sometimes after 30 minutes or so of use. If you suspect your development platform is overheating, unplug all connections, including the power barrel jack, USB C connector, and powered USB 3.0 hub, and then allow the development platform to cool before attempting to use it again.
  2. Power management and configuration:
    • Restarting is a known issue with Reference Linux* OS for IoT Build 76 or 77. To fix this:
      1. Disable the power management in the BIOS.
      2. Boot to the BIOS menu by pressing F2 during boot.
      3. From the BIOS menu, choose Device Manager > System Setup > ACPI Settings > Disable Low Power S0 Idle Capability.
    • It may help to disable the runtime watchdog. To do so, locate and delete the /etc/systemd/system.conf.d/00-runtime-watchdog.conf file on your development platform and reboot the development platform. Alternatively, you can comment out the two lines in the file and reboot.
Why is my keyboard or my mouse working erratically, and I cannot boot to the BIOS?
This can be caused by a bad USB hub. Try a different powered USB 3.0 hub to see if this is the issue, and be sure that your keyboard, mouse, or other peripheral is not the issue.

Try unplugging and reconnecting your device. You may want to plug a replacement device in to see if this resolves the problem.

You may experience intermittent delays between entering keyboard commands and the input appearing onscreen. This is a known issue, and your keystrokes should appear onscreen in a few seconds.
I unplugged my development platform, but why won't it turn off?
Be sure that you have unplugged ALL connections to your development platform over which it might be receiving power. This includes:
  • 12 V power supply attached to the barrel jack
  • The USB Type C connection
  • The powered USB 3.0 hub. The development platform can end up drawing enough power from the USB hub to turn the lights on, but will not have enough power to perform tasks like flashing your BIOS.
    Why do I get an error that mentions "throttling" while I am flashing the eMMC or doing processor-intensive tasks?
    This error occurs when the CPU gets too hot. Find a way to cool down your CPU by using a heatsink or fan.
    My development platform is asking me to log in, but I don't know my password. What do I do?
    By default, your user name is root and the password is blank.

    If you set a password for your development platform and forgot it, you can reset your development platform's password by reflashing Reference Linux* OS for IoT onto the development platform. You'll need to create a bootable device, boot from it, and set up your password. Note that when you flash the development platform with a new Reference Linux* OS for IoT image, you'll also need to re-enable SSH and unblock the ports on your development platform.
    How do I set the maximum power of the module to match my workload and cooling capacity?
    You can learn how to adjust the module power limit here.
    What is the maximum number of insertion cycles for the module?
    The Hirose* DF40C-100DS-0.4V(51) board-to-board connectors are rated at 30 lifetime install and remove cycles. Learn more.


    Connecting to Your Board

    How do I enable SSH?
    1. From the command line on the Intel Joule module, enter the command:
      echo 'PermitRootLogin yes' >> /etc/ssh/sshd_config
    2. Set a password for the root account by entering the command:

      See the instructions on the Reference Linux* OS for IoT Project website for detailed instructions.
    How do I enable Ethernet, Wi-Fi*, or Bluetooth® technology?
    See the following for steps on using each of these technologies:
    • Wi-Fi: Connecting the development platform to Wi-Fi
    • Ethernet: Connecting the development platform to Ethernet
    • Bluetooth: Pairing the development platform with a Bluetooth® device
    Why won't my board connect to Wi-Fi* or pick up networks?
    Make sure that you have connected both antennas to your development platform. The antennas should snap securely into the connectors.
    Why am I getting a "Not registered" message when trying to connect to Wi-Fi?
    If you see a "not registered" message when trying to connect the development platform to a Wi-Fi network, make sure that you have turned the agent on. From the command line, enter:

    agent on
    Why can't I connect to my development platform in the Intel® XDK?
    Try unblocking your ports and enabling root login.
    Why is my board unable to download or access anything?
    Make sure you have unblocked your ports on the development platform.
    Why do I get an error message when trying to connect to Wi-Fi?

    If you get a message when connecting to a Wi-Fi network that indicates you are not registered, make sure that you have turned the agent on for the connection manager.

    From the command line, enter: agent on

    Why do I experience issues with the PuTTY interface when I connect my board?
    When communicating with your development platform over a serial connection in PuTTY, maximize your PuTTY window. The issue should resolve itself and the output should become readable again.
    Why is my PuTTY screen blank?
    It is likely that you simply missed the log messages as the development platform was starting. For example, this can happen if you started your development platform, and then connected to it using PuTTY a minute or two later.
    Why do I get an "Error getting VPN connections" message when entering connmanctl interface?
    When trying to access connmanctl, you may see a message similar to the following:

    root@intel-corei7-64:~# connmanctl
    Error getting VPN connections: The name net.connman.vpn was not provided by any .service

    This message is normal and can be ignored.
    Why can't I get the LED to blink?
    If you are unable to see the LED on the development platform blink, check that you have set the correct pin number. Pins 100, 101, 102, and 103 represent the onboard LEDs.


    Flashing the BIOS

    How do I access the BIOS (EFI shell)?
    When the system starts, press F2 to go to the EFI shell.
    How do I flash a new BIOS image?
    See Flashing the BIOS and visit the downloads page for the latest version of the BIOS.
    Why do I get an "ERROR: Downloading failed!" message when trying to flash the BIOS?
    You may experience this error if you try to flash the BIOS and your internet connection has a corporate proxy. Try running the Flash.bat script on an open network instead.
    Why do I get a "\DN was unexpected at this time" message when trying to flash BIOS?
    Download the archive file to a folder of the same name as the original zip file (minus the .zip extension). For example, if you downloaded the archive file twice, you might have extracted the contents to a folder named something like Joule-Firmware-2016-09-23-131_Public (1). This can cause errors when running the script. In this case, you'd need to remove the (1) at the end of the folder name.


    Starting the Development Board

    Why won't my USB device show up in BIOS?
    Try using a different USB device, port, or USB hub.
    Why won't my development platform start from a USB drive or microSD* card?

    Make sure you don't have a microSD* card and a USB drive plugged into the development platform at the same time. Confirm that your device is securely connected to the development platform.

    Next, try starting your board and changing the boot order to start from your bootable device first.

    If you still encounter problems, rewrite the latest version of Reference Linux* OS for IoT onto your bootable device and restart your device. Be sure to extract the .xz archive file and write the Reference Linux* OS for IoT image to the bootable device, not the archive file.


    Installing Reference Linux* OS for IoT

    How do I install a Reference Linux* OS for IoT image to the development platform eMMC?
    See Creating a bootable device.
    I can't install Reference Linux* OS for IoT onto my board. What do I do?

    Make sure your development platform is booting from your bootable device by going into the BIOS and setting the boot order to start from the EFI USB Device first. See Installing Your Operating System for detailed steps.

    If you are seeing a message about the image on the USB drive being "tainted":

    1. Delete the /etc/machine.id file from the eMMC.
    2. Rewrite the Reference Linux* OS for IoT image on your bootable device and try booting your development platform again. Once the development platform fully starts using the image on your bootable device, you should automatically be presented with the choice to install Reference Linux OS for IoT on your development platform.
    How do I know what version of Reference Linux* OS for IoT is running on the development platform?

    From the command line on your development platform, enter the command:

    cat /etc/*-release

    Information about the Reference Linux* OS for IoT build is displayed, as shown in the example output below.

    NAME="Ostro OS"
    PRETTY_NAME="Ostro OS 1.0-snapshot-20160609"

    What does it mean when I get an "in use by another process" message when I try to write Reference Linux* OS for IoT to my microSD* card?

    This can be an issue if your file is included for backup in a program like Syncplicity*. Be sure that no other applications are using the Reference Linux* OS for IoT image file.

    For Syncplicity, right-click the file and select Syncplicity > Exclude. You may need to exclude the containing folder and restart your computer before the file is released.

    How do I setup my environment to cross-compile my application code for the Intel® Joule™ module?
    Please see Configuring Environment for Cross-Compilation for steps.
    What do I do if nothing happens when I try to press F2 to access the boot menu?

    If you experience this issue while trying to flash the Intel® Joule™ development platform with the latest version of the Reference Linux* OS for IoT, you may need to use a separate keyboard and/or mouse (which should be attached to the development platform) to enter commands.

    • If you are using a bootable microSD* card:
      Attach a powered USB hub to the Type A USB port on the development platform. Attach your USB keyboard and USB mouse to the powered hub. Afterwards, you can use the keyboard to enter F2 during the boot process to access the setup menu and flash your board.
    • If you are using a bootable USB drive:
      Attach a powered USB hub to the Type A USB port on the development platform. Attach your bootable USB drive, USB keyboard, and USB mouse to the powered hub. Afterwards, you can use the keyboard to enter F2 during the startup process to access the setup menu and flash your board.

    For detailed requirements for the powered USB hub, see the Material Requirements.

    I can't install Docker* or Intel® System Studio IoT Edition. What do I do?

    If you have issues installing Docker*, virtualization may be disabled in your host computer's BIOS. In the BIOS, make sure that you enable virtualization. The option name will be listed as Enable Intel VT-x or something similar. Steps to enter your system's BIOS, as well as the name of the option on your computer, may vary from system to system. Check the documentation for your host computer for specifics.

    When installing the Intel® System Studio IoT Edition on a Windows* host, you may run into issues when VirtualBox* tries to create a virtual machine. Try the following:

    1. Open Network Connections.
    2. Right-click the VirtualBox Host-Only Network adapter (created as part of the installation process) and select Properties.
    3. Select the VirtualBox NDIS6 Bridged Networking Drive check box. Click OK.
    4. Right-click the network adapter again, and then select Disable.
    5. Right-click the network adapter again, and then select Enable.

    If you are still having issues, try the following:

    1. Uninstall Docker Toolbox and VirtualBox.
    2. Right-click the installer and select Run as Administrator.
    3. Follow the steps in the setup wizard until you reach the Select Additional Tasks page.
    4. Select the Install VirtualBox with NDIS5 driver check box, then continue to install Docker Toolbox.
    5. After the setup process is complete, run Docker Quickstart Terminal and wait for the process to finish. It may take 5-10 minutes. Afterwards, continue to run the Intel® System Studio IoT Edition from the iss-iot-launcher.bat file.

    Submit a ticket to get expert help with a technical or warranty issue.   Get Started