Integrating RTEMS with ARM Cortex R4
sebastian.huber at embedded-brains.de
Wed Jun 5 15:29:26 UTC 2013
On 06/05/2013 05:17 PM, Pritesh Gudge wrote:
> Sebastian Huber <sebastian.huber at ...> writes:
>> On 26/01/13 15:07, Jiri Freyvald wrote:
>>> -------- Original Message --------
>>> Subject: Re: Integrating RTEMS with ARM Cortex R4
>>> Date: Sat, 26 Jan 2013 14:01:55 +0000
>>> From: Jiri Freyvald <jiri.freyvald at ...>
>>> To: priteshgudge at ...
>>> I have been using RTEMS port for Cortex-M4 and so far it works
>>> perfectly for me
>>> (namely STM32F4DISCOVERY board, STM32F407 processor)
>>> I don't know how close M4 and R4 cores are, but I guess porting BSP
>>> from R4 to M4 shouldn't be too difficult.
>> The ARMv7-M and ARMv7-R are quite different (e.g. in the ARMv7-M we have
>> the mandatory NVIC).
> So, as far as I have understood, here are the following points which need to
> be considered for RTEMS-based development:
> 1. Check if the CPU is supported: Cortex-R CPUs are supported as per the
> wiki page http://www.rtems.org/wiki/index.php/ARM-EABI
Yes, the Cortex-R is supported. You should use the Thumb-2 instruction set.
> 2. Write a BSP for the requisite Board as it is not available for mine -
> This part I will figure out in due time.
> But kindly confirm statement 1.
> I have read your previous comment about the template LPC32XX BSP.
> I will be using the Texas Instrument Microcontroller TMS570LS3137 for the
> development. http://www.ti.com/product/tms570ls3137
> I just need a confirmation whether my understanding to this stage is
> correct. Only then will it make sense to commit to developing the requisite
I added a Cortex-A9 BSP recently. If your chip uses the GIC interrupt
controller, then please use the code in
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users