On 7/29/2016 7:06 AM, [email protected] wrote: > > fragment@1 { > target = <&ocp>; > __overlay__ { > ecap_helper { > compatible = "ecap-helper"; > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&ecap_example>;
What is ecap-helper? The ecap target is usually something like ecap0: https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/cape-universaln-00A0.dts#L1432 I suspect your overlay fragment 1 isn't matching any kernel driver, so the ecap_example pinmux isn't getting loaded. When the cape manager is finished, you should see something like the following in dmesg: > [1206258.362090] bone-capemgr bone_capemgr.9: slot #7: Applied #23 overlays. > ... > [1206259.733221] bone-capemgr bone_capemgr.9: slot #8: Applied #1 overlays. ...this is from loading my 'universal' overlay (slot 7) and the iio overlay (slot 8). I didn't see anything like this in your dmesg output, which leads me to think your overlay target isn't matching anything. -- Charles Steinkuehler [email protected] -- 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/939cf9ec-9a15-93aa-af0d-7ee9526866ee%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
