Skip to content

Latest commit

 

History

History
 
 

IoT-GPIO

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
topic languages products
sample
csharp
cpp
js
windows
uwp

General Purpose Input/Output (GPIO) sample

Shows how to use the Windows.Devices.Gpio namespace to allow apps to set, read, and react to state changes in the General Purpose Input/Output (GPIO) pins on a Windows IoT (Internet of Things) device. These pins are often used to access sensors, motors, LEDs, etc.

Note: This sample is part of a large collection of UWP feature samples. If you are unfamiliar with Git and GitHub, you can download the entire collection as a ZIP file, but be sure to unzip everything to access shared dependencies. For more info on working with the ZIP file, the samples collection, and GitHub, see Get the UWP samples from GitHub. For more samples, see the Samples portal on the Windows Dev Center.

This sample demonstrates the following:

  • Setting GPIO pin values.
  • Getting GPIO pin values.
  • Listening for changes in GPIO pin values.

Note The Windows universal samples require Visual Studio 2017 to build and Windows 10 IoT Core to execute.

To obtain information about Windows 10 IoT Core, go to Windows on Devices

To see more samples specifically describing how to leverage Windows 10 IoT Core, click on the Samples tab here.

To obtain information about Microsoft Visual Studio and the tools for developing Windows apps, go to Visual Studio

System requirements

IoT: Windows 10 IoT Core

Build the sample

  1. If you download the samples ZIP, be sure to unzip the entire archive, not just the folder with the sample you want to build.
  2. Start Microsoft Visual Studio 2017 and select File > Open > Project/Solution.
  3. Starting in the folder where you unzipped the samples, go to the Samples subfolder, then the subfolder for this specific sample, then the subfolder for your preferred language (C++, C#, or JavaScript). Double-click the Visual Studio Solution (.sln) file.
  4. Press Ctrl+Shift+B, or select Build > Build Solution.

Run the sample

The next steps depend on whether you just want to deploy the sample or you want to both deploy and run it.

Deploying the sample

  • Select the appropriate architecture for the device you want to deploy to (i.e. ARM for Raspberry Pi 2 or x86 for MinnowBoard Max)
  • For C#, select Remote Machine from Debug > Target device in your Project properties. For C++ and JavaScript, select Remote Machine from Debugger to launch dropdown in the Debugging tab of your Project properties.
  • For C#, enter the target device name or IP address in Debug > Remote Machine in your Project properties. For C++ and JavaScript, enter the target device name or IP address in Debugging > Machine Name in your Project properties.
  • For C#, deselect the Use Athentication checkbox in the Debug tab of your Project properties. For C++ and JavaScript, select No for Debugging > Require Authentication in your Project properties.
  • Select Build > Deploy Solution.

Deploying and running the sample

  • Select the appropriate architecture for the device you want to deploy to (i.e. ARM for Raspberry Pi 2 or x86 for MinnowBoard Max)
  • For C#, select Remote Machine from Debug > Target device in your Project properties. For C++ and JavaScript, select Remote Machine from Debugger to launch dropdown in the Debugging tab of your Project properties.
  • For C#, enter the target device name or IP address in Debug > Remote Machine in your Project properties. For C++ and JavaScript, enter the target device name or IP address in Debugging > Machine Name in your Project properties.
  • For C#, deselect the Use Athentication checkbox in the Debug tab of your Project properties. For C++ and JavaScript, select No for Debugging > Require Authentication in your Project properties.
  • Press F5 or select Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or select Debug > Start Without Debugging.