Over the years I've learned that when someone is enthusiastic regarding their suggestions it's a very good indicator that "It's working for them" and that the problem is between my ears. OK I'll keep trying to sort it out. However, I have observed one thing that requires some comment.
The code than is within Machinekit and especially as it applies to the CRAMPS board, depends upon files that are not to be found in the Machinekit code base. /boot/uEnv.txt and all the dtbs that are to be found in /lib/firmware for instance. So, if I someone were to come up with some code tweek, that applied directly to a file that normally resides outside the code base of Machinekit. Where would you put it? The first few lines of CRAMPS.bbio for instance. Specifically, > overlay cape-universal > overlay cape-bone-iio Other than a small handful of guys, who would know? And if the code isn't needed, why is it still there? Those few lines of code might as well be land mines buried along my path, primed and ready to blow my time and life away. Even more frustrating is that two years ago my cramps board was working just fine. Loaded it up and shabam. Worked right out of the box. Actually, that's not completely true as as recall, it was fundamentally a LinuxCNC project and not Machinekit. And then I thought to upgrade my system. If I had only known.... dammit. running sudo /opt/scripts/tools/version.sh produced git:/opt/scripts/:[5b2e16aa1e5c0f627f1d48a6dd1c13b446b9f53b] eeprom:[A335BNLT00A54079BBBK2600] model:[TI_AM335x_BeagleBone_Black] dogtag:[Machinekit Debian Image 2019-08-25] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gbb4af0f50f]:[location: dd MBR] kernel:[4.19.59-bone-rt-r36] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/cape-universal-00A0.dtbo] uboot_overlay_options:[disable_uboot_overlay_audio=1] uboot_overlay_options:[disable_uboot_overlay_wireless=1] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-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.20190812.0-0rcnee0~stretch+20190812] pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227] pkg:[kmod]:[23-2rcnee1~stretch+20171005] WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED] pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217] groups:[machinekit : machinekit adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide] cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] dmesg | grep remote [ 1.180967] remoteproc remoteproc0: wkup_m3 is available [ 1.518683] remoteproc remoteproc0: powering up wkup_m3 [ 1.518702] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168 [ 1.520798] remoteproc remoteproc0: remote processor wkup_m3 is now up dmesg | grep pru dmesg | grep pinctrl-single [ 0.746436] pinctrl-single 44e10800.pinmux: 142 pins, size 568 dmesg | grep gpio-of-helper [ 0.757592] gpio-of-helper ocp:cape-universal: ready lsusb Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 045e:009d Microsoft Corp. Wireless Optical Desktop 3.0 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub END Looks like I've got a little work to do. On Sunday, August 25, 2019 at 4:01:29 PM UTC-7, [email protected] wrote: > > The CRAMPS.bbio file has a line commented out that drives a test led on > the CRAMPS board. > When this line is enabled by removing the # and run it provokes a series > of error messages starting with P9_25 pinmux file not found! > NOT GOOD!! > > I'm presently running the latest RCN release -- > bone-debian-9.9-machinekit-ARMhf-2019-06-30-4gb > > There is no doubt that all my troubles as noted in my post yesterday are > related to a broken pinmux definition. > > Would anyone care to point to a known good release? > > Thanks, > > Chuck > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" 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/machinekit/5acbc26b-14b1-4e5d-951f-9f71d258e46e%40googlegroups.com.
