FYI, the problem got resolved by adding delays between the individual PWM
cape activation and the first access to their directories. Had to be around
500ms.
Thanks.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
:
On 07/28/2014 01:06 PM, BubbleBone wrote:
Actually all the details were given in the first message.
I even had the impression that I put too much of details and made it
unreadable ... which may explain why I didn't get any answer :-)
Let me know if you need any detail which
/period,
/sys/devices/ocp.3/pwm_test_P9_14.16);
fd = open(buf, O_WRONLY);
if (fd 0) {
perror(pwm/period);
printf(pwm/period, %s, buf);
return fd;
}
Le lundi 28 juillet 2014 22:45:31 UTC+2, don a écrit :
On 07/28/2014 01:06 PM, BubbleBone wrote:
Actually
Anybody has a clue ?
The cape manager is well installed but a C program run by the system
service at bootup will not access the PWM device tree correctly.
How are you guys doing ? I would believe I am not the first person starting
some PWM at boot up.
Have a good day
--
For more options,
Actually all the details were given in the first message.
I even had the impression that I put too much of details and made it
unreadable ... which may explain why I didn't get any answer :-)
Let me know if you need any detail which is not in the initial message.
--
For more options, visit
Hi,
I am having trouble with configuring my PWM at start-up.
A C progam b1, which include the setup of the PWMs, is called at start-up
by a System Service.
The cape get well installed. But the periods, duty cycles and polarity
won't be set correctly.
- If I restart the service afterwards, it
