public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001753] New: enhancements in RedBoot to support embedded Flash MCU targets and XIP operation
Date: Mon, 04 Feb 2013 16:21:00 -0000	[thread overview]
Message-ID: <bug-1001753-777@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001753

            Bug ID: 1001753
           Summary: enhancements in RedBoot to support embedded Flash MCU
                    targets and XIP operation
           Product: eCos
           Version: unknown
          Hardware: All
  Architecture/Host Other
                OS:
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: low
         Component: RedBoot
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: Stefan.Singer@freescale.com
                CC: ecos-bugs@ecos.sourceware.org

Created attachment 2058
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2058&action=edit
redboot patches

Hi, we are using RedBoot with MCUs with embedded Flash to load the code into
that embedded Flash and execute from there. For those targets there are usually
two constraints with Redboot:
- internal Flash blocks are not of uniform size and therefore adresses are more
difficult to calculate (walk the table instead of a simple division)
- internal RAM size is very limited, often static memory allocation is
prefered.

The patches in the attachement address those two restrictions.

-- 
You are receiving this mail because:
You are the assignee for the bug.


             reply	other threads:[~2013-02-04 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 16:21 bugzilla-daemon [this message]
2013-02-04 16:21 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=bug-1001753-777@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.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).