Porting to a NXP K6x series chip

[Alan Cudmore]

For the RAM, maybe 128k can be used for the workspace,heap, and initial
stack, and the other 128k bank can be used for data.
If you get this working, I would not mind trying to port it to the Teensy
3.6 board, which has a similar CPU:
https://www.pjrc.com/store/teensy36.html
Alan



On Fri, Feb 24, 2017 at 9:35 AM, Gedare Bloom <gedare at rtems.org> wrote:

> You have the gist of it. Read through the
> https://docs.rtems.org/branches/master/cpu-supplement/index.html and
> https://docs.rtems.org/branches/master/bsp-howto/index.html for a bit
> more guidance. There is currently no official "porting guide" beyond
> that, so keep asking questions.
>
> On Thu, Feb 23, 2017 at 1:19 PM,  <george at n3ysa.org> wrote:
> > I've got a FRDM-K64F and would like to get RTEMS running on it for a
> personal project. It has the standard ARM interrupt controller. One
> complication is that the SRAM is divided into two banks of 128K as the
> banks are connected to different buses in the MCU, and causes hard faults
> if an unaligned access crosses the boundary.
> >
> > Looking at the existing code, anything specific too the K6x would go in
> libcpu, and anything specific to board (such as clock setup/debug uart)
> would appear to go in libsp?
> >
> > Thanks,
> > George
> >
> > _______________________________________________
> > devel mailing list
> > devel at rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170224/ebb3338c/attachment.html>