attaching an interrupt in beaglebone bsp

[Ben Gras]

That is a feature, not a bug :-). RSB is telling you it is missing some
parts on your system that it needs to run. Specifically:

error: exe: not found: (__bison) /usr/bin/bison
error: exe: not found: (__cvs) /usr/bin/cvs
error: exe: not found: (__flex) /usr/bin/flex

So you have to install cvs, flex and bison, then re-run sb-check, and
assuming it says the environment is then OK, continue.

Good luck!





On Mon, Jun 15, 2015 at 2:17 AM, Angelo Fraietta <
newsgroups at smartcontroller.com.au> wrote:

> I got an error on first part of tutorial
>
> angelo at debian:~/development/rtems/sources$ git clone -b beagle
> https://github.com/bengras/rtems-source-builder.git
> Cloning into rtems-source-builder...
> remote: Counting objects: 5104, done.
> remote: Total 5104 (delta 0), reused 0 (delta 0), pack-reused 5104
> Receiving objects: 100% (5104/5104), 3.22 MiB | 694 KiB/s, done.
> Resolving deltas: 100% (3163/3163), done.
> angelo at debian:~/development/rtems/sources$
> ./rtems-source-builder/source-builder/sb-
> sb-bootstrap     sb-check         sb-reports       sb-set-builder
> sb-builder       sb-defaults      sb-rtems-config
> angelo at debian:~/development/rtems/sources$
> ./rtems-source-builder/source-builder/sb-
> sb-bootstrap     sb-check         sb-reports       sb-set-builder
> sb-builder       sb-defaults      sb-rtems-config
> angelo at debian:~/development/rtems/sources$
> ./rtems-source-builder/source-builder/sb-check
> RTEMS Source Builder - Check, v0.5.0
> error: exe: not found: (__bison) /usr/bin/bison
> error: exe: not found: (__cvs) /usr/bin/cvs
> error: exe: not found: (__flex) /usr/bin/flex
>
>
> On Mon, Apr 13, 2015 at 10:14 PM, Andrew Harris <andrew.unit at gmail.com>
>  wrote:
>
>> Hello,
>>
>>    I'm not sure how to attach an interrupt in the beaglebone ARM bsp.  I
>> learned that the "rtems_interrupt_catch" method of binding an interrupt to
>> an ISR won't work by noticing that the CPU_SIMPLE_VECTORED_INTERRUPTS is
>> set to FALSE in cpu.h for the beaglebone BSP.  I want to try binding an
>> interrupt from the I2C Bus 1 into RTEMS, but I'm not sure where to go next
>> in terms of how to attach the interrupt.  Any help would be appreciated.
>>
>> -andrew
>>
>> _______________________________________________
>> users mailing list
>> users at rtems.org
>> http://lists.rtems.org/mailman/listinfo/users
>>
>
>
> On Mon, Jun 1, 2015 at 6:06 PM, Ben Gras <beng at shrike-systems.com> wrote:
>
>> Hi Angelo,
>>
>> Nice to hear of your interest!
>>
>> This tutorial covers everything from scratch and I recently verified the
>> instructions work & the built result works :).
>>
>>
>> http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html
>>
>> Personally I've been using Ubuntu 14.04 to build lately. Not my first
>> choice in working environment but it's what I have at the moment.
>>
>>
>>
>> On Mon, Jun 1, 2015 at 7:27 AM, angelo fraietta <
>> newsgroups at smartcontroller.com.au> wrote:
>>
>>>  I have been given go-ahead to actually start looking at testing
>>> beaglebone with RTEMS.
>>>
>>> Does anyone have the most current instructions for building and running
>>> on BB.
>>>
>>> Also, what platforms are people using for development?
>>>
>>> Thanks
>>>
>>>
>>> On 13/04/2015 10:14 PM, Andrew Harris wrote:
>>>
>>>  Hello,
>>>
>>>     I'm not sure how to attach an interrupt in the beaglebone ARM bsp.
>>> I learned that the "rtems_interrupt_catch" method of binding an interrupt
>>> to an ISR won't work by noticing that the CPU_SIMPLE_VECTORED_INTERRUPTS is
>>> set to FALSE in cpu.h for the beaglebone BSP.  I want to try binding an
>>> interrupt from the I2C Bus 1 into RTEMS, but I'm not sure where to go next
>>> in terms of how to attach the interrupt.  Any help would be appreciated.
>>>
>>>  -andrew
>>>
>>>
>>> _______________________________________________
>>> users mailing listusers at rtems.orghttp://lists.rtems.org/mailman/listinfo/users
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>   [image: Avast logo] <http://www.avast.com/>
>>>
>>> This email has been checked for viruses by Avast antivirus software.
>>> 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/20150615/49e84e77/attachment-0002.html>