On 19/07/2014 8:39 am, emanuel stiebler wrote:
On 2014-07-18 09:39, Giovanni Macciocu wrote:
Hi Emanuel,
RTEMS has a BSP which is named xilinx_zynq_zedboard, I use the
following configuration to build RTEMS for this BSP.
$ ../configure --target=arm-rtems4.11
--enable-rtemsbsp=xilinx_zynq_zed
On 2014-07-18 09:39, Giovanni Macciocu wrote:
Hi Emanuel,
RTEMS has a BSP which is named xilinx_zynq_zedboard, I use the following
configuration to build RTEMS for this BSP.
$ ../configure --target=arm-rtems4.11 --enable-rtemsbsp=xilinx_zynq_zedboard
--prefix=/opt/rtems-4.11 --enable-posix
The ASM macro needs to be properly used in rtems/score/cpu.h.
I sent a patch to devel@ but it is really a hack. Things compile but
I wouldn't trust it.
+ ASM should protect C only code from being used in .S code.
And vice-versa.
When I started, there was C code exposed to .S. When I blocked
off
---
cpukit/score/cpu/or1k/cpu.c| 4 ++-
cpukit/score/cpu/or1k/or1k-exception-handler-low.S | 1 -
cpukit/score/cpu/or1k/rtems/score/cpu.h| 33 +-
3 files changed, 22 insertions(+), 16 deletions(-)
diff --git a/cpukit/score/cpu/or1k/cpu.c b
On Fri, Jul 18, 2014 at 10:35 PM, Gedare Bloom wrote:
>
>
>
> On Fri, Jul 18, 2014 at 4:15 PM, Hesham Moustafa
> wrote:
>>
>> On Fri, Jul 18, 2014 at 4:17 PM, Gedare Bloom wrote:
>> > On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
>> > wrote:
>> >>
>> >> On Thu, Jul 17, 2014 at 3:10 PM, Joel
On Fri, Jul 18, 2014 at 4:15 PM, Hesham Moustafa
wrote:
> On Fri, Jul 18, 2014 at 4:17 PM, Gedare Bloom wrote:
> > On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
> > wrote:
> >>
> >> On Thu, Jul 17, 2014 at 3:10 PM, Joel Sherrill
> >> wrote:
> >> > This definitely sounds like not handling th
On Fri, Jul 18, 2014 at 4:19 PM, Gedare Bloom wrote:
> I see you are kind of copying the file structure of ARM. I'm not sure
> this is a good example for a simple port. m68k is more
> straightforward.
>
Which file?
> -Gedare
>
> On Fri, Jul 18, 2014 at 10:17 AM, Gedare Bloom wrote:
>> On Fri, Jul
On Fri, Jul 18, 2014 at 4:17 PM, Gedare Bloom wrote:
> On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
> wrote:
>>
>> On Thu, Jul 17, 2014 at 3:10 PM, Joel Sherrill
>> wrote:
>> > This definitely sounds like not handling the context switch necessary
>> > part of the
>> > IRQ processing properly
---
This is an updated version of an earlier unmerged patch, which extends the
cpukit/score/cpu/i386/ model with guards to distinguish between
paravirtualized (--enable-paravirt) and native environments.
cpukit/score/cpu/i386/Makefile.am | 1 +
cpukit/score/cpu/i386/cpu.c
On 07/18/2014 05:57 PM, Gedare Bloom wrote:
> On Fri, Jul 18, 2014 at 11:37 AM, Philipp Eppelt
> wrote:
>> ---
>> This is an updated version of an earlier unmerged patch, which extends the
>> cpukit/score/cpu/i386/ model with guards to distinguish between
>> paravirtualized (--enable-paravirt) and
On Fri, Jul 18, 2014 at 11:37 AM, Philipp Eppelt
wrote:
> ---
> This is an updated version of an earlier unmerged patch, which extends the
> cpukit/score/cpu/i386/ model with guards to distinguish between
> paravirtualized (--enable-paravirt) and native environments.
>
> cpukit/score/cpu/i386/Mak
Hi Emanuel,
RTEMS has a BSP which is named xilinx_zynq_zedboard, I use the following
configuration to build RTEMS for this BSP.
$ ../configure --target=arm-rtems4.11 --enable-rtemsbsp=xilinx_zynq_zedboard
--prefix=/opt/rtems-4.11 --enable-posix --enable-networking
Regards,
Giovanni
>>> ema
---
This is an updated version of an earlier unmerged patch, which extends the
cpukit/score/cpu/i386/ model with guards to distinguish between
paravirtualized (--enable-paravirt) and native environments.
cpukit/score/cpu/i386/Makefile.am | 1 +
cpukit/score/cpu/i386/cpu.c
Hello Alan
On 07/18/14 14:06, Alan Cudmore wrote:
Hi André,
I have a couple of SPI devices to try now. I have the SPI FRAM chip:
https://www.adafruit.com/product/1897
I have here a similar device
http://www.microchip.com/wwwproducts/Devices.aspx?product=23K256
Will try to test it with the PI
I see you are kind of copying the file structure of ARM. I'm not sure
this is a good example for a simple port. m68k is more
straightforward.
-Gedare
On Fri, Jul 18, 2014 at 10:17 AM, Gedare Bloom wrote:
> On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
> wrote:
>>
>> On Thu, Jul 17, 2014 at 3
On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
wrote:
>
> On Thu, Jul 17, 2014 at 3:10 PM, Joel Sherrill
> wrote:
> > This definitely sounds like not handling the context switch necessary
> > part of the
> > IRQ processing properly so always returning to IDLE. I call this a
> > simple return.
>
Hi all,
is there any description how to get RTEMS on the Zynq?
I know how to use RTEMS on ARM, but I'm asking the Zynq specific
parts. On the Wiki, the Zynq BSP is not even mentioned, but I see a lot
of Git commits.
I have a ZedBoard for starters ...
Thanks a lot in advance
Hi André,
I have a couple of SPI devices to try now. I have the SPI FRAM chip:
https://www.adafruit.com/product/1897
and something that could be interesting, an SPI based LCD/touchscreen:
https://www.adafruit.com/products/1601
I can also verify that the RTEMS BSP works fine on the new Raspberry Pi
Make RSB download newlib-cvs for or1k targets as OpenRISC
support has been added to newlib recently; thus, newlib-2.1 release
and its or1k support patch is not used anymore.
---
rtems/config/4.11/rtems-or1k.bset | 5 +
rtems/config/tools/rtems-gcc-4.8.2-newlib-cvs-1.cfg | 2
19 matches
Mail list logo
