Re: [beagleboard] Re: PWM Pin Error on Boot

2016-03-30 Thread John Syne
One more thing, you may want to look at /driver/pinctrl/pinctrl-single.c as this is where the pinmux gets set.You could also use dynamic tracing to help find the responsible routine. Look in /Documentation/dynamic-debug-howto.txt. Probably a little bit of trial and error will be needed to

Re: [beagleboard] Re: PWM Pin Error on Boot

2016-03-30 Thread M House
Thanks for the reply John. I'm pretty new to modifying kernel modules and I haven't worked with u-boot at all. I'm not sure at the moment when the GPIO is modified but I think it happens whenever the system resets, most likely on startup. Should I try a kernel dump right after I boot?

Re: [beagleboard] Re: PWM Pin Error on Boot

2016-03-30 Thread John Syne
Well, that depends on how skilled you are at modifying u-boot and the linux kernel? In each case, modify the code that toggles the GPIO pin by printing text to the console when the GPIO you want is modified. You could always issue a kernel dump when that GPIO is modified, which will list the

[beagleboard] Re: PWM Pin Error on Boot

2016-03-30 Thread M House
Hey everyone I'm still stuck as to why my beaglebone keeps changing the polarity to 1 on boot. I can go in and manually change it but it always resets after reboot. Should I maybe write a start up script to force the polarity to 0? I'd rather find the root cause rather than a hack but at

[beagleboard] Re: PWM Pin Error on Boot

2016-03-20 Thread M House
I should clarify that it is every time I start my node.js server file that a has a required module that uses P9_14. I can manually change the polarity to 0 but it resets every time I reboot. On Saturday, March 19, 2016 at 11:30:58 PM UTC-7, M House wrote: > > I'm doing a project right now that