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 1001623] New: [RFC] eCos FLASH startup from RedBoot Date: Sat, 14 Jul 2012 16:26:00 -0000 [thread overview] Message-ID: <bug-1001623-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623 Summary: [RFC] eCos FLASH startup from RedBoot Product: eCos Version: CVS Platform: Other (please specify) OS/Version: Cortex-M Status: NEW Severity: enhancement Priority: low Component: Patches and contributions AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: ilijak@siva.com.mk CC: ecos-patches@ecos.sourceware.org Depends on: 1001561 Class: Advice Request Created an attachment (id=1825) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1825) Kinetis Flash startup from RedBoot This Bug was inspired by http://sourceware.org/ml/ecos-discuss/2012-06/msg00011.html The attached patch provides what I have called FLASH startup by combining ROM and RAM startups. The image can be flashed (needs Bug #1001561) and run by means of Redboot. RFC: 1. Am I reinventing hot watter? 2. The CDL defines CYG_HAL_STARTUP_ROM and CYG_HAL_STARTUP_RAM. Is there a caveat? Ilija -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2012-07-14 16:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-14 16:26 bugzilla-daemon [this message] 2012-07-17 12:58 ` [Bug 1001623] " bugzilla-daemon 2012-07-17 18:37 ` bugzilla-daemon 2012-07-18 14:44 ` bugzilla-daemon 2012-07-18 14:48 ` bugzilla-daemon 2012-07-19 1:52 ` bugzilla-daemon 2012-08-07 14:14 ` bugzilla-daemon 2012-08-07 14:31 ` bugzilla-daemon 2013-02-11 15:01 ` 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-1001623-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: linkBe 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).