From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: sagar.behere@gmail.com
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Using hardware PWM generators with Xenomai
Date: Sat, 10 Aug 2013 17:23:33 +0200 [thread overview]
Message-ID: <52065AF5.5020106@xenomai.org> (raw)
In-Reply-To: <52039EC3.4050908@gmail.com>
On 08/08/2013 03:36 PM, Sagar Behere wrote:
> Hello,
>
> I wish to generate PWM signals from Xenomai, using the beaglebone black,
> kernel 3.8.13 patched with xenomai.
>
> There already exist linux kernel modules for the hardware PWM generator
> (eHRPWM) on the am335x chip in the beaglebone. The PWM generator can be
> configured and controlled via the /sysfs interface and the whole thing
> works very well.
>
> I understand that the /sysfs interface cannot be used by xenomai tasks
> without triggering a transition away from the primary xenomai (hard
> realtime) domain. So my question is: What is the least effort way to
> change the duty cycle of the hardware PWM generator, from a xenomai task?
>
> Does the following approach sound feasible?
>
> 1. Configure the PWM generator (freq, polarity etc.) from the /sysfs
> interface at application startup. This need not be realtime
> 2. Assuming that the duty-cycle is controlled by the value of some
> memory-mapped register, use mmap()/ioremap() to map that register's
> address into the xenomai task's address space.
> 3. Write the duty-cycle values to the mapped memory, from within the
> xenomai task
>
> So this is like a hybrid approach that uses the existing linux kernel
> module for initializing/configuring the hardware PWM and the xenomai
> task only changes the value of one register that affects the duty cycle
> of the output waveform.
>
> Thanks in advance,
It could probably work, but does not seem like a good idea:
- it is not future proof, as you will need to change the application
code if one day you want to run the application with different hardware,
an RTDM driver with a well defined interface would avoid that;
- it is not really safe as it does not prevent several applications to
access the same hardware at the same time.
Regards.
--
Gilles.
prev parent reply other threads:[~2013-08-10 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:36 [Xenomai] Using hardware PWM generators with Xenomai Sagar Behere
2013-08-08 13:58 ` Lennart Sorensen
2013-08-08 14:26 ` Michael Haberler
2013-08-09 17:28 ` Robert
2013-08-10 9:15 ` Sagar Behere
2013-08-10 9:36 ` Andrey Nechypurenko
[not found] ` <52060B80.1080601@gmail.com>
2013-08-10 12:29 ` Robert
2013-08-10 12:42 ` Gilles Chanteperdrix
2013-08-10 12:55 ` Gilles Chanteperdrix
2013-08-10 15:14 ` Andrey Nechypurenko
2013-08-10 15:19 ` Andrey Nechypurenko
2013-08-10 15:23 ` Gilles Chanteperdrix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52065AF5.5020106@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=sagar.behere@gmail.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.