adafruit / adafruit/adafruit-beaglebone-io-python
BeagleBone Black Wireless PWM: RuntimeError: Problem with the cape manager
- Dominant language
- C
- Stars
- 479
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Hello, first time here. I got an issue.
I was trying to use PWM but an error showed.
```
Traceback (most recent call last):
File "dc_motor.py", line 14, in
p = PWM.start(P_W_M, 50)
RuntimeError: Problem with the cape manager
```
This is the python file:
```
import Adafruit_BBIO.GPIO as GPIO
import Adafruit_BBIO.PWM as PWM
P_W_M = 'P9_42'
IN4 = 'P9_25'
IN3 = 'P9_27'
GPIO.setup(IN4, GPIO.OUT)
GPIO.setup(IN3, GPIO.OUT)
GPIO.output(IN4, GPIO.LOW)
GPIO.output(IN3, GPIO.LOW)
GPIO.setup(P_W_M, GPIO.OUT)
p = PWM.start(P_W_M, 50)
```
I did run:
```
sudo /opt/scripts/tools/version.sh
```
**output:**
git:/opt/scripts/:[721f317b40aabe880c34e8e16311812eeb464ce4]
eeprom:[A335BNLTBWA51646BBWG1556]
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-00002-g07d5700e21 (Mar 06 2020 - 11:24:55 -0600)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-BBBW-WL1835-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0.bb.org-overlays]
kernel:[4.9.147-ti-r121]
nodejs:[v10.24.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20210821.0-0~buster+20210821]
pkg:[bb-customizations]:[1.20210810.1-0~buster+20210810]
pkg:[bb-usb-gadgets]:[1.20210816.0-0~buster+20210816]
pkg:[bb-wl18xx-firmware]:[1.20210520.0-0~buster+20210520]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[ 1.641203] remoteproc remoteproc0: wkup_m3 is available
[ 1.947766] remoteproc remoteproc0: powering up wkup_m3
[ 1.947788] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[ 1.948041] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
[ 39.460533] pruss-soc-bus 4a326004.pruss-soc-bus: platform data (reset configuration information) missing
dmesg | grep pinctrl-single
[ 1.342737] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 1.595620] pinctrl-single 44e10800.pinmux: pin PIN74 already requested by 481a6000.serial; cannot claim for leds
[ 1.606156] pinctrl-single 44e10800.pinmux: pin-74 (leds) status -22
[ 1.612664] pinctrl-single 44e10800.pinmux: could not request pin 74 (PIN74) from group pinmux_bt_pins on device pinctrl-single
dmesg | grep gpio-of-helper
[ 1.344088] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
I hope you can help me to fix this 🙏.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the dc_motor.py example and the Adafruit_BBIO.PWM.start call for P9_42, then reproduce the reported cape-manager error on the BeagleBone Black Wireless setup described. Read the supplied version.sh output and dmesg pinctrl/cape-universal messages to identify the cause; done means the failure has a documented, reproducible resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100