RTEMS on Beaglebone Black
Steve B
sbattazzo at gmail.com
Fri Feb 20 17:26:07 UTC 2015
I think Xenomai (alongside Linux) works quite well on Beaglebone Black in
my experience, so you might consider that. There's a pretty easy to follow
guide on getting that up and running, also.
I was considering RTEMS for a particular project but device drivers were
not available and I wasn't sure about developing those from the ground up.
I ended up having to port drivers for Xenomai eventually but I think the
actual work of driver porting took less time than it would have with RTEMS.
For an example of how to get an interrupt off of a GPIO, this white paper
may be useful, it looks like they did something close to what you want to
do: https://www.osadl.org/fileadmin/dam/rtlws/12/Brown.pdf
On Mon, Feb 16, 2015 at 12:59 PM, angelo fraietta <
newsgroups at smartcontroller.com.au> wrote:
>
> On 16/02/2015 5:34 PM, Mathew Benson wrote:
>
>> You're doing that in the CPU? If all your doing is toggling a GPIO at a
>> steady rate, why don't you just use the PRU and a PWM pin? Or do you have
>> RTEMS running in the PRU?
>>
>
> That is all I did in the test to see what sort of performance I could get
> just toggling a pin. What I actually need to do is interrupt every 640ns,
> and during that time, read 14 pins and store values in memory. Then, after
> 16 of these, toggle a pint. After 10ms of this, I need to raise an event
> to read the 10ms worth of data, encode it, and send it via UDP.
>
>
>
> Sent from my iPad
>>
>> On Feb 16, 2015, at 12:15 AM, angelo fraietta <
>>> newsgroups at smartcontroller.com.au> wrote:
>>>
>>> Greetings
>>>
>>> Have you got interrupts working on the GPIOs. Also, do you have any
>>> sample of reading and writing to GPIO. I need to see whether it is going to
>>> be fast enough,
>>>
>>> I ran a program (on linux) on beagle that used registers basically
>>> toggling an output. EG
>>> http://vabi-robotics.blogspot.com.au/2013/10/register-
>>> access-to-gpios-of-beaglebone.html
>>>
>>> It toggled at rate of just under 1Mhz, and what was just doing a while 1
>>> loop. I did not look even look at interrupts there and did nothing else - I
>>> didn't even do any reads of GPIO.
>>>
>>> I want to get interrupts happening at 1.56Mhz (preferable) and read 14
>>> GPOI, sbut I could go to half the rate by reducing my sample rate. The
>>> beagle runs at 1Ghz, so I think it should be able to handle it.
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> On 23/01/2015 4:19 PM, Ben Gras wrote:
>>>> All,
>>>>
>>>> A while ago I finished the basics needed to use the beaglebones and
>>>> beagleboards with RTEMS. The hardware support isn't very complete yet.
>>>> The code is merged with RTEMS mainline though. My fork of rtems-tools
>>>> and RSB is needed for help with building.
>>>>
>>>> Full details on how to build it are here:
>>>> http://www.shrike-systems.com/beagleboard-xm-beaglebone-
>>>> black-and-everything-else-rtems-on-the-beagles.html
>>>>
>>>> I hope you like it :-). Let me know if you'd like any followup.
>>>>
>>>> Cheers,
>>>> Ben
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jan 22, 2015 at 4:46 AM, angelo fraietta
>>>> <newsgroups at smartcontroller.com.au> wrote:
>>>>
>>>>> Greetings
>>>>> Does anyone know the status of the beaglebone port?
>>>>>
>>>>> Thanks
>>>>>
>>>>> ---
>>>>> This email has been checked for viruses by Avast antivirus software.
>>>>> http://www.avast.com
>>>>>
>>>>> _______________________________________________
>>>>> users mailing list
>>>>> users at rtems.org
>>>>> http://lists.rtems.org/mailman/listinfo/users
>>>>>
>>>> --
>>> Dr Angelo Fraietta
>>> A.Eng, A.Mus.A, BA(Hons), Ph.D.
>>>
>>> PO Box 859
>>> Hamilton NSW 2303
>>>
>>> Home Page
>>>
>>>
>>> http://www.smartcontroller.com.au/
>>>
>>> There are those who seek knowledge for the sake of knowledge - that is
>>> CURIOSITY
>>> There are those who seek knowledge to be known by others - that is VANITY
>>> There are those who seek knowledge in order to serve - that is LOVE
>>> Bernard of Clairvaux (1090 - 1153)
>>>
>>>
>>> ---
>>> This email has been checked for viruses by Avast antivirus software.
>>> http://www.avast.com
>>>
>>> _______________________________________________
>>> users mailing list
>>> users at rtems.org
>>> http://lists.rtems.org/mailman/listinfo/users
>>>
>>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20150220/f9394fa2/attachment-0002.html>
More information about the users
mailing list