Skip to content

Latest commit

 

History

History
241 lines (230 loc) · 9.68 KB

TroubleShooting.md

File metadata and controls

241 lines (230 loc) · 9.68 KB
Raw
layout title permalink
default
Troubleshooting
/TroubleShooting.htm

Troubleshooting

Hardware

Check the Galileo Power.
  • Is the barrel plugged into the board?
  • Is the outlet plugged in and have power?
  • Does the board have lights on?
If the power is connected, and the board plugged in, then you may have a bad adapter or board. Try another power supply or board.

Visual Studio

There are a number of reasons why Visual Studio won't connect to the Galileo:
  • The Galileo isn't powered on.

  • The Galileo isn't connected on the same subnet as the desktop computer.

    This is often caused by a laptop on wireless attempting to communitcate with a wired galileo. The best solution is to have the Galileo's ethernet connected to the desktop via a dedicated ehternet port or USB ethernet adapter.

When you have received this message after creating a new project and trying to build and compile, then you may be missing the Galileo C++ SDK NuGet package. Also, Intellisense will be underlining all code relating the Arduino SDK (pictured below).



To recover, go to the TOOLS->NuGet Package Manager->Manage NuGet Packages for Solution... menu.

  • Confirm the NuGet Package is not already installed...

  • Search for the Galileo C++ SDK NuGet package


  • Install the NuGet package
When you return to your project, the Intellisense errors should be cleared up and your project should compile.

Windows on Intel Galileo

To Diagnose Windows not booting, it would be helpful to have a Windows Kernel Debugger installed while booting so the Experiences team can help diagnose the issue. 
      <ol>
        <li>
          Install <a href="http://msdn.microsoft.com/en-US/windows/desktop/bg162891">Debugging tools for Windows</a>
        </li>
        <li>
          Connect to your Galileo via serial. (See <a href="UpdateYourGalileo.htm">Updating your Galileo</a> for details on how to connect a serial connection.
        </li>
        <li>
          Open <kbd>WinDBG</kbd> and connect the kernel debugger (File -> Kernel Debugger...) to the COM port above.
        </li>
        <li>Boot windows and look for failures.</li>
      </ol>

      The most likely cause of Windows boot failure is incompatible Galileo Firmware. Ensure that you are <a href="IBoughtAGalileo.htm">running the latest firmware</a>.
    </div>
  </div>
</div>
<div class="panel panel-default">
  <div class="panel-heading">
    <h4 class="panel-title">
      <a data-toggle="collapse" data-parent="#accordion4" href="#collapseApplyBootMedia">
        ApplyBootMedia.cmd does not work
      </a>
    </h4>
  </div>
  <div id="collapseApplyBootMedia" class="panel-collapse collapse">
    <div class="panel-body">
        If ApplyBootMedia is failing, follow these steps to check for known issues:<br/>
        <ul>
            <li>Make sure that the SD card has been reformatted with the FAT32 system and that it is empty.</li>
            <li>Make sure that the path for both the .wim and ApplyBootMedia.cmd do not contain spaces.</li>
        </ul>
    </div>
  </div>
</div>

GalileoWatcher

Make sure you have allowed it through the firewall. 
      To check it's firewall configurations go to Control Panel > System and Security > Windows Firewall > Allowed Apps</li>
      <img src="images/GalileoWatcherFirewall.png"/>
    </div>
  </div>
</div>

Remote Deployment

Don't freak out! This happens due to the debugging over ethernet. 
<div class="panel panel-default">
  <div class="panel-heading">
    <h4 class="panel-title">
      <a data-toggle="collapse" data-parent="#accordian7" href="#collapseRemoteDeployment2">
        Unable to start debugging. The connection with the remote endpoint was terminated.
      </a>
    </h4>
  </div>
  <div id="collapseRemoteDeployment2" class="panel-collapse collapse">
    <div class="panel-body">
        This can sometimes happen when the name resolution is not working. Try using the IP Address shown for your Galileo in the the GalileoWatcher.
    </div>
  </div>
</div>
<div class="panel panel-default">
  <div class="panel-heading">
    <h4 class="panel-title">
      <a data-toggle="collapse" data-parent="#accordian9" href="#collapseRemoteDeployment4">
        Unable to start program 'c:\{File}'. The system cannot find the file specified.
      </a>
    </h4>
  </div>
  <div id="collapseRemoteDeployment4" class="panel-collapse collapse">
    <div class="panel-body">
        <h3>Configure remote deploying for your project</h3>
        Right click on your project and select Properties.<br/>
        Select the <kbd>Configuration Manager...</kbd> button from the upper right corner.<br/>
        Make sure "Deploy" is checked for your project<br/>
        Also make sure that your remote Debugger settings are set correctly. See <a href="AdvancedUsage.htm#collapseRemoteDebugging">Configure Remote Debugging</a> on the "Advanced Usage" page.
    </div>
  </div>
</div>
<div class="panel panel-default">
  <div class="panel-heading">
    <h4 class="panel-title">
      <a data-toggle="collapse" data-parent="#accordian10" href="#collapseRemoteDeployment5">
        Unable to start debugging. The debugger cannot connect to the remote computer. The debugger was unable to resolve the specified computer name.
      </a>
    </h4>
  </div>
  <div id="collapseRemoteDeployment5" class="panel-collapse collapse">
    <div class="panel-body">
        Make sure your project's remote debugger settings have the correct Remote Server Name. It should match the name of your Galileo board.
    </div>
  </div>
</div>

Return to homepage