0

I'm new to RPI and to Python 3 and I have a problem running this code on a RPI 2.

import RPi.GPIO as GPIO
import time
GPIO.setmode(GPIO.BCM)
GPIO.setwarnings(False)
redled = 4
greenled = 26
GPIO.setup(redled, GPIO.OUT)
GPIO.setup(greenled, GPIO.OUT)
count = 1
while count < 100000:
    GPIO.output(redled, 1)
    GPIO.output(greenled, 1)
    time.sleep(.1)
    GPIO.output(redled, 0)
    GPIO.output(greenled, 0)
    time.sleep(.1)
    count = count + 1

GPIO.cleanup()

I get this error.

Traceback (most recent call last): File "/home/pi/testreactionrepeat.py", line 7, in GPIO.setup(redled, GPIO.OUT) RuntimeError: No access to /dev/mem. Try running as root!

I was using this code with no problems a couple of days ago and can't figure out what I'm doing wrong now. I found a similar problem and the answer was to run "sudo su" but I get a syntax error when I try that.

Milliways
  • 59,890
  • 31
  • 101
  • 209
nashville_bill
  • 1
  • 1
  • 2

1 Answers1

2

Let's assume that your program is called

program.py

Open terminal and type 

sudo python program.py

This will run your python program as root giving it the necessary permissions to access/modify the GPIO pins.

evolutionizer
  • 296
  • 2
  • 6
  • I get this when I type sudo python reactionrepeat.py into terminal. Traceback (most recent call last): File "reactionrepeat.py", line 3, in GPIO.setmode(GPIO.BCM) AttributeError: 'module' object has no attribute 'setmode' – nashville_bill Aug 21 '15 at 11:07
  • can you run "sudo apt-get update && sudo apt-get upgrade" in terminal, this will update your system with the latest software and hopefully with the latest RPi.GPIO modules and thuis fix this issue. – evolutionizer Aug 21 '15 at 11:33
  • I did the update/upgrade, and it appeared to go well. However, my code still won't run, even though it ran just fine a couple of days before I had the problem. I still get the same messages as before when I run the program and when I type in sudo python reactionrepeat.py. Could this be a hardware problem? – nashville_bill Aug 21 '15 at 21:53
  • @nashville_bill no this is definitely a software problem. Are you on the latest raspbian OS? – evolutionizer Aug 22 '15 at 03:22
  • I'm getting this experience with Ubuntu Mate 15.10 when trying to use dot3k. –  Mar 20 '16 at 17:10
  • @mjwittering can you please post the exact error that you are facing – evolutionizer Mar 21 '16 at 18:12
  • @evolutionizer the error I had was: "No access to /dev/mem. Try running as root!"

    The answer regarding permissions by Joan on this page resolved my issues: http://raspberrypi.stackexchange.com/questions/40105/access-gpio-pins-without-root-no-access-to-dev-mem-try-running-as-root.

     –  Mar 22 '16 at 12:19