Khanh,

Have you got the PWMs working yet?  This documentation 
(http://processors.wiki.ti.com/index.php/Linux_Core_PWM_User's_Guide) most 
closely matches what I am seeing under the 4.1 kernel, but I had to fall 
back on these same old overlays to even see the PWMs.  Seem to able to 
export, configure, and enable the PWM, but I'm just not seeing anything on 
the output pin.

-Kevin


On Wednesday, September 9, 2015 at 3:20:19 AM UTC-5, Khanh Nguyen wrote:
>
> Hey guys, I'm working on a project where as I was using the 
> ocp.X/bone_pwm_P9_11 and such in kernel 3.8. I just recently updated my 
> Beaglebone black to kernel 4.1 and couldn't get PWM to work...
>
> I was trying to use dtc, rebuild the device tree overlay. I pulled the old 
> am33xx_pwm from 
> https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/am33xx_pwm-00A0.dts
>  
> and some of these bad boys bone_pwm_PX_YZ from 
> https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/bone_pwm_P8_13-00A0.dts.
>  
> I know that these are pretty old, but was just thinking maybe it would work 
> with the new kernel?
>
> Then I was able to build these device tree overlays and load them into the 
> /boot/uEnv.txt. However, when I went to /sys/devices/platform, I only saw 
> ocp:pwm and it's nothing like the old kernel 3.8 where you'd have duty, 
> period, and all that good stuff. Is this the right way to access PWM or I 
> had to use the example in the Bacon device tree overlay? If so, is there a 
> document on how to know which PWM pin to export?
>
> I've been playing with this new kernel for quite a while now and still 
> haven't got any luck. Any advice or pointers will be greatly appreciated.
>
> Thanks
>
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to