public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions
Date: Thu, 14 Apr 2011 11:11:00 -0000	[thread overview]
Message-ID: <BANLkTin0A=nTiMSa7fdzkT7E3e8RgUMoRw@mail.gmail.com> (raw)
In-Reply-To: <4DA6D20B.7080908@siva.com.mk>

Hi Ilija,
for my curiosity, what is the footprint of this port ?

If I am not mistaken,  K60 have only 128KB of on-chip SRAM. Can it fit ?

BR,
Drasko

On Thu, Apr 14, 2011 at 12:52 PM, Ilija Kocho <ilijak@siva.com.mk> wrote:
> On 14.04.2011 09:28, jjp jjp wrote:
>> Hi,
>> I have a TWR-K60N512 too!
>> Is it possible to apply patchs to Mercurial version?
>
> Actually, our Kinetis port is not yet committed to CVS. It is in
> Bugzilla, in a queue for review by maintainers.
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001187
> You can download the Kinetis Port diff files from there and patch your
> eCos repository. Please observe the note (Comment 3) regarding patching.
>
> I recommend to checkout a fresh eCos repository from CVS/Mercurial
> unless you have revision later than 2011-04-06 17:59:20 BST, since it
> has resolved bugs 1001184, 1001186 which are needed for this port.
>
> I also recommend for first run to use official eCos gnutools. Later you
> can try gcc-4.6.0
>
> Tell me if you need additional info.
>
> Regards
> Ilija
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-04-14 11:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 17:24 jjp jjp
2011-01-28 16:05 ` Ilija Kocho
     [not found]   ` <SNT129-W29DA08015F0442D154694DADA70@phx.gbl>
2011-04-08 20:16     ` Ilija Kocho
     [not found]     ` <4D9F6B61.705@siva.com.mk>
2011-04-11  7:42       ` jjp jjp
2011-04-12 18:09         ` Ilija Kocho
2011-04-13  8:01           ` jjp jjp
2011-04-13 15:55             ` Ilija Kocho
2011-04-14  7:29               ` jjp jjp
2011-04-14 10:53                 ` Ilija Kocho
2011-04-14 11:11                   ` Drasko DRASKOVIC [this message]
2011-04-14 13:09                     ` Ilija Kocho
2011-04-14 15:05                       ` Drasko DRASKOVIC
2011-04-15  9:56                         ` Ilija Kocho
2011-04-15 10:21                           ` Ross Younger
2011-04-14 12:14                   ` jjp jjp
2011-04-14 13:18                     ` Edgar Grimberg
2011-04-14 14:11                       ` jjp jjp
2011-05-03 15:07                         ` jjp jjp
2011-05-03 17:10                           ` Ilija Kocho
2011-05-04 10:47                             ` jjp jjp
2011-05-04 22:36                               ` Ilija Kocho
2011-05-05 14:30                                 ` jjp jjp
2011-05-06  7:36                                   ` Ilija Kocho
2011-05-11  8:47                                     ` jjp jjp
2011-05-11 17:13                                       ` Ilija Kocho
2011-04-14 13:50                     ` Ilija Kocho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTin0A=nTiMSa7fdzkT7E3e8RgUMoRw@mail.gmail.com' \
    --to=drasko.draskovic@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).