Cpu.Pin Enumeration
Indentifies the General Purpose Input/Output (GPIO) pins.
Namespace: Microsoft.SPOT.Hardware
Assembly: Microsoft.SPOT.Hardware (in microsoft.spot.hardware.dll)
Syntax
public enum Cpu.Pin
Members
Member name | Description | |
---|---|---|
GPIO_NONE | Indicates that no GPIO pin is specified. | |
GPIO_Pin0 | Specifies GPIO pin 0. | |
GPIO_Pin1 | Specifies GPIO pin 1. | |
GPIO_Pin2 | Specifies GPIO pin 2. | |
GPIO_Pin3 | Specifies GPIO pin 3. | |
GPIO_Pin4 | Specifies GPIO pin 4. | |
GPIO_Pin5 | Specifies GPIO pin 5. | |
GPIO_Pin6 | Specifies GPIO pin 6. | |
GPIO_Pin7 | Specifies GPIO pin 7. | |
GPIO_Pin8 | Specifies GPIO pin 8. | |
GPIO_Pin9 | Specifies GPIO pin 9. | |
GPIO_Pin10 | Specifies GPIO pin 10. | |
GPIO_Pin11 | Specifies GPIO pin 11. | |
GPIO_Pin12 | Specifies GPIO pin 12. | |
GPIO_Pin13 | Specifies GPIO pin 13. | |
GPIO_Pin14 | Specifies GPIO pin 14. | |
GPIO_Pin15 | Specifies GPIO pin 15. |
Remarks
Because pin assignments are implementation-specific, this enumeration defines only constant for the first 16 pins and well as GPIO_NONE. When the SDK is ported to a specific hardware platform, it is expected that those who do the port will use this enumeration as the basis of an enumerated type for that platform that defines the GPIO pin assignments. Doing so will enable the platform-specific enumeration to be cast to the type Cpu.Pin. In this way, all SDK methods maintain type safety while still enabling full portability.
To use the correct pin definitions, you probably need to include a using statement in your code. For example, an application that uses the sample Freescale implementation would require the following statement in its .cs
files:
using Microsoft.SPOT.Hardware.FreescaleMXSDemo;
Version Information
Available in the .NET Micro Framework versions 2.0, 2.5, 3.0, 4.0, 4.1, and 4.2.