CHIP_IO icon indicating copy to clipboard operation
CHIP_IO copied to clipboard

No signs of life with Servo

Open fredkelly opened this issue 4 years ago • 0 comments

Hi there, I know the CHIP is now a long neglected device, but I'm hoping to get some use from mine to control a servo for a hobby project I'm working on.

I've updated my CHIP to Debian 10 and installed the library using the python-chip-io_0.7.1-1_armhf.deb file. I am running the test servo code with a servo wired up to the CHIP (5v, gnd & CSID4). I can't seem to stir any life from it and I am getting the below error running my test code:

chip@chip:~$ sudo python servo_test.py 
 ** debug enabled
 ** init_module: setup complete **
 ** gpio_allowed: found match
 ** is_this_chippro: total system ram: 491.0 mb
 ** is_this_chippro: we are a chip
 ** gpio_allowed: pin allowed for chip or both and we're a chip
 ** gpio_export **
gpio_export: something went wrong: Device or resource busy
servo_start failedTraceback (most recent call last):
  File "servo_test.py", line 13, in <module>
    SERVO.start("CSID4", 50)
RuntimeError: Error starting servo on pin U14_35 (gpio_export: could not write '136' to /sys/class/gpio/export (Device or resource busy)
Error setting up servo on pin 136, maybe already exported? (gpio_export: could not write '136' to /sys/class/gpio/export (Device or resource busy)))

I'm sure there's probably something obvious I'm doing wrong and wondered if anyone can help?

Many thanks.

fredkelly avatar Mar 06 '21 09:03 fredkelly