[okl4-developer] porting OKL4 to a different architecture

[Gary Gibson]

As I recall, not all of Atmel's AVR microcontrollers support Virtual Memory
(that is, they do not MMUs). OKL4 3.0 (both the full feature set and feature
reduced nano option) does not support machines without MMUs.  I would double
check that you are using one of the newer AVR32s with MMU support as there
would be a fair amount of code and build system/tools to comprehend and
rewrite to make use of a machine w/o an MMU.

 

Building AVR32 cross GNU bin tools will be a project in of itself.  The OKL4
Microkernel code (and build system) has non-trivial tool version
dependencies that you will need to work out in your cross tool chain.

 

The license terms are in the copyright notices within the headers of the
source files - you need to review the language there.


Gary

  _____  

From: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org] On
Behalf Of Gabi Voiculescu
Sent: Tuesday, November 03, 2009 6:02 AM
To: Andrei Voinescu
Cc: developer at okl4.org
Subject: Re: [okl4-developer] porting OKL4 to a different architecture

 


Hi.


--- On Tue, 11/3/09, Andrei Voinescu <voinescu.andrei at gmail.com> wrote:


From: Andrei Voinescu <voinescu.andrei at gmail.com>
Subject: [okl4-developer] porting OKL4 to a different architecture
To: developer at okl4.org
Date: Tuesday, November 3, 2009, 2:10 PM

Hi,

We (two colleagues and myself) would be interested in porting okl4 to the
avr32 architecture. I would like to ask you a couple of questions:


1) Is there any license difference between okl4-3.0 and 2.1?
2) What steps should we take to port? First the arch/avr32 then go through
the SoC porting process?

Yes.

 

3) What would be the minimal subset of features needed to test the build for
a different architecture?

arch/avr32

platform/platformavr32
drivers/v2serial_on_platformavr32
drivers/v2timer_on_platformavr32

You need the first three functional for ktest unit test suite.
You need the first four functional for ctest.

So hardware requirements are: 2 separate timers, at least one serial port.

Thanks,


Andrei




-----Inline Attachment Follows-----

_______________________________________________
Developer mailing list
Developer at okl4.org
https://lists.okl4.org/mailman/listinfo/developer

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20091103/b7b7a0d2/attachment.htm