djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

examples/hwapi: button_led: Add GPIO pin read example.

Browse Source 
Requires BUTTON defined in hwconfig, so far tested on DragonBoard 410c.
This commit is contained in:
Paul Sokolovsky 2016-11-12 00:09:20 +03:00
parent 1375c52772
commit 3c0da6a359
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
examples/hwapi/button_led.py Normal file
View File

@ -0,0 +1,9 @@
import utime
from hwconfig import LED, BUTTON
# Light LED when (and while) a BUTTON is pressed
while 1:
LED.value(BUTTON.value())
# Don't burn CPU
utime.sleep_ms(10)

7
examples/hwapi/hwconfig_dragonboard410c.py
View File

@ -1,12 +1,19 @@
from machine import Pin from machine import Pin
# 96Boards/Qualcomm DragonBoard 410c # 96Boards/Qualcomm DragonBoard 410c
#
# By default, on-board LEDs are controlled by kernel LED driver. # By default, on-board LEDs are controlled by kernel LED driver.
# To make corresponding pins be available as normal GPIO, # To make corresponding pins be available as normal GPIO,
# corresponding driver needs to be unbound first (as root): # corresponding driver needs to be unbound first (as root):
# echo -n "soc:leds" >/sys/class/leds/apq8016-sbc:green:user1/device/driver/unbind # echo -n "soc:leds" >/sys/class/leds/apq8016-sbc:green:user1/device/driver/unbind
# Note that application also either should be run as root, or # Note that application also either should be run as root, or
# /sys/class/gpio ownership needs to be changed. # /sys/class/gpio ownership needs to be changed.
# Likewise, onboard buttons are controlled by gpio_keys driver.
# To release corresponding GPIOs:
# echo -n "gpio_keys" >/sys/class/input/input1/device/driver/unbind
# User LED 1 on gpio21 # User LED 1 on gpio21
LED = Pin(21, Pin.OUT) LED = Pin(21, Pin.OUT)
# Button S3 on gpio107
BUTTON = Pin(107, Pin.IN)