Hold the phone...I got it working. I simply did an update *before *running dpkg-reconfigure (instead of after - as the instructions indicates).
sudo apt update && sudo apt upgrade librobotcontrol Thank you for the help! On Tuesday, March 26, 2019 at 9:14:41 PM UTC-4, Scott Harding wrote: > > > here's the output from sudo /opt/scripts/tools/version.sh > > git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7] > eeprom:[A335BNLTBLA21717EL001649] > model:[TI_AM335x_BeagleBone_Blue] > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2018.09-00002-g0b54a51eee]:[location: dd MBR] > kernel:[4.14.71-ti-r80] > nodejs:[v6.14.4] > uboot_overlay_options:[enable_uboot_overlays=1] > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg check: to individually upgrade run: [sudo apt install --only-upgrade > <pkg>] > pkg:[bb-cape-overlays]:[4.4.20180928.0-0rcnee0~stretch+20180928] > pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517] > pkg:[kmod]:[23-2rcnee1~stretch+20171005] > pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005] > pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328] > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video > plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep > admin spi tisdk weston-launch xenomai] > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 quiet] > dmesg | grep pinctrl-single > [ 1.070379] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 > size 568 > dmesg | grep gpio-of-helper > > Also here's systemct status: > systemctl status robotcontrol.service > ● robotcontrol.service - robotcontrol > Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; > vendor preset: enabled) > Active: failed (Result: exit-code) since Sun 2018-10-07 16:51:01 UTC; > 1min 14s ago > Process: 1533 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, > status=255) > > Oct 07 16:51:01 beaglebone systemd[1]: Starting robotcontrol... > Oct 07 16:51:01 beaglebone rc_startup_routine[1533]: timeout reached while > waiting for pwm drive > Oct 07 16:51:01 beaglebone rc_startup_routine[1533]: TIMEOUT REACHED > Oct 07 16:51:01 beaglebone systemd[1]: robotcontrol.service: Control > process exited, code=exited > Oct 07 16:51:01 beaglebone systemd[1]: Failed to start robotcontrol. > Oct 07 16:51:01 beaglebone systemd[1]: robotcontrol.service: Unit entered > failed state. > Oct 07 16:51:01 beaglebone systemd[1]: robotcontrol.service: Failed with > result 'exit-code'. > > thank you, > Scott > > > On Tuesday, March 26, 2019 at 8:26:51 PM UTC-4, RobertCNelson wrote: >> >> On Tue, Mar 26, 2019 at 7:15 PM <[email protected]> wrote: >> > >> > I guess I need to give more details. I’m using the eduMips platform. It >> looks like it’s failing to start the PWM module. I’ve seen some postings >> related to PWM but I can’t seem to find a solution. >> >> Let's see: >> >> sudo /opt/scripts/tools/version.sh >> >> Regards, >> >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3909cf75-f465-4408-89d1-4b263d3d9a96%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
