I remember the first time I loaded Linux. It was a Slackware 0.95 release. I must have loaded it a dozen times before I got the hang of it.
I find myself doing the same thing again, this time with various releases for the BBB and Machinekit. Bone-debian-9.9-machinekit-armhf-2019-08-25-4gb seems to be almost correct for my particular problem. Except ... Today I used config-pin and the results matched up with the CRAMPS.bbio file. I'm even able to yank on a few pins and see the effect. Slow progress. In earlier version from a few years ago I was able to use the led (P9_25) for signaling. No more. It's very clear that at some fairly recent time a decision was made to muck with P9_25. Why? Further, calling up other configurations will break because /sys/devices/platform/ocp/ocp:P9_25_pinmux no longer exists. That isn't very nice. For some reason, that for me at least is completely obscure, this pin was disabled. Will someone, anyone with a knowledge of the events around this pin please comment. I would really like to know when so I can load up the release just before that happened. cg -- 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/ac82e04c-4745-4940-a4c5-147e638efba8%40googlegroups.com.
