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 1001864] New: Data not relocated to RAM during ROMINT startup
Date: Wed, 12 Jun 2013 20:12:00 -0000	[thread overview]
Message-ID: <bug-1001864-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=1001864

            Bug ID: 1001864
           Summary: Data not relocated to RAM during ROMINT startup
           Product: eCos
           Version: CVS
            Target: stm3240g_eval (ST STM3240G EVAL board)
  Architecture/Host Cortex-M
                OS:
            Status: NEW
          Severity: normal
          Priority: normal
         Component: HAL
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: john@dallaway.org.uk
                CC: ecos-bugs@ecos.sourceware.org

The STM32x0G-EVAL platform HAL provides a ROMINT startup type (CYG_HAL_STARTUP
== "ROMINT"), but the Cortex-M architectural HAL does not recognize this
startup type as one which requires data relocation to RAM during system
initialization.

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


             reply	other threads:[~2013-06-12 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 20:12 bugzilla-daemon [this message]
2013-06-12 22:47 ` [Bug 1001864] " bugzilla-daemon
2014-10-03 15:03 ` bugzilla-daemon
2014-10-04 12:52 ` bugzilla-daemon
2014-10-05 10:20 ` bugzilla-daemon
2014-10-07 13:44 ` bugzilla-daemon
2014-10-07 16:54 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2013-06-12 20:12 [Bug 1001864] New: " 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-1001864-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).