public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001114] New port: NXP LPC17XX Variant, Olimex LPC-1766-STK platform
Date: Mon, 17 Jan 2011 09:47:00 -0000	[thread overview]
Message-ID: <20110117094734.1848D2F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001114-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001114

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |1001116

--- Comment #5 from John Dallaway <john@dallaway.org.uk> 2011-01-17 09:47:30 GMT ---
Ilija

It's great to see this contribution. Thank you.

(In reply to comment #0)

> 3. lwIP and LPC17xx AHB memory block(s)
> 
> lwIP makes use of statically allocated memory for buffers and heap (objects
> defined as global static variables). LPC17XX, on the other hand, contains one
> or two AHB memory blocks (16 KiB each) intended for "peripheral use". In order
> to utilize this memory for lwIP usage:
>     - a new memory section ahb_bss is defined
> (include/pkgconf/mlt_cortexm_lpc17xx_inc.ldi);
>     - CDL component "LPC17xx specific memory option" is submitted to lwIP
> memory options by LPC-1766-STK CDL;
>     - lwIP is patched to use special section if one is defined. lwIP patches
> are submitted in a separate bug referenced below.

It's a good idea to allow access to these memory blocks. I would like to ensure
that the implementation is as future proof as possible. A few
questions/observations:

a) Your .ldi files suggest that the two AHB memory blocks are not of equal
size. Is that correct?

b) The use of an extra file mlt_cortex_lpx17xx_inc.ldi to define
SECTION_ahb_bss is not conventional. This memory could also be used as an
additional .data section or even as a raw buffer (not allocated by the linker)
if required. Perhaps the section names should be more generic? Note that
cortex.ld in the architectural HAL defines SECTION_sram. The STM3210E-EVAL
platform HAL uses this to allow access to unused on-chip RAM when eCos is using
external RAM.

c) Are there other Cortex-M variants which provide "peripheral" memory? I
wonder if it would be cleaner to add (for example) SECTION_ahb_sram0 and
SECTION_ahb_sram1 definitions to cortex.ld? Usage would be similar to the
existing SECTION_sram. These sections can be used or ignored by other
variants/platforms.

The above comments are intended for discussion only at present. They should not
be interpreted as a request for changes.

Comments?

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2011-01-17  9:47 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1001114-104@http.bugs.ecos.sourceware.org/>
2011-01-16  8:52 ` bugzilla-daemon
2011-01-16 17:20 ` bugzilla-daemon
2011-01-17  9:47 ` bugzilla-daemon [this message]
2011-01-17 12:59 ` bugzilla-daemon
2011-01-18  0:56 ` bugzilla-daemon
2011-01-18  1:43 ` bugzilla-daemon
2011-01-18  1:48 ` bugzilla-daemon
2011-01-18  2:00 ` bugzilla-daemon
2011-01-18 10:06 ` bugzilla-daemon
2011-01-18 10:45 ` bugzilla-daemon
2011-01-18 11:04 ` bugzilla-daemon
2011-01-18 11:48 ` bugzilla-daemon
2011-01-19 19:02 ` bugzilla-daemon
2011-01-22 21:22 ` bugzilla-daemon
2011-01-25 14:48 ` bugzilla-daemon
2011-01-26 20:15 ` bugzilla-daemon
2011-01-31 21:57 ` bugzilla-daemon
2011-02-01  9:54 ` bugzilla-daemon
2011-02-01 10:48 ` bugzilla-daemon
2011-02-01 11:52 ` bugzilla-daemon
2011-02-03 17:01 ` bugzilla-daemon
2011-02-03 17:02 ` bugzilla-daemon
2011-02-03 17:08 ` bugzilla-daemon
2011-02-08 21:09 ` bugzilla-daemon
2011-02-17 14:19 ` bugzilla-daemon
2011-02-21 18:11 ` bugzilla-daemon
2011-02-27 16:21 ` bugzilla-daemon
2011-02-27 16:56 ` bugzilla-daemon
2011-02-28 12:46 ` bugzilla-daemon
2011-02-28 13:40 ` bugzilla-daemon
2011-02-28 20:47 ` bugzilla-daemon
2011-03-05 12:34 ` bugzilla-daemon
2011-03-06 18:29 ` bugzilla-daemon
2011-03-06 20:54 ` bugzilla-daemon
2011-03-07 12:20 ` bugzilla-daemon
2011-03-07 12:23 ` bugzilla-daemon
2011-03-07 12:43 ` bugzilla-daemon
2011-03-07 19:04 ` bugzilla-daemon
2011-03-07 19:14 ` bugzilla-daemon
2011-03-10 22:06 ` bugzilla-daemon
2011-03-10 22:41 ` bugzilla-daemon
2011-03-11  7:58 ` bugzilla-daemon
2011-03-11  9:40 ` bugzilla-daemon
2011-03-11 11:19 ` bugzilla-daemon
2011-03-13 14:24 ` bugzilla-daemon
2011-03-13 15:34 ` bugzilla-daemon
2011-03-13 16:45 ` bugzilla-daemon
2011-03-14 11:02 ` bugzilla-daemon
2011-03-14 11:33 ` bugzilla-daemon
2011-03-14 12:15 ` bugzilla-daemon
2011-04-15  6:44 ` bugzilla-daemon
2011-05-12 10:56 ` bugzilla-daemon
2011-05-12 12:53 ` bugzilla-daemon
2011-05-12 13:00 ` bugzilla-daemon
2011-05-12 13:15 ` bugzilla-daemon
2011-05-13  7:05 ` bugzilla-daemon

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=20110117094734.1848D2F78004@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.org \
    /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).