public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001623] [RFC] eCos FLASH startup from RedBoot
Date: Tue, 17 Jul 2012 18:37:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Please do not reply to this email. Use the web interface provided at:

--- Comment #2 from Ilija Kocho <> 2012-07-17 19:36:52 BST ---
Hello Nicolas

(In reply to comment #1)
> Hello Ilija,
> We also worked on it and add a new startup type too. However, we also had to
> add the new startup into hal_misc.c and twr_k60n512_misc.c files for it to
> work.

Changes to platform files usually are not a big issue, but every touch of
architecture files may impact other variants/platforms and would be good if we
can avoid. As a consequence it may require overview of more people which can
take more time.
I wanted to try it with least impact on architecture level. It seems that by
defining/combining CYG_HAL_STARTUP_ROM and CYG_HAL_STARTUP_RAM we get what we
need without touching architecture files. I tried it worked but I had little
time for testing because I went on vacation. We should check for possible
caveats caused by defining CYG_HAL_STARTUP_ROM and CYG_HAL_STARTUP_RAM, both
startup types in their own right.

> With this, we can load an eCos application with telnet and launch it. I could
> post a patch if you want.

It would be good if you post, thanks.


Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-07-17 18:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14 16:26 [Bug 1001623] New: " bugzilla-daemon
2012-07-17 12:58 ` [Bug 1001623] " bugzilla-daemon
2012-07-17 18:37 ` bugzilla-daemon [this message]
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:

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

  git send-email \ \ \ \

* 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).